sudo echo b43 >> /etc/modules On Sat, Apr 9, 2016 at 5:17 PM, message <letter@xxxxxxxxxxxxxxx> wrote: > Readers, > > Can anyone explain if the following 'dmesg' outputs are useful to understand > why after start of X session, the wireless driver fails sometimes? The > wireless driver does not start automatically and is always started manually > with the command (as root): > > modprobe b43 > > Below is the dmesg output when the command above, starts successfully the > wireless driver: > > b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0 > b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver ... > IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > b43-phy0: Broadcom 4311 WLAN found (core revision 10) > b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8 > b43-phy0: Found Radio: Manuf 0x17F, ID 0x2050, Revision 2, Version 0 > Broadcom 43xx driver loaded [ Features: PNLS ] > ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' > IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) > IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > wlan0: authenticate with ... > wlan0: send auth to ... (try 1/3) > wlan0: authenticated > wlan0: associate with ... (try 1/3) > wlan0: RX AssocResp from ... (capab=0x431 status=0 aid=1) > wlan0: associated > IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > > Below when the 'modprobe b43' fails to start the wireless driver: > > b43-phy0: Broadcom 4311 WLAN found (core revision 10) > b43-phy0: Found PHY: Analog 4, Type 2 (G), Revision 8 > b43-phy0 ERROR: FOUND UNSUPPORTED RADIO (Manuf 0xFFF, ID 0xFFFF, Revision > 15, Version 0) > b43: probe of ssb0:0 failed with error -95 > Broadcom 43xx driver loaded [ Features: PNLS ] > > The only solution seems to be to switch off the computer and start again, > sometimes 3 or 4 times repeated failure occurs.
