LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Broadcom b43 driver - appears in lsmod, can't find interface (https://www.linuxquestions.org/questions/linux-wireless-networking-41/broadcom-b43-driver-appears-in-lsmod-cant-find-interface-788917/)

fatman 02-13-2010 01:50 PM

Broadcom b43 driver - appears in lsmod, can't find interface
 
I'm trying to get my Linksys WMP11 (Broadcom BCM4306/3, PCI ID 4e4:4320) wireless adapter up. I have no internet access on that machine and it's in the basement, so posting dmesg, etc. would be a problem (a lot of up and down stairs for me today).


I followed the steps at http://linuxwireless.org/en/users/Dr...e_installation
for a manual install of fw-cutter and the 2.6.24 b43 kernel firmware version.

I can lsmod and see b43 running. I run dmesg and ssb sees a bunch of cores - no apparent errors. There is no mention of b43 in dmesg (or /var/log/syslog & messages)

However, iwconfig only sees eth0 (which is not connected) and lo.
Any attempt with iwconfig eth1 or wlan, or ifconfig eth1/wlan0 up gives me a "no such device" error.

Any suggestions would be wonderful - even a narrowing of possible problem areas (driver, firmware, etc...)

jschiwal 02-13-2010 02:14 PM

Try "sudo /sbin/update-pciids" to update your manufacturer device codes.

Also could you post the output of "sudo /sbin/modinfo b43". I'm interested in the options.

Also, are you certain about your kernel version? I thought that the b43 module is in 2.6.25 and newer kernels.

Check for a physical switch disabling wireless. Also a FN key which disables/enables wireless.

reed9 02-13-2010 02:36 PM

Quick way to check that there isn't a firmware error is to do
Code:

dmesg | grep firmware
Also check
Code:

dmesg | grep b43
and see if that returns anything.

What distribution are you running?

fatman 02-13-2010 09:51 PM

Well....

Without an internet connection, I downloaded http://pciids.sourceforge.net/v2.2/pci.ids.bz2
and (ran downstairs and) dumped it into /usr/share/misc. Rebooted. No change. (Please let me know if I'm doing it wrong.)

No physical switch, no love from the function keys.

Here's some results from the suggested commands:

Code:

matt@HTPC:~$ sudo /sbin/modinfo b43
filename:      /lib/modules/2.6.24-26-generic/kernel/drivers/net/wireless/b43/b43.ko
license:        GPL
author:        Michael Buesch
author:        Stefano Brivio
author:        Martin Langer
description:    Broadcom B43 wireless driver
srcversion:    A63CC27F8D98EBDFDB9623F
alias:          ssb:v4243id0812rev0F*
alias:          ssb:v4243id0812rev0D*
alias:          ssb:v4243id0812rev0B*
alias:          ssb:v4243id0812rev0A*
alias:          ssb:v4243id0812rev09*
alias:          ssb:v4243id0812rev07*
alias:          ssb:v4243id0812rev06*
alias:          ssb:v4243id0812rev05*
depends:        mac80211,ssb,input-polldev,led-class,rfkill
vermagic:      2.6.24-26-generic SMP mod_unload
parm:          pio:enable(1) / disable(0) PIO mode (int)
parm:          bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm:          short_retry:Short-Retry-Limit (0 - 15) (int)
parm:          long_retry:Long-Retry-Limit (0 - 15) (int)
parm:          fwpostfix:Postfix for the .fw files to load. (string)
parm:          hwpctl:Enable hardware-side power control (default off) (int)
parm:          nohwcrypt:Disable hardware encryption. (int)

Kernel Version:
Code:

matt@HTPC:~$ uname -a
Linux HTPC 2.6.24-26-generic #1 SMP Tue Dec 1 17:55:03 UTC 2009 x86_64 GNU/Linux

I'm running Ubuntu Hardy Heron. According to http://linuxwireless.org/en/users/Dr...e_installation
b43 runs with 2.6.24, with older firmware.

Here's what I get from dmesg:

Code:

matt@HTPC:~$ dmesg | grep firmware
[  51.618566] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)

I'm almost certain this is my Hauppage Win-PVR card, and isn't related to wireless.

Code:

matt@HTPC:~$ dmesg | grep b43   
matt@HTPC:~$

Any solutions/ideas/guesses?

nimnull22 02-14-2010 10:46 AM

Please, do:
modprobe -r b43
modprobe b43
dmesg | tail -n 30

Post the output please.

fatman 02-14-2010 11:20 AM

Code:

matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ sudo modprobe -r b43
matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ sudo modprobe b43
matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ dmesg |  tail -n 30
[24555.285731] ACPI: PCI interrupt for device 0000:02:07.0 disabled
[24556.986072] ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKB] -> GSI 18 (level, low) -> IRQ 18
[24556.986387] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)
[24556.986396] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24556.986400] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x01, vendor 0x4243)
[24556.986403] ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
[24556.986407] ssb: Core 4 found: PCI (cc 0x804, rev 0x07, vendor 0x4243)
[24556.986410] ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24556.986412] ssb: Ignoring additional 802.11 core
[24556.988832] ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
[24580.493899] ACPI: PCI interrupt for device 0000:02:07.0 disabled
[24582.566035] ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKB] -> GSI 18 (level, low) -> IRQ 18
[24582.566127] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)
[24582.566132] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24582.566136] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x01, vendor 0x4243)
[24582.566139] ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
[24582.566143] ssb: Core 4 found: PCI (cc 0x804, rev 0x07, vendor 0x4243)
[24582.566146] ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24582.566148] ssb: Ignoring additional 802.11 core
[24582.567832] ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
[24659.152053] ACPI: PCI interrupt for device 0000:02:07.0 disabled
[24660.598252] ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKB] -> GSI 18 (level, low) -> IRQ 18
[24660.598545] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x02, vendor 0x4243)
[24660.598555] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24660.598559] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x01, vendor 0x4243)
[24660.598562] ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
[24660.598565] ssb: Core 4 found: PCI (cc 0x804, rev 0x07, vendor 0x4243)
[24660.598569] ssb: Core 5 found: IEEE 802.11 (cc 0x812, rev 0x04, vendor 0x4243)
[24660.598570] ssb: Ignoring additional 802.11 core
[24660.601005] ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$

Note that 2+ rounds of removing and re-adding the b43 module are captured here.
As I was tinkering, the add & remove starting with the [24580.493899] timestamp was an experimental try with the 2.6.25+ "newer" firmware (the b43 driver from linux-2.6.25 or newer - according to linuxwireless.org). So as to get a clean result in response to nimnull22's post, I switched back to the 2.6.24 firmware and re-cycled the b43 module (starting at timestamp [24659.152053]).

The outputs on both tries are identical - does this mean I can narrow it down to a firmware problem?

Also, supposing the b43 module and the firmware were working properly, what would I expect to see? Would I just be able to "modprobe b43" and then the interface would pop up on "iwconfig"? Or is there another step in there?

Thank you all for helping me work on this.

nimnull22 02-14-2010 02:02 PM

I have to ask you to do some searches.
Look in /var/log for any files which contain "Broadcom B43 wireless driver" or just "Broadcom" or b43.
Because "dmesg" showed nothing.

And please post output of: "ifconfig -a"

Thanks

camphor 02-14-2010 02:58 PM

Quote:

Originally Posted by fatman (Post 3863421)
Also, supposing the b43 module and the firmware were working properly, what would I expect to see? Would I just be able to "modprobe b43" and then the interface would pop up on "iwconfig"? Or is there another step in there?

Generally, that's the case. Make sure all the necessary modules are being loaded (b43 has several, iirc) and check if it is recognized with ifconfig -a.

fatman 02-14-2010 07:15 PM

As requested:

Code:

matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr:  XXXXXXX.... 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:22

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2702 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2702 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:135100 (131.9 KB)  TX bytes:135100 (131.9 KB)

matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$

I then ran:

Code:

matt@HTPC:/var/log$ grep -i broadcom /var/log/*

matt@HTPC:/var/log$ grep -i b43 /var/log/*

And got nothing but auth.log entries, which I believe are just my sudo commands. (those grep lines would have found something if it was there, right?)

And there are a bunch of other modules loading:

Code:

matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ lsmod | grep b43
b43                  159280  0
ssb                    39428  1 b43
rfkill                10144  1 b43
mac80211              192660  1 b43
led_class              7176  1 b43
input_polldev          6928  1 b43
matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$


nimnull22 02-14-2010 08:01 PM

Type it on root console "grep -i broadcom /var/log/*".
Also search for b43: "grep -i b43 /var/log/*"

minrich 02-14-2010 08:27 PM

Hi guys, what do you have in /lib/firmware? There should be a b43 directory there that contains the firmware that the b43 module uses. I just need a list of the 4 file names therein to see which version you have - perhaps you already know if you have downloaded b43-fwcutter.

fatman 02-14-2010 09:26 PM

I ran the grep searched in a root console - no change, just auth.log sudo entires.

When I ran the firmware directories, I came across another possible problem, and created another problem myself...

Here's the directory listing for 2.6.24 firmware:

Code:

matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$ sudo ls -l /lib/firmware/b43
total 128
-rw-r--r-- 1 root root  158 Feb 14 22:39 a0g0bsinitvals5.fw
-rw-r--r-- 1 root root  1858 Feb 14 22:39 a0g0initvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:39 a0g1bsinitvals13.fw
-rw-r--r-- 1 root root  158 Feb 14 22:39 a0g1bsinitvals5.fw
-rw-r--r-- 1 root root  2056 Feb 14 22:39 a0g1initvals13.fw
-rw-r--r-- 1 root root  1858 Feb 14 22:39 a0g1initvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:39 b0g0bsinitvals13.fw
-rw-r--r-- 1 root root  158 Feb 14 22:39 b0g0bsinitvals5.fw
-rw-r--r-- 1 root root  2056 Feb 14 22:39 b0g0initvals13.fw
-rw-r--r-- 1 root root  1858 Feb 14 22:39 b0g0initvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:39 lp0bsinitvals13.fw
-rw-r--r-- 1 root root  2052 Feb 14 22:39 lp0initvals13.fw
-rw-r--r-- 1 root root  1320 Feb 14 22:39 pcm5.fw
-rw-r--r-- 1 root root 26600 Feb 14 22:39 ucode11.fw
-rw-r--r-- 1 root root 24424 Feb 14 22:39 ucode13.fw
-rw-r--r-- 1 root root 22088 Feb 14 22:39 ucode5.fw
matt@HTPC:/usr/src/broadcom-wl-4.80.53.0/kmod$

Here's after my switch to the 2.6.25+ firmware:

Code:

matt@HTPC:/usr/src/broadcom-wl-4.150.10.5/driver$ sudo ls -l /lib/firmware/b43
total 284
-rw-r--r-- 1 root root  158 Feb 14 22:36 a0g0bsinitvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 a0g0bsinitvals9.fw
-rw-r--r-- 1 root root  1840 Feb 14 22:36 a0g0initvals5.fw
-rw-r--r-- 1 root root  2002 Feb 14 22:36 a0g0initvals9.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 a0g1bsinitvals13.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 a0g1bsinitvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 a0g1bsinitvals9.fw
-rw-r--r-- 1 root root  2080 Feb 14 22:36 a0g1initvals13.fw
-rw-r--r-- 1 root root  1840 Feb 14 22:36 a0g1initvals5.fw
-rw-r--r-- 1 root root  2002 Feb 14 22:36 a0g1initvals9.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 b0g0bsinitvals13.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 b0g0bsinitvals5.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 b0g0bsinitvals9.fw
-rw-r--r-- 1 root root  2080 Feb 14 22:36 b0g0initvals13.fw
-rw-r--r-- 1 root root  1840 Feb 14 22:36 b0g0initvals5.fw
-rw-r--r-- 1 root root  2002 Feb 14 22:36 b0g0initvals9.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 lp0bsinitvals13.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 lp0bsinitvals14.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 lp0bsinitvals15.fw
-rw-r--r-- 1 root root  3618 Feb 14 22:36 lp0initvals13.fw
-rw-r--r-- 1 root root  2064 Feb 14 22:36 lp0initvals14.fw
-rw-r--r-- 1 root root  2052 Feb 14 22:36 lp0initvals15.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 n0absinitvals11.fw
-rw-r--r-- 1 root root  158 Feb 14 22:36 n0bsinitvals11.fw
-rw-r--r-- 1 root root  2100 Feb 14 22:36 n0initvals11.fw
-rw-r--r-- 1 root root  1320 Feb 14 22:36 pcm5.fw
-rw-r--r-- 1 root root 29864 Feb 14 22:36 ucode11.fw
-rw-r--r-- 1 root root 32232 Feb 14 22:36 ucode13.fw
-rw-r--r-- 1 root root 31384 Feb 14 22:36 ucode14.fw
-rw-r--r-- 1 root root 30488 Feb 14 22:36 ucode15.fw
-rw-r--r-- 1 root root 22384 Feb 14 22:36 ucode5.fw
-rw-r--r-- 1 root root 25160 Feb 14 22:36 ucode9.fw
matt@HTPC:/usr/src/broadcom-wl-4.150.10.5/driver$

However, in both fw-cutter firmware installs the "/lib/firmware/b43" directory permission is set so that only root can read (or execute) it. Does the b43 module run as root? Could this be a source of the problem?

Also, when I was clearing /lib/firmware/b43 for re-install of firmware, I ran the following:

Code:

matt@HTPC:/usr/src/broadcom-wl-4.150.10.5/driver$ ls /lib/firmware
2.6.22-14-generic  2.6.22-15-generic  2.6.24-21-generic  2.6.24-24-generic  2.6.24-26-generic  b43
matt@HTPC:/usr/src/broadcom-wl-4.150.10.5/driver$ sudo rm -rf /lib/firmware

And accidentally zapped my whole firmware directory. I re-ran fw-cutter to put the b43 stuff back, but did I lose anything important in the other directories?

fatman 02-15-2010 11:19 PM

No luck on changing permissions.

Any other ideas, guesses, or even likely places to look?

minrich 02-16-2010 12:54 AM

a) I am wondering why you have a prompt address, viz. /usr/src/broadcom-wl-4.150.10.5/driver which leads me to believe that you have the wl (also known as STA) driver installed alongside the b43 driver? Do a quick 'lsmod | grep wl' to determine if the wl module is loaded.

b) What kernel version are you using? A quick 'uname -r' will give you the answer I need. I am expecting something like 2.6.31 which is buggy with respect to the broadcom drivers, and

c) Are you using encryption on your wireless? Have you tried 'open' mode i.e. unencrypted - you will have to change the settings on your router access point - is this possible?

fatman 02-16-2010 01:25 PM

lsmod | grep wl returned nothing.

uname -r returned 2.6.24-26-generic

I figured if I can't even bring up the wireless interface, the encryption settings of the router wouldn't matter. If I'm wrong, let me know and I'll try.


All times are GMT -5. The time now is 10:03 PM.