On Thu, Mar 07, 2013 at 07:32:52AM +0100, Julien Pecqueur wrote: > Hi > > I have the dame wireless chipset and it "works" on my Archlinux > setup (64bits, GNOME, b43-firmware and network manager). > > I sa y "works" because i can use the wireless connection but the > connection is slow. > > What does dmesg says after a connection try? I've been struggling enough with this damn wireless chipset lately to start thinking about getting a new laptop. Anyway, here's what dmesg says: ~~~~ [ 54.440439] wlan0: authenticate with b0:b2:dc:d1:99:a4 [ 54.453312] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded [ 54.467051] wlan0: send auth to b0:b2:dc:d1:99:a4 (try 1/3) [ 54.468936] wlan0: authenticated [ 54.469132] b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use [ 54.469690] wlan0: associate with b0:b2:dc:d1:99:a4 (try 1/3) [ 54.473986] wlan0: RX AssocResp from b0:b2:dc:d1:99:a4 (capab=0xc11 status=0 aid=3) [ 54.474823] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 54.474920] wlan0: associated [ 71.715677] fuse init (API version 7.20) [ 179.609102] ieee80211 phy0: wlan0: No probe response from AP b0:b2:dc:d1:99:a4 after 500ms, disconnecting. [ 179.642723] cfg80211: Calling CRDA for country: SE [ 180.950693] wlan0: authenticate with b0:b2:dc:d1:99:a4 [ 180.963233] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded [ 180.963421] wlan0: send auth to b0:b2:dc:d1:99:a4 (try 1/3) [ 181.165948] wlan0: send auth to b0:b2:dc:d1:99:a4 (try 2/3) [ 181.368875] wlan0: send auth to b0:b2:dc:d1:99:a4 (try 3/3) [ 181.571809] wlan0: authentication with b0:b2:dc:d1:99:a4 timed out ~~~~ Not sure if it matters, but the laptop was bought in the UK and we've since moved to Sweden (I did notice the mention of SE above). As you understand I'm pretty ignorant about this whole thing, so I can't make heads nor tails of it. After booting the network is up, for a little while, just enough to ping the router a few times: ~~~~ % ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=11.4 ms 64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=10.0 ms 64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=4.51 ms 64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=6.56 ms 64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=5.24 ms 64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=14.2 ms ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ^C --- 192.168.1.254 ping statistics --- 12 packets transmitted, 6 received, 50% packet loss, time 30030ms rtt min/avg/max/mdev = 4.510/8.686/14.278/3.527 ms ~~~~ Any suggestion on what I can do to fix it is welcome. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@xxxxxxxxxxxx jabber: magnus@xxxxxxxxxxxx twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay
Attachment:
pgpJWphogoKRH.pgp
Description: PGP signature
