LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
LinkBack Search this Thread
Old 08-13-2011, 01:14 PM   #1
ADX
Member
 
Registered: Jul 2011
Location: 127.0.0.1
Distribution: Slackware64-13.37
Posts: 47

Rep: Reputation: 0
Question Missing modules after compiling new kernel


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?
 
Old 08-13-2011, 01:22 PM   #2
kilgoretrout
Senior Member
 
Registered: Oct 2003
Posts: 2,284

Rep: Reputation: 136Reputation: 136
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.
 
1 members found this post helpful.
Old 08-13-2011, 01:23 PM   #3
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
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
 
1 members found this post helpful.
Old 08-13-2011, 01:36 PM   #4
ADX
Member
 
Registered: Jul 2011
Location: 127.0.0.1
Distribution: Slackware64-13.37
Posts: 47

Original Poster
Rep: Reputation: 0
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.
 
Old 08-13-2011, 01:42 PM   #5
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Quote:
Originally Posted by ADX View Post
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
 
1 members found this post helpful.
  


Reply

Tags
firewire, modprobe, modules


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Missing modules after building new kernel? lugoteehalt Debian 9 11-11-2009 03:36 PM
/lib/modules/2.4.33.3/kernel/sound folder is missing after compiling kernel Paulo Ges Slackware - Installation 2 04-15-2007 08:42 PM
Missing modules when upgrade kernel 2.6 letdoit Slackware 7 05-26-2004 12:42 AM
new kernel (2.4.22 up from 2.4.20-6) - missing modules - use old modules? Simon Bridge Linux - Software 1 02-04-2004 05:52 AM
missing kernel modules? guthrie Debian 7 01-02-2004 11:13 AM


All times are GMT -5. The time now is 07:55 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration