[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Feedback needed] "brcmsmac" wifi driver in testing



On Mon, 25 Jul 2011 16:46:56 +0000 (UTC), Camaleón writes:
> Our cell phone provider has given us a netbook that embeds a broadcom 
> 4313 wifi chipset¹.
>
> This card seems to be supported by the new -and open source- brcmsmac 
> driver² (still in a staging development) but I am having problems to 
> associate it with my AP.
>
> All seems going fine (wlan0 interface is created and NM sees the AP) but 
> I only get "authentication with [ap-mac] timed out" in dmesg and nothing 
> more. Other USB cards I have tested (based on rt73 and rt2xxx chipsets) 
> are working okay so I guess the AP is not the problem here but the driver.
>
> I wonder if someone is currently using this driver and what are his/her 
> experiences.
>
> ¹http://wiki.debian.org/brcm80211
> ²http://linuxwireless.org/en/users/Drivers/brcm80211

I'm using brcmsmac since 1 year without a problem.

--8<---------------cut here---------------start------------->8---
$ lspci -vnn | grep Broadcom -A 5
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: Askey Computer Corp. Device [144f:7179]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f3800000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: brcmsmac

$ lsmod | grep -E brcm
brcmsmac              485123  0
mac80211              152890  1 brcmsmac
cfg80211               98676  2 brcmsmac,mac80211

$ uname -r
2.6.39.3-vy.20110710
--8<---------------cut here---------------end--------------->8---


BTW, if I were you, instead of relying on nm, I'd manually try to
connect to the AP. That is,

--8<---------------cut here---------------start------------->8---
# ifconfig wlan0 up
# emacs /etc/wpa_supplicant/wpa_supplicant.conf
# wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0
--8<---------------cut here---------------end--------------->8---

Now check the wpa_supplicant debug outputs. Moreover, if you can see a
valid mac addr in the "Access Point" field of the "iwconfig wlan0"
output, Wi-Fi assoc is ok and you're struggling with the encryption
part.


Best.


Reply to: