jockey fails to enable broadcom STA driver

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

?

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?

I make a same blacklist above. :-)
This helped me:
http://djkaos.wordpress.com/2008/10/25/installing-broadcom-80211-linux-sta-driver/

I quote:
Installing Broadcom 802.11 Linux STA driver
 25 10 2008

This driver includes
 BCM4311, BCM4312, BCM4321, and BCM4322

Finally my HP 6515b with BCM4312 is free from ndiswrapper !!!!

A)

1) Depending on your system download 32 or 64 bit package

from http://www.broadcom.com/support/802.11/linux_sta.php

2) Go to a terminal to the dir with package.

3) tar -xvzf hybrid-portsrc-.tar.gz

Replace version with one you have

4) Install kernel headers (eg. in fedora "yum install kernel-headers")

5) make -C /lib/modules/`uname -r`/build M=`pwd`

if There were no errors

6) Unload Modules from memory

rmmod ndiswrapper b43 ssb bcm43xx b43legacy

7) For WPA

modprobe ieee80211_crypt_tkip

8)Check if Compiled Module is working

insmod wl.ko

Now Probably a new interface will be there for wireless (wlan0 or eth-1)

To check it run

iwconfig

iwlist scanning

AND YES !! ITS Working !!!!!

B)Making it load on boot

1)cp wl.ko /lib/modules/`uname-r`/kernel/net/wireless/

2)depmod -a

3)rmmod wl

4)modprobe wl

5)Add following Lines to /etc/rc.local (in openSuse /etc/rc/rc.d/boot.local)

modprobe wl

NOTE: If You Have Problems See README on the package page or post in troubleshooting page

please not blacklist the "b44" module
because this manage the wired ethernet controller:
lspci
03:00.0 Ethernet Conroller: Broadcom Corporation BCM4401-B0 100Base-TX (Rev 02)

in DELL Inspiron 1520

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?

You're talking about modaliases prompted me to look further, and here's what I'm seeing:

First, there are 2 broadcom network devices that use the same "ssb" module:

03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0b:00.0 0280: 14e4:4328 (rev 01)

0b:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 01)
03:00.0 0200: 14e4:170c (rev 02)

Next, notice in dmesg that the boot process results in the ssb driver being loaded for the wifi before it gets loaded for the ethernet:

[ 2.993455] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 2.993468] b43-pci-bridge 0000:0b:00.0: setting latency timer to 64
[ 3.061098] ssb: Sonics Silicon Backplane found on PCI device 0000:0b:00.0
[ 3.061098] ssb: Sonics Silicon Backplane found on PCI device 0000:0b:00.0
[ 3.129114] ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0

Next, looking at the modules to see why, we have the same aliases in the ssb and wl, but b44 is different, although it depends on ssb:

paul :~$ modinfo ssb
filename: /lib/modules/2.6.28-8-generic/kernel/drivers/ssb/ssb.ko
description: Sonics Silicon Backplane driver
         < snip >
alias: pci:v000014E4d00004328sv*sd*bc*sc*i*
         < snip >

paul :~$ modinfo wl
filename: /lib/modules/2.6.28-8-generic/volatile/wl.ko
         < snip >
alias: pci:v000014E4d00004328sv*sd*bc*sc*i*
         < snip >

paul :~$ modinfo b44
filename: /lib/modules/2.6.28-8-generic/kernel/drivers/net/b44.ko
version: 2.0
license: GPL
description: Broadcom 44xx/47xx 10/100 PCI ethernet driver
author: Felix Fietkau, Florian Schirmer, Pekka Pietikainen, David S. Miller
srcversion: D926C0FD72CC929295E14A0
alias: ssb:v4243id0806rev*
alias: pci:v000014E4d0000170Csv*sd*bc*sc*i*
alias: pci:v000014E4d00004402sv*sd*bc*sc*i*
alias: pci:v000014E4d00004401sv*sd*bc*sc*i*
depends: ssb,mii
vermagic: 2.6.28-8-generic SMP mod_unload modversions
parm: b44_debug:B44 bitmapped debugging message enable value (int)

OK, so armed with this information, I tried some different lines in /etc/modprobe.d/blacklist-bcm43, and nothing works. Here's what I tried:

install b44 modprobe -r b43 b43legacy ssb; modprobe wl $CMDLINE_OPTS; modprobe --ignore-install b44 $CMDLINE_OPTS

install ssb modprobe -r b43 b44 b43legacy; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe --ignore-install ssb $CMDLINE_OPTS

install ssb modprobe -r b43 b44 b43legacy; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe --ignore-install ssb $CMDLINE_OPTS; modprobe --ignore-install b44 $CMDLINE_OPTS

I must be misreading "man modprobe.conf" or somethings wrong about the way the kernel is using etc/modprobe.d/blacklist-bcm43 because any one of these should work.

Any other ideas?

Of course, I can always put a command in /etc/init.d/local to execute "modprobe -r b44 ssb ; modprobe wl ; modprobe b44", but this shouldn't be required.

Indeed wl, ssb and b43 take the same modalias space, that's why the jockey-generated blacklist has this rule:

# 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

That means: "if you install wl, remove b43 b44 b43legacy ssb, install wl, and then load b43 again". b43 and friends won't get autoloaded due to the blacklisting. I actually thought that this got successfully tested in the intrepit timeframe, but maybe it was, and it stopped working in Jaunty.

At first I'd think that b44 is loaded first, which pulls in ssb as a dependency, and then the kernel doesn't bother modprobing again, since there's already a driver which (supposedly) covers the device. However, you already said that ssb would be loaded first, then b43, then b44?

Since you already tried blacklisting b44, it seems that something in udev doesn't respect the blacklist. However, a "grep modprobe /lib/udev/rules.d" shows that all calls have -b ("use blacklist"). So I'm quite stunned now.

Do you happen to have an /etc/modules which explicitly loads b44 or b43 or ssb?

Also, to checkout whether the blacklist is actually being used, could you try appending these:

  install b44 echo b44 >> /tmp/modprobe.log; /sbin/modprobe --ignore-install b44
  install b43 echo b43 >> /tmp/modprobe.log; /sbin/modprobe --ignore-install b43
  install ssb echo ssb >> /tmp/modprobe.log; /sbin/modprobe --ignore-install ssb
  install wl echo wl >> /tmp/modprobe.log; modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe -Qba b44

(and remove the other install rules for those three, but do keep the blacklist entries). Do you get a /tmp/modprobe.log? If so, then something is not adhering the blacklist.

Thank you!

> Indeed wl, ssb and b43 take the same modalias space, that's why the
> jockey-generated blacklist has this rule:
>
> # 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
>
> That means: "if you install wl, remove b43 b44 b43legacy ssb, install
> wl, and then load b43 again". b43 and friends won't get autoloaded due
> to the blacklisting. I actually thought that this got successfully
> tested in the intrepit timeframe, but maybe it was, and it stopped
> working in Jaunty.

Yes, I had inserted this same line in intrepid /etc/modprobe.d/wl and it was working for me there, so it's definitely a change in jaunty.

> At first I'd think that b44 is loaded first, which pulls in ssb as a
> dependency, and then the kernel doesn't bother modprobing again, since
> there's already a driver which (supposedly) covers the device. However,
> you already said that ssb would be loaded first, then b43, then b44?

I'm confused by the output of "lshw -C network" which shows this for the ethernet:

       product: BCM4401-B0 100Base-TX
       bus info: pci@0000:03:00.0
       configuration: broadcast=yes driver=b44 driverversion=2.0 ip=65.191.200.226 latency=64 module=ssb multicast=yes

You say the ethernet uses b44 and pulls in ssb as a dependency, but why does it show the module as ssb instead of b44. I guess I'm confused about the difference between a module and a driver. I thought they were the same. I would have expected the driver and module listings to both be b44.

Anyway, the output for the wifi shows:

       product: BCM4328 802.11a/b/g/n
       bus info: pci@0000:0b:00.0
       configuration: driver=b43-pci-bridge latency=0 module=ssb

Isnt' the ssb module the reason that the STA "wl" module won't ever get called? Apparently, the "blacklist ssb" statement isn't working (more below). Do we need some blacklist statement for "b43-pci-bridge" (whatever that is, since it's no a module in /lib/modules/).

>
> Since you already tried blacklisting b44, it seems that something in
> udev doesn't respect the blacklist. However, a "grep modprobe
> /lib/udev/rules.d" shows that all calls have -b ("use blacklist"). So
> I'm quite stunned now.
>
> Do you happen to have an /etc/modules which explicitly loads b44 or b43
> or ssb?

Here's the contents of /etc/modules

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
loop
lp
rtc
fuse

> Also, to checkout whether the blacklist is actually being used, could
> you try appending these:
>
> install b44 echo b44 >> /tmp/modprobe.log; /sbin/modprobe --ignore-install b44
> install b43 echo b43 >> /tmp/modprobe.log; /sbin/modprobe --ignore-install b43
> install ssb echo ssb >> /tmp/modprobe.log; /sbin/modprobe --ignore-install ssb
> install wl echo wl >> /tmp/modprobe.log; modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl ...

Hello Pauls,

pauls [2009-03-05 0:15 -0000]:
> Yes, I had inserted this same line in intrepid /etc/modprobe.d/wl and it
> was working for me there, so it's definitely a change in jaunty.

OK, marked as jaunty regression.

> I'm confused by the output of "lshw -C network" which shows this for the
> ethernet:
>
> product: BCM4401-B0 100Base-TX
> bus info: pci@0000:03:00.0
> configuration: broadcast=yes driver=b44 driverversion=2.0 ip=65.191.200.226 latency=64 module=ssb multicast=yes

That driver/module is indeed confusing. But then again I don't know
lshw at all.

> Isnt' the ssb module the reason that the STA "wl" module won't ever get
> called?

Presumably, yes. Either ssb, or b43.

> Apparently, the "blacklist ssb" statement isn't working (more
> below). Do we need some blacklist statement for "b43-pci-bridge"
> (whatever that is, since it's no a module in /lib/modules/).

No, that'll only work for modules. But maybe you can give me the
output of "lsmod" (lsmod > /tmp/modules.txt and attach that file
here). Maybe there's yet another one by now.

> Here's the contents of /etc/modules

OK, nothing here.

> After rebooting there is no modprobe.log.

Interesting. So it seems that yet another module is pulling in any of
those as a dependency. Maybe the lsmod output will tell me which. If
not, we have to use some stronger weapons, like replacing
/sbin/modprobe with a shell wrapper which logs loaded modules and
$PPID to a file. I'll get to that later.

Okay, I just checked with

   for m in `cat modules.txt | awk '{print $1'}`; do echo "-- $m"; modinfo $m | grep '^alias.*14E4'; done

that it's indeed just b44 and ssb which should get autoloaded. So I don't understand why they still get autoloaded even if they are blacklisted in /etc/modprobe.d/blacklist-bcm43.

As one possible workaround, if you drop /etc/modprobe.d/blacklist-bcm43 completely and add "wl" to /etc/modules, this *should* make things work, and be much more robust. Can you please try this, too?

Some notes with the discussion with Scott:

 - Should be called "blacklist-bcm43.conf" (other suffices are deprecated and modutils complains)
 - modprobe -Qba -> modprobe -b
 - Most probably the difference between intrepid and jaunty is that those modules get auto-loaded in initramfs already
 - I forgot to tell you to call "sudo update-initramfs -u" after modifying the blacklist.

So, please try out the following:

 (1) Replace /etc/modprobe.d/blacklist-bcm43 with this:

----------------- 8< ------------------
blacklist bcm43xx
blacklist b43
blacklist b43_legacy
blacklist ssb
blacklist b44
----------------- 8< ------------------

    Run "sudo update-initramfs -u", reboot, and check lsmod that it didn't load any of b43, ssb, b44. You should get wl loaded, and wifi running. This should break your ethernet card.

  (2) Don't reboot yet. Replace /etc/modprobe.d/blacklist-bcm43 with this:

----------------- 8< ------------------
blacklist bcm43xx
blacklist b43
blacklist b43legacy
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 -b b44
----------------- 8< ------------------

(Note that the previous version had a typo: "b43_legacy"; it needs to be "b43legacy"). Now run "sudo update-initramfs -u".

Find out the modalias of your wifi card with

  grep MODALIAS=pci.*4328 /var/log/udev

and give me the output of

  sudo modprobe -n -b pci:v000014E4d...

(Use the modalias you just found with that grep).

> Some notes with the discussion with Scott:
>
> - Should be called "blacklist-bcm43.conf" (other suffices are deprecated and modutils complains)
> - modprobe -Qba -> modprobe -b
> - Most probably the difference between intrepid and jaunty is that those modules get auto-loaded in initramfs already
> - I forgot to tell you to call "sudo update-initramfs -u" after modifying the blacklist.
>
> So, please try out the following:
>
> (1) Replace /etc/modprobe.d/blacklist-bcm43 with this:
>
> ----------------- 8< ------------------
> blacklist bcm43xx
> blacklist b43
> blacklist b43_legacy
> blacklist ssb
> blacklist b44
> ----------------- 8< ------------------
>
> Run "sudo update-initramfs -u", reboot, and check lsmod that it
> didn't load any of b43, ssb, b44. You should get wl loaded, and wifi
> running. This should break your ethernet card.

Yes, this worked as you expected .. b43 b44 not loaded and wifi working with wl.

>
> (2) Don't reboot yet. Replace /etc/modprobe.d/blacklist-bcm43 with
> this:
>
> ----------------- 8< ------------------
> blacklist bcm43xx
> blacklist b43
> blacklist b43legacy
> 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 -b b44
> ----------------- 8< ------------------
>
> (Note that the previous version had a typo: "b43_legacy"; it needs to be
> "b43legacy"). Now run "sudo update-initramfs -u".

Rebooting gives me the wifi, but no ethernet, and b44 is still not getting loaded.

> Find out the modalias of your wifi card with
>
> grep MODALIAS=pci.*4328 /var/log/udev

paul :~$ grep MODALIAS=pci.*4328 /var/log/udev
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00

> and give me the output of
>
> sudo modprobe -n -b pci:v000014E4d...

paul :~$ sudo modprobe -n -b
pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
WARNING: Not loading blacklisted module ssb
paul :~$ sudo modprobe -n -b
pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
WARNING: Not loading blacklisted module ssb

> (Use the modalias you just found with that grep).

FWIW, I also ran the test of adding wl to /etc/modules.

> Okay, I just checked with
>
> for m in `cat modules.txt | awk '{print $1'}`; do echo "-- $m";
> modinfo $m | grep '^alias.*14E4'; done
>
> that it's indeed just b44 and ssb which should get autoloaded. So I
> don't understand why they still get autoloaded even if they are
> blacklisted in /etc/modprobe.d/blacklist-bcm43.
>
> As one possible workaround, if you drop /etc/modprobe.d/blacklist-bcm43
> completely and add "wl" to /etc/modules, this *should* make things work,
> and be much more robust. Can you please try this, too?
>

Without the blacklist file, it does not work. But, with this blacklist file, it does work .. I get both wifi and eth0. Here's what I ended up using:

paul :~$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
loop
lp
rtc
wl

paul :~$ cat /etc/modprobe.d/blacklist-bcm43
blacklist bcm43xx
blacklist b43
blacklist b43legacy
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 -b b44

pauls [2009-03-06 14:46 -0000]:
> Yes, this worked as you expected .. b43 b44 not loaded and wifi working
> with wl.

Good. So we know that blacklisting does work, and we just forgot the
update-initramfs.

> > (2) Don't reboot yet. Replace /etc/modprobe.d/blacklist-bcm43 with
> > this:
> >
> > ----------------- 8< ------------------
> > blacklist bcm43xx
> > blacklist b43
> > blacklist b43legacy
> > 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 -b b44

Argh, sorry. The last -b is wrong, of course. Can you try again with

install wl modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install wl $CMDLINE_OPTS; modprobe --ignore-install b44

> Rebooting gives me the wifi, but no ethernet, and b44 is still not
> getting loaded.

Right, due to the erroneous -b.

> MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00

Ah, thanks.

> > sudo modprobe -n -b pci:v000014E4d...
>
> paul :~$ sudo modprobe -n -b
> pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
> WARNING: Not loading blacklisted module ssb

Okay, but it doesn't mention wl; presumably because it's already
loaded; Can you please keep above blacklist file, stop NetworkManager
(sudo /etc/init.d/network-manager stop), sudo rmmod wl, and do the
same modprobe -n -b call again?

pauls [2009-03-06 14:50 -0000]:
> Without the blacklist file, it does not work.

Right, /etc/modules is processed after initramfs, so this can't.

> But, with this blacklist file, it does work .. I get both wifi and
> eth0. Here's what I ended up using:

I hope we can do with just the blacklist file, with the extra -b
removed. *crossing fingers*

I am experiencing the same issue where wl is not being loaded, after doing modprobe wl wireless is then enabled, but network manager then asks to access keyring and then whole system freezes have to force a boot.

The freezing seems to be related to this bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/217551

CrYpTiC_MauleR [2009-03-06 17:01 -0000]:
> I am experiencing the same issue where wl is not being loaded, after
> doing modprobe wl wireless is then enabled, but network manager then
> asks to access keyring and then whole system freezes have to force a
> boot.

"Freeze" in which sense? Does the screen still get updated? Can you
move the mouse?

Can you still switch to a text console with Ctrl+Alt+F1? If so, please
log in, do

  dmesg > dmesg.txt
  cp /var/log/Xorg.0.log .
  sudo reboot
  [ enter your password ]

and then attach dmesg.txt and Xorg.0.log.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

> Argh, sorry. The last -b is wrong, of course. Can you try again with
>
> install wl modprobe -r b43 b44 b43legacy ssb; modprobe --ignore-install
> wl $CMDLINE_OPTS; modprobe --ignore-install b44

Yes, this works. I now have both wifi and eth0 lan.

>> MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
>
> Ah, thanks.
>
>>> sudo modprobe -n -b pci:v000014E4d...
>> paul :~$ sudo modprobe -n -b
>> pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
>> WARNING: Not loading blacklisted module ssb
>
> Okay, but it doesn't mention wl; presumably because it's already
> loaded; Can you please keep above blacklist file, stop NetworkManager

Maybe I misunderstand. I'm rebooted using the corrected blacklist-bcm43 file, so now everything is loaded. Do you want me to go back to the original one that loads nothing and just has the blacklist?

> (sudo /etc/init.d/network-manager stop), sudo rmmod wl, and do the

I don't have an /etc/init.d/network-manager, but have "networking" instead, and it won't stop it eth0.
paul :~$ ls /etc/init.d/*net*
/etc/init.d/networking
paul :~$ sudo /etc/init.d/networking stop
 * Deconfiguring network interfaces...Ignoring unknown interface eth0=eth0.

> same modprobe -n -b call again?

paul :~$ sudo rmmod wl
paul :~$ grep MODALIAS=pci.*4328 /var/log/udev
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
paul :~$ sudo modprobe -n -b pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
WARNING: Not loading blacklisted module ssb

I just get the same result. Even if I remove all the b44, b43, ssb, wl, I still don't get anything about wl:

paul :~$ sudo rmmod b44
paul :~$ sudo rmmod b43
ERROR: Module b43 does not exist in /proc/modules
paul :~$ sudo rmmod ssb
paul :~$ sudo rmmod wl
ERROR: Module wl does not exist in /proc/modules
paul :~$ grep MODALIAS=pci.*4328 /var/log/udev
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
MODALIAS=pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
paul :~$ sudo modprobe -n -b pci:v000014E4d00004328sv00001028sd00000009bc02sc80i00
WARNING: Not loading blacklisted module ssb

Did I misunderstand?

CrYpTiC_MauleR
> asks to access keyring and then whole system freezes have to force a

Unfortunately, I do not have a network to connect with, so can't verify your problem. All I can say is that the wifi is able to scan successfully.

regards,

>>"Freeze" in which sense? Does the screen still get updated? Can you
>>move the mouse?
>>
>>Can you still switch to a text console with Ctrl+Alt+F1? If so, please
>>log in, do

Well when the password prompt comes up it freezes to the point where I can move mouse but not do anything with it and keyboard I assume does not work because cannot shutdown using it. This was when I had manually entered in a wireless network using the network manager. This time I deleted the entry and then waited until wireless network loaded before I chose my network and then put in password. It all worked great!...for awhile, before the whole system froze where not even the mouse would work and then had to force shutdown. I could not use Ctrl+Alt+F1 either.

@ pauls: oh, great! so you are saying that if you have this file:

----------------- 8< ------------------
blacklist bcm43xx
blacklist b43
blacklist b43legacy
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 b44
----------------- 8< ------------------

and do update-initramfs, then everything works as it should? Did you also remove "wl" from /etc/modules again?

If that works, I know everything how to fix it in jockey properly. Thanks for bearing with me and for your great help with debugging this! (I don't have that hardware, so I depend on testing feedback)

> @ pauls: oh, great! so you are saying that if you have this file:
>
> ----------------- 8< ------------------
> blacklist bcm43xx
> blacklist b43
> blacklist b43legacy
> 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 b44
> ----------------- 8< ------------------

It's almost the same .. just the --ignore-install option on b44 at the end:

paul :~$ cat /etc/modprobe.d/blacklist-bcm43
blacklist bcm43xx
blacklist b43
blacklist b43legacy
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 --ignore-install b44

>
> and do update-initramfs, then everything works as it should? Did you
> also remove "wl" from /etc/modules again?

Yes, I removed "wl" from /etc/modules.

This works now for at least a couple reboots. Thanks for the great job Martin.

Wait a minute, I want to try one more thing. I want to try it with "blacklist bcm43xx" commented out because I don't find any such module in /lib/modules/ or in the /boot/config-<> list. I'll do a quick test and get back

Yes, it works ok without bcm43xx too. But, I just realized that "bcm43xx" might be from some other software source that's not installed on my system. So, forget my last post and keep it in.

regards,

pauls [2009-03-07 13:47 -0000]:
> I want to try it with "blacklist bcm43xx" commented out because I
> don't find any such module in /lib/modules/ or in the
> /boot/config-<> list.

Right, it has been removed in Linux 2.6.28. It's still present in
2.6.27, so for the sake of backportability, or people running older
kernels I just keep it; it's a no-op if the module doesn't exist.

r311

This bug was fixed in the package jockey - 0.5-0ubuntu3

---------------
jockey (0.5-0ubuntu3) jaunty; urgency=low

  * data/handlers/broadcom_wl.py: Fix spelling of the b43legacy module.
  * data/handlers/broadcom_wl.py: Fix ordering of module loading if b44 is
    needed/loaded as well: Blacklist b44, and load it in the "install wl"
    rule, so that wl always comes first. (LP: #333903)
  * Merge bug fixes from trunk:
    - oslib.py: Do not grab lsb-release stderr.
    - oslib.py: Append ".conf" suffix to blacklist file, since current
      modutils deprecates anything else.
  * data/handlers/{b43,broadcom_wl}.py: Rename blacklist-bcm43 to
    blacklist-bcm43.conf, for the same reason.
  * debian/jockey-common.postinst: Rename blacklist-{bcm43,local} to *.conf on
    upgrades.

 -- Martin Pitt <email address hidden> Sat, 07 Mar 2009 15:34:09 +0100

Was this suppose to fix the problem where the wl module is not loaded on boot? Because it still is not being loaded by itself for me when using this update so I can have modprobe wl when I want the wireless to be enabled.

CrYpTiC_MauleR [2009-03-08 18:29 -0000]:
> Was this suppose to fix the problem where the wl module is not loaded on
> boot?

Yes, that was the purpose.

> Because it still is not being loaded by itself for me when using
> this update so I can have modprobe wl when I want the wireless to be
> enabled.

Did you just update the package, or did you also disable/enable the wl
driver in jockey after that? Only the latter will actually rewrite the
configuration file.

Ok I disabled and enabled the driver, and then wireless began to work, but after rebooting it no longer works and have to modprobe wl again.

CrYpTiC_MaulerR, this report is already closed, can you please open a new one with "ubuntu-bug jockey-gtk"? This will attach some information about your specific hardware and will make debugging easier for me. Thank you!