loading modules for old kernel during boot up

valemon · 2011-07-06 22:11:37

Hello

After a kernel update I noticed this message during boot

Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]

And taking a look at everything.log this came out

May 24 13:57:54 localhost kernel: Pid: 1772, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:31:25 localhost kernel: Pid: 1952, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:34:45 localhost kernel: Pid: 1872, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 14:54:53 localhost kernel: Pid: 1966, comm: modprobe Tainted: G C 2.6.37-ARCH #1
May 24 15:14:03 localhost modprobe: FATAL: Could not load /lib/modules/2.6.37-ARCH/modules.dep: No such file or directory
Jun 13 13:34:20 localhost modprobe: FATAL: Could not load /lib/modules/2.6.38-ARCH/modules.dep: No such file or directory

I am using 2.6.39 kernel.
Could anybody help me solve this??

jni · 2011-07-06 23:35:31

Was the boot image re-done for the proper kernel? try re-building it with mkinitcpio

Doing "uname -r" should say you are using 2.6.39... right?

Once booted, try loading a module by hand... does it say the same error?

Samana · 2011-07-09 14:14:38

I get this error as well and I have not found a solution yet. Let me know what info I can provide to help solve it.

I just did a clean install yesterday on an Asus eeePC 1015PX. All I have in my MODULES section in rc.conf is

MODULES=(acpi_cpufreq)

and my daemons array is

DAEMONS=(hwclock crond syslog-ng dbus @sensors @acpid @alsa @laptop-mode @wicd @netfs gdm)

slytux · 2011-07-09 15:29:44

Check /lib/modules/ and delete any older kernel module directories not in use.

Last edited by slytux (2011-07-09 15:30:43)

Samana · 2011-07-09 15:39:25

slytux wrote:

Check /lib/modules/ and delete any older kernel module directories not in use.

Hmm, yeah, not really a newbie, but I have a fresh install, so why would I get the message?

Plus, I looked in that directory, and sheesh, no idea where to start.

slytux · 2011-07-09 16:21:03

If you have a clean install, you should only have one directory for the current Arch kernel: 2.6.39-ARCH/ You shouldn't need to touch it--it just has all the kernel modules that were built.

The OP seems to have crud left over from 2.6.37-ARCH/ He can rm -rf that.

slytux · 2011-07-09 16:27:27

Samana, what does your error message say? Do you have anything in /lib/modules/2.6.39-ARCH/misc/ ?

You can also try rebuilding the initrd image as jni suggested.

 mkinitcpio -p kernel26

Samana · 2011-07-09 17:35:35

slytux wrote:

Samana, what does your error message say? Do you have anything in /lib/modules/2.6.39-ARCH/misc/ ?
You can also try rebuilding the initrd image as jni suggested.
 mkinitcpio -p kernel26 

I have no "misc" folder in 2.6.39-ARCH

The error is like a resonse from bad syntax when running a modprobe command

Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]

I rebuilt the image and got a few errors in autodetect that might be a clue.

#  mkinitcpio -p kernel26 
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'
:: Image generation successful
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'
:: Image generation successful
==> SUCCESS

Note that the error does not show up when I boot in fallback mode. So it looks like the error has something to do with autodetect. But I have no idea what it is. I am going to try to get rid of the oldusbload and see what happens. [NOTE: Getting rid of oldusbload did n
ot fix the error]

Last edited by Samana (2011-07-09 17:46:02)

slytux · 2011-07-09 17:43:46

It's probably from that then because the fallback options for kernel26 skips the autodetect hook.

In /etc/mkinitcpio.d/kernel26.preset you see there is fallback_options="-S autodetect"

In /etc/mkinitcpio.conf you can remove the 'autodetect' phrase and add 'usb' if that is applicable to your system.

Last edited by slytux (2011-07-09 17:46:08)

slytux · 2011-07-09 17:51:09

If you make any changes, you need to rebuild the image again as in note#7. I usually add 'keymap' to my Hooks line and enable compression.

Samana · 2011-07-09 18:30:31

slytux wrote:

It's probably from that then because the fallback options for kernel26 skips the autodetect hook.
In /etc/mkinitcpio.d/kernel26.preset you see there is fallback_options="-S autodetect"
In /etc/mkinitcpio.conf you can remove the 'autodetect' phrase and add 'usb' if that is applicable to your system.

Trying to think about this...I am having trouble with normal boot, not fallback. It seems that something in autodetect is sending a bad modprobe command.

I do see a line in /lib/initcpio/install/autodetect that reads

allfs="${fs} $(modprobe --set-version ${KERNELVERSION} --resolve-alias ${fs})"

I think there is a problem with that line. Well, that is what my intution is telling me.

valemon · 2011-07-12 18:26:50

I didn't have enough time to check your solutions, but it seems that with the latest kernel update the problem seems solved.

Arch Linux

#1 2011-07-06 22:11:37

loading modules for old kernel during boot up

#2 2011-07-06 23:35:31

Re: loading modules for old kernel during boot up

#3 2011-07-09 14:14:38

Re: loading modules for old kernel during boot up

#4 2011-07-09 15:29:44

Re: loading modules for old kernel during boot up

#5 2011-07-09 15:39:25

Re: loading modules for old kernel during boot up

#6 2011-07-09 16:21:03

Re: loading modules for old kernel during boot up

#7 2011-07-09 16:27:27

Re: loading modules for old kernel during boot up

#8 2011-07-09 17:35:35

Re: loading modules for old kernel during boot up

#9 2011-07-09 17:43:46

Re: loading modules for old kernel during boot up

#10 2011-07-09 17:51:09

Re: loading modules for old kernel during boot up

#11 2011-07-09 18:30:31

Re: loading modules for old kernel during boot up

#12 2011-07-12 18:26:50

Re: loading modules for old kernel during boot up

Board footer