"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
Andreas Jaeger aj-at-suse.de |suse-amd64| wrote:
"Stephen Williams" <1mc9i5i02@sneakemail.com> writes:
following the normaly YaST2 based install. I haven't tried to debug it thoroughly (I spent the last few hours figuring out how to revert the kernel.) so I'm not sure if the kernel is broken, or the kernel *install* is broken. Do you use lilo? Did you run lilo again after the test? Did the older kernel work for you? What kind of system do you have?
Not LILO, grub-0.92-247. I noticed that the install of -249 also created a vmlinuz.installed from the old kernel, but the "failsafe" boot selection didn't work either.
Dual Opteron 244, 1Gig, Adaptec SCSI interface and a single SCSI disk, IDE cdrom and ZIP drive. Fairly conventional, actually.
Yes, that should be fine.
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.
Sorry, I'm used to LILO (and would have known to run lilo after an install) and I'm used to aboot on the alpha not needing any special effort. I believe grub is happy with its lst file and can read the filesystem just fine.
Exactly, grub shouldn't case a problem. Can you try again with the new kernel and write down where it fails? I need some more details... Cheers, 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