modprobe problems (even though not using loadable modules!)

colonel_dolphin · n00b Joined: 12 Jan 2004 Posts: 39

I have not checked [ ] Loadable Module Support in the "make menuconfig". However, I still get lots of these errors in my /var/log/messages:

FATAL: Could not load /lib/modules/2.6.1-gentoo/modules.dep: No such file or directory

When I upgraded from 2.6.0 to 2.6.1, everything ran fine for a day or so, and then my root filesystem suddenly became "read only", with an endlessly looping display on the console of the "FATAL" modprobe error listed above. Bizarre. I have no loadable modules, nor support them enabled.

After rebooting, I created an empty file at /lib/modules/2.6.1-gentoo/modules.dep, but I'd prefer if nothing needed to look here.

How can I properly configure everything so that nothing thinks I'm using loadable modules? My system currently works fine (MySQL, PHP, Apache 2, etc.), but obviously something is unecessarily modprob'ing.

This file contains only comments: /etc/modules.autoload.d/kernel-2.6

Thanks for any and all tips.

zfc-tinkerer · Tux's lil' helper Joined: 05 May 2003 Posts: 126

did you try still running a make modules modules_install? this might tell your kernel to place somewhere information about there not being any modules.

tomk · Posted: Thu Jan 15, 2004 2:46 pm Post subject:

You don't have to bother with make modules modules_install with 2.6 kernels, a simple make will do everything for you.

Have you had a look at the files in /etc/modules.d/ I'm not sure what effect commenting out these lines will have, but it's worth a try (just make a backup first just in case). Also is the /etc/modules.autoload symlink pointing to /etc/modules.autoload.d/kernel-2.6?

HTH
_________________
Search | Read | Answer | Report | Strip

floffe · Posted: Thu Jan 15, 2004 3:09 pm Post subject:

colonel_dolphin · n00b Joined: 12 Jan 2004 Posts: 39

Q: Also is the /etc/modules.autoload symlink pointing to /etc/modules.autoload.d/kernel-2.6?
A: No. The link did not exist. I manually created it.
However, something in the kernel or used by one of my system applications is causing the modprobe errors to be logged (and possibly hung my system earlier). I wish I new what caused it and why (since I have nothing installed or configured as a kernel module). I suppose manually setting everything up to convince the system that it has a "normal" config for modules (albeit an empty definition) can work, but it seems like a hack that might cause trouble later.

Q: Whats in /etc/modules.d/ ?
A:
-rw-r--r-- 1 root root 0 Dec 20 19:34 .keep
-rw-r--r-- 1 root root 1310 Dec 20 19:34 aliases
-rw-r--r-- 1 root root 122 Dec 20 19:34 i386

The aliases and i386 files only contain lines starting with either '#' or 'alias'. The aliases look meaninful, important, and interesting to me. For example, "alias char-major-10-175 agpgart" in the 'aliases' file is probably needed, since I've included agpgart in my 2.6.1 kernel (but not included as a module).

Q: try running a make module and make modules_install?
A:
# make modules

The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.

make: *** [modules] Error 1

# make modules_install

The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.

make: *** [modules_install] Error 1

rob.sharp · Posted: Sat Jan 17, 2004 11:19 pm Post subject:

Try running modules-update as root. Should create a valid file for ya...

I use modules so no idea if it will work, but thats how i keep my modules dependencies updated.

colonel_dolphin · n00b Joined: 12 Jan 2004 Posts: 39

When the 2.6 kernel is built without using autoloaded modules, I spotted this process "/sbin/devfsd /dev" doing a modprobe (WRONG!!!).

My root filesystem (ext3) had suddenly and unexpectedly become ready-only. There was a small amount of corruption corrected by e2fsck. I don't yet know if there was a connection between devfsd and the root filesystem corruption, but I found the following entry in /etc/devfsd.conf, so I commented the MODLOAD entries.

# Enable module autoloading. You may comment this out if you don't use
# autoloading
#LOOKUP .* MODLOAD

.
.
.

# ALSA/OSS stuff
# Comment/change these if you want to change the permissions on
# the audio devices
#LOOKUP snd MODLOAD ACTION snd
#LOOKUP dsp MODLOAD
#LOOKUP mixer MODLOAD
#LOOKUP midi MODLOAD