Matt Parnell wrote: > Output of dmesg | grep b43 (see the line that says status changed to > DISABLED): > > b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8 > b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 > b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config > b43 ssb0:0: firmware: requesting b43/ucode5.fw > b43 ssb0:0: firmware: requesting b43/pcm5.fw > b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw > b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw > b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) > b43-phy0 debug: Chip initialized > b43-phy0 debug: 32-bit DMA initialized > Registered led device: b43-phy0::tx > Registered led device: b43-phy0::rx > Registered led device: b43-phy0::radio > b43-phy0 debug: Wireless interface started > b43-phy0 debug: Adding Interface type 2 > b43-phy0: Radio turned on by software > b43-phy0: Radio hardware status changed to DISABLED
The software is doing exactly as it should. Your radio kill switch is _OFF_, which tells the system to forbid the transmitter from generating a radio signal. The problem is that your radio kill switch does not generate a keycode. This kind of hardware is handled by the hp-wmi module, but you will need to load it manually. It will not load automatically as there is no way to detect that the switch on your laptop is of that type. Note that WMI stands for Windows Management Interface. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
