On Sunday 07 February 2010 13:48:59 Rafał Miłecki wrote: > 2010/2/7 strk <s...@keybit.net>: > > 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. > > I'm not sure... if radio is turned off physically (by hardware) can > compiling without RFKILL help at all? AFAIU rfkill is just for > disabling radio by software...
rfkill is a hardware lock in the case of broadcom. Software can only read the state. (There may be laptops with broadcom cards where rfkill can be changed by software. But that's done by other means (BIOS) and the broadcom hardware doesn't know about it.) -- Greetings, Michael. _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
