Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora Resources > Guides & Solutions (No Questions)
FedoraForum Search

Forgot Password? Join Us!

Guides & Solutions (No Questions) Post your guides here (No links to Blogs accepted). You can also append your comments/questions to a guide, but don't start a new thread to ask a question. Use another forum for that.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 9th January 2007, 09:50 PM
beissemj Offline
Registered User
 
Join Date: Jan 2007
Posts: 43
Troubleshooting native bcm43xx driver (FC6)

Updated: 9 Jan '07
There is nothing ppc specific here

This thread is not for ndiswrapper questions/problems.

Q. Do I have to update my kernel?
A. As long as you are using at least 2.6.18.1 then no.
To check your kernel do:
Code:
#uname -r
Q. Are all broadcom bcm43xx cards the same?
A. No. All cards are not the same, and in fact it is very important to identify which revision you have, as this will directly determine your success with the drivers. No one can help you if you don't specify what card version you have.

To find out what card version you have:
Code:
#lspci | grep -i bcm43

0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Q. What cards aren't fully supported?
A.
  • If you have 432x and 433x cards (N PHY cards), then you are out of luck because the devel's haven't even started on them yet.
  • 4320 is actually a 4306 in Master which also is not supported due to a SoftMAC issue.
  • 4309 cards are not supported at the time due to issues with the A PHY.
  • 4311 or 4312 work but only under 2.6.18.1 and requires a kernel
    patch. (Patching a kernel is not difficult and there is a great how-to here)
  • 4318 has sometimes has transmission power problems, but does work.
Q. My card is supported, now what?
A. You need to find drivers for your card. If you have Windows installed you probably already have the files that you need. Do a search for bcmwl5.inf or bcmwl564.inf and open it up in a text editor.
If you see something like
Code:
DriverVer=10/20/2004, 3.70.22.0
then you may be in luck. Check your version against the ones listed in /usr/share/doc/bcm43xx-fwcutter-005/README (or similar). If you don't find a match then try to find a version that is relatively close to the one that you have. (The README, provides many links.)

Q. I don't have Windows installed, my driver isn't on the list, I use OS X, what do I do?
A. Again consult the readme.

Q. I have a correct driver, now what?
A. You need to extract the firmware from it
Code:
 #bcm43xx-fwcutter -w /lib/firmware bcmwl5.sys
(or similar)
and have Network Manger automatically connect to your wireless and wired connections.
Code:
#chkconfig --level 345 NetworkManager on
#chkconfig --level 345 NetworkManagerDispatcher on
#service NetworkManager start ; service NetworkManagerDispatcher start
Q. iwconfig shows my card, but I can't connect to my network. Why not?
A. Your router must be setup to allow wireless 'b' connections as that is the only mode the driver works in. Check the channel of your router; 1 or 11 is good. Also don't try to get everything working at 1 time if you are using WEP/WPA. Make sure you can connect without encryption first.

Q. iwconfig does not show my card. Why not?
A. That's a tough one. Make sure that you have a line like alias eth1 bcm43xx in your /etc/modprobe.conf. If that doesn't help try unloading the module then loading the module and bringing up the device.
Code:
#modprobe -r bcm43xx && modprobe -v bcm43xx && ifup eth1
Q. I have 64 Gigs of Ram installed and my computer freezes up when I boot.
A. That actually means the driver is working, because it is not designed to work with more than 1 Gig of Ram. To restrict the RAM to 1 GB (and remove any possibility of a DMA problem) add mem=1024M to the kernel load line.

Q. What's that stuff in dmesg mean about the core's?
Code:
0: Chip Common Core - Contains information about the device and which cores are in here (Enabled to get info)
1: 802.11 Core - Wireless (Not enabled yet)
2: V.90 Core - Modem (Never enabled, we don't even have a driver to write specs for, and it's a win-modem anyway)
3: PCMCIA Core - Disabled, not in use (usually the PCI core is used even on PCMCIA Cards)
4: PCI Core - Enabled, that's how you're using the card
See here for more information.

Q. What do I need to have enabled in my kernel for the bcm43xx driver to work?
Code:
Networking --> 
     <M>   Generic IEEE 802.11 Networking Stack
     [x]    Enable full debugging output 
     <M>     IEEE 802.11 WEP encryption (802.1x) 
     <M>     IEEE 802.11i CCMP support 
     <M>     IEEE 802.11i TKIP encryption
     <M>     Software MAC add-on to the IEEE 802.11 networking stack
     [x]      Enable full debugging output
Device Drivers --> Network device support --> Wireless LAN drivers (non-hamradio) &
Wireless Extensions
     <M>   Broadcom BCM43xx wireless support
     [x]     Broadcom BCM43xx debugging (RECOMMENDED)

Last edited by beissemj; 9th January 2007 at 11:44 PM.
Reply With Quote
Reply

Tags
bcm43xx, driver, fc6, native, troubleshooting

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
ndiswrapper or native driver? sebelk Servers & Networking 3 25th February 2010 03:36 AM
How to use native bcm43xx support for Broadcom BCM4318 [AirForce One 54g] in FC5 smfinley Guides & Solutions (No Questions) 131 15th October 2007 01:51 PM
FC 6 native bcm43xx with wpa_supplicant working. kubus007 Guides & Solutions (No Questions) 0 4th August 2007 09:20 PM
Broadcom working with native support (bcm43xx)! Now... question about ifup... jacksmash Hardware & Laptops 5 15th March 2007 01:43 PM
Does native Broadcom driver bcm43xx actually work? slippytoad Servers & Networking 4 27th March 2006 09:45 AM


Current GMT-time: 10:02 (Saturday, 25-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat