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've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors:
Quote:
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev ( or not mounted )
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh
As a once off solution, I can rebuild the kernel however I'd like to not do that otherwise it means I have to do it each time a new kernel is released. I'll try the depmod option ...
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev ( or not mounted )
It's telling you that your initrd image does not have /dev/sda2 in it.
What does
Code:
ls -l /boot/initrd-tree/dev/
give you? (I am assuming that you left initrd-tree alone after building initrd.gz.)
I had the same problem, never did fix it. I think there was a post about changing all the drives to sdx from hdx in /etc/fstab? to get them mounted? Libata switchover? In the end I just used alien BOBS other script to create a current boot cd set to get started. I think the huge-smp kernel would work if I had set the frame buffer to default on boot, that was my other problem, the screen would go blank when it did get the drive mounted.
Using Generic 2.6.33-4-smp, I had to add modules for ext4, jdb2 and mbcache to the initrd. I think the problem is that if you're running with a kernel that has ext4 built in, the -m ext4 flag on mkinitrd doesn't actually load the module. I had to copy the ext4.ko over to the right location in the initrd-tree/lib/modules folder and add an insmod line to the load_kernel_modules file. Once ext4 _and it's dependencies_ were there, my system booted just fine. Btw, I had to go to a initrd boot because of my SATA RAID card that wasn't supported in the kernel. (Rocket Raid 2600x4).
-----wade
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.