Comment 11 for bug 291220

Oh, one more thing:

If I start my laptop with the same contents /etc/modprobe.d/blacklist has by default, then the WiFi LED never turns on and to connect to my network I have to do the next procedure every time I start my computer: Go to System -> Hardware Drivers and enable the B43 wireless driver (the first of the list; there are two with the same title, but the second one has no description; by the way, before enabling it, I see a message that warns that another version of the driver is in use). Note that this is with an updated Intrepid system, as when Intrepid was just out this didn't even work without the procedure I mentioned when I reported this bug.

When I enable that driver, knetworkmanager connects to my WiFi network quickly. However, my eth0 interface is apparently disabled.

On the other hand, with the b43/ssb modules blacklisted, there's only one driver available whose name is "wl".

This is a mess. In Gutsy and Hardy I just enabled the only available driver _once_ and I _never_ had problems.

Please let me know if I can help you further. I wouldn't like newcomers to face this problem.