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.
Actually I'm experiencing the same problem overhere after the kernelupgrade with slackpkg. I can't get into my system anymore, nor with the huge nor with the generic kernel. I get the same message at boot as you Adriv: "ERROR: No /sbin/init found on dev (or not mounted). Trouble ahead." And then I get a kernel-panic
In the meanwhile I made a succesfull entry to my slackware installation, and discovered that the file vmlinuz was linked to the generic kernel, and the initrd.gz to the huge kernel. (the list of my boot files is virtually the same as yours, Adriv).I don't know if this info is helpfull in this discussion, but I can now approach my Slackware using the huge kernel, by specifying vmlinuz. (I use grub by the way)
Last edited by Hannes Worst; 08-20-2009 at 01:50 PM.
I just had this problem. I installed the security update (on current), and I also decided to start using the generic kernel with an initrd, instead of the "huge" kernel. So I'm not sure where the problem came from.
I remade the initrd with mkinitrd -F -c. I had my root partitions filesystem in mkinitrd.conf already, and so I assumed it was there. I also ran lilo and it seemed fine. But when I rebooted I came across the same init and unable to load modules error message you've all been getting. (I did later find out by looking at the modules in /boot/initrd-tree that my fs module wasn't there...)
I could, however, boot via the "huge" kernel, which I put in lilo via booting into my system with a rescue cd, chroot'ing into my root partition, making sure all hard disk devices are the same in /dev (i had to symlink sda to hda), and editing lilo.conf and running lilo.
To get the generic kernel working, however, things may be a little strange. Try mkinitrd -c -F -k YOURKERNELNUMBER -m YOURFSMODULEHERE. Then see /boot/initrd-tree/lib/modules/YOURKERNELNUMBER/kernel/fs/ contains your root filesystem module. Then run lilo. That all worked for me, but the error message on boot was still there.
I deleted /boot/initrd.gz and the /boot/initrd-tree ran the mkinitrd command again and it all worked. Lord knows why.
The biggest problem you had was not mounting everything you needed,
which is what Robby was trying to tell you in his post.
For future reference, when you boot with the Slackware CD/DVD, it has
a line that tells you a much easier way, which is what bgeddy was
telling you ... boot back into the installed Slackware system:
Code:
In a pinch, you can boot your system from here with a command like:
boot: hugesmp.s root=/dev/hda1 rdinit= ro
In the example above, /dev/hda1 is the / Linux partition.
So all you needed to do was enter "hugesmp.s root=/dev/sda3 rdinit= ro"
and you would have been into your Slackware system. That would have
saved you a lot of time and typing from another system. You're typing
rather than being able to paste also had incorrect data for us to read:
Code:
vmlinuz -> vmlinuz-generic-2.6.27.31
I have always used that, never had to chroot as Robby posted, and have
always been able to get back into an installed Slackware system.
Glad you got it fixed and can now use Slackware again.
To get the generic kernel working, however, things may be a little strange. Try mkinitrd -c -F -k YOURKERNELNUMBER -m YOURFSMODULEHERE. Then see /boot/initrd-tree/lib/modules/YOURKERNELNUMBER/kernel/fs/ contains your root filesystem module. Then run lilo. That all worked for me, but the error message on boot was still there.
The more I think about this, the more I think I did something stupid like running mkinitrd after I'd ran lilo. Aw, well.
Just noticed something and I'm curious ... and it's probably in
Website Suggestions & Stuff, but, oh well.
On the left under our nick are a few items. The last one down is
Tux on the right, but then some different icons on the right.
For instance, the OP has a Debian swirl icon and a Tux.
Mine has a Tux head on the left and Tux on the right.
dwr1 has a Windows logo (we'll beat him with a wet noodle later)
and a Tux.
I had thought maybe that was set by what we have in Distribution
until I saw dwr1 -- he has slack-current, mine has Slackware. So
that doesn't seem to be it; though LQ's spellchecker doesn't
have Slackware has an entry.
What must I do to change the Tux head to the Slackware logo?
Something like this, but I can supply a better image ... just
have little time atm.
__________________
Edit: That's spooky ... it's changed, and this threads OP
is not the Debian guy, either.
Last edited by Bruce Hill; 08-21-2009 at 05:08 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.