You are not logged in.

#1 2010-05-04 10:42:05

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

[Solved] BCM4312 and Kernel 2.6.33 Troubles

Hi, I recently updated to the 2.6.33 kernel and needed to update the wireless driver. I tried the broadcom-wl package and the broadcom-wl-patched with no luck. Since then b43 driver, however when bringing up the interface it fails.

$ sudo ifconfig wlan0 up
Password: 
SIOCSIFFLAGS: Unknown error 132
lspci -vnn | grep 14e4:
04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)

I followed the instructions from the wiki:[url]http://wiki.archlinux.org/index.php/Wireless#b43 and have installed b43-tools-git and b43-firmware-newest[/url]
rc.conf:

MODULES=(!b43legacy b43 !snd_pcsp !pcspkr powernow-k8 cpufreq_ondemand cpufreq_powersave)

dmseg tail:

ACPI: Thermal Zone [TZS0] (73 C)
acpi device:1b: registered as cooling_device2
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZS1] (76 C)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:01:09.1: SDHCI controller found [1180:0822] (rev 22)
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 10
sdhci-pci 0000:01:09.1: PCI INT B -> Link[LNK2] -> GSI 10 (level, low) -> IRQ 10
Registered led device: mmc0::
mmc0: SDHCI controller on PCI [0000:01:09.1] using PIO
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: AC Adapter [ADP1] (on-line)
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 11
firewire_ohci 0000:01:09.0: PCI INT A -> Link[LNK1] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LK4E] enabled at IRQ 21
b43-pci-bridge 0000:04:00.0: PCI INT A -> Link[LK4E] -> GSI 21 (level, low) -> IRQ 21
b43-pci-bridge 0000:04:00.0: setting latency timer to 64
EDAC amd64_edac:  Ver: 3.3.0 Apr 26 2010
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
firewire_ohci: Added fw-ohci device 0000:01:09.0, OHCI version 1.10
ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0
ACPI: Battery Slot [BAT0] (battery present)
b43-phy0: Broadcom 4312 WLAN found (core revision 15)

Last edited by 7x1x (2010-05-27 20:44:31)

Offline

#2 2010-05-04 11:12:42

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

b43 needs firmware. all the steps are available on the wireless wiki page.


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2010-05-05 03:18:16

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

what I have done was; install b43-firmware-newest and b43-tools-git from AUR, followed the instructions from the wireless setup wiki:

sudo pacman -S git
Create a new folder to your home (wifi or any other name)
mkdir wifi
cd wifi
git clone http://git.bu3sch.de/git/b43-tools.git
cd b43-tools/fwcutter
make
cd ..
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
tar xjf broadcom-wl-4.178.10.4.tar.bz2
cd broadcom-wl-4.178.10.4/linux
sudo ../../fwcutter/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o
reboot your computer

Have I missed anything?

Offline

#4 2010-05-05 04:38:20

mits
Member
From: Bucharest/Romania
Registered: 2008-01-10
Posts: 129

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

Folow these http://wiki.archlinux.org/index.php/Broadcom_BCM4312
with broadcom-wl from AUR.
It works for me.

Offline

#5 2010-05-05 05:05:46

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

Thanks for the help. I installed the broadcom-wl-patched package. I can now bring the interface up, however it will not scan.

$ sudo iwconfig
lo        no wireless extensions.

eth0      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

eth1      no wireless extensions.

$ sudo iwlist eth0 scan
eth0      Failed to read scan data : Invalid argument

dmesg tail. Would the kernel taint have anything to do with this?

udev: starting version 151
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'TKIP'
wl: module license 'Mixed/Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
ACPI: PCI Interrupt Link [LK4E] enabled at IRQ 22
wl 0000:04:00.0: PCI INT A -> Link[LK4E] -> GSI 22 (level, low) -> IRQ 22
wl 0000:04:00.0: setting latency timer to 64
eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36

Offline

#6 2010-05-05 09:39:31

mits
Member
From: Bucharest/Romania
Registered: 2008-01-10
Posts: 129

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

See in the wiki the trick that stop interface swaping.

Offline

#7 2010-05-05 12:42:30

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

eth0 is is bound to the ethernet and eth1 to the wireless but still no luck.

$ sudo iwlist scan
lo        Interface doesn't support scanning.
eth1      Failed to read scan data : Invalid argument
eth0      Interface doesn't support scanning.

Offline

#8 2010-05-05 17:20:24

mits
Member
From: Bucharest/Romania
Registered: 2008-01-10
Posts: 129

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

$ sudo iwlist scan

 
lo        Interface doesn't support scanning.

lan0      Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:1F:1F:04:A9:B3
                    ESSID:"privat"
                    Mode:Managed
                    Frequency=2.462 GHz (Channel 11)
                    Quality:5/5  Signal level:-50 dBm  Noise level:-92 dBm
                    IE: WPA Version 1
                        Group Cipher : TKIP                                                                    
                        Pairwise Ciphers (1) : TKIP                                                            
                        Authentication Suites (1) : PSK                                                        
                    Encryption key:on                                                                          
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s                                        
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s                                       
                              48 Mb/s; 54 Mb/s                                                                 
          Cell 02 - Address: 00:1B:FC:57:59:4D                                                                 
                    ESSID:"default"                                                                            
                    Mode:Managed                                                                               
                    Frequency=2.412 GHz (Channel 1)                                                            
                    Quality:2/5  Signal level:-79 dBm  Noise level:-93 dBm                                     
                    IE: WPA Version 1                                                                          
                        Group Cipher : TKIP                                                                    
                        Pairwise Ciphers (1) : TKIP                                                            
                        Authentication Suites (1) : PSK                                                        
                    Encryption key:on                                                                          
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s                                       
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s                                        
                              12 Mb/s; 48 Mb/s                                                                 
                                                                                                               
pan0      Interface doesn't support scanning.

See http://wiki.archlinux.org/index.php/Broadcom_BCM4312
"Interfaces swapped every time"

Last edited by mits (2010-05-05 17:23:37)

Offline

#9 2010-05-06 12:07:06

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

All that was needed was to install rfkill and now b43 and broadcom-wl work. I'm not sure why this wasn't needed for the previous kernels or why isn't mentioned in the wiki.

Thanks for the help.

Last edited by 7x1x (2010-05-08 01:56:02)

Offline

#10 2010-05-11 09:14:30

fnord0
Member
Registered: 2010-03-11
Posts: 18

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

I am getting the SAME issue with broadcom-wl and the "Failed to read scan data : Invalid argument" when running iwlist, so it will not work at all for me. this only started happening at the most recent kernel26 update (yesterday for me). I've installed rfkill, and tried everything imaginable. hoping someone call help here. I've tried different kernels, and everything ... any suggestion? 7x1x u maybe wanna explain the process u went through to get yours working?

Offline

#11 2010-05-12 06:42:56

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

Here's what I did for the broadcom-wl driver:

Make the package broadcom-wl 5.60.48.36-2 from the AUR. You should also try the patched driver.
Install: pacman -U broadcom-wl-5.60.48.36-2-x86_64.pkg.tar
Edit /etc/rc.conf: MODULES=(!b43 lib80211_crypt_tkip wl ...
reboot
rfkill unblock all
ifconifig eth0 up
iwlist scan

Also you should check to see if your card version is supported by b43: http://wireless.kernel.org/en/users/Dri … CI_devices
I have managed to get both working.

Offline

#12 2010-05-18 05:27:59

fnord0
Member
Registered: 2010-03-11
Posts: 18

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

thanks 7x1x for the headsup, I *really* appreciate the response. I have tried everything you suggested, but continue to get the error ::

> sudo iwlist scan
eth1      Failed to read scan data : Invalid argument

I even gave b43 a shot, etc... MANY, MANY hours of futzing, with no results. my thought is full-uninstall/reinstall of arch, as I had this working during fresh install (maybe i've fubar'd something along the way?!) I tried multiple kernels, manually installing the driver from broadcom, tried ALL the different AUR broadcom-wl(-xxxxx) packages, etc. time to go with a reinstall - I will post if this resolves anything.

just as FYI ::

> sudo lspci -n
08:00.0 0280: 14e4:4353 (rev 01)

> sudo lspci -vvk
08:00.0 Network controller: Broadcom Corporation Device 4353 (rev 01)
        Subsystem: Dell Device 000e
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at f1200000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [d0] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 128 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us
                        ClockPM+ Surprise- LLActRep+ BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [13c v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [160 v1] Device Serial Number 00-00-fe-xx-xx-xx-xx-xx
        Capabilities: [16c v1] Power Budgeting <?>
        Kernel driver in use: wl
        Kernel modules: wl

Last edited by fnord0 (2010-05-18 05:31:56)

Offline

#13 2010-05-18 07:39:03

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

Can you actually bring the interface up? Does the wireless light turn on(assuming you have one)?
Try bringing the interface up followed by a scan and then check the log files in /var/log/. I'm not sure which file the log is written to.
Let us know how it goes.

Offline

#14 2010-05-18 14:10:26

rb
Member
From: Argentina
Registered: 2010-05-07
Posts: 143

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

I was able to install b43 drivers for the very same card, and everything works out of the box. Despite my original problem was't the same, maybe this could help you.


Sorry for my English. Feel free to point out my errors.

Offline

#15 2010-05-18 15:15:07

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,774

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

7x1x wrote:

Thanks for the help. I installed the broadcom-wl-patched package. I can now bring the interface up, however it will not scan.

$ sudo iwconfig
lo        no wireless extensions.

eth0      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

eth1      no wireless extensions.

$ sudo iwlist eth0 scan
eth0      Failed to read scan data : Invalid argument

dmesg tail. Would the kernel taint have anything to do with this?

udev: starting version 151
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'TKIP'
wl: module license 'Mixed/Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
ACPI: PCI Interrupt Link [LK4E] enabled at IRQ 22
wl 0000:04:00.0: PCI INT A -> Link[LK4E] -> GSI 22 (level, low) -> IRQ 22
wl 0000:04:00.0: setting latency timer to 64
eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36

It has been my experience that you must have the Tx power on prior to initiating the scan with this chip.

I see you had used ifconfig ethn up previously, did you do that this time? It should enable the radio.
If that does not work, try (working from memory so this may not be exactly correct) ifconfig eth1 txpower on


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#16 2010-05-18 23:07:40

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

Hi, ewaller and rb I have got my card working with b43. Its fnord0 that's now having trouble with a BCM43224 14e4:4353 (rev 01).

Offline

#17 2010-05-27 00:00:43

fnord0
Member
Registered: 2010-03-11
Posts: 18

Re: [Solved] BCM4312 and Kernel 2.6.33 Troubles

thanks everyone for the help, especially 7x1x! it came down to my own stupidity! my laptop (alienware m11x) has the ability to turn ON and OFF the radio on the wireless card, turns out I didnt have the radio turned ON in linux!@#!$@#!$!!!! all I had to do was the following to get things working ::

modprobe wl
press FN+F3 to enable wireless
ifconfig wlan0 up
iwlist scan

everything is right in the world again! thanks for the help, seriously!

Offline

Board footer

Powered by FluxBB