Description of problem:
After upgrading, some modules no longer load during startup.
Good example is the floppy module. I have also seen that the alsa oss
compat modules are not loading as well.
Version-Release number of selected component (if applicable):
I have seen this with both a custom 2.6.3 kernel and kernel-2.6.3-1.118
We have two machines not loading the modules.
Not loading as in loading them fails, or they aren't getting loaded
when they should be?
Note that both of these should be loaded on demand.
Yes, same thing here. For example, loop device doesn't load when
needed. Neither does the nvidia driver. Modprobing them they load just
fine, but kernel simply won't load them when needed.
I did some tracing in the kernel but that really did not help =)
kobj_lookup does not find anything from the map, looks like the major
numbers aren't initialized or something.
Not loading when demanded. I have to load the floppy module by hand.
The Alsa OSS emulation stuff is the same. My modprobe.conf lists it
with the regular alsa modules.
What modutils packages do you have installed? What does your
modprobe.conf look like?
Created attachment 98409 [details]
I have modutils-2.4.26-6 installed.
currently this machine is running a custom 2.6.3 kernel. Our dual Opteron
system isn't hooked up so I am not sure what version of modutils it's running.
The last kernel installed was on the Opteron was 2.6.3-1.118.
Aha, reproduced here.
/sbin/modprobe isn't getting called at all for kmod-type events ->
NOTE: I have seen this both with the Fedora Devel Kernels (2.6.3)
and a custom build kernel built with straight kernel.org sources.
I just compiled a new custom version of 2.6.4 with patches for
x86_64 (x86_64-2.6.4rc3.bz2 patch from x86-64.org) and the lastest
alsa patch. Now the floppy modules loads. So I don't know what
changed as it worked before 2.6.3 and it works after.
Andi Kleen's patch got accepted by linus and is in the 2.6.4 kernel
Yep, 2.6.4-1.275 works correctly.