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 had the same problem using LILO! (I was going to try Grub instead) Cannot boot from hard-drive, but boot floppy works perfectly?!? (get same kernel panic)
Even after re-installing LILO it does the same thing happens.
Distribution: Slack Puppy Debian DSL--at the moment.
Posts: 341
Rep:
You can flame me if I'm wrong.
I seem to remember that linux doesn't like drive-swapping. It keeps a record of the hardware between boots so that you don't have to sit through a complete set of detection routines at boot up.
The system is mapped when you install. Having linux on a removable drive bay, when it isn't the only drive--and grub or lilo is in the MBR of the first IDE hard drive==crash city.
You may have to set up an alternate etc/sysconfig/hw and system.map_kernel_version to compensate for the removable drive.
umm I don't have a scsi drive but grub and your menu.ist I will translate that may give you some tips?
If root is truly (hd0,1) then root= /dev/sda2 (or hda2 if IDE drive)
However, your slackware /boot folder may not be on the same partition and a normal slack does not use an initrd image.
try
title slack
kernel (hd0,1)/boot/vmlinuz root=/dev/sda2 ro hdc=ide-scsi
change hd0,1 to where your /boot partition is MINUS one digit so sd9= (hd0,8)
Distribution: Slack Puppy Debian DSL--at the moment.
Posts: 341
Rep:
If you use the ls -Al (L) you will see that vmlinuz is a link to the full name of the kernel. This means that when you update your kernel, you can always have the newest one as the default by changing the link.
My machine has every kernel I have ever played with still on it because I have been too lazy to clean it up. The deal is; in an emergency, you just have to point to vmlinuz from the command-line and the link is to be to the last working kernel. Of course that isn't how redhat does it. (It always does the link to the newest kernel--which may be the one which was hosed up.)
I may be mistaken, I go with what I know. Things may have changed when I wasn't looking.
I really did have trouble with removable drives. Maybe it was that I had cheap ones.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.