Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
I installed Slackware 12.0 with the default 2.6.21-SMP Kernel on my USB hard drive. It starts loading the kernel and then I get a Kernel Panic (8,3). It can't load partition 3 of my USB drive as root.
I found a thread for a similar problem using Slackware 10.1. It says to recompile the Kernel including certain modules:
Then it goes on with other instructions. Now I've never had any good luck compiling a kernel, and those instructions are for 2.4.29(? if memory serves me) and I'm using 2.6. So is there anything I should do different?
I say try making an initrd instead, it'll be easier, especially if you don't have luck with compiling kernels. Looks like you'll need the right USB related modules to allow it to boot from a USB HDD. Those are approximately the ones, but try the initrd first.
Make an initrd? .... Initial RamDisk? How do I do that?
As stated you need to make a initrd!
The easiest way would be to use the Slackware install cd1 to boot the system as if you were going to install.
After you get to the login then from the cli (command line);
Code:
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #this is the device you
#installed to
~#chroot /slacktemp #change to yours
~#cd /boot #you can now create your
#initrd via instruction in
#README.initrd
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf,add the
#initrd = /boot/initrd.gz
#to proper stanza then;
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write MBR to your_device
If you create the initrd with the proper modules then you should now be able to boot your system.
There is probably one additional step, which is to write a script to re-scan the usb bus
or panics will continue for lack of an init.
If the initrd and proper modules are setup then the scan should be handled via the boot session. If the udev is working then the scan should be done by the device mapper.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.