Re: [SuSE Linux] SuSE 5.3 not as nice as 5.2
Well, first impressions of 5.3 are not all that good. Tried to install on a laptop that had a 1GB primary partition(NT) and 2gb unpartation space(for LINUX) First the pcmcia module couldn't start the cardmanager as I started the install (the 5.2 does fine). Then when I said a new install and went to partition the disk, it gives a big red message saying error occurred and stops. So..... go to 5.2, install just fine, then have to do an update! Not great for a first impression with four more laptops to do and a few servers. Hope second and third impressions are better. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Fri, Sep 04, punt wrote: The two big problems we're still investigating...
First the pcmcia module couldn't start the cardmanager as I started the install (the 5.2 does fine).
This has been reported by two customers: Suddenly the PCMCIA hardware is not detected anymore. Unfortunately we are unable to reproduce the problem here. So we need to go the hard way and just try. First of all I will create a new bootdisk with the newest version of the pcmcia package. Second, I assume the experimental cardbus code now creates problems on some machines (it has been in on 5.2 also, so there seems to have been some change to the pcmcia code that makes it unusable on some machines). We need a machine that shows the problem in order to find the reason of the failure. If you are willing to test some bootdisks, please send me a short mail and I will be very happy to send you a test bootdisk (you don't need to trash your existing installation, but only boot with the disk and see if the cardmanager works).
Then when I said a new install and went to partition the disk, it gives a big red message saying error occurred and stops.
And this is the biggest bug so far: Under certain circumstances YaST just crashes when entering the partition menu. We still are collecting data as this also is a problem we cannot reproduce despite trying to get it on some dozens of machines. The problem seems to be hardware independant and unfortunately does not happen very often. Currently we do not know what triggers this bug. Fortunately, we finally found one machine in our US office that shows this problem so chances now are better we can fix this nasty bug.
So..... go to 5.2, install just fine, then have to do an update! Not great for a first impression with four more laptops to do and a few servers.
Hope second and third impressions are better. -o) Hubert Mantel /\\ _\_v
Yes, this bug is unacceptable and currently many people are working on finding the solution. Did you try switching to console 2 and creating the partitions manually using fdisk (needs a reboot for continuing)? Of course this is a very ugly workaround but this information could help us find the cause of the problem. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
And this is the biggest bug so far: Under certain circumstances YaST just crashes when entering the partition menu. We still are collecting data as this also is a problem we cannot reproduce despite trying to get it on some dozens of machines. The problem seems to be hardware independant and unfortunately does not happen very often. Currently we do not know what triggers this bug. Fortunately, we finally found one machine in our US office that shows this problem so chances now are better we can fix this nasty bug.
This occurred during installation (a coupe of times out of probably 8-10 attempts) on my home machine. I am at this box currently and will be here through Tuesday am if you would like to ask me any questions about it. The installation is good now, but I was wondering if I had caused the menu crash. Now I understand. <A HREF="http://www.millsphoto.com"><A HREF="http://www.millsphoto.com</A">http://www.millsphoto.com</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sun, Sep 06, Steve Mills wrote:
And this is the biggest bug so far: Under certain circumstances YaST just crashes when entering the partition menu. We still are collecting data as
[...]
This occurred during installation (a coupe of times out of probably 8-10 attempts) on my home machine. I am at this box currently and will be here
Umm, does this mean it isn't even reproducable on the same machine? ;-(
through Tuesday am if you would like to ask me any questions about it.
Well, I just would like to confirm that it's not hardware dependant. Could you please tell me which (harddisk) hardware you use? SCSI or EIDE, number of disks, partition layout when the bug occurred. I understand you tried it several times. Did you something different when it crashed and when it worked? We are having a really hard time finding a machine that _reproducible_ shows that bug. I hope to get additional info from Oakland (I just learned that Monday is holiday in the USA ;-( ).
The installation is good now, but I was wondering if I had caused the menu crash. Now I understand.
<A HREF="http://www.millsphoto.com"><A HREF="http://www.millsphoto.com</A">http://www.millsphoto.com</A</A>> -o) Hubert Mantel /\\ _\_v
No, you did nothing wrong. There is a bug in YaST. We need to find it. I just did another test installation but this damned thing wouldn't crash ;-( What really puzzles me is the fact that nobody in Germany has reported this problem. We fixed one minor bug in YaST w.r.t. new disks with uninitialized MBR, but I can not see how this could explain this problem. Of course we are doing all of our tests with the international edition and still are not able to reproduce the bug. But we WILL find it! - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
*********** REPLY SEPARATOR *********** On 9/6/98, at 4:46 PM, Hubert Mantel wrote:
Hi,
On Sun, Sep 06, Steve Mills wrote:
And this is the biggest bug so far: Under certain circumstances YaST just crashes when entering the partition menu. We still are collecting data as
[...]
This occurred during installation (a coupe of times out of probably 8-10 attempts) on my home machine. I am at this box currently and will be here
Umm, does this mean it isn't even reproducable on the same machine? ;-(
through Tuesday am if you would like to ask me any questions about it.
Well, I just would like to confirm that it's not hardware dependant. Could you please tell me which (harddisk) hardware you use? SCSI or EIDE, number of disks, partition layout when the bug occurred.
I understand you tried it several times. Did you something different when it crashed and when it worked? We are having a really hard time finding a machine that _reproducible_ shows that bug. I hope to get additional info from Oakland (I just learned that Monday is holiday in the USA ;-( ).
As I remember, this occurred only when I had previously done a full installation and was trying to reinstall without formatting the Linux disk again. I was also having trouble with my floppy drive and had to replace it. It was eating discs, including the boot. I made a new boot disk (in Windows, I selected "setup" on the 1st CD and that makes a new installation disc...cool trick) and went back at it. I have done so many things this past week with 5.3 on 2 different boxes that it is hard to recall exactly. I assumed I was doing something wrong and not even mentally noting all the circumstances. It did only happen on this Micron Millennia Mx, 166 with MMX, 1.6 Seagate hdb1, 3.5 Seagate hda1, swap and Linux are on hdb1. I will have to pretend to reinstall in order to tell you all the particulars about my drives and partitions. I will try to do that soon today. Steve <A HREF="http://www.millsphoto.com"><A HREF="http://www.millsphoto.com</A">http://www.millsphoto.com</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Sun, 6 Sep 1998 14:07:28 +0200, hubert wrote:
Hi,
On Fri, Sep 04, punt wrote:
[snip]
Then when I said a new install and went to partition the disk, it gives a big red message saying error occurred and stops.
And this is the biggest bug so far: Under certain circumstances YaST just crashes when entering the partition menu. We still are collecting data as this also is a problem we cannot reproduce despite trying to get it on some dozens of machines. The problem seems to be hardware independant and unfortunately does not happen very often. Currently we do not know what triggers this bug. Fortunately, we finally found one machine in our US office that shows this problem so chances now are better we can fix this nasty bug.
So..... go to 5.2, install just fine, then have to do an update! Not great for a first impression with four more laptops to do and a few servers.
Yes, this bug is unacceptable and currently many people are working on finding the solution. Did you try switching to console 2 and creating the partitions manually using fdisk (needs a reboot for continuing)? Of course this is a very ugly workaround but this information could help us find the cause of the problem.
for the record, i had same problem here with partitioning. my solution was to fire up the rescue system on the installation menu and run fdisk manually - the error message was very unhelpful, particularly as the [return] key was disabled. took me 3 hrs to work out what was going on. (i had used partition magic to trash what was left of my previous installation prior to resizing my win95 partition from 512Kb to 2Mb - it might have gone from fat16 to fat32 in the process) best regards morgad -- ODB++ compatible - been there, seen it, done it, got the t-shirt ! pgp: 1024/AB181ED9 58 12 68 68 47 87 16 81 47 93 F6 75 31 61 C8 26 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
mantel＠suse.de -
morgad＠mail.eclipse.co.uk -
punt＠gte.net -
steve＠millsphoto.com