Comment 6 for bug 333903

Martin, sorry for the delay in getting back, but here's the information you requested:

>So it seems that the wl module does not autoload for some reason; I wonder why, if jockey detects the wl >module, its modaliases should be okay. But just to be sure, can you please give me the output of
>
> lspci | grep 0b:00

paul :~$ lspci | grep 0b:00
0b:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 01)

>Just for debugging, what happens if you modify /etc/modprobe.d/blacklist-bcm43 to look like this:
>----------------- 8< ------------------
>blacklist bcm43xx
>blacklist b43
>blacklist b43_legacy
>blacklist ssb
>blacklist b44
>----------------- 8< ------------------
>
>Please be aware that this will break your ethernet card, i. e. you most likely won't have an ethernet network >connection if you do that and reboot; thus please create a backup of the file, and move it back after the test. >With above file, does the wl module load automatically?

OK, no success with this either. Here's what I tried:

paul :~$ cat /etc/modprobe.d/blacklist-bcm43
blacklist bcm43xx
blacklist b43
blacklist b43_legacy
blacklist ssb
blacklist b44
# load wl before b44 so that both work
install wl modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe -Qba b44

and after rebooting, still no wireless. But, unexpectedly, the b44 got loaded and my wired network is working.

Could there be something else going on here .. perhaps modprobe is misbehaving and not executing this blacklist file?