Actually not. b43 being blacklisted it isn&#39;t loaded at startup (I verified it)<br><br>On the contrary I unload bcm43xx<br>load b43<br>unload b43<br>and then load again bcm43xx<br><br>It seems to me that b43 does some kind of initialisation which allows iwlist scanning to work but not to associate with an AP. Then by reloading bcm43xx I can associate with AP<br>
<br><br><br><div class="gmail_quote">2008/4/26 krop &lt;<a href="mailto:kropx77@gmail.com">kropx77@gmail.com</a>&gt;:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[quote]<br>
<div class="Ih2E3d">sudo modprobe -r b43<br>
sudo modprobe bcm43xx<br>
</div>[/quote]<br>
<br>
That just means you&#39;re using the same workaround : unloading the b43<br>
module and loading bcm43xx instead.<br>
<div><div></div><div class="Wj3C7c"><br>
--<br>
bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn&#39;t work.<br>
<a href="https://bugs.launchpad.net/bugs/182716" target="_blank">https://bugs.launchpad.net/bugs/182716</a><br>
You received this bug notification because you are a direct subscriber<br>
of the bug.<br>
</div></div></blockquote></div><br>