F14 Broadcom wireless problem

Raymond001 · #1 18th November 2010, 02:49 AM

I have a Lenovo N500 which I had to use acpi=off to install F14. Uses the PAE kernel.

Ethernet works. The wireless does not work. It is a Broadcom BCM4312. Worked under F13. Works runing Puppy 5.1.1 from a cd - uses the Broadcom B43 Wireless Driver on the PCMCIA bus. Used the same procedure for F14 that I used for F13. Shows up as disconnected under the wireless icon in the top panel, but no networks show up and no wifi light on the PC. The Network Configuration shows status - inactive, device - wlan0, nickname - wlan0, type - wireless.

Looked a the following but still can not get it to work.
http://forums.fedoraforum.org/showthread.php?t=254506
http://forums.fedoraforum.org/showthread.php?t=239922
and
http://www.linuxwireless.org/

Could it have something to do with acpi=off?

Experience/knowledge is still a newbie.
If you need more information, please tell me what to do to post it here.
Hopefully someone could tell me what I missed, doing wrong, or to try.
Thanks.

magnusk · #2 18th November 2010, 05:13 AM

Have you added RPM Fusion http://rpmfusion.org/ and installed kmod-wl or akmod-wl? If you choose akmod-wl and have PAE-kernel you also have to install the kernel-PAE-devel package.

Breeze · #3 18th November 2010, 05:27 AM

http://fedoramobile.org/fc-wireless/...nux-sta-driver

bbfuller · #4 18th November 2010, 10:17 AM

Hello Raymond001

There are two ways of controlling a broadcom 4312. There is the open source b43 that you appear to have used successfully in Puppy and the broadcom-wl driver that others have mentioned here.

The b43 is known to not work with some variants of the 4312, but that shouldn't be the case if it worked OK on Puppy.

In Fedora you have to install some firmware for the b43 driver using an already installed program called b43-fwcutter.

The actual firmware is not "free" and therefore doesn't get installed as standard in Fedora. I can't say if it is included by default in Puppy.

It's also complicated by the fact that there are several different firmware packages that can be downloaded depending on the kernel you are using.

If any of that appears to apply to your situation and you are still pursuing b43, post back and we can talk again.

Raymond001 · #5 19th November 2010, 04:58 AM

Thanks for your suggestions.

The Kernel is 2.6.35.6-48.fc14.i686.PAE

The procedure I used in F13 and used in F14:

Install the RPM Fusion repositories.
'yum install b43-fwcutter'. This got me from 'firmware missing' to 'disconnected' status.
yum install broadcom-wl
yum install wl-kmod
yum install kmod-wl-PAE

I have tried some of the procedures from the links above but so far no luck.
I will try some more variations and see what happens.

bbfuller · #6 19th November 2010, 09:43 AM

Hello Raymond001

Just to clear up a few points.

b43-fwcutter is as far as I am aware a part of a standard installation. It is for my F14 installs from the KDE Live CD and from the DVD. For me, it doesn't need installing. I suppose it might be different from one of the other Live CD's.

However, it does not provide any wireless firmware, just the ability to cut it from a proprietary Broadcom package and install the resulting files in /lib/firmware/b43.

If you were to look in that folder now, you would probably see three files. Those are thanks to the efforts of a group of developers to provide some free firmware. Those files work with a limited range of broadcom cards.

If you intend to use the b43 driver then you need to download an extra file from a third party source. I'll look it up if you need it, then issue a command like:

Code:

b43-fwcutter -w /lib/firmware <path and filename of downloaded file>

Without that step b43-fwcutter does nothing.

Then the b43 driver works with a greater range of cards, but still not all.

When you install the broadcom-wl driver the b43 driver should automatically duck out of the way and all of the b43 bits are superfluous, though won't do any harm.

The broadcom-wl driver consists of three components. If you are connected to the internet when you try to run:

Code:

yum install kmod-wl-PAE

It should bring in all three. This example shows the files from when I did it on Fedora 12:

Quote:

kmod-wl-PAE-5.10.91.9.3-3.fc12.6.i686.rpm
kmod-wl-2.6.31.5-127.fc12.i686.PAE-5.10.91.9.3-3.fc12.6.i686.rpm
broadcom-wl-5.10.91.9.3-1.fc12.noarch.rpm

If you are trying to install without the internet on that machine then you need to download the three equivalent files for F14 and from within the folder where you have stored those - and no other rpm files - issue the command:

Code:

rpm -ivh *.rpm

You need to check several things now. Which driver is loading, in a terminal use:

Code:

lsmod | grep b43

and:

Code:

lsmod | grep wl

only one of those should return results.

Also run:

Code:

yum list installed | grep wl

to see how many of the wl components are installed.

If you would care to copy and paste back the results of those we can think again.

Raymond001 · #7 21st November 2010, 01:23 AM

So after trying different things from the this thread and site and other sites still can't get passed the 'disconnected' status for the wireless. Still wonder if it has something to do with the 'acpi=off' param that I had to install F14 with.

This is my latest attempt.
This is where my system is now:

Did a fresh install of F14 with the 'acpi=off' parameter. Installed the Fedora and Fedora update repositories during the install. (the wired connection works)
Kernel 2.6.35.6-48.fc14.i686.pae
Panel icon - Wireless status 'device not ready (firmware missing)'. Enable wireless is checked. Nothing shows up under 'network connections'
Network Configuration - status - inactive, device - wlan0, nick - wlan0, type - wireless

installed RPM fusion repositories.

yum install b43-fwcutter
Package b43-fwcutter-013-2.fc14.i686 already installed and latest version

dmesg|grep b43
[ 10.453536] b43-pci-bridge 0000:04:00.0: PCI->APIC IRQ transform: INT A -> IRQ 18
[ 10.453555] b43-pci-bridge 0000:04:00.0: setting latency timer to 64
[ 12.323543] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 12.815944] Registered led device: b43-phy0::tx
[ 12.815963] Registered led device: b43-phy0::rx
[ 12.815984] Registered led device: b43-phy0::radio
[ 22.015987] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[ 22.015992] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[ 22.015994] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

wget http://downloads.openwrt.org/sources...0.10.5.tar.bz2
tar xjf broadcom-wl-4.150.10.5.tar.bz2
cd broadcom-wl-4.150.10.5/driver
b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o
service NetworkManager restart

Panel icon - Wireless status 'wireless is disabled'. Enable wireless is grayed out and unchecked. Nothing shows up under 'network connections'
Network Configuration - status - inactive, device - wlan0, nick - wlan0, type - wireless

yum install kmod-wl-PAE
reboot

Panel icon - Wireless status 'disconnected'. Enable wireless is checked. Nothing shows up under 'network connections'.
Network Configuration - status - inactive, device - wlan0, nick - wlan0, type - wireless
Wireless light on the pc is off. The physical switch for the wireless is on.

----- nothing I have tried will get rid of the 'disconnected' status. No wireless networks show up -----

output from some commands:

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:off
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller
02:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller
02:00.3 System peripheral: JMicron Technology Corp. MS Host Controller
04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
07:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express (rev 02)

installed lshw
lshw -C network
*-network
description: Wireless interface
product: BCM4312 802.11b/g LP-PHY
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:04:00.0
logical name: wlan0
version: 01
serial: 00:21:00:9e:30:6f
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=wl0 driverversion=5.60.48.36 latency=0 multicast=yes wireless=IEEE 802.11bg
resources: irq:18 memory:f4700000-f4703fff
*-network
description: Ethernet interface
product: NetLink BCM5906M Fast Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:07:00.0
logical name: eth0
version: 02
serial: 00:23:5a:17:04:01
size: 100MB/s
capacity: 100MB/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.110 duplex=full firmware=sb v3.04 ip=192.168.1.108 latency=0 link=yes multicast=yes port=twisted pair speed=100MB/s
resources: irq:48 memory:f4600000-f460ffff

ifconfig wlan0 up
--- returns nothing ---

iwlist wlan0 scan
wlan0 Failed to read scan data : Invalid argument

lsmod | grep b43
--- returns nothing ---

lsmod | grep wl
wl 1954536 0
lib80211 4107 2 lib80211_crypt_tkip,wl

yum list installed | grep wl
broadcom-wl.noarch 5.60.48.36-1.fc13
iwl1000-firmware.noarch
iwl3945-firmware.noarch
iwl4965-firmware.noarch
iwl5000-firmware.noarch
iwl5150-firmware.noarch
iwl6000-firmware.noarch
iwl6050-firmware.noarch
kmod-wl-2.6.35.6-48.fc14.i686.PAE.i686
kmod-wl-PAE.i686 5.60.48.36-2.fc14.2
python-iwlib.i686 0.1-3.fc14 @anaconda-InstallationRepo-201010211814.i386

bbfuller · #8 21st November 2010, 10:24 AM

Hello Raymond001

Your output from lspci:

Quote:

04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

is interesting. The b43 site used to mention a difficulty with "LP-PHY" but I can't see the reference now. They do say however:

Quote:

14e4:4312 not supported - ID is duplicated BCM4312 b/g

which is yours! They do say that the version supported is identified in exactly the same way except for "a/b/g" in place of "b/g".

I guess that about wraps it up for the b43 driver and your card.

As to the broadcom-wl driver, it's odd that it is going as far as identifying a "wlan0" interface in "iwconfig" and not in NetworkManager. I assume that iwconfig output is after the broadcom-wl driver is installed?

Try these two commands and see if we can trap any error messages as the driver loads:

Code:

dmesg | grep wl

Code:

dmesg | grep wlan0

Though the latter should only give a subset of the former.

buffalosolja42 · #9 21st November 2010, 04:16 PM

I am having problems as well and I have tried all above now not seeing wireless at all, did say missing firmware now it doesn't see wireless. My kernel version is 2.6.35.6-48. fc14.i686 using broadcom bcm 4312 rev.1 on dell inspiron if anyone can help will be much appreciated.

bbfuller · #10 21st November 2010, 05:16 PM

Hello buffalosolja42

You'll see what I said to Raymond001 in the post above this.

You need to run:

Code:

lspci

to determine which version of the 4312 you have and then tell us what steps you have taken so far.

That way we may be able to decide what to do next.

buffalosolja42 · #11 21st November 2010, 06:30 PM

Broadcom Corporation BCM4312 802.11/bg LP-PHY (Rev 01)

Raymond001 · #12 21st November 2010, 08:16 PM

Quote:

Originally Posted by bbfuller

Hello Raymond001

Your output from lspci:

is interesting. The b43 site used to mention a difficulty with "LP-PHY" but I can't see the reference now. They do say however:

which is yours! They do say that the version supported is identified in exactly the same way except for "a/b/g" in place of "b/g".

I guess that about wraps it up for the b43 driver and your card.

As to the broadcom-wl driver, it's odd that it is going as far as identifying a "wlan0" interface in "iwconfig" and not in NetworkManager. I assume that iwconfig output is after the broadcom-wl driver is installed?

Try these two commands and see if we can trap any error messages as the driver loads:

Code:

dmesg | grep wl

Code:

dmesg | grep wlan0

Though the latter should only give a subset of the former.

Yes, the iwconfig output is after the broadcom-wl driver is installed.

I have used F12 and F13 on this PC and the wireless worked. But neither F12 or F13 I had to install with the 'acpi=off' parameter. And the wireless works with Puppy 5.1.1 (as noted above). But if for some reason it is not supported now I guess that I will have to find something else to run on this PC.

Also interesting is that I also installed F14 on a Dell E6400 laptop (without acpi=off) with the same card and the wireless works.

dmesg | grep wl
[ 11.318542] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.338975] wl 0000:04:00.0: PCI->APIC IRQ transform: INT A -> IRQ 18
[ 11.338990] wl 0000:04:00.0: setting latency timer to 64
[ 11.603488] udev[349]: renamed network interface eth1 to wlan0
[ 32.253508] wlan0: no IPv6 routers present

dmesg | grep wlan0
[ 11.603488] udev[349]: renamed network interface eth1 to wlan0
[ 32.253508] wlan0: no IPv6 routers present

Thanks for your help. If you think of anything else please post it here.

bbfuller · #13 21st November 2010, 08:28 PM

Hello buffalosolja42

As you will see from my post #8, that card appears not to work with the b43 driver.

That means you will need to install the broadcom-wl driver. It will be interesting to see if you have more luck with this card than Raymond001.

I did ask you if you have taken any steps to install the wireless parts for your car but you didn't answer. I do need to know that and also what kernel your system is using.

When you post back, please also include the output from:

Code:

uname -r

---------- Post added at 08:28 PM GMT ---------- Previous post was at 08:25 PM GMT ----------

Hello Raymond001

I'm still a little surprised that if "iwconfig" lists as wireless interface that you see it nowhere else.

I assume that you are using NetworkManager by the clock on the panel and not any other form of controlling the card. Any network configuration options off the menus can have odd interactions with NetworkManager.

Are you using Gnome or KDE?

Raymond001 · #14 21st November 2010, 11:55 PM

NetworkManager Applet 0.8.1

system-config-network 1.6.1

Gnome 2.32.0

Kernel 2.6.35.6-48.fc14.i686.pae

buffalosolja42 · #15 22nd November 2010, 02:01 AM

says: " lo no wireless extensions.

eth0 no wireless extensions?

Quote:

Originally Posted by Raymond001

Yes, the iwconfig output is after the broadcom-wl driver is installed.

I have used F12 and F13 on this PC and the wireless worked. But neither F12 or F13 I had to install with the 'acpi=off' parameter. And the wireless works with Puppy 5.1.1 (as noted above). But if for some reason it is not supported now I guess that I will have to find something else to run on this PC.

Also interesting is that I also installed F14 on a Dell E6400 laptop (without acpi=off) with the same card and the wireless works.

dmesg | grep wl
[ 11.318542] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.338975] wl 0000:04:00.0: PCI->APIC IRQ transform: INT A -> IRQ 18
[ 11.338990] wl 0000:04:00.0: setting latency timer to 64
[ 11.603488] udev[349]: renamed network interface eth1 to wlan0
[ 32.253508] wlan0: no IPv6 routers present

dmesg | grep wlan0
[ 11.603488] udev[349]: renamed network interface eth1 to wlan0
[ 32.253508] wlan0: no IPv6 routers present

Thanks for your help. If you think of anything else please post it here.