Actually not. b43 being blacklisted it isn't loaded at startup (I verified it)
On the contrary I unload bcm43xx load b43 unload b43 and then load again bcm43xx 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 2008/4/26 krop <[EMAIL PROTECTED]>: > [quote] > sudo modprobe -r b43 > sudo modprobe bcm43xx > [/quote] > > That just means you're using the same workaround : unloading the b43 > module and loading bcm43xx instead. > > -- > bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP > doesn't work. > https://bugs.launchpad.net/bugs/182716 > You received this bug notification because you are a direct subscriber > of the bug. > ** Attachment added: "unnamed" http://launchpadlibrarian.net/13936945/unnamed -- bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't work. https://bugs.launchpad.net/bugs/182716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
