SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
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
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?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.