LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   Having real problems with fedora 14 and broadcom [14e4:4324] wireless card (https://www.linuxquestions.org/questions/linux-wireless-networking-41/having-real-problems-with-fedora-14-and-broadcom-%5B14e4-4324%5D-wireless-card-842665/)

lmcilwain 11-05-2010 10:47 PM

Having real problems with fedora 14 and broadcom [14e4:4324] wireless card
 
Hey guys,

Its been a while since I have decided to use linux and I am going back to what I love. However I am running to so major issues getting wireless to work on my laptop. As it seems, I think ndiswrapper has gone the way of the dinos and so I am curious as to what I can do to get things working. Here is what I have done and what I know so far.

When I go and take a look at my network connections, my wireless seems to show up but it shows that its not ready and I am missing firmware.

So here is what I have done to try and install firmware.

I have run the following command to see what kind of broadcom card I have:
Code:

lspci -vnn | grep 14e4
The response I get is:

02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet [14e4:16a6] (rev 02)
02:03.0 Network controller [0280]: Broadcom Corporation BCM4309 802.11a/b/g [14e4:4324] (rev 02)

From what I can tell, I have tried broadcom-wl and kmod-wl from the rpm repositories and neither seem to work. I have not seen any documentation that shows that either of these rpms will support my wireless card. I tend to think that they do not since after installation and reboot of each, my wireless entry in my network connections interface disappears.

Does anyone have any idea of what will work with this particular broadcom card?

Hangdog42 11-06-2010 07:44 AM

Quote:

02:03.0 Network controller [0280]: Broadcom Corporation BCM4309 802.11a/b/g [14e4:4324] (rev 02)

That is your wireless card running a 4309 chipset.

Quote:

rom what I can tell, I have tried broadcom-wl and kmod-wl from the rpm repositories and neither seem to work.
That isn't surprising. The wl/sta driver only works with 4311, 4312, 4321 and 4322 chipsets. The good news is that the b43 driver that comes with the kernel should work with a 4309.

Quote:

When I go and take a look at my network connections, my wireless seems to show up but it shows that its not ready and I am missing firmware.
That means that Fedora is trying to use the b43 driver (check in lsmod and see if it is loaded). Unfortunately, no one can distribute the firmware needed for b43 to work, so you have to install that yourself. If you check out these instructions, hopefully that will get you on the road to getting firmware installed.

lmcilwain 11-06-2010 08:47 AM

I went to the link that you posted and followed each line step by step. I rebooted my system and the wireless has disappeared from my network connections icon in the upper right (All I see is eth0). However, it shows that I have a wireless card when I go to edit my network connections.

Is there some way that it needs to be enabled or turned on or something to that effect? or is it that the firmware is still not installed?

Hangdog42 11-06-2010 09:17 AM

Quote:

However, it shows that I have a wireless card when I go to edit my network connections.
I'm really not familiar with the GUI tools Fedora uses but isn't there a way to edit your wireless card so that it is active?. As a backup, lets see what the console offers.

Do you see the wireless card in your iwconfig output?
Do you see the wireless card in you ifconfig output?

If no to both of those, is b43 showing up in lsmod?

Also, are there any wireless related error messages in your log files? And look in /lib/firmware and see if the firmware is installed there. It should be pretty obvious from the file/directories names.

lmcilwain 11-06-2010 10:03 AM

The iwconfig output shows:
lo no wireless extensions.

eth0 no wireless extensions.

The ifconfig output shows:
eth0 Link encap:Ethernet HWaddr 00:0D:56:DF:A9:2D
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20d:56ff:fedf:a92d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2042 errors:0 dropped:0 overruns:0 frame:0
TX packets:809 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:944467 (922.3 KiB) TX bytes:139074 (135.8 KiB)
Interrupt:11

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:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1584 (1.5 KiB) TX bytes:1584 (1.5 KiB)

When I type lsmod b43 is not in the listing.

when I checked dmesg I didn't see anything wireless related.

In my messages log I have the following:

Nov 6 09:38:37 theman NetworkManager[1045]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ...
Nov 6 09:38:37 theman NetworkManager[1045]: ifcfg-rh: read connection 'System lomac (wlan0)'
Nov 6 09:41:35 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0
Nov 6 09:41:35 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0
Nov 6 09:41:36 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0
Nov 6 09:41:36 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0
Nov 6 09:41:36 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0
Nov 6 09:41:36 theman NetworkManager[1045]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-wlan0

In /lib/firmware/b43 I have the following files:
a0g0bsinitvals5.fw a0g1bsinitvals9.fw b0g0bsinitvals9.fw lp0bsinitvals15.fw n0initvals11.fw ucode5.fw
a0g0bsinitvals9.fw a0g1initvals13.fw b0g0initvals13.fw lp0initvals13.fw pcm5.fw ucode9.fw
a0g0initvals5.fw a0g1initvals5.fw b0g0initvals5.fw lp0initvals14.fw ucode11.fw
a0g0initvals9.fw a0g1initvals9.fw b0g0initvals9.fw lp0initvals15.fw ucode13.fw
a0g1bsinitvals13.fw b0g0bsinitvals13.fw lp0bsinitvals13.fw n0absinitvals11.fw ucode14.fw
a0g1bsinitvals5.fw b0g0bsinitvals5.fw lp0bsinitvals14.fw n0bsinitvals11.fw ucode15.fw

Hangdog42 11-06-2010 10:32 AM

Quote:

When I type lsmod b43 is not in the listing.
Well that certainly explains the lack of a wireless device in iwconfig and ifconfig. Try loading it (modprobe b43) and see if that allows wireless to work. If nothing else, there should leave some clues in the log files after trying to load it.

lmcilwain 11-06-2010 12:24 PM

When I typed modprobe b43 and then do lsmod I do see b43 in the listing now. When I look in my network connections manager I see the same issue I had before which is "wireless device isn't ready firmware missing".

When I tail the messages log I get the following:

Nov 6 13:19:30 theman NetworkManager[1045]: <warn> (wlan0): firmware may be missing.
Nov 6 13:19:30 theman NetworkManager[1045]: <info> (wlan0): deactivating device (reason: 2).
Nov 6 13:19:30 theman kernel: [13276.375584] b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
Nov 6 13:19:30 theman kernel: [13276.375603] b43legacy-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Dr...devicefirmware and download the correct firmware (version 3).
Nov 6 13:19:30 theman NetworkManager[1045]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1e.0/0000:02:03.0/ssb0:0/ieee80211/phy0/rfkill0) (driver <unknown>)

Hangdog42 11-06-2010 04:54 PM

Quote:

b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
Hmm. Looks like the 4309 is trying to use b43legacy, not b43. That's OK, but you do need different firmware. Have a look at these instructions for a link to version 3 firmware. The process is a lot like what you've already done, but it should create /lib/fimrware/b43legacy and the firmware files will be slightly different.

lmcilwain 11-07-2010 12:25 AM

outstanding. that is exactly what I needed. Thank you for all of your patience and effort in getting me up and running with my wireless..

lmcilwain 11-07-2010 01:19 AM

Hmm I guess I have one more minor issue which is, I can't seem to get this to load on reboot. It looks like /etc/modprobe.conf no longer exists and I have seen places where they say to create a local.conf file in the /etc/modprobe.d/ directory. I have tried both and rebooted but neither will work. I am going to try the /etc/modprobe.d/network.conf and see if that is where it needs to be but I am curious as to what I may be doing wrong.

The command I am using is:
echo alias wlan0 b43 >> /etc/modprobe.d/local.conf
or should it be...
echo alias wlan0 b43legacy >> /etc/modprobe.d/local.conf

lmcilwain 11-07-2010 01:42 AM

OK nevermind, I guess adding "modprobe b43" to /etc/rc.local seems to do the trick. Though I wonder why I couldn't find the modprobe file I needed.

Hangdog42 11-07-2010 06:47 AM

Congrats on getting it to work!

Quote:

OK nevermind, I guess adding "modprobe b43" to /etc/rc.local seems to do the trick. Though I wonder why I couldn't find the modprobe file I needed.
That certainly will work, although I would think there would be some way to load it earlier in the process so that the normal network boot processes can function with b43 in place. I'm just not familiar enough with the guts of Fedora, so maybe this would be worth starting a thread in the Fedora forum to see if there is a better way.

glorsplitz 11-15-2010 07:12 PM

hangdog if you're still there
 
Yes I know I'm hijacking but I thought this might help others using the slackbuilds.

Maybe you can answer quick question please.

I installed b43 on my thinkpad long time ago another way.

Just got b43-firmware, b43-fwcutter from slackbuilds for 13.1.

Installed b43-fwcutter then b43-firmware and the card works.

Question is, not sure what I did, I was expecting to use fwcutter to install the firmware, something did, what?

Thanks

Hangdog42 11-16-2010 07:17 AM

Quote:

Originally Posted by glorsplitz
Question is, not sure what I did, I was expecting to use fwcutter to install the firmware, something did, what?

That is actually a very good question. If you look in the b43-firmware Slackbuild, you'll see this:

Code:

tar xvf $CWD/broadcom-wl-$TARBALL_VERSION.tar.bz2
chown -R root:root broadcom-wl-$TARBALL_VERSION
mkdir -p $PKG/lib/firmware
b43-fwcutter \
  -w $PKG/lib/firmware \
  broadcom-wl-$TARBALL_VERSION/linux/wl_apsta.o
chmod 0755 $PKG/lib/firmware/b43

Which I think is using fwcutter to extract the firmware for you. That is likely the reason b43-fwcutter is a prerequisite for b43-firmware.

glorsplitz 11-17-2010 08:14 AM

oops, I'm sure I was getting around to looking at b43-firmware Slackbuild
 
thanks hangdog42

as I said I did this a while back by hand from b43 web site probably for slackware 12.2 but I found the slackbuilds and really wanted to use those, amazingly simple!


All times are GMT -5. The time now is 06:26 AM.