[SOLVED] Missing modules after compiling new kernel

ADX · 08-13-2011, 01:14 PM

I'm having a problem getting firewire modules to load. Basically, I need firewire_core and firewire_ohci so I can use dvgrab. I tried the following:

Code:

[root@x:/]# modprobe firewire_core
[root@x:/]# modprobe firewire_ohci

But the modules aren't showing with lsmod:

Code:

[root@x:/]# lsmod | grep firewire
[root@x:/]#

I decided to then investigate the kernel module folders.

This kernel (3.0.0) was compiled with firewire support by default. When I compared the directory /lib/modules/2.6.37.6/kernel/drivers/firewire with /lib/modules/3.0.0/kernel/drivers/firewire/, there seemed to be missing modules in the newer kernel.

Code:

[root@x:/lib/modules/2.6.37.6/kernel/drivers/firewire]# ls
firewire-core.ko  firewire-net.ko  firewire-ohci.ko  firewire-sbp2.ko  nosy.ko

Code:

[root@x:/lib/modules/3.0.0/kernel/drivers/firewire]# ls
firewire-net.ko  nosy.ko

I switched back over to the 2.6 kernel and ran lsmod | grep firewire again and the modules were loaded? Why aren't they doing the same in the newer one?

kilgoretrout · 08-13-2011, 01:22 PM

Quote:

This kernel (3.0.0) was compiled with firewire support by default.

Are you sure you compiled these as modules rather than in the kernel directly? If you did the later, lsmod won't show the firewire modules as firewire support is not through loadable kernel modules.

markush · 08-13-2011, 01:23 PM

Hello ADX,

normally you should get an errormessage when you try to load a module which is missing. If there's no message this means that the module is successfully loaded.

Are you sure that you built the drivers as modules and not into the kernel? Are you missing the drivers for firewire? is there anything which does not work with firewire?

Markus

ADX · 08-13-2011, 01:36 PM

I ran make xconfig in the /usr/src/linux-3.0 directory so I could look at the current configuration, and you both correct -- the new firewire stack is built directly into the kernel.

One other quick question, besides running "make xconfig" in the source directory, is there a more efficient way to see if drivers have been compiled as modules or directly into the kernel?

Thanks for the help guys.

markush · 08-13-2011, 01:42 PM

Quote:

Originally Posted by ADX

One other quick question, besides running "make xconfig" in the source directory, is there a more efficient way to see if drivers have been compiled as modules or directly into the kernel?

Yes there is, as an example

Code:

grep -i firewire .config

this command has to be executed within the sources-directory (where .config resides) and it will show you as an example

Code:

# IEEE 1394 (FireWire) support
# You can enable one or both FireWire driver stacks.
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# Supported FireWire (IEEE 1394) Adapters
# CONFIG_DVB_FIREDTV_FIREWIRE is not set

the output here. But it tells you if it's built if it's a module or compiled into the kernel.

Markus