Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
Hello, I am having problems with a problematic driver for the Broadcom Chipset (4306 Rev 3). This is a known problem but the fix appears to be not so simple. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux User jkwilborn's Avatar
    Join Date
    Nov 2012
    Posts
    278

    Need to locate the 'driver name' of a Wireless lan interface


    Hello, I am having problems with a problematic driver for the Broadcom Chipset (4306 Rev 3). This is a known problem but the fix appears to be not so simple. I have, I believe been able to create the driver. Unfortuneatly the named driver in the instructions do not match the ones installed in my machine. If I try to unload it, via the "modprobe", it gags on the 'module name'. If anyone knows how to find that actual loaded 'module name' please reply. Thanks....

    Jack

    P.S. I don't have Internet access for this machine, so keep that in mind.

  2. #2
    Linux Guru rokytnji's Avatar
    Join Date
    Jul 2008
    Location
    Desert
    Posts
    4,168
    Without internet which can be a pain in the butt.

    Code:
    $ cat /etc/issue
    Welcome to antiX. Powered by Debian Testing.
    $ lspci -knn
    00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: agpgart-intel
    00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    00:03.0 Communication controller [0780]: Intel Corporation 82Q35 Express MEI Controller [8086:29b4] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: mei
    00:03.2 IDE interface [0101]: Intel Corporation 82Q35 Express PT IDER Controller [8086:29b6] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: ata_generic
    00:03.3 Serial controller [0700]: Intel Corporation 82Q35 Express Serial KT Controller [8086:29b7] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: serial
    00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: e1000e
    00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: ehci_hcd
    00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: snd_hda_intel
    00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: uhci_hcd
    00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: ehci_hcd
    00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92)
    00:1f.0 ISA bridge [0601]: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller [8086:2914] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: lpc_ich
    00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] [8086:2920] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: ata_piix
    00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: i801_smbus
    00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] [8086:2926] (rev 02)
    	Subsystem: Lenovo Device [17aa:3037]
    	Kernel driver in use: ata_piix
    11:0c.0 Network controller [0280]: Ralink corp. RT2561/RT61 802.11g PCI [1814:0301]
    	Subsystem: Ralink corp. EW-7108PCg [1814:2561]
    	Kernel driver in use: rt61pci
    Broadcom can be a chore sometimes in Debian.

    Code:
    $ cat /etc/os-release
    PRETTY_NAME="Debian GNU/Linux wheezy/sid"
    NAME="Debian GNU/Linux"
    ID=debian
    ANSI_COLOR="1;31"
    Linux Registered User # 475019
    Lead,Follow, or get the heck out of the way. I Have a Masters in Raising Hell
    Tech Books
    Free Linux Books
    Newbie Guide
    Courses at Home

  3. #3
    Linux User jkwilborn's Avatar
    Join Date
    Nov 2012
    Posts
    278
    rokytnji, Thanks for the reply. I followed you instructions, and got the results that said, in a nutshell..

    ...... Network Controller ... BCM4306 802.11b/g Wireless Lan controller ... (rev 03)
    .
    .
    Kernel driver in use: b43-pci-bridge

    I attempted this:

    modprobe -r b43-pci-bridge
    FATAL: Module _ not found

    The results always seem to be the same, do you know what I'm doing incorrectly? Could there be a lower level controller code?

    Thanks...

    Jack

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru rokytnji's Avatar
    Join Date
    Jul 2008
    Location
    Desert
    Posts
    4,168
    All I can say is look through

    bcm43xx - Debian Wiki

    Identification

    <!> The PCI ID is not sufficient to determine the Broadcom chipset within.

    The relevant driver has built-in logic to probe the actual chipset, for example:
    Since It seems that kernel 2.6.37 is the latest listed in the link with the modules in Debians Kernel that support Broadcom. Plus. You have not posted what kernel in Debian you are using. Mine for example.

    Code:
    $ uname -r
    3.6.6-antix.1-amd64-smp
    Also. Just for grins. what does (I used my root terminal, You may have to use sudo ifconfig -a)

    Code:
    # ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:1a:6b:55:6a:32  
              inet addr:192.168.2.17  Bcast:192.168.2.255  Mask:255.255.255.0
              inet6 addr: fe80::21a:6bff:fe55:6a32/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:103884 errors:0 dropped:0 overruns:0 frame:0
              TX packets:83015 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:124037668 (118.2 MiB)  TX bytes:11786290 (11.2 MiB)
              Interrupt:16 Memory:d0280000-d02a0000 
    
    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:162 errors:0 dropped:0 overruns:0 frame:0
              TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:16054 (15.6 KiB)  TX bytes:16054 (15.6 KiB)
    
    wlan0     Link encap:Ethernet  HWaddr 00:1a:ef:05:1e:09  
              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)
    Spit out also? I don't run Broadcom gear. I stick with Atheros, Raylink,Intel, and Realtek wireless chips . So I am not too Broadcom savvy myself.

    I wonder at your statement also

    I believe been able to create the driver
    When no creation should be necessary in recent kernels after 2.6.37 in Debian. b43 seems to be the only kernel module you need for 4306/3 according to Debians Wiki.

    b43 - Linux Wireless

    supported: yes


    BCM4306/3


    ?


    G (r2)
    scroll to top of page in the link to see what I mean (read the whole page also). So b43 should be in Debians kernel 2.6.24 unless you are running ancient Debian. No need to install any Driver. But firmware may be what is killing you and internet connection of some kind (eth0 ?, land line) will be needed for next link

    Install B43 Broadcom Wireless Drivers Using Debian

    Like I said. PITA.
    Last edited by rokytnji; 12-19-2012 at 07:30 PM.
    Linux Registered User # 475019
    Lead,Follow, or get the heck out of the way. I Have a Masters in Raising Hell
    Tech Books
    Free Linux Books
    Newbie Guide
    Courses at Home

  6. #5
    Linux User jkwilborn's Avatar
    Join Date
    Nov 2012
    Posts
    278
    Posted a reply last night, before bed and I don't see it... Anyway, I read about it and thought, as you did that it would just work. But it doesn't seem to, but I don't know if I have to do additional configuration to the wifi to get it operational.

    After describing what happened to the box, I notice that when I enter the wrong 'shutdown' command and it started to bring up the interfaces that the software complained about the firmware with the following line, there is a bunch of numbers ahead of the following, I believe it's the hardware or mac address:

    firmware: requesting b43/ucode5.fw

    I did read about this somewhere and it stated that the software was indicating a problem. I will see what I can find about it on the internet. I did give you the version but I don't see it, so here it is again...

    2.6.32-5-powerpc64

    I would like express to you that you have been invaluable to my getting this machine working, please accept my heartfelt thanks.

    Thanks,
    Jack

  7. #6
    Linux Guru rokytnji's Avatar
    Join Date
    Jul 2008
    Location
    Desert
    Posts
    4,168
    This guy (craigevil) is one Debian go to type of guy I pay attention to on the net. The whole thread pretty much covers and explains

    firmware: requesting b43/ucode5.fw
    I figured it was non free firmware that was killing your wireless. That is why Broadcom can be a PITA compared to the wireless chips I run.

    Debian User Forums &bull; View topic - [Solved] Firmware missing, old files?

    read the whole thread also.

    This may help for offline install of firmwarwe also

    Are there DVD or CD images with non-free firmware?

    Yes. Debian provides an unofficial netinst image for i386/amd64/powerpc with the non-free firmware, you can find it here:
    http://cdimage.debian.org/cdimage/un...ding-firmware/

    I found that reading

    http://raphaelhertzog.com/2011/03/14...h-the-problem/
    Linux Registered User # 475019
    Lead,Follow, or get the heck out of the way. I Have a Masters in Raising Hell
    Tech Books
    Free Linux Books
    Newbie Guide
    Courses at Home

  8. #7
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    Have you resolved this yet? If not I think that I can help.

    I have attached a compressed file containing all of the Broadcom firmware files. Download it and transfer it to your home folder on your Linux PC. Then, uncompress it with this command:

    Code:
     gunzip b43-firmware.tar.gz
    This should create a folder named b43 in your home directory, containing the firmware. Then copy it to your /lib/firmware folder with this command:

    Code:
    sudo cp -R b43 /lib/firmware/
    Reboot the computer, and the wireless should now work.
    Attached Files Attached Files
    Please do not send Private Messages to me with requests for help. I will not reply.

  9. #8
    Linux User jkwilborn's Avatar
    Join Date
    Nov 2012
    Posts
    278

    Success, fixed, so far...

    Thanks for the fix from Waterhead... The fw code seems to have fixed it... I just can't get past the key.. I'm sure I will.

    Thanks to all.

    Jack

  10. #9
    Linux User jkwilborn's Avatar
    Join Date
    Nov 2012
    Posts
    278
    Well, I can see the iPhone and the phone seems to think it's connected, but the Linux end keeps requesting a password (security key). I have the key on the iPhone set to a 13 character phrase and I enter that, but it won't connect. I even tried setting the Linux driver with a password, but no luck. I use the command "iwconfig wlan0 key s:'xxxxxxxxxxxxx' Not really x's, but I know what it is and I keep trying. Could I have missed another part of the config?

    Any suggestions would be appreciated... It would be nice to have the box on the air so to speak.

    Thanks
    Jack

  11. #10
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    An iPhone? Isn't that Bluetooth?

    You should be using NetworkManager to connect wirelessly, not terminal commands. That would be found in the system taskbar, and depending on the window manger you use, is either at the top or bottom of the desktop. The icon for it will also be different, depending on the window manager/theme you are using. When you click on it it should then show a list of available connections.
    Please do not send Private Messages to me with requests for help. I will not reply.

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •