SlackwareThis Forum is for the discussion of Slackware Linux.
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.
It's also /boot/vmlinuz on Slack, what changes is the root= thing, where you should point to your Slack partition.
#root points to other disk where slack is
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.