| View previous topic :: View next topic |
| Author |
Message |
swingkyd
Guru
Joined: 13 Jan 2005
Posts: 334
|
 Posted: Wed Nov 12, 2008 2:10 am Post subject: ipw3495 and iwl3495 kernel modules |
 |
|
I had at one time used the ipw3495 kernel module. I have since recompiled my kernel to exclude this module and include the iwl3495 kernel module. After rebooting into the new kernel, both ipw3495 and iwl3495 load up. I have removed ipw3945 from the system as far as I can say and it is not being called by the kernel modules.autoload under /etc. . . I'm mistified! I'm thinking the module is there as cruft and the system is automatically loading it anyway.
How can this be removed?
I have run the --depclean and revdep-rebuild on the system and there is no difference in behaviour.
thanks! |
|
| Back to top |
|
 |
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3468
Location: Canada
|
| Posted: Wed Nov 12, 2008 5:50 am Post subject: Re: ipw3495 and iwl3495 kernel modules |
|
|
| swingkyd wrote: | I had at one time used the ipw3495 kernel module. I have since recompiled my kernel to exclude this module and include the iwl3495 kernel module. After rebooting into the new kernel, both ipw3495 and iwl3495 load up. I have removed ipw3945 from the system as far as I can say and it is not being called by the kernel modules.autoload under /etc. . . I'm mistified! I'm thinking the module is there as cruft and the system is automatically loading it anyway.
How can this be removed?
I have run the --depclean and revdep-rebuild on the system and there is no difference in behaviour.
thanks! |
probably udev loads them both at coldplug stage.
To avoid this list ipw one in
/etc/modprobe.d/blacklist |
|
| Back to top |
|
|
swingkyd
Guru
Joined: 13 Jan 2005
Posts: 334
|
| Posted: Wed Nov 12, 2008 6:09 am Post subject: |
|
|
thanks for your reply. ... so even though the kernel module is removed , it still gets loaded? that is what is confusing me too. after disabling the kernel module and recompiling, and performing "make modules_install", shouldn't that remove the old modules? Or perhaps they stay so that different versions of the same 2.6 kernel can use it?
so black-listing it will stop the behaviour I hope. |
|
| Back to top |
|
|
JeliJami
Veteran
Joined: 17 Jan 2006
Posts: 1086
Location: Belgium
|
| Posted: Wed Nov 12, 2008 1:45 pm Post subject: |
|
|
check to see if the module is still there:
| Code: | | find /lib/modules/$(uname -r) -name "ipw*.ko" |
_________________
Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
|
swingkyd
Guru
Joined: 13 Jan 2005
Posts: 334
|
| Posted: Wed Nov 12, 2008 6:31 pm Post subject: |
|
|
it sure is there! How would I know what should and should not be there?
| Code: | $ find /lib/modules/$(uname -r) -name "ipw*.ko"
/lib/modules/2.6.24-tuxonice-r9/net/wireless/ipw3945.ko
|
|
|
| Back to top |
|
|
Stupendoussteve
n00b
Joined: 06 Sep 2005
Posts: 72
Location: US West
|
| Posted: Wed Nov 12, 2008 7:40 pm Post subject: |
|
|
| If you removed it from the build list, it is still there because it was built in a previous kernel. |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3468
Location: Canada
|
| Posted: Wed Nov 12, 2008 7:42 pm Post subject: |
|
|
| swingkyd wrote: | thanks for your reply. ... so even though the kernel module is removed , it still gets loaded? that is what is confusing me too. after disabling the kernel module and recompiling, and performing "make modules_install", shouldn't that remove the old modules?
|
It should |
|
| Back to top |
|
|
swingkyd
Guru
Joined: 13 Jan 2005
Posts: 334
|
| Posted: Wed Nov 12, 2008 11:31 pm Post subject: |
|
|
so would a "make clean" then
| Code: | | make && make modules_install |
fix it? |
|
| Back to top |
|
|
JeliJami
Veteran
Joined: 17 Jan 2006
Posts: 1086
Location: Belgium
|
| Posted: Thu Nov 13, 2008 9:18 am Post subject: |
|
|
| swingkyd wrote: | so would a "make clean" then
| Code: | | make && make modules_install |
fix it? |
'make clean' only cleans your source tree, i think
you should remove the /lib/modules/$(uname -r) directory (or move it somewhere as a backup), and then 'make modules_install'
_________________
Unanswered Post Initiative | Search | FAQ
Former username: davjel |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3468
Location: Canada
|
| Posted: Thu Nov 13, 2008 7:50 pm Post subject: |
|
|
| JeliJami wrote: | | swingkyd wrote: | so would a "make clean" then
| Code: | | make && make modules_install |
fix it? |
'make clean' only cleans your source tree, i think
you should remove the /lib/modules/$(uname -r) directory (or move it somewhere as a backup), and then 'make modules_install' |
ll
somehow make modules_install always did automatically for me. Never so modules from previousl compilation left there. But of course removing this directory manually won't hurt and will make things certain |
|
| Back to top |
|
|
|
Kernel & Hardware
