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