http://bugzilla.novell.com/show_bug.cgi?id=485014
User robin.listas@telefonica.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=485014#c18
--- Comment #18 from Carlos Robinson
Well, thanks for trying.
Comment #16 is worrisome, since it means there are serious problems with the current mainline kernel on your system.
Remember, though, that rpm was run inside a chroot of the 11.1 partition in the running 11.0 system - in case that has any effect.
Anyway, unfortunately, the old-style IDE drivers are not really well tested any more, since distributions have been using PATA/libata by default for quite some time. The original problem may also be related to these drivers (of course, they shouldn't break as a result of a kernel update, but this is a consequence of the lack of testing coverage).
The previous stable kernel of 11.1 worked (I mean, the one in the dvd). The current one in the update repo does not (2.6.27.19-3.2-debug). It does hibernate, but it does not power off the machine at the end of the process. A normal halt does power off correctly. My guess is simply that s2disk is calling the wrong (acpi?) function to power off. And the current KOTD doesn't boot.
Since you are not able to test the current mainline kernel, the only way do figure out the real cause of the problem would be to test the stable kernel that 2.6.27.19-3.2 is based on and then go back to the previous stable kernels if it fails, but that would require you to build the kernel yourself (probably many times).
I can compile departing from the kernel-source rpm or equivalent. Each compile takes about 2 or 3 hours in this machine, and testing it depends on whether it is convenient to reboot or not at that moment - which may mean several days for each test. If you tell me what to do, I can try.
Alternatively, you can check if switching to PATA/libata makes any difference.
Hugh... remember that I have 20 partitions, and AFAIK libata doesn't support more than 15 -- unless the necessary changes have been applied, and don't need a change in udev. How does one activate libata, short of reinstalling?
Generally, we need to identify the exact change which caused the problem to appear and that's impossible on the basis of the symptoms description alone.
I guess so... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.