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.
Well, the message "No kernel modules found for Linux ...." comes from this bit of code in /boot/initrd-tree/init:
Code:
# Load kernel modules:
if [ ! -d /lib/modules/`uname -r` ]; then
echo "No kernel modules found for Linux `uname -r`."
elif [ -x ./load_kernel_modules ]; then # use load_kernel_modules script:
echo "${INITRD}: Loading kernel modules from initrd image:"
. ./load_kernel_modules
else # load modules (if any) in order:
if ls /lib/modules/`uname -r`/*.*o 1> /dev/null 2> /dev/null ; then
echo "${INITRD}: Loading kernel modules from initrd image:"
for module in /lib/modules/`uname -r`/*.*o ; do
insmod $module
done
unset module
fi
fi
So the message comes out when init cannot find a directory containing modules for the running kernel in your initrd.
Same problem here.
Slackware-current (x86). Upgrading to Kernel 2.6.33.2, on a Notebook with IDE Hard Disk.
Tried generic, generic-smp, huge e huge-smp. No deal =(.
Same problem here.
Slackware-current (x86). Upgrading to Kernel 2.6.33.2, on a Notebook with IDE Hard Disk.
Tried generic, generic-smp, huge e huge-smp. No deal =(.
If you have an IDE hard drive and upgraded straight from slack 13 there was a change in the kernel config concerning data/IDE drives. Searching the forum will tell you what it was and how to resolve it. I think the change came with the 2.6.32.X kernel.
Just to make sure: You folks with the problem are seeing a "No kernel modules found for Linux " followed by a kernel version number. Is that correct?
(There's another matter of your block devices not being available, but the init script is supposed to use a lightweight version of udev to figure that out.)
This looks the same problem reported here. http://www.linuxquestions.org/questi...orking-800757/
It is likely that your initrd.gz does not contain all the necessary modules to support the ext4 file system that is the default in Slackware 13.
When using the generic kernel you need an initrd. See /boot/README.initrd for details.
After a kernel upgrade you need to build a new initrd.gz.
As root, change to /boot and run '/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 2.6.33.2' or -k <whatever kernel version> to get the correct invocation for mkinitrd.
Having run 'mkinitrd' you can then edit '/etc/lilo.conf' to reflect your kernel update changes and then run 'lilo'.
I can't find any of the old threads I was saying to search for, but I did look through the changelogs for current and found the point when the switch happened. This MIGHT help to figure out if this is what is causing this problem:
Quote:
Mon Jan 4 21:43:02 UTC 2010
New kernels... and this deserves a mention/warning: the last bits of the
"old" IDE/ATA system have been removed now. Everything should be using
the libata based drivers now, so if you have any drives that are currently
running as /dev/hda, /dev/hdb, etc., when you reboot with these kernels all
drives will be renamed as /dev/sda, /dev/sdb, etc. If you had any /dev/sd*
already, they might get renamed. Adjustments may be required in
/etc/lilo.conf, /etc/fstab, the initrd, and elsewhere. Good luck!
I think I'm going to give up on this one and try to update again from the mirrors from within Ubuntu using chroot - if I can work out why it keeps coming up with an error on the mirrors when I try this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
