I have iwl3945 and mac80211 as kernel modules (2.6.24-gentoo) if I rmmod or modprobe -r iwl3945, Two LEDS start flashind and the PC freezes, i am forced to reboot... # modinfo iwl3945 filename: /lib/modules/2.6.24-gentoo/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko license: GPL author: Copyright(c) 2003-2007 Intel Corporation version: 1.1.17kds description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux srcversion: 84FCA8FBB1030866AE48574 alias: pci:v00008086d00004227sv*sd*bc*sc*i* alias: pci:v00008086d00004222sv*sd*bc*sc*i* depends: mac80211 vermagic: 2.6.24-gentoo SMP mod_unload CORE2 parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: disable:manually disable the radio (default 0 [radio on]) (int) parm: hwcrypto:using hardware crypto engine (default 0 [software]) (int) parm: debug:debug output mask (int) parm: disable_hw_scan:disable hardware scanning (default 0) (int) parm: queues_num:number of hw queues. (int) parm: qos_enable:enable all QoS functionality (int) Reproducible: Always
i try to rmmod with -v option: output: rmmod iwl3945,wait=no Oops:0000 [#1]SMP Modules linked in:fuse
Does anything appear after that? If you run the rmmod on a root console outside of X, you will probably see a much more detailed crash report. Please capture that, either with digital camera or serial console.
the output of rmmod -v iwl3945 i have paste was from the tty1 console and there was no more details...
I succeded in having a stack trace, i photographed that... (attachement)
Created attachment 142716 [details] error message screenshot
Great, thanks. Sorry to be a pain, any chance you could enable a framebuffer with higher resolution so that more text appears on screen? The top of the message has been cut off, and it might not have even been the first stack trace.
With a framebuffer we can see the beginning of the message. I uploaded the photo: http://img176.imageshack.us/img176/1468/spa0203ur5.jpg Scuse for the quality of the picture
I have posted the bug on Bughost ( http://bughost.org/bugzilla/show_bug.cgi?id=1548 ) and one tolds to me that the driver included in the kernel causes that bug...and advices to me to upgrade to iwlwifi-1.2.23, i think the ebuild of iwlwifi have to be modified so that we will be able to compile this driver with the new kernel. thx
I don't see any bug reports stating that 1.2.23 doesn't compile on 2.6.24. If that's the case, could you please file a new bug for that issue and mention it here?
(In reply to comment #8) > I have posted the bug on Bughost ( > http://bughost.org/bugzilla/show_bug.cgi?id=1548 ) and one tolds to me that the > driver included in the kernel causes that bug...and advices to me to upgrade to > iwlwifi-1.2.23, i think the ebuild of iwlwifi have to be modified so that we > will be able to compile this driver with the new kernel. > > thx > Maybe other option would be patch kernel iwlwifi for updating it to 1.2.23 (or maybe do both: update iwlwifi provided by kernel (for Gentoo 2008.0 install) and also maintain iwlwifi ebuild for being able to get the latest iwlwifi if needed)
we'll work on backporting a fix when it is confirmed that there is one
Please can you test the latest development kernel, currently 2.6.25-rc5, and see how things work there?
Ok with the vanilla 2.6.25-RC5, I can modprobe -r iwl3945, i see that the version of the driver is 1.2.23... But this kernel don't leave me install the nvidia driver so I would install this driver with portage and with my actual kernel (2.6.24) Why the ebuild contains that: if kernel_is gt 2 6 23 ; then eerror "iwlwifi is included in 2.6.24, this ebuild is not guaranteed to" eerror "build against the newer kernel." die "invalid /usr/src/linux symlink"
I don't understand why you're looking at the ebuild when you are using the in-kernel drivers. Nevertheless, thanks for the testing, it looks like we'll be waiting for 2.6.25 to close this one.
(In reply to comment #14) > I don't understand why you're looking at the ebuild when you are using the > in-kernel drivers. > > Nevertheless, thanks for the testing, it looks like we'll be waiting for 2.6.25 > to close this one. > Hello! I have this problem too. I absolutely want to emerge iwlwifi driver, and not to use the one included into the kernel. That driver doesn't work as well as the portage one. It frequently disconnects from the AP, and it's not a good thing. Is there a workaround to emerge that driver anyway? Thanks
Have you tried the latest development kernel, currently 2.6.25-rc7?
(In reply to comment #16) > Have you tried the latest development kernel, currently 2.6.25-rc7? > No I haven't. I prefer to use the last stable kernel release, which is 2.6.24-r4 at the moment. Thanks.
It would be useful if you could at least briefly try 2.6.25-rc8 for testing purposes. I think you will find the driver there is more up to date than what you will find externally, and hopefully your issues will be gone.
And if you want to use the external version and it is not working with 2.6.24 you are welcome to file a new bug. This bug is about the kernel, but the iwlwifi external package is maintained by other people.
gentoo-sources-2.6.25 is now in portage
