multi boot after kernel upgrade

WilliamS · 06-23-2004, 11:37 AM

I have win98/slack9.1/mandrake9.1 on hdb, and have just upgraded from kernel 2.4.22 to 2.4.26
hda is unplugged.

The choice has always been boot slack from floppy or the mandrake lilo, now the mandrake lilo won't boot slack, I see words "loading slack........................."
and a blinking cursor underneath.

There must be something to change in mdk lilo, but can't think what it could be.
I ran /sbin/lilo after the upgrade, but from habit, as this one doesn't do anything AFAIK.

alsa and lm_sensors also don't work, but can fix those later. (um, maybe)

How do I make slack boot again from the mandrake lilo?

ringwraith · 06-23-2004, 12:12 PM

You need to make sure that /etc/lilo.conf in mandrake is pointing to the new kernel and using the proper name.

WilliamS · 06-23-2004, 12:19 PM

Only identifier for the kernel in mandrake lilo is /boot/vmlinuz, not sure how to identify the new update.

Where would I look in slack?

gbonvehi · 06-23-2004, 12:34 PM

It's also /boot/vmlinuz on Slack, what changes is the root= thing, where you should point to your Slack partition.
IE:
image=/boot/vmlinuz
root=/dev/hda1
label="Mandrake"
read-only
image=/boot/vmlinuz
#root points to other disk where slack is
root=/dev/hdb1
label="Slackware"
read-only

WilliamS · 06-23-2004, 12:49 PM

Yes, that is what was in the mandrake lilo, /boot/vmlinuz as image, and
root=/dev/hdb3

so I don't see why it doesn't boot, as I thought vmlinuz was a link, and should be pointing to the updated kernel.

320mb · 06-23-2004, 01:01 PM

Quote:

so I don't see why it doesn't boot, as I thought vmlinuz was a link, and should be pointing to the updated kernel.

Nope, vmlinuz IS the kernel........there should be NO symlink at all

gbonvehi · 06-23-2004, 02:27 PM

Well i guess he's using Slackware 9.1 and in that version at least, vmlinuz is a symlink to the kernel he installed (normally, vmlinuz-ide-2.X.X).
I had that problem WIlliams when i didn't run lilo after kernel upgrade, maybe you are running lilo with the wrong lilo.conf?

WilliamS · 06-23-2004, 02:41 PM

AHA!!! Victory is Mine!
Removed Slackware entry in mdk lilo.conf, run lilo -v.
Reboot into mdk.
Re-enter Slackware entry in mdk ~/lilo.conf, run lilo -v3.
Reboot, choose slackware, it really loads this time.

OK, I suspected that the image part of the slack entry in mdk lilo.conf was the old kernel, so this.
Maybe reboot not needed, but might be more thorough.

Now to figure why alsa doesn't work, even after remove/re-install+alsaconfig.