SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2011-04-12 23:34:57

bigbrother
New Member
Registered: 2011-04-12
Posts: 4

#! with BCM4312. Works but drops after connecting

So I've just installed #! on my Lenovo S10 notebook that has the BCM4312 wireless chipset. (I hate broadcom). After installing it picked up the card just fine and I tried to connect to my router. After 2 seconds it dropped the connection. So I looked up the issue on these forums and found http://crunchbanglinux.org/forums/topic … 312-lpphy/
Well the solution corenominal posted looked promising after checking my lspci.

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

But still nothing was working. Same issue as before. So I just tried to connect and checked dmesg

[   47.751104] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
[   47.751132] b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
[   47.751148] b43-phy0: Controller RESET (DMA error) ...
[   47.988371] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[   53.425281] b43-phy0: Controller restarted
[  177.875706] tg3: eth0: Link is down.
[  195.416588] wlan0: direct probe to AP 00:1d:7e:c2:9c:b1 (try 1)
[  195.426505] wlan0: direct probe responded
[  195.426515] wlan0: authenticate with AP 00:1d:7e:c2:9c:b1 (try 1)
[  195.428636] wlan0: authenticated
[  195.428697] wlan0: associate with AP 00:1d:7e:c2:9c:b1 (try 1)
[  195.431360] wlan0: RX AssocResp from 00:1d:7e:c2:9c:b1 (capab=0x401 status=0 aid=3)
[  195.431373] wlan0: associated
[  195.433134] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  200.316100] No probe response from AP 00:1d:7e:c2:9c:b1 after 500ms, disconnecting.
[  201.308565] wlan0: direct probe to AP 00:1d:7e:c2:9c:b1 (try 1)
[  201.508152] wlan0: direct probe to AP 00:1d:7e:c2:9c:b1 (try 2)
[  201.708169] wlan0: direct probe to AP 00:1d:7e:c2:9c:b1 (try 3)
[  201.908159] wlan0: direct probe to AP 00:1d:7e:c2:9c:b1 timed out
[  205.604120] wlan0: no IPv6 routers present

Anyone have any ideas as to what is happening?

Offline

Help fund CrunchBang, donate to the project!

#2 2011-04-13 00:32:40

kook
#! CrunchBanger
Registered: 2009-10-25
Posts: 101

Re: #! with BCM4312. Works but drops after connecting

yes had the same dmesg, ubuntu natty is calling to you and saying come and use lw with me big_smile

Offline

#3 2011-04-13 00:57:19

tranche
#! CrunchBanger
Registered: 2011-02-04
Posts: 111
Website

Re: #! with BCM4312. Works but drops after connecting

Please run these and post the outputs

lspci -nn | grep -i broadcom
lspci -k

On this one, you only need to post the stanza (three lines) for the broadcom driver.

And finally

lsmod | grep 80211

This will help us decide what driver you're running and what driver you need.

Last edited by tranche (2011-04-13 01:04:50)

Offline

#4 2011-04-13 01:04:09

bigbrother
New Member
Registered: 2011-04-12
Posts: 4

Re: #! with BCM4312. Works but drops after connecting

02:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express [14e4:1713] (rev 02)
05:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
    Subsystem: Broadcom Corporation Device 04b5
    Kernel driver in use: b43-pci-bridge

and the lsmod |grep 80211 returns

mac80211              123574  1 b43
cfg80211               87661  2 b43,mac80211
rfkill                 10264  3 bluetooth,cfg80211

Last edited by bigbrother (2011-04-13 01:23:37)

Offline

#5 2011-04-13 01:36:05

tranche
#! CrunchBanger
Registered: 2011-02-04
Posts: 111
Website

Re: #! with BCM4312. Works but drops after connecting

"14E4:4315" means that you need the "wl" driver.

"b43  ...  132615  0" means that you're running the "b43" driver.

The standard procedure for removing b43 and installing wl under Squeeze is here;

http://wiki.debian.org/wl#Squeeze

Here's a script that has worked on a number of Debian and Statler installtions:

http://crunchbanglinux.org/forums/post/110823/#p110823

Offline

#6 2011-04-13 01:40:04

tranche
#! CrunchBanger
Registered: 2011-02-04
Posts: 111
Website

Re: #! with BCM4312. Works but drops after connecting

Also, you need to add mac80211 to the "modprobe -r" line in the procedure.

Offline

#7 2011-04-14 23:54:51

bigbrother
New Member
Registered: 2011-04-12
Posts: 4

Re: #! with BCM4312. Works but drops after connecting

Thanks tranche. I got it going now

Offline

#8 2011-04-15 00:17:32

tranche
#! CrunchBanger
Registered: 2011-02-04
Posts: 111
Website

Re: #! with BCM4312. Works but drops after connecting

Glad you got it running.  Broadcom, you know.  smile

Offline

#9 2011-04-16 19:23:56

AlexMex90
#! CrunchBanger
From: Mexicali, Mexico
Registered: 2009-07-09
Posts: 180
Website

Re: #! with BCM4312. Works but drops after connecting

I have a netbook with this wireless card, and it does not drop the connection for me, but completely refuses to connect to WPA  networks... instead my laptop (with a BCM4311) connects to WPA nicely. Damn... I hate broadcom! lol


Statler: Are you running Mac or PC?

Waldorf: After that... I'm running away!

Offline

#10 2011-04-17 00:10:40

nathwill
#! CrunchBanger
From: Portland, OR USA
Registered: 2010-11-05
Posts: 215
Website

Re: #! with BCM4312. Works but drops after connecting

greetings fellow broadcom haters. @bigbrother, i sympathize completely, i have the same 14e4:4315 card, and it's been a PITA on every distro i've used. glad to hear that you got this working under Statler. smile

fyi: you'll probably keep getting the dmesg gripe about PIO vs DMA, this card doesn't work well w/ DMA mode in linux, but it'll failover to PIO and work after it complains. if i stumble across the guide i saw for forcing it into PIO from the get go i'll throw a link up here later.


NOTICE: alloc: /dev/null: filesystem full

Offline

#11 2011-08-23 03:05:43

nathwill
#! CrunchBanger
From: Portland, OR USA
Registered: 2010-11-05
Posts: 215
Website

Re: #! with BCM4312. Works but drops after connecting

ok. to revive an old thread for anyone else who's been suffering like i have, i found a solution that may work well for some folks.

status: 14e4:4315 aka broadcom 4312 lp-phy appears to be fully supported w/ the b43 driver. i've confirmed that this is working for connecting to most networks, but i had still had tons of difficulty connecting at home. i tried changing  all kinds of things trying various fixes from the debian wl wiki to wireless.kernel.org, updated compat-wireless, and on and on... then stumbled across a very useful tip...

you may have luck if you're in the same pain point as i was by passing the options for pio and qos into modprobe when loading the b43 module...

modprobe b43 pio=1 qos=0

after doing this, i could then connect to my home network (a d-link router, which some other folks said they had problems w/ using this network card...)

if that does it for you, you can make the change stick with:

sudo touch /etc/modprobe.d/b43.conf
echo "options b43 pio=1 qos=0 | sudo tee -a /etc/modprobe.d/b43.conf

omg. i'm so happy i could dance.

edit: fwiw, the key here seems to be "qos=0", i haven't tried it without forcing pio mode, though i will do so shortly and report back. right now i have to go get my tuxedo for my wedding!

last edit: ok. so trying to remove pio=1 from that sequence seems to have not achieved anything other than to get some errors in dmesg like:

b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
b43-phy0: Controller RESET (DMA error) ...

so it appears that pio=1 and qos=0 are both required if the other methods still won't work for you. cheers smile

Last edited by nathwill (2011-08-23 04:10:30)


NOTICE: alloc: /dev/null: filesystem full

Offline

#12 2012-01-12 05:23:31

mynis01
#! Die Hard
From: 127.0.0.1
Registered: 2010-07-02
Posts: 1,965

Re: #! with BCM4312. Works but drops after connecting

You could try installing the default squeeze 2.6.32 kernel along with the firmware-b43-lpphy-installer package and see if that works better for you.

Offline

#13 2012-02-27 21:00:58

sieken
New Member
Registered: 2012-02-27
Posts: 9

Re: #! with BCM4312. Works but drops after connecting

I followed the instructions on http://wiki.debian.org/wl#Squeeze, but when I tried to connect to my wireless network, there was no change. Then I read this thread again, and saw:

tranche wrote:

Also, you need to add mac80211 to the "modprobe -r" line in the procedure.

This made my day. It seems to work without flaw, for now at least. Thank you tranche!

Offline

#14 2012-07-30 00:12:49

Ozitraveller
#! Junkie
From: Far from the madding crowd!
Registered: 2011-04-26
Posts: 261

Re: #! with BCM4312. Works but drops after connecting

I just thought I would post what I did to get my wifi working. I'm running debian sid.
I used the squeeze instructions from http://wiki.debian.org/wl#Squeeze (sid repositories)

aptitude update
aptitude install module-assistant wireless-tools
m-a a-i broadcom-sta
# echo blacklist brcm80211 >> /etc/modprobe.d/broadcom-sta-common.conf (DID NOT DO THIS)
update-initramfs -u -k $(uname -r)
# replaced brcm80211 with mac80211 see above
modprobe -r b44 b43 b43legacy ssb mac80211
modprobe wl
iwconfig

Last edited by Ozitraveller (2012-07-30 04:19:41)

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo