On Wednesday 14 July 2004 06.25, Max Beerli wrote:
From: Jerry Feldman
To: suse-linux-e@suse.com Subject: Re: [SLE] problems running the lilo command after kernel update Date: Tue, 13 Jul 2004 21:29:48 -0400 At first glance, below I see in /var/log/messages refers to /lib/modules/2.6.5-7.75-smp/modules.dep not /lib/modules/2.6.5-7.95-smp/modules.dep
Hello Jerry. Yes I found it odd when I saw this too. I mentioned this in my
original post:
You will notice if you scroll down that when lilo is run for some reason the system is looking for /lib/modules/2.6.5-7.75-smp/modules.dep when it should be looking for /lib/modules/2.6.5-7.95-smp/modules.dep instead. Can I do something manually to ensure that this computer will boot up properly with the new kernel?
But I don't know why it is doing this.
because you haven't rebooted. You're still running -7.75, so it wants its own modules.dep
I have installed the latest kernel update and it shows when I launch rpm -qi kernel-smp This is really weird to me. How can I ensure that the boot loader reintialization process is complete. I don't want to reboot this computer until I'm sure that it will reboot properly!
I guess it could be an issue with the scsi driver, but did you try running lilo manually? Maybe it was just a temporary thing. Perhaps try unmounting and remounting /boot? Changing lilo to point to the MBR (/dev/sda) instead of /boot?