Re: [arch-general] Broadcom B43 problems
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: mag...@therning.org jabber: mag...@therning.org 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 pgpxAwX2tuC80.pgp Description: PGP signature
Re: [arch-general] Broadcom B43 problems
On 26 Mar 2013 11:55, Magnus Therning mag...@therning.org wrote: 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: mag...@therning.org jabber: mag...@therning.org 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 I had problems as well with archlinux and Ubuntu b43 driver. I tried many times without success so I abandoned the idea and bought a new WiFi card for my laptop. Not helpful I know..
Re: [arch-general] Broadcom B43 problems
Which card did you bought? Cordialement, Julien Pecqueur
Re: [arch-general] Broadcom B43 problems
On Mar 26, 2013 7:55 AM, Magnus Therning mag...@therning.org wrote: 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. For what it's worth, I had a broadcom chipset in my netbook that gave me nothing but trouble. I bought a ten dollar realtek chipset on ebay, and my life has markedly improved since. If you can replace the wifi chipset, I would recommend you to consider it.
Re: [arch-general] Broadcom B43 problems
There are few steps with can help you trobleshoot this:
1. try to connect with plain wpa_supplicant. Kill networkmanager,
wpa_supplicant and dhcpcd and everything else; create configuration
file:
network={
ssid=$WIRELESS_SSID
psk=$WIRELESS_PASSPHRASE
}
Save it as wpa_supplicant.conf, start wpa_supplicant:
wpa_supplicant -iwlan0 -c/home/magnus/wpa_supplicant.conf, try to
fetch configuration from dhcp: dhcpcd wlan0. This way nm won't mess
with wifi chipset.
2. you can also load b43 module with verbose=3 hwtkip=0 nohwcrypt=1
or other options (check modinfo b43).
3. maybe latest kernel just have issues with this chip, try linux-lts.
--
Krzysztof Warzecha
Re: [arch-general] Broadcom B43 problems
On 03/26/13 at 01:37pm, Julien Pecqueur wrote: Which card did you bought? Cordialement, Julien Pecqueur There was a mention above about buying a Realtek card. I just want to mention that my experience with Realtek wireless chipsets has been nothing but hell. My Thinkpad came with a Realtek that used the rtl8192ce module, and it was terrible. I recently was forced to try it again, and it had gotten better, but was still of pretty questionable quality. The first time I replaced it I was able to flash a modified bios that removed the Lenovo wifi card whitelist, and replaced it with an Intel Centrino Advanced-N 6235 which was amazing. This time, I was unable to remove the whitelist (or rather flash the newly modified bios, removal was the same as always) so I was able to find the Intel Centrino Wireless-N 2230 that was apparently an option with this laptop. My experience with Intel wireless has been fantastic, and I highly recommend them. I have also been told that Atheros support is very good as well. Though it has been quite some time since my last use of an Atheros chipset on Linux (my old MacBook 2,1 has an Atheros, but that machine has since gone back to OS X as a family computer). -- Curtis Shimamoto sugar.and.scruffy [at] gmail.com
Re: [arch-general] Broadcom B43 problems
On 26 Mar 2013 15:56, Curtis Shimamoto sugar.and.scru...@gmail.com wrote: On 03/26/13 at 01:37pm, Julien Pecqueur wrote: Which card did you bought? Cordialement, Julien Pecqueur There was a mention above about buying a Realtek card. I just want to mention that my experience with Realtek wireless chipsets has been nothing but hell. My Thinkpad came with a Realtek that used the rtl8192ce module, and it was terrible. I recently was forced to try it again, and it had gotten better, but was still of pretty questionable quality. The first time I replaced it I was able to flash a modified bios that removed the Lenovo wifi card whitelist, and replaced it with an Intel Centrino Advanced-N 6235 which was amazing. This time, I was unable to remove the whitelist (or rather flash the newly modified bios, removal was the same as always) so I was able to find the Intel Centrino Wireless-N 2230 that was apparently an option with this laptop. My experience with Intel wireless has been fantastic, and I highly recommend them. I have also been told that Atheros support is very good as well. Though it has been quite some time since my last use of an Atheros chipset on Linux (my old MacBook 2,1 has an Atheros, but that machine has since gone back to OS X as a family computer). -- Curtis Shimamoto sugar.and.scruffy [at] gmail.com I had mine replaced with an Intel as it was an option foot my Dell Latitude E4300 laptop.
Re: [arch-general] Broadcom B43 problems
On Mar 26, 2013 10:56 AM, Curtis Shimamoto sugar.and.scru...@gmail.com wrote: On 03/26/13 at 01:37pm, Julien Pecqueur wrote: Which card did you bought? Cordialement, Julien Pecqueur There was a mention above about buying a Realtek card. I just want to mention that my experience with Realtek wireless chipsets has been nothing but hell. My Thinkpad came with a Realtek that used the rtl8192ce module, and it was terrible. I recently was forced to try it again, and it had gotten better, but was still of pretty questionable quality. The first time I replaced it I was able to flash a modified bios that removed the Lenovo wifi card whitelist, and replaced it with an Intel Centrino Advanced-N 6235 which was amazing. This time, I was unable to remove the whitelist (or rather flash the newly modified bios, removal was the same as always) so I was able to find the Intel Centrino Wireless-N 2230 that was apparently an option with this laptop. My experience with Intel wireless has been fantastic, and I highly recommend them. I have also been told that Atheros support is very good as well. Though it has been quite some time since my last use of an Atheros chipset on Linux (my old MacBook 2,1 has an Atheros, but that machine has since gone back to OS X as a family computer). -- Curtis Shimamoto sugar.and.scruffy [at] gmail.com I just wanted to add that I have had good experience with Atheros as well (ath9k driver in particular). It should work out of box.
Re: [arch-general] Broadcom B43 problems
Sounds like a QoS problem, so why don't you try this: https://bbs.archlinux.org/viewtopic.php?pid=780128#p780128
Re: [arch-general] Broadcom B43 problems
On Tue, Mar 26, 2013 at 8:37 AM, Julien Pecqueur jpe...@gmail.com wrote: Which card did you bought? Cordialement, Julien Pecqueur http://www.amazon.com/HP-RTL8188CE-Wireless-639967-001-640926-001/dp/B008U5B8B2 Not this exact card, but close to it. I got mine on ebay, any of the common realtek chipsets will work far and away better than broadcom. Broadcom's linux support is (for lack of a nicer term) terrible. -- --Zootboy Sent from some sort of computing device.
Re: [arch-general] Broadcom B43 problems
On Mar 26, 2013 11:56 AM, Curtis Shimamoto sugar.and.scru...@gmail.com wrote: On 03/26/13 at 01:37pm, Julien Pecqueur wrote: Which card did you bought? Cordialement, Julien Pecqueur There was a mention above about buying a Realtek card. I just want to mention that my experience with Realtek wireless chipsets has been nothing but hell. My Thinkpad came with a Realtek that used the rtl8192ce module, and it was terrible. I recently was forced to try it again, and it had gotten better, but was still of pretty questionable quality. The first time I replaced it I was able to flash a modified bios that removed the Lenovo wifi card whitelist, and replaced it with an Intel Centrino Advanced-N 6235 which was amazing. [snip] Curtis Shimamoto sugar.and.scruffy [at] gmail.com Might I ask what problems you had? My experience with the 8192 was poor only because the drivers were in staging until the 3.0 kernel release. I switched to the 8188 in my netbook and the 8171 (maybe, my memory is failing me on that one) on my main laptop. Not all realtek chipsets are equal...
Re: [arch-general] Broadcom B43 problems
On 03/26/13 at 02:02pm, Sean Greenslade wrote: On Mar 26, 2013 11:56 AM, Curtis Shimamoto sugar.and.scru...@gmail.com wrote: On 03/26/13 at 01:37pm, Julien Pecqueur wrote: Which card did you bought? Cordialement, Julien Pecqueur There was a mention above about buying a Realtek card. I just want to mention that my experience with Realtek wireless chipsets has been nothing but hell. My Thinkpad came with a Realtek that used the rtl8192ce module, and it was terrible. I recently was forced to try it again, and it had gotten better, but was still of pretty questionable quality. The first time I replaced it I was able to flash a modified bios that removed the Lenovo wifi card whitelist, and replaced it with an Intel Centrino Advanced-N 6235 which was amazing. [snip] Curtis Shimamoto sugar.and.scruffy [at] gmail.com Might I ask what problems you had? My experience with the 8192 was poor only because the drivers were in staging until the 3.0 kernel release. I switched to the 8188 in my netbook and the 8171 (maybe, my memory is failing me on that one) on my main laptop. Not all realtek chipsets are equal... No not all Realtek chipsets are created equal. My issues were with some crazy latency any time I tried to do anything. Once it started loading something, likea web page for instance, it was fine. But getting to that point was just really sluggish. The first time I used it was when I got my Thinkpad in mid 2012, and it was so horribly painful it was awful. It was so bad that it would actually case other devices on the network to lose their connection sometimes. I am not sure how or why this would happen, but it wouldn't if I were not connected. The second time, was just a couple weeks ago when I had to have the mobo replaced. I now have the Lenovo wifi whitelist back, so I had to resort to the Realtek. It was much much better than the first time, but when I got an Intel to stick in the machine, it was like night and day. This particular module (the rtl8192ce) I see people having issues with all the time on the forums. So I know that the pain is not mine alone. I have not had the chance to try other Realtek cards, but you are not the first to tell me that there are others out there that work well. Still this chipset seems to be particularly common today, so I just wanted to throw this out there. I think it was the rtl8188/8192? I don't know specifically w/o putting the card back into the machine. -- Curtis Shimamoto sugar.and.scruffy [at] gmail.com
Re: [arch-general] Broadcom B43 problems
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? Cordialement, Julien Pecqueur -- http://julienpecqueur.net Le 6 mars 2013 22:59, Magnus Therning mag...@therning.org a écrit : I have seen some indications that my Broadcom B43 *ought* to work with the kernel's b43 driver, but I've never managed to get it working on my own. I'd love to be able to switch away from the broadcom-wl package is possible. Using a kernel from a few days ago, 3.7.9 and the b43-firmware package from AUR I only get as far as connecting to my router (at least that's what NetworkManager says), but then I can't actually connect to any site. If I then bring down the network and then bring it back up again the connection to the router will fail (NetworkManager keeps asking for the password). Any suggestions on what might be causing this, and what I should try next? /M % lspci -nn|grep Broadcom 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Wireless network uses WPA2 -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org 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
[arch-general] Broadcom B43 problems
I have seen some indications that my Broadcom B43 *ought* to work with the kernel's b43 driver, but I've never managed to get it working on my own. I'd love to be able to switch away from the broadcom-wl package is possible. Using a kernel from a few days ago, 3.7.9 and the b43-firmware package from AUR I only get as far as connecting to my router (at least that's what NetworkManager says), but then I can't actually connect to any site. If I then bring down the network and then bring it back up again the connection to the router will fail (NetworkManager keeps asking for the password). Any suggestions on what might be causing this, and what I should try next? /M % lspci -nn|grep Broadcom 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Wireless network uses WPA2 -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org 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 pgpCkGmdcAmxe.pgp Description: PGP signature
