Wireless Not Working, openSUSE 11, HP 2133, Broadcom WLAN

English Network/Internet
#1

Greetings all and hello to the community.

I’ve been trying for the past 10 days or so to get my Broadcom WLAN card to work in Linux. I’ve been through multiple flavors and distributions and am currently working with openSUSE 11.

As a bit more hardware background, the laptop in question is an HP Mini-Note 2133 with a VIA 1.2GHz processor and 2GB of RAM. I’m a complete newbie when it comes to Linux, but I already know how to go between the GUI (I’m using GNOME at the moment) and a terminal, I have root level access, and know how to get around to different utilities in each. I’m running NetworkManager Applet 0.7.0 and I’ve read through other threads about getting “ndiswrapper” installed, which I’ve done. I’ve also configured it to use the bmcwl6.inf file that is the driver for Windows Vista. I know that the device should be wlan0, but I don’t see where that gets configured. When I run “ifconfig,” the interface doesn’t even show up. Here are some various commands I’ve tried to get more information about this problem:

# iwlist wlan0 scan
wlan0     Interface doesn't support scanning : Network is down

# uname -r
2.6.25.5-1.1-default

# lspci -v ***(truncated to display only the wireless card information)***
02:00.0 Network controller: Broadcom Corporation BCM4312 801.11a/b/g (rev 02)
        Subsystem: Hewlett-Packard Company Device 1370
        Flags: bus master, fast devsel, latency 0, IRQ 24
        Memory at fdffc000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information <?>
        Capabilities: [e8] Message Signaled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
        Capabilities: [d0] Express Endpoint, MSI 00
        Kernel driver in use: b43-pci-bridge
        Kernel modules: ssb

# ndiswrapper -l
bcmw16 : driver installed
        device (14e4:4312) present (alternate driver: ssb)

One (possibly incorrect) tangent I was on was editting the /etc/X11/xorg.conf file to add devices, back in Fedora 9 where I couldn’t get GNOME to work. Now that it does, I’m leary about editting xorg.conf any more than I have to, but for the life of me I can’t figure out where wlan0 is specified as a device.

Can anybody in the community shed some light on where I need to go next? I have a wired connection that works well, so if I have to download anything or get new repositories or whatever, I can.

Thanks in advance for your support in this regard.

  • Will “PaleGringo” Bowlin[/size]
#2

PaleGringo wrote:
> Greetings all and hello to the community.
>
> I’ve been trying for the past 10 days or so to get my Broadcom WLAN
> card to work in Linux. I’ve been through multiple flavors and
> distributions and am currently working with openSUSE 11.
>
> As a bit more hardware background, the laptop in question is an HP
> Mini-Note 2133 with a VIA 1.2GHz processor and 2GB of RAM. I’m a
> complete newbie when it comes to Linux, but I already know how to go
> between the GUI (I’m using GNOME at the moment) and a terminal, I have
> root level access, and know how to get around to different utilities in
> each. I’m running NetworkManager Applet 0.7.0 and I’ve read through
> other threads about getting “ndiswrapper” installed, which I’ve done.
> I’ve also configured it to use the -bmcwl6.inf- file that is the driver
> for Windows Vista. I know that the device -should be- wlan0, but I
> don’t see where that gets configured. When I run “-ifconfig-,” the
> interface doesn’t even show up. Here are some various commands I’ve
> tried to get more information about this problem:
>
>
> Code:
> --------------------
> # iwlist wlan0 scan
> wlan0 Interface doesn’t support scanning : Network is down
>
> # uname -r
> 2.6.25.5-1.1-default
>
> # lspci -v -(truncated to display only the wireless card information)-
> 02:00.0 Network controller: Broadcom Corporation BCM4312 801.11a/b/g (rev 02)
> Subsystem: Hewlett-Packard Company Device 1370
> Flags: bus master, fast devsel, latency 0, IRQ 24
> Memory at fdffc000 (64-bit, non-prefetchable) [size=16]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information <?>
> Capabilities: [e8] Message Signaled Interrupts: Mask- 64bit+ Queue=0/3 Enable-
> Capabilities: [d0] Express Endpoint, MSI 00
> Kernel driver in use: b43-pci-bridge
> Kernel modules: ssb
>
> # ndiswrapper -l
> bcmw16 : driver installed
> device (14e4:4312) present (alternate driver: ssb)
>
> --------------------
>
>
> One (possibly incorrect) tangent I was on was editting the
> -/etc/X11/xorg.conf- file to add devices, back in Fedora 9 where I
> couldn’t get GNOME to work. Now that it does, I’m leary about editting
> xorg.conf any more than I have to, but for the life of me I can’t figure
> out where wlan0 is specified as a device.
>
> Can anybody in the community shed some light on where I need to go
> next? I have a wired connection that works well, so if I have to
> download anything or get new repositories or whatever, I can.
>
> Thanks in advance for your support in this regard.

The BCM4312 works with 11.0 using the b43 driver. In fact, I’m using one now.

The bottom line with the native driver on Linux is that you need to install the
firmware. It is not distributed by anyone due to the restrictions of Broadcom.
Because you have network access while in Linux, you should open a terminal and
enter the following command:

sudo /usr/sbin/install_bcm43xx_firmware

This will install the necessary firmware. If you have blacklisted any drivers to
try to get ndiswrapper installed, reverse those changes.

To configure the wireless device, you should use YaST. Select Network Devices /
Network Settings. Your wireless device will likely show up there, but add it if
not. My preference is to use NetworkManager (selected in the global tab). Once
you have added the device there and finished, click on the KNetworkManager icon,
select “Edit Connections” and add a wireless connection.

If your laptop has a wifi kill switch, please be certain that the switch is on.

If you have any problems, please post the output of “dmesg | grep b43”.
[/size]

#3

Thank you for the direct and prompt suggestion, lwfinger. I ran that command while hooked up to a wired connection and got the “b43 firmware successfully installed” message.

I went into YaST and then to Network Settings, Clicked “Remove” on the currently installed Broadcom card, and lo and behold… it started working flawlessly. I don’t know if there’s a way I can deify you, but you are a Linux-god as far as I’m concerned. Very amazing, and thank you infinitely for the help!

#4

PaleGringo wrote:
> Thank you for the direct and prompt suggestion, lwfinger. I ran that
> command while hooked up to a wired connection and got the “b43 firmware
> successfully installed” message.
>
> I went into YaST and then to Network Settings, Clicked “Remove” on the
> currently installed Broadcom card, and lo and behold… it started
> working -flawlessly-. I don’t know if there’s a way I can deify you,
> but you are a Linux-god as far as I’m concerned. Very amazing, and
> thank you infinitely for the help!

You are very welcome. I’m not a god, but I do know my way around the bcm43xx
software. I am a member of the team that developed that driver. My part was
minor, but I did get the BCM4311/1 and BCM4311/2 devices working for the first
time. At the moment, I’m working on reverse-engineering the BCM4310 USB (so
called) device that is PCI, not USB, and has a new 802.11 core.

#5

Thank you verrry much for your clear and concise answer to this gentleman’s question. I have been struggling for about 4 months and trying at least 6 different ‘distros’ of linux until finally settling on Opensuse 11.0. With the final release of version 11.0 I was able to get everything working on my HP DV9000 notebook with the exception of the B4312 wireless unit. Your few, but essential instructions took me over the top. Thanks again!! JBL

#6

Thanks from me too. Ive been trying to get broadcom wireless working on a hp laptop for quite a long time, and youre instructions are the first time ive gotten it working with about 8 different distros.

Thanks, o lord of broadcom wireless.

#7

Asus G1S-B1 (C2D T7700 @ 2.4) w/ Intel 4965. WiFi connects fine when 10.3 is booted. Checked 11.0 WiFi compatability using fresh (just DLd ~1 hour ago) Live CD {86-x64}, noted strength much less, was able to just select the network & connected OK in a few moments.

After installing 11.0 am unable to connect as the broadcast signal detected is now too low! While 10.3 still has almost 100% strength, automatically connected.
I am a bit confused as all hardware is the same & works fine w/ 10.3

#8

Uh, can anyone provide help for me…I’m running a completely wi-fi network and the PC I want to run openSuse on does not have access to an ethernet connection within 100ft. Is there a package I can download to a USB drive on another PC and hook it up to my openSuse box to install? By the way, this problem is unique to openSuse as I’ve run without any issues Ubuntu and Fedora via wifi.

#9

@blueflyt
could you please start a new topic,tacking on the end of one already started probably won’t garner the responses you require. Also, have a look at the stickies at the start of the wireless section, plenty of good info there

Andy

#10

I have exactly same issue to which you provide the solution. But I am unable to start my wireless with your solution, neither I have any output for “dmesg |grep b43”[/size]

#11

I have exactly same issue to which you provide the solution. But I am unable to start my wireless with your solution, neither I have any output for “dmesg |grep b43”
if that’s what you get,then either you haven’t installed the drivers/firmware,or your device doesn’t have the broadcom chipset. post the output of /sbin/lspci -v from a console

Andy

#12

hi
HP2133 suse 11, have uploaded firmware, seemed to work but I only see the ethernet controller in Network settings. Any ideas?

Any help much appreciated.

#13

neillricketts wrote:
> hi
> HP2133 suse 11, have uploaded firmware, seemed to work but I only see
> the ethernet controller in Network settings. Any ideas?

Post the output of the command ‘dmesg | grep b43’. If that provides no output,
then try ‘dmesg | grep ssb’.

Larry

#14

cheers Larry,

Nothing from the dmesg

linux-8qw2:/ # sudo /usr/sbin/install_bcm43xx_firmware
Downloading b43 firmware
######################################################################## 100.0%
Extracting b43 firmware
This file is recognised as:
ID : FW13
filename : wl_apsta_mimo.o
version : 410.2160
MD5 : cb8d70972b885b1f8883b943c0261a3c
Extracting b43/pcm5.fw
Extracting b43/pcm4.fw
Extracting b43/ucode15.fw
Extracting b43/ucode14.fw
Extracting b43/ucode13.fw
Extracting b43/ucode11.fw
Extracting b43/ucode9.fw
Extracting b43/ucode5.fw
Extracting b43/ucode4.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/lp0initvals15.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/lp0initvals14.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/lp0initvals13.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/n0initvals11.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/a0g0bsinitvals4.fw
Extracting b43/a0g0initvals4.fw
Extracting b43/b0g0bsinitvals4.fw
Extracting b43/b0g0initvals4.fw

Downloading b43legacy firmware
######################################################################## 100.0%
Extracting b43legacy firmware
This file is recognised as:
ID : FW10
filename : wl_apsta.o
version : 295.14
MD5 : e08665c5c5b66beb9c3b2dd54aa80cb3
Extracting b43legacy/ucode2.fw
Extracting b43legacy/ucode4.fw
Extracting b43legacy/ucode5.fw
Extracting b43legacy/ucode11.fw
Extracting b43legacy/pcm4.fw
Extracting b43legacy/pcm5.fw
Extracting b43legacy/a0g0bsinitvals2.fw
Extracting b43legacy/b0g0bsinitvals5.fw
Extracting b43legacy/a0g0initvals5.fw
Extracting b43legacy/a0g1bsinitvals5.fw
Extracting b43legacy/a0g0initvals2.fw
Extracting b43legacy/a0g1initvals5.fw
Extracting b43legacy/b0g0bsinitvals2.fw
Extracting b43legacy/b0g0initvals5.fw
Extracting b43legacy/b0g0initvals2.fw
Extracting b43legacy/a0g0bsinitvals5.fw

b43 firmware successfully installed.
b43legacy firmware successfully installed.
linux-8qw2:/ #
linux-8qw2:/ # dmesg | grep b43
linux-8qw2:/ # dmesg | grep ssb
linux-8qw2:/ #

#15

neillricketts wrote:
> cheers Larry,
>
>
>
> Nothing from the dmesg

That means that your Broadcom device is neither supported nor recognized by the
driver. What does ‘/sbin/lspci -nnv’ have to say about your BCM43XX?

Larry

#16

linux-8qw2:/home/neillricketts # lspci -nn
00:00.0 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:0364]
00:00.1 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:1364]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:2364]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:3364]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:4364]
00:00.5 PIC [0800]: VIA Technologies, Inc. P4M900 I/O APIC Interrupt Controller [1106:5364]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. P4M900 Security Device [1106:6364]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. P4M900 Host Bridge [1106:7364]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI Bridge [1106:b198]
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller [1106:a364] (rev 80)
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller [1106:c364] (rev 80)
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. Device [1106:5372]
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237S PCI to ISA Bridge [1106:3372]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VT8251 Ultra VLINK Controller [1106:287e]
00:13.0 Host bridge [0600]: VIA Technologies, Inc. VT8237A Host Bridge [1106:337b]
00:13.1 PCI bridge [0604]: VIA Technologies, Inc. VT8237A PCI to PCI Bridge [1106:337a]
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. Chrome9 HC IGP [1106:3371] (rev 01)
02:00.0 Network controller [0280]: Broadcom Corporation BCM4310 USB Controller [14e4:4315] (rev 01)
07:03.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet [14e4:169c] (rev 03)
80:01.0 Audio device [0403]: VIA Technologies, Inc. VIA High Definition Audio Controller [1106:3288] (rev 10)

Many thanks for the help,

#17

neillricketts wrote:
> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4310 USB
> Controller [14e4:4315] (rev 01)

That one is not supported by the b43 driver. Your options are using the Broadcom
hybrid driver, or ndiswrapper with the Windows driver. Both options have
drawbacks. Please check the other postings in this forum for pointers to each,
and the problems.

Larry

#18

Thanks for your help Larry, much appreciated.

Just my luck!!

Life is nothing if not interesting. Funny thing is worked out of the box with 10.3

#19

Larry

I am using a HP2133 same as the other guys, it should be a BCM4312 (sticker on the bottom), any ideas? Should be the same as the others? Why does it show up as a USB device?

#20

neillricketts wrote:

> I am using a HP2133 same as the other guys, it should be a BCM4312
> (sticker on the bottom), any ideas? Should be the same as the others?

There have been some reports of two different devices that are called BCM4312.
One has a PCI ID of 0x4312 and works with b43. If the PCI ID is 0x4315, then it
doesn’t.

> Why does it show up as a USB device?

Good question. That is programmed (by Broadcom) in the device string. The fact
that it shows up in the lspci, not lsusb, output shows that it is a PCI device.
Many of the Broadcom devices have both PCI and USB cores, with the USB one not
connected. Perhaps they put this sting in to indicate that this one has such an
inactive core.

If your device worked with 10.3, then you had to be using ndiswrapper. With a
2.6.22 kernel (the one found in that version), even a BCM4312 wouldn’t have
worked with the bcm43xx driver.

Larry