On 02/07/2010 05:57 AM, strk wrote: > On Sat, Feb 06, 2010 at 06:54:44PM -0600, Larry Finger wrote: > >> You can get the wireless-compat sources for kernel 2.6.26 and build that. >> Othersise, go to kernel.org and get the full sources. > > I opted for an upgrade first (debian lenny to debian squeeze). > So I'm now at kernel version 2.6.32 and the problem is somehow > different (still related to kill switch). > > The messages in this case are more clear (on ifconfig wlan0 xxxx): > > b43legacy ssb0:0: firmware: requesting b3legacy/ucode2.fw > b43legacy ssb0:0: firmware: requesting b3legacy/pcm4.fw > b43legacy ssb0:0: firmware: requesting b3legacy/b0g0initvals2.fw > b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 > 02:36:27) > b43legacy-phy0: Radio hardware status changed to DISABLED > b43legacy-phy0: Radio turned on by software > b43legacy-phy0: The hardware RF-kill button still turns the radio physically > off. Press th ebutton to turn it on. > > Same suggestions applies ? Or was some load-time option added in 2.6.32 ?
There is no load-time option to ignore RFKILL, and as you have read, there never will be. I assume that your laptop has a mini-PCI BCM4303 card. Neither of my two devices uses that format, nor do either of mine implement the "RF silent" input, which is on pin 13, according to http://www.interfacebus.com/MiniPCI_Pinout_124Pin.html You did not see any logged rfkill messages with bcm43xx as it did not examine this input. The hardware must have honored that input and suppressed the radio whenever it was set. If you generate a system with the RFKILL subsystem disabled, all that will happen is that the messages will go away, and your radio will be silently disabled on an intermittent basis. You need to discover why that input is being generated? There could be a failure in the motherboard circuits that generate the signal. There could be a bug in the software that processes whatever WMI info that your system generates. WMI (Windows Management Interface) code handles the functions of the top row of your keyboard that are generated by a fn+FX key. One alternative would be to alter the MB or the card so that the "RF silent" input cannot be changed. BTW, I have no idea if it is a high or a low here that kills the radio. I suspect that the radio will be on if the pin is floating, but that is a guess. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
