"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Since even the .installed kernel didn't boot, but I was able to but things back together with an rpm -Uvh --oldpackage k_smp-*.rpm, I wonder if the modules were not installed/depmoded properly by the patch. Or mkinitrd not called? But this is done via the rpm automatically.
It was called.
Can you try again with the new kernel and write down where it fails? I need some more details...
It crashed very early. After grub loaded it, the screen went dark, then within 5 seconds the computer rebooted. I was unable to see any boot messages from the new kernel.
Add "vga=0" to the linuxrc command line to not use the graphical screen. That way you can see even the early boot messages. Another solution is attaching a serial console and logging the output there. A third idea: Wait until the middle of next week, I'll test some odd systems with the new kernel and see whether really all of them work (as they did so far).
The unfortunate part about the kernel rpms is that the module set is not versioned with the kernel (i.e. there is no -249 modules directory) so it is a little tricky setting up a backup kernel for when it fails.
I agree, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126