You are not logged in.

#1 2012-03-13 17:05:30

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Broadcom b43 wireless can't connect wirless

hi guys , my Wireless card is:

#  lspci -vnn | grep 14e4
03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: Broadcom Corporation Device [14e4:051a]

from wiki I should use brcmsmac driver, It has been including the kernel

# lsmod|grep brc
brcmsmac              533512  0
cordic                  1073  1 brcmsmac
crc8                    1186  1 brcmsmac
brcmutil                3617  1 brcmsmac
mac80211              228527  2 b43,brcmsmac
cfg80211              172260  3 mac80211,b43,brcmsmac

Before I install the b43-firmware from the AUR , the kernel can get the Wireless Device: wlan0

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 576 qdisc pfifo_fast state UP qlen 1000
    link/ether 5c:26:0a:32:71:81 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 88:25:2c:cf:6b:aa brd ff:ff:ff:ff:ff:ff

then I install the b43-firmware from the AUR and add the "b43" to the /etc/rc.conf
after reboot it can load the "b43" kernel module

# lsmod |grep b43
b43                   338777  0 
ssb                    48207  1 b43
pcmcia                 36225  2 ssb,b43
mmc_core               80910  2 ssb,b43
mac80211              228527  2 b43,brcmsmac
cfg80211              172260  3 mac80211,b43,brcmsmac

I want connect my Wireless AP by wpa_supplicant.

this is my /etc/wpa_supplicant.conf
I can not  find the WPA-PSK2/AES encrypted method.

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=1

network={
    ssid="ink"
    proto=RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    # psk="..."
    # wpa_passphrase <ssid> <password>
    psk=43708052...424
}

first , I active the wlan0 device
second , I connect to the Wireless AP

# ifconfig wlan0 up

# wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
Trying to associate with b0:48:7a:30:f6:a4 (SSID='ink' freq=2472 MHz)
Authentication with b0:48:7a:30:f6:a4 timed out.
Trying to associate with b0:48:7a:30:f6:a4 (SSID='ink' freq=2472 MHz)
Authentication with b0:48:7a:30:f6:a4 timed out.
Trying to associate with b0:48:7a:30:f6:a4 (SSID='ink' freq=2472 MHz)

the wpa_supplicant are always print these Messages

then I try to use this run wpa_supplicant in the background.

# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf 

# iwconfig 
lo        no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"ink"  
          Mode:Managed  Frequency:2.472 GHz  Access Point: Not-Associated   
          Tx-Power=19 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

eth0      no wireless extensions.

and then use dhcpcd to get the DHCP IP

# dhcpcd wlan0
dhcpcd[8124]: version 5.5.4 starting
dhcpcd[8124]: wlan0: waiting for carrier
dhcpcd[8124]: timed out

I find some info about wireless for dmesg:

[   95.261982] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[   95.264981] sd 4:0:0:0: [sdb] Asking for cache data failed
[   95.264990] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  106.422170] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement)
[  106.422178] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement)
[  106.422700] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
[  106.423132] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  146.888536] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  146.891529] sd 4:0:0:0: [sdb] Asking for cache data failed
[  146.891537] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[  168.370300] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 1/3)
[  168.570117] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 2/3)
[  168.770109] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 3/3)
[  168.970103] wlan0: direct probe to b0:48:7a:30:f6:a4 timed out
[  169.136739] ------------[ cut here ]------------
[  169.136766] WARNING: at drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]()
[  169.136770] Hardware name: Inspiron 1120
[  169.136773] Modules linked in: arc4 snd_hda_codec_hdmi btusb bluetooth uvcvideo videodev v4l2_compat_ioctl32 media uas ums_realtek usb_storage joydev snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_timer i2c_algo_bit drm_kms_helper ttm drm ohci_hcd brcmsmac cordic crc8 i2c_piix4 edac_mce_amd shpchp dell_wmi serio_raw snd ehci_hcd soundcore sp5100_tco atl1c sparse_keymap usbcore usb_common evdev edac_core k10temp pci_hotplug pcspkr psmouse brcmutil battery button dell_laptop dcdbas wmi video processor ac b43 ssb pcmcia mmc_core pcmcia_core mac80211 cfg80211 rfkill lm90 i2c_core kvm_amd kvm fuse ext4 crc16 jbd2 mbcache dm_mod sd_mod ahci libahci libata scsi_mod
[  169.136846] Pid: 109, comm: kworker/u:3 Not tainted 3.2.9-1-ARCH #1
[  169.136850] Call Trace:
[  169.136860]  [<ffffffff810660af>] warn_slowpath_common+0x7f/0xc0
[  169.136865]  [<ffffffff8106610a>] warn_slowpath_null+0x1a/0x20
[  169.136877]  [<ffffffffa054d179>] brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]
[  169.136886]  [<ffffffffa053f1bb>] brcms_ops_flush+0x3b/0x60 [brcmsmac]
[  169.136900]  [<ffffffffa025e5d2>] __ieee80211_recalc_idle+0x202/0x240 [mac80211]
[  169.136913]  [<ffffffffa025f4d3>] ieee80211_recalc_idle+0x33/0x60 [mac80211]
[  169.136925]  [<ffffffffa025bc1f>] ieee80211_work_work+0x4df/0x1340 [mac80211]
[  169.136931]  [<ffffffff81459dde>] ? __schedule+0x33e/0x980
[  169.136944]  [<ffffffffa025b740>] ? free_work+0x20/0x20 [mac80211]
[  169.136950]  [<ffffffff81082a66>] process_one_work+0x116/0x4d0
[  169.136955]  [<ffffffff810833fe>] worker_thread+0x15e/0x350
[  169.136960]  [<ffffffff810832a0>] ? manage_workers.isra.29+0x230/0x230
[  169.136965]  [<ffffffff8108843c>] kthread+0x8c/0xa0
[  169.136970]  [<ffffffff8145feb4>] kernel_thread_helper+0x4/0x10
[  169.136975]  [<ffffffff810883b0>] ? kthread_worker_fn+0x190/0x190
[  169.136979]  [<ffffffff8145feb0>] ? gs_change+0x13/0x13
[  169.136982] ---[ end trace 982350940558154b ]---
[  179.646864] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 1/3)
[  179.846779] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 2/3)
[  180.046781] wlan0: direct probe to b0:48:7a:30:f6:a4 (try 3/3)
[  180.246774] wlan0: direct probe to b0:48:7a:30:f6:a4 timed out

this is from the /var/log/messages.log

Mar 14 00:29:56 king-netbook kernel: [   95.261982] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 14 00:30:08 king-netbook kernel: [  106.423132] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 14 00:30:48 king-netbook kernel: [  146.888536] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 14 00:31:10 king-netbook kernel: [  169.136739] ------------[ cut here ]------------
Mar 14 00:31:10 king-netbook kernel: [  169.136766] WARNING: at drivers/net/wireless/brcm80211/brcmsmac/main.c:8234 brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]()
Mar 14 00:31:10 king-netbook kernel: [  169.136770] Hardware name: Inspiron 1120
Mar 14 00:31:10 king-netbook kernel: [  169.136773] Modules linked in: arc4 snd_hda_codec_hdmi btusb bluetooth uvcvideo videodev v4l2_compat_ioctl32 media uas ums_realtek usb_storage joydev snd_
hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_page_alloc snd_timer i2c_algo_bit drm_kms_helper ttm drm ohci_hcd brcmsmac cordic crc8 i2c_piix4 edac_mce_amd shpchp de
ll_wmi serio_raw snd ehci_hcd soundcore sp5100_tco atl1c sparse_keymap usbcore usb_common evdev edac_core k10temp pci_hotplug pcspkr psmouse brcmutil battery button dell_laptop dcdbas wmi video
processor ac b43 ssb pcmcia mmc_core pcmcia_core mac80211 cfg80211 rfkill lm90 i2c_core kvm_amd kvm fuse ext4 crc16 jbd2 mbcache dm_mod sd_mod ahci libahci libata scsi_mod
Mar 14 00:31:10 king-netbook kernel: [  169.136846] Pid: 109, comm: kworker/u:3 Not tainted 3.2.9-1-ARCH #1
Mar 14 00:31:10 king-netbook kernel: [  169.136850] Call Trace:
Mar 14 00:31:10 king-netbook kernel: [  169.136860]  [<ffffffff810660af>] warn_slowpath_common+0x7f/0xc0
Mar 14 00:31:10 king-netbook kernel: [  169.136865]  [<ffffffff8106610a>] warn_slowpath_null+0x1a/0x20
Mar 14 00:31:10 king-netbook kernel: [  169.136877]  [<ffffffffa054d179>] brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]
Mar 14 00:31:10 king-netbook kernel: [  169.136886]  [<ffffffffa053f1bb>] brcms_ops_flush+0x3b/0x60 [brcmsmac]
Mar 14 00:31:10 king-netbook kernel: [  169.136900]  [<ffffffffa025e5d2>] __ieee80211_recalc_idle+0x202/0x240 [mac80211]
Mar 14 00:31:10 king-netbook kernel: [  169.136913]  [<ffffffffa025f4d3>] ieee80211_recalc_idle+0x33/0x60 [mac80211]
Mar 14 00:31:10 king-netbook kernel: [  169.136925]  [<ffffffffa025bc1f>] ieee80211_work_work+0x4df/0x1340 [mac80211]
Mar 14 00:31:10 king-netbook kernel: [  169.136931]  [<ffffffff81459dde>] ? __schedule+0x33e/0x980
Mar 14 00:31:10 king-netbook kernel: [  169.136944]  [<ffffffffa025b740>] ? free_work+0x20/0x20 [mac80211]
Mar 14 00:31:10 king-netbook kernel: [  169.136950]  [<ffffffff81082a66>] process_one_work+0x116/0x4d0
Mar 14 00:31:10 king-netbook kernel: [  169.136955]  [<ffffffff810833fe>] worker_thread+0x15e/0x350
Mar 14 00:31:10 king-netbook kernel: [  169.136960]  [<ffffffff810832a0>] ? manage_workers.isra.29+0x230/0x230
Mar 14 00:31:10 king-netbook kernel: [  169.136965]  [<ffffffff8108843c>] kthread+0x8c/0xa0
Mar 14 00:31:10 king-netbook kernel: [  169.136970]  [<ffffffff8145feb4>] kernel_thread_helper+0x4/0x10
Mar 14 00:31:10 king-netbook kernel: [  169.136975]  [<ffffffff810883b0>] ? kthread_worker_fn+0x190/0x190
Mar 14 00:31:10 king-netbook kernel: [  169.136979]  [<ffffffff8145feb0>] ? gs_change+0x13/0x13
Mar 14 00:31:10 king-netbook kernel: [  169.136982] ---[ end trace 982350940558154b ]---
Mar 14 00:31:39 king-netbook kernel: [  198.088632] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 14 00:32:31 king-netbook kernel: [  249.288435] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled

thanks for your help !!!


Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#2 2012-03-13 17:25:26

Dheart
Member
From: Sofia, Bulgaria
Registered: 2006-10-26
Posts: 943

Re: Broadcom b43 wireless can't connect wirless

Seems like your adaptor is not supported by b43 (check here http://linuxwireless.org/en/users/Drivers/b43).
That's why you can't connect after you modprobe b43. It sais on that page that it should work with brcm80211, but you probably need to blacklist b43, which might be causing conflicts. If those don't work try the proprietary broadcom-wl. Which should also work.
You should check b43 page for updates to see when they fully support your card.


My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

Offline

#3 2012-03-13 20:09:08

Wilco
Member
Registered: 2008-11-09
Posts: 431

Re: Broadcom b43 wireless can't connect wirless

I have the same card as you and the b43 and brcmsmac drivers don't work, I get the same timeout errors as you. I've installed the broadcom-wl from aur and it works fine. It keeps spawning error messages in kernel.log but at least it works, connected to WPA2 access point as I'm typing this. You need to modprobe wl after installing and blacklist these modules:

blacklist brcmsmac
blacklist b43
blacklist bcma
blacklist ssb

Harmless warnings with the wl driver:

Mar 13 21:05:04 localhost kernel: [ 2712.438541] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Mar 13 21:05:06 localhost kernel: [ 2714.447137] net_ratelimit: 2 callbacks suppressed

Offline

#4 2012-03-15 14:13:49

Piki
Member
From: Cyberspace
Registered: 2012-03-13
Posts: 12

Re: Broadcom b43 wireless can't connect wirless

Is the firmware for the b43 driver actually installed? Just because the fwcutter is installed, doesn't mean the firmware is. Check in the directory /lib/firmware if you don't know, you should see the b43 folder there.

If it isn't, click the link to linuxwireless.org that Dheart. That should give you instructions on how to use the b43-fwcutter to get the firmware. After, reload the b43 driver and it should work.


--
Piki
"Many people have died for their beliefs. The real courage is in living and suffering for what you believe in." Brom, character in 'Eragon' by Christopher Paolini

Offline

#5 2012-03-15 14:21:42

Gusar
Member
Registered: 2009-08-25
Posts: 3,452

Re: Broadcom b43 wireless can't connect wirless

b43 doesn't support BCM4313, so it won't work even if you get the firmware. The driver choices for BCM4313 are wl and brcmsmac.

Offline

#6 2012-03-16 16:40:27

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Re: Broadcom b43 wireless can't connect wirless

hi guys , I install broadcom-wl from AUR and after I reboot

the modules all loaded like that:

# lsmod|grep wl
wl                   2557323  0 
lib80211                3981  2 wl,lib80211_crypt_tkip
cfg80211              172260  1 wl
# cat /etc/modprobe.d/broadcom-wl.conf 
blacklist b43
blacklist bcma
blacklist ssb

After reboot , names of devices are different :

eth0    --> eth1
wlan0   --> eth0

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 88:25:2c:cf:6b:aa brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8a25:2cff:fecf:6baa/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 5c:26:0a:32:71:81 brd ff:ff:ff:ff:ff:ff
# iwconfig
lo        no wireless extensions.

eth1      no wireless extensions.

eth0      IEEE 802.11abg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
# sudo ifconfig eth0 up
# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet6 fe80::8a25:2cff:fecf:6baa  prefixlen 64  scopeid 0x20<link>
        ether 88:25:2c:cf:6b:aa  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17 
# iwlist eth0 scan
eth0      No scan results
# sudo wpa_supplicant -Dwext -i eth0 -c /etc/wpa_supplicant.conf
^CCTRL-EVENT-TERMINATING - signal 2 received

BUT there has no output info, I found some info from /var/log/messages.log

Mar 17 00:30:37 king-netbook kernel: [ 1304.011689] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:31:28 king-netbook kernel: [ 1355.208380] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:32:20 king-netbook kernel: [ 1406.408559] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:33:11 king-netbook kernel: [ 1457.608502] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:34:02 king-netbook kernel: [ 1508.808561] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled

AM I doing in a wrong way nor missing any steps ?

thanks !


Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#7 2012-03-17 03:24:40

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Re: Broadcom b43 wireless can't connect wirless

sorry , I am not executing as root :

# sudo iwlist eth0 scan|grep ink
                   ESSID:"TP-LINK_CA95C6"
                   ESSID:"TP-LINK_46C38E"

but there is not my wireless point "ink"

I don't know if there is relative to the kernel version:

 · uname -a
Linux king-netbook 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012
x86_64 AMD Athlon(tm) II Neo K345 Dual-Core Processor AuthenticAMD GNU/Linux

modprobe command '-l' option can't exist , I can't found if there is a module named "bcma"

· modinfo bcma
ERROR: Module bcma not found.

 · lsmod|grep bcma

I want to know if I use 'brcmsmac' module , should I install a firmware ?

this guy, maybe use the default kernel module , can get work:

https://bbs.archlinux.org/viewtopic.php?id=129381#2

thanks guys


Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#8 2012-03-17 14:00:46

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,004

Re: Broadcom b43 wireless can't connect wirless

Mar 17 00:30:37 king-netbook kernel: [ 1304.011689] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:31:28 king-netbook kernel: [ 1355.208380] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:32:20 king-netbook kernel: [ 1406.408559] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:33:11 king-netbook kernel: [ 1457.608502] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 17 00:34:02 king-netbook kernel: [ 1508.808561] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled

This is your hard drive (or thumb drive)!  Seems to be complaining about write protection.

Last edited by nomorewindows (2012-03-17 14:01:42)


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#9 2012-03-19 13:56:21

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Re: Broadcom b43 wireless can't connect wirless

@nomorewindows I have google with ""Test WP failed, assume Write Enabled"
but can't find about any obvious info about  wireless driver

but my message shows this unnormal info , I am not sure it is problem of wireless driver ?

how can get some more debug info ?


Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#10 2012-03-19 14:05:45

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Re: Broadcom b43 wireless can't connect wirless

there are some info in dmeg:

· dmesg |grep brcm
[    5.760790] brcmsmac 0000:03:00.0: bus 3 slot 0 func 0 irq 10
[    5.760842] brcmsmac 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    5.760850] brcmsmac 0000:03:00.0: setting latency timer to 64
[   84.065121] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement)
[   84.065128] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement)
[   84.065616] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)

Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#11 2012-03-19 14:13:09

Wilco
Member
Registered: 2008-11-09
Posts: 431

Re: Broadcom b43 wireless can't connect wirless

You're still using the brcmsmac driver, there are some serious bugs in kernel 3.2 that prevent newer BCM4313 chips from working:
https://bugzilla.redhat.com/show_bug.cgi?id=787649
https://bugzilla.kernel.org/show_bug.cgi?id=42840

You need to update your kernel to 3.3 (in AUR kernel-mainline) or use the broadcom-wl driver (expect some hard crashes).

The naming issues, wlan0, eth1, eth0 changing every boot, can be fixed with some udev rules, see here:
https://wiki.archlinux.org/index.php/Ud … vice_names

Offline

#12 2012-03-19 15:16:43

57lvii
Member
From: China
Registered: 2010-04-23
Posts: 38

Re: Broadcom b43 wireless can't connect wirless

https://bbs.archlinux.org/viewtopic.php?id=135439

this guy has the same dmesg info  above

Now I  had uninstall al thel third firmware and used the default kernel module: brcmsmac

# lspci -nnk | grep -iA2 net

03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: Broadcom Corporation Device [14e4:051a]
        Kernel driver in use: brcmsmac

why  after I update after  2012-03-04, I can't connect the wireless network ?

so sad and so puzzled


Life is fantastic, we all pray it gives us the plain comfort life, do not tempt us.
But only in the face of difficult choices, we face the real self, we define ourselves !

Offline

#13 2012-03-20 08:38:35

sultanoswing
Member
Registered: 2008-07-23
Posts: 286

Re: Broadcom b43 wireless can't connect wirless

I've got the exact same wireless card in my new HP Folio 13 (a nice piece of kit, BTW). I also had the 'weak wireless' problem.

Solved by:
a) blacklist 'b43, ssb, bcma, brcmsmac' in /etc/modprobe.d/broadcom-wl.conf
b) yaourt -S broadcom-wl from AUR
c) reboot

ps - am looking forward to kernel 3.3 arriving.

Last edited by sultanoswing (2012-03-20 08:39:34)


Arch 4.4.13-lts (x86_64) w/Gnome 3.20.2
ASUS P7P55-E-Pro, Geforce GT430, i5-750, 8GB, Samsung 830 SSD | Intel NUC 5i5RYK | ASUS ux303ua | HP Folio 13

Offline

#14 2012-03-20 13:22:23

Wilco
Member
Registered: 2008-11-09
Posts: 431

Re: Broadcom b43 wireless can't connect wirless

Unfortunately, the 3.3 kernel does not fix the brcmsmac driver for bcm4313, I just tried it. The signal is still very weak (1 mbit) and dmesg is full of brcmsmac error messages

Offline

#15 2012-04-27 21:38:29

ivanoff
Member
Registered: 2012-03-18
Posts: 12

Re: Broadcom b43 wireless can't connect wirless

Absolutely true, even in 3.3 the signal is low and driver's unstable. Wl driver gives a lot of identification problems (sometimes can't get to connect to my home wifi, even after several tries).... I used an external wifi key ==> shame !

Offline

#16 2012-05-01 06:53:00

mabunix
Member
Registered: 2012-02-19
Posts: 1

Re: Broadcom b43 wireless can't connect wirless

I had the same problems with BCM4313. Only broadcom-wl worked for me (Samsung RF511 S05). Recently I changed the Mini PCIe BCM4313 to Intel Centrino Advanced N 6230. ALl problems are gone, the signal is strong and the connection is more stable.

Offline

Board footer

Powered by FluxBB