* Faulty 14e4:4315 (BCM4312)?
@ 2011-06-08 20:25 Rafał Miłecki
2011-06-08 20:37 ` Gábor Stefanik
0 siblings, 1 reply; 16+ messages in thread
From: Rafał Miłecki @ 2011-06-08 20:25 UTC (permalink / raw)
To: b43-dev
Hey,
I've just discovered I can not connect with my 14e4:4315 to my home network.
dmesg:
[ 119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz.
[ 121.130067] b43-phy0 debug: Chip initialized
[ 121.130348] b43-phy0 debug: 64-bit DMA initialized
[ 121.130416] b43-phy0 debug: QoS enabled
[ 121.139857] b43-phy0 debug: Wireless interface started
[ 121.145095] b43-phy0 debug: Adding Interface type 2
[ 121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1)
[ 128.300285] wlan0: authenticated
[ 128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1)
[ 128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411
status=0 aid=3)
[ 128.303715] wlan0: associated
[ 128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 128.429557] b43-phy0 debug: Using hardware based encryption for
keyidx: 0, mac: 00:23:69:c2:65:06
[ 128.429611] b43-phy0 debug: Using hardware based encryption for
keyidx: 2, mac: ff:ff:ff:ff:ff:ff
[ 132.208036] ieee80211 phy0: wlan0: No probe response from AP
00:23:69:c2:65:06 after 500ms, disconnecting.
wpa_supplicant fills my console with:
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz)
> Associated with 00:23:69:c2:65:06
> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP]
> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=]
> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0
It seems it was already reported, for example in:
"No probe response from AP <address> after 500ms, disconnecting." by
Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800.
http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html
What's really surprising I can not connect to this network also when
using wl 5.100.82.38!
Did anyone of you already got some faulty BCM4312 hardware? Did it
behave like this? I'm surprised than scanning works, but connection is
quickly dropped. It does not really sound like a faulty hardware.
Of course I'll experiment with this more, for now just early-asking.
--
Rafa?
^ permalink raw reply [flat|nested] 16+ messages in thread* Faulty 14e4:4315 (BCM4312)? 2011-06-08 20:25 Faulty 14e4:4315 (BCM4312)? Rafał Miłecki @ 2011-06-08 20:37 ` Gábor Stefanik 2011-06-08 20:59 ` Rafał Miłecki 2011-06-08 20:59 ` Rafał Miłecki 0 siblings, 2 replies; 16+ messages in thread From: Gábor Stefanik @ 2011-06-08 20:37 UTC (permalink / raw) To: b43-dev 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: > Hey, > > I've just discovered I can not connect with my 14e4:4315 to my home network. > > dmesg: > [ ?119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > [ ?119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. > [ ?121.130067] b43-phy0 debug: Chip initialized > [ ?121.130348] b43-phy0 debug: 64-bit DMA initialized > [ ?121.130416] b43-phy0 debug: QoS enabled > [ ?121.139857] b43-phy0 debug: Wireless interface started > [ ?121.145095] b43-phy0 debug: Adding Interface type 2 > [ ?121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ ?128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1) > [ ?128.300285] wlan0: authenticated > [ ?128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1) > [ ?128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411 > status=0 aid=3) > [ ?128.303715] wlan0: associated > [ ?128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > [ ?128.429557] b43-phy0 debug: Using hardware based encryption for > keyidx: 0, mac: 00:23:69:c2:65:06 > [ ?128.429611] b43-phy0 debug: Using hardware based encryption for > keyidx: 2, mac: ff:ff:ff:ff:ff:ff > [ ?132.208036] ieee80211 phy0: wlan0: No probe response from AP > 00:23:69:c2:65:06 after 500ms, disconnecting. > > wpa_supplicant fills my console with: >> ioctl[SIOCSIWENCODEEXT]: Invalid argument >> ioctl[SIOCSIWENCODEEXT]: Invalid argument >> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz) >> Associated with 00:23:69:c2:65:06 >> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP] >> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=] >> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0 > > It seems it was already reported, for example in: > "No probe response from AP <address> after 500ms, disconnecting." by > Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800. > http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html > > What's really surprising I can not connect to this network also when > using wl 5.100.82.38! > > Did anyone of you already got some faulty BCM4312 hardware? Did it > behave like this? I'm surprised than scanning works, but connection is > quickly dropped. It does not really sound like a faulty hardware. Chances are, your card can happily communicate with the AP using CCK, but once it tries to do OFDM, it fails. Is the AP close enough for OFDM communication? > > Of course I'll experiment with this more, for now just early-asking. > > -- > Rafa? > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 20:37 ` Gábor Stefanik @ 2011-06-08 20:59 ` Rafał Miłecki 2011-06-08 20:59 ` Rafał Miłecki 1 sibling, 0 replies; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 20:59 UTC (permalink / raw) To: b43-dev W dniu 8 czerwca 2011 22:37 u?ytkownik G?bor Stefanik <netrolller.3d@gmail.com> napisa?: > 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: >> Hey, >> >> I've just discovered I can not connect with my 14e4:4315 to my home network. >> >> dmesg: >> [ ?119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) >> [ ?119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. >> [ ?121.130067] b43-phy0 debug: Chip initialized >> [ ?121.130348] b43-phy0 debug: 64-bit DMA initialized >> [ ?121.130416] b43-phy0 debug: QoS enabled >> [ ?121.139857] b43-phy0 debug: Wireless interface started >> [ ?121.145095] b43-phy0 debug: Adding Interface type 2 >> [ ?121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready >> [ ?128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1) >> [ ?128.300285] wlan0: authenticated >> [ ?128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1) >> [ ?128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411 >> status=0 aid=3) >> [ ?128.303715] wlan0: associated >> [ ?128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> [ ?128.429557] b43-phy0 debug: Using hardware based encryption for >> keyidx: 0, mac: 00:23:69:c2:65:06 >> [ ?128.429611] b43-phy0 debug: Using hardware based encryption for >> keyidx: 2, mac: ff:ff:ff:ff:ff:ff >> [ ?132.208036] ieee80211 phy0: wlan0: No probe response from AP >> 00:23:69:c2:65:06 after 500ms, disconnecting. >> >> wpa_supplicant fills my console with: >>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz) >>> Associated with 00:23:69:c2:65:06 >>> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP] >>> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=] >>> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0 >> >> It seems it was already reported, for example in: >> "No probe response from AP <address> after 500ms, disconnecting." by >> Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800. >> http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html >> >> What's really surprising I can not connect to this network also when >> using wl 5.100.82.38! >> >> Did anyone of you already got some faulty BCM4312 hardware? Did it >> behave like this? I'm surprised than scanning works, but connection is >> quickly dropped. It does not really sound like a faulty hardware. > > Chances are, your card can happily communicate with the AP using CCK, > but once it tries to do OFDM, it fails. > Is the AP close enough for OFDM communication? Interesting, thanks! I surely will experiment with forcing rate to 1/2/5.5/11. I'll also try applying my old patch for TX ctl word1. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 20:37 ` Gábor Stefanik 2011-06-08 20:59 ` Rafał Miłecki @ 2011-06-08 20:59 ` Rafał Miłecki 2011-06-08 21:08 ` Gábor Stefanik 1 sibling, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 20:59 UTC (permalink / raw) To: b43-dev W dniu 8 czerwca 2011 22:37 u?ytkownik G?bor Stefanik <netrolller.3d@gmail.com> napisa?: > 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: >> Hey, >> >> I've just discovered I can not connect with my 14e4:4315 to my home network. >> >> dmesg: >> [ ?119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) >> [ ?119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. >> [ ?121.130067] b43-phy0 debug: Chip initialized >> [ ?121.130348] b43-phy0 debug: 64-bit DMA initialized >> [ ?121.130416] b43-phy0 debug: QoS enabled >> [ ?121.139857] b43-phy0 debug: Wireless interface started >> [ ?121.145095] b43-phy0 debug: Adding Interface type 2 >> [ ?121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready >> [ ?128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1) >> [ ?128.300285] wlan0: authenticated >> [ ?128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1) >> [ ?128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411 >> status=0 aid=3) >> [ ?128.303715] wlan0: associated >> [ ?128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> [ ?128.429557] b43-phy0 debug: Using hardware based encryption for >> keyidx: 0, mac: 00:23:69:c2:65:06 >> [ ?128.429611] b43-phy0 debug: Using hardware based encryption for >> keyidx: 2, mac: ff:ff:ff:ff:ff:ff >> [ ?132.208036] ieee80211 phy0: wlan0: No probe response from AP >> 00:23:69:c2:65:06 after 500ms, disconnecting. >> >> wpa_supplicant fills my console with: >>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz) >>> Associated with 00:23:69:c2:65:06 >>> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP] >>> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=] >>> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0 >> >> It seems it was already reported, for example in: >> "No probe response from AP <address> after 500ms, disconnecting." by >> Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800. >> http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html >> >> What's really surprising I can not connect to this network also when >> using wl 5.100.82.38! >> >> Did anyone of you already got some faulty BCM4312 hardware? Did it >> behave like this? I'm surprised than scanning works, but connection is >> quickly dropped. It does not really sound like a faulty hardware. > > Chances are, your card can happily communicate with the AP using CCK, > but once it tries to do OFDM, it fails. > Is the AP close enough for OFDM communication? My AP is about 2 meters from the card, antennas are attached OFC. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 20:59 ` Rafał Miłecki @ 2011-06-08 21:08 ` Gábor Stefanik 2011-06-08 21:19 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Gábor Stefanik @ 2011-06-08 21:08 UTC (permalink / raw) To: b43-dev 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: > W dniu 8 czerwca 2011 22:37 u?ytkownik G?bor Stefanik > <netrolller.3d@gmail.com> napisa?: >> 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: >>> Hey, >>> >>> I've just discovered I can not connect with my 14e4:4315 to my home network. >>> >>> dmesg: >>> [ ?119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) >>> [ ?119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. >>> [ ?121.130067] b43-phy0 debug: Chip initialized >>> [ ?121.130348] b43-phy0 debug: 64-bit DMA initialized >>> [ ?121.130416] b43-phy0 debug: QoS enabled >>> [ ?121.139857] b43-phy0 debug: Wireless interface started >>> [ ?121.145095] b43-phy0 debug: Adding Interface type 2 >>> [ ?121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready >>> [ ?128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1) >>> [ ?128.300285] wlan0: authenticated >>> [ ?128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1) >>> [ ?128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411 >>> status=0 aid=3) >>> [ ?128.303715] wlan0: associated >>> [ ?128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >>> [ ?128.429557] b43-phy0 debug: Using hardware based encryption for >>> keyidx: 0, mac: 00:23:69:c2:65:06 >>> [ ?128.429611] b43-phy0 debug: Using hardware based encryption for >>> keyidx: 2, mac: ff:ff:ff:ff:ff:ff >>> [ ?132.208036] ieee80211 phy0: wlan0: No probe response from AP >>> 00:23:69:c2:65:06 after 500ms, disconnecting. >>> >>> wpa_supplicant fills my console with: >>>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>>> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz) >>>> Associated with 00:23:69:c2:65:06 >>>> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP] >>>> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=] >>>> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0 >>> >>> It seems it was already reported, for example in: >>> "No probe response from AP <address> after 500ms, disconnecting." by >>> Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800. >>> http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html >>> >>> What's really surprising I can not connect to this network also when >>> using wl 5.100.82.38! >>> >>> Did anyone of you already got some faulty BCM4312 hardware? Did it >>> behave like this? I'm surprised than scanning works, but connection is >>> quickly dropped. It does not really sound like a faulty hardware. >> >> Chances are, your card can happily communicate with the AP using CCK, >> but once it tries to do OFDM, it fails. >> Is the AP close enough for OFDM communication? > > My AP is about 2 meters from the card, antennas are attached OFC. > > -- > Rafa? > You are too close to the AP then - the AP's signal is jamming the card's receiver (or vice versa). Again, CCK is more resilient in this aspect than OFDM, hence no problems until association. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 21:08 ` Gábor Stefanik @ 2011-06-08 21:19 ` Rafał Miłecki 2011-06-08 22:55 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 21:19 UTC (permalink / raw) To: b43-dev W dniu 8 czerwca 2011 23:08 u?ytkownik G?bor Stefanik <netrolller.3d@gmail.com> napisa?: > 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: >> W dniu 8 czerwca 2011 22:37 u?ytkownik G?bor Stefanik >> <netrolller.3d@gmail.com> napisa?: >>> 2011/6/8 Rafa? Mi?ecki <zajec5@gmail.com>: >>>> Hey, >>>> >>>> I've just discovered I can not connect with my 14e4:4315 to my home network. >>>> >>>> dmesg: >>>> [ ?119.744050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) >>>> [ ?119.746744] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. >>>> [ ?121.130067] b43-phy0 debug: Chip initialized >>>> [ ?121.130348] b43-phy0 debug: 64-bit DMA initialized >>>> [ ?121.130416] b43-phy0 debug: QoS enabled >>>> [ ?121.139857] b43-phy0 debug: Wireless interface started >>>> [ ?121.145095] b43-phy0 debug: Adding Interface type 2 >>>> [ ?121.145605] ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>> [ ?128.295371] wlan0: authenticate with 00:23:69:c2:65:06 (try 1) >>>> [ ?128.300285] wlan0: authenticated >>>> [ ?128.300319] wlan0: associate with 00:23:69:c2:65:06 (try 1) >>>> [ ?128.303709] wlan0: RX AssocResp from 00:23:69:c2:65:06 (capab=0x411 >>>> status=0 aid=3) >>>> [ ?128.303715] wlan0: associated >>>> [ ?128.304711] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >>>> [ ?128.429557] b43-phy0 debug: Using hardware based encryption for >>>> keyidx: 0, mac: 00:23:69:c2:65:06 >>>> [ ?128.429611] b43-phy0 debug: Using hardware based encryption for >>>> keyidx: 2, mac: ff:ff:ff:ff:ff:ff >>>> [ ?132.208036] ieee80211 phy0: wlan0: No probe response from AP >>>> 00:23:69:c2:65:06 after 500ms, disconnecting. >>>> >>>> wpa_supplicant fills my console with: >>>>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>>>> ioctl[SIOCSIWENCODEEXT]: Invalid argument >>>>> Trying to associate with 00:23:69:c2:65:06 (SSID='zajec_poznan_160' freq=2427 MHz) >>>>> Associated with 00:23:69:c2:65:06 >>>>> WPA: Key negotiation completed with 00:23:69:c2:65:06 [PTK=CCMP GTK=CCMP] >>>>> CTRL-EVENT-CONNECTED - Connection to 00:23:69:c2:65:06 completed (auth) [id=0 id_str=] >>>>> CTRL-EVENT-DISCONNECTED bssid=00:23:69:c2:65:06 reason=0 >>>> >>>> It seems it was already reported, for example in: >>>> "No probe response from AP <address> after 500ms, disconnecting." by >>>> Miklos Vajna on Thu, 14 Jan 2010 17:29:20 -0800. >>>> http://www.mail-archive.com/bcm43xx-dev at lists.berlios.de/msg09481.html >>>> >>>> What's really surprising I can not connect to this network also when >>>> using wl 5.100.82.38! >>>> >>>> Did anyone of you already got some faulty BCM4312 hardware? Did it >>>> behave like this? I'm surprised than scanning works, but connection is >>>> quickly dropped. It does not really sound like a faulty hardware. >>> >>> Chances are, your card can happily communicate with the AP using CCK, >>> but once it tries to do OFDM, it fails. >>> Is the AP close enough for OFDM communication? >> >> My AP is about 2 meters from the card, antennas are attached OFC. >> >> -- >> Rafa? >> > > You are too close to the AP then - the AP's signal is jamming the > card's receiver (or vice versa). Again, CCK is more resilient in this > aspect than OFDM, hence no problems until association. I believe that even if one is jamming the other, connection should still work. I can accept lower performance, packet loss, but not disconnection at all. Actually after receiving tip about OFDM from you, I went back to the machine and checked for the news. It was running wpa_supplicant for all this time. I'm glad to say dmesg said the same thing you did. TX transmission errors :) The old known friend from N-PHY cards. Forcing rate to 1M workarounded this issue. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 21:19 ` Rafał Miłecki @ 2011-06-08 22:55 ` Rafał Miłecki 2011-06-08 23:05 ` Larry Finger 0 siblings, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 22:55 UTC (permalink / raw) To: b43-dev W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?: > Forcing rate to 1M workarounded this issue. Working state seems to be random and not related to rate. Even if I manage to connect, I do not have a chance to achieve 1MB/s. At least ndiswrapper seems to work fine. I got easy&stable connection and speed around 10MB/s. Nice to know my card is not faulty. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 22:55 ` Rafał Miłecki @ 2011-06-08 23:05 ` Larry Finger 2011-06-08 23:14 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Larry Finger @ 2011-06-08 23:05 UTC (permalink / raw) To: b43-dev On 06/08/2011 05:55 PM, Rafa? Mi?ecki wrote: > W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com> napisa?: >> Forcing rate to 1M workarounded this issue. > > Working state seems to be random and not related to rate. > > Even if I manage to connect, I do not have a chance to achieve 1MB/s. > > At least ndiswrapper seems to work fine. I got easy&stable connection > and speed around 10MB/s. Nice to know my card is not faulty. What is the nature of that 4315 card? Mine is currently in use and has been working correctly. This is one of the original PCIe units with the SPROM at 0x1000. When I use the one in the netbook with the SPROM at 0x0800, the unit is a lot less stable. Larry ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 23:05 ` Larry Finger @ 2011-06-08 23:14 ` Rafał Miłecki 2011-06-08 23:30 ` Larry Finger 0 siblings, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 23:14 UTC (permalink / raw) To: b43-dev W dniu 9 czerwca 2011 01:05 u?ytkownik Larry Finger <Larry.Finger@lwfinger.net> napisa?: > On 06/08/2011 05:55 PM, Rafa? Mi?ecki wrote: >> >> W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com> >> ?napisa?: >>> >>> Forcing rate to 1M workarounded this issue. >> >> Working state seems to be random and not related to rate. >> >> Even if I manage to connect, I do not have a chance to achieve 1MB/s. >> >> At least ndiswrapper seems to work fine. I got easy&stable connection >> and speed around 10MB/s. Nice to know my card is not faulty. > > What is the nature of that 4315 card? Mine is currently in use and has been > working correctly. This is one of the original PCIe units with the SPROM at > 0x1000. > > When I use the one in the netbook with the SPROM at 0x0800, the unit is a > lot less stable. 14e4:4315 Mini PCIe MMIO 16K BCM94312HMG / DW1397 SSB 2.6 BCM4312 SPROM 8 (0x1000) PMU 1 PHY LP / 1 RADIO 0x2062 / 2 -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 23:14 ` Rafał Miłecki @ 2011-06-08 23:30 ` Larry Finger 2011-06-08 23:47 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Larry Finger @ 2011-06-08 23:30 UTC (permalink / raw) To: b43-dev On 06/08/2011 06:14 PM, Rafa? Mi?ecki wrote: > W dniu 9 czerwca 2011 01:05 u?ytkownik Larry Finger > <Larry.Finger@lwfinger.net> napisa?: >> On 06/08/2011 05:55 PM, Rafa? Mi?ecki wrote: >>> >>> W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com> >>> napisa?: >>>> >>>> Forcing rate to 1M workarounded this issue. >>> >>> Working state seems to be random and not related to rate. >>> >>> Even if I manage to connect, I do not have a chance to achieve 1MB/s. >>> >>> At least ndiswrapper seems to work fine. I got easy&stable connection >>> and speed around 10MB/s. Nice to know my card is not faulty. >> >> What is the nature of that 4315 card? Mine is currently in use and has been >> working correctly. This is one of the original PCIe units with the SPROM at >> 0x1000. >> >> When I use the one in the netbook with the SPROM at 0x0800, the unit is a >> lot less stable. > > 14e4:4315 > Mini PCIe > MMIO 16K > BCM94312HMG / DW1397 > SSB 2.6 > BCM4312 > SPROM 8 (0x1000) > PMU 1 > PHY LP / 1 > RADIO 0x2062 / 2 ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) ssb: chipcommon status is 0x10 ssb: Found rev 1 PMU (capabilities 0x02A62F01) ssb: SPROM offset is 0x1000 ssb: SPROM revision 8 detected. ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0 b43-phy0: Broadcom 4312 WLAN found (core revision 15) b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 b43 ssb0:0: wlan0: Features changed: 0x00004800 -> 0x00004000 b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01) b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. b43-phy0 debug: Chip initialized b43-phy0 debug: 64-bit DMA initialized b43-phy0 debug: QoS enabled 04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01) Subsystem: Hewlett-Packard Company BCM4312 802.11b/g Wireless LAN Controller [103c:137c] Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at fc000000 (64-bit, non-prefetchable) [size=16K] Other than mine is HP-branded, they appear to be the same. I am also 2 m from the AP and my rate is 36 Mbps. Larry ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 23:30 ` Larry Finger @ 2011-06-08 23:47 ` Rafał Miłecki 2011-06-09 0:27 ` Larry Finger 2011-06-11 7:53 ` Rafał Miłecki 0 siblings, 2 replies; 16+ messages in thread From: Rafał Miłecki @ 2011-06-08 23:47 UTC (permalink / raw) To: b43-dev W dniu 9 czerwca 2011 01:30 u?ytkownik Larry Finger <Larry.Finger@lwfinger.net> napisa?: > On 06/08/2011 06:14 PM, Rafa? Mi?ecki wrote: >> >> W dniu 9 czerwca 2011 01:05 u?ytkownik Larry Finger >> <Larry.Finger@lwfinger.net> ?napisa?: >>> >>> On 06/08/2011 05:55 PM, Rafa? Mi?ecki wrote: >>>> >>>> W dniu 8 czerwca 2011 23:19 u?ytkownik Rafa? Mi?ecki<zajec5@gmail.com> >>>> ?napisa?: >>>>> >>>>> Forcing rate to 1M workarounded this issue. >>>> >>>> Working state seems to be random and not related to rate. >>>> >>>> Even if I manage to connect, I do not have a chance to achieve 1MB/s. >>>> >>>> At least ndiswrapper seems to work fine. I got easy&stable connection >>>> and speed around 10MB/s. Nice to know my card is not faulty. >>> >>> What is the nature of that 4315 card? Mine is currently in use and has >>> been >>> working correctly. This is one of the original PCIe units with the SPROM >>> at >>> 0x1000. >>> >>> When I use the one in the netbook with the SPROM at 0x0800, the unit is a >>> lot less stable. >> >> 14e4:4315 >> Mini PCIe >> MMIO 16K >> BCM94312HMG / DW1397 >> SSB 2.6 >> BCM4312 >> SPROM 8 (0x1000) >> PMU 1 >> PHY LP / 1 >> RADIO 0x2062 / 2 > > ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) > ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) > ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) > ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) > ssb: chipcommon status is 0x10 > ssb: Found rev 1 PMU (capabilities 0x02A62F01) > ssb: SPROM offset is 0x1000 > ssb: SPROM revision 8 detected. > ssb: Sonics Silicon Backplane found on PCI device 0000:04:00.0 > b43-phy0: Broadcom 4312 WLAN found (core revision 15) > b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1 > b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 > b43 ssb0:0: wlan0: Features changed: 0x00004800 -> 0x00004000 > b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01) > b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. > b43-phy0 debug: Chip initialized > b43-phy0 debug: 64-bit DMA initialized > b43-phy0 debug: QoS enabled > > 04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g > LP-PHY [14e4:4315] (rev 01) > ? ? ? ?Subsystem: Hewlett-Packard Company BCM4312 802.11b/g Wireless LAN > Controller [103c:137c] > ? ? ? ?Flags: bus master, fast devsel, latency 0, IRQ 21 > ? ? ? ?Memory at fc000000 (64-bit, non-prefetchable) [size=16K] > > Other than mine is HP-branded, they appear to be the same. I am also 2 m > from the AP and my rate is 36 Mbps. Yeah, that's exactly the same card. The same cores, revisions, cc status, PMU capabilities. I just didn't try 508.1084 firmware. I've been playing with 410.2160, 478-104, 508.1103, 508.1107 however, so switching to your's version probably won't help. What is your network encryption and freq? BSS 00:23:69:c2:65:06 (on wlan0) TSF: 665805184 usec (0d, 00:11:05) freq: 2427 beacon interval: 100 capability: ESS Privacy ShortSlotTime (0x0411) signal: -14.00 dBm last seen: 778 ms ago SSID: zajec_poznan_160 Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 DS Parameter set: channel 4 ERP: <no flags> Extended supported rates: 24.0 36.0 48.0 54.0 RSN: * Version: 1 * Group cipher: CCMP * Pairwise ciphers: CCMP * Authentication suites: PSK * Capabilities: 16-PTKSA-RC (0x000c) WMM: * Parameter version 1 * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec network={ ssid="zajec_poznan_160" key_mgmt=WPA-PSK proto=WPA RSN pairwise=CCMP TKIP group=CCMP TKIP psk="psssst" } -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 23:47 ` Rafał Miłecki @ 2011-06-09 0:27 ` Larry Finger 2011-06-11 7:53 ` Rafał Miłecki 1 sibling, 0 replies; 16+ messages in thread From: Larry Finger @ 2011-06-09 0:27 UTC (permalink / raw) To: b43-dev On 06/08/2011 06:47 PM, Rafa? Mi?ecki wrote: > > Yeah, that's exactly the same card. The same cores, revisions, cc > status, PMU capabilities. > > I just didn't try 508.1084 firmware. I've been playing with 410.2160, > 478-104, 508.1103, 508.1107 however, so switching to your's version > probably won't help. > > What is your network encryption and freq? > > BSS 00:23:69:c2:65:06 (on wlan0) > TSF: 665805184 usec (0d, 00:11:05) > freq: 2427 > beacon interval: 100 > capability: ESS Privacy ShortSlotTime (0x0411) > signal: -14.00 dBm > last seen: 778 ms ago > SSID: zajec_poznan_160 > Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 > DS Parameter set: channel 4 > ERP:<no flags> > Extended supported rates: 24.0 36.0 48.0 54.0 > RSN: * Version: 1 > * Group cipher: CCMP > * Pairwise ciphers: CCMP > * Authentication suites: PSK > * Capabilities: 16-PTKSA-RC (0x000c) > WMM: * Parameter version 1 > * BE: CW 15-1023, AIFSN 3 > * BK: CW 15-1023, AIFSN 7 > * VI: CW 7-15, AIFSN 2, TXOP 3008 usec > * VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec > > network={ > ssid="zajec_poznan_160" > key_mgmt=WPA-PSK > proto=WPA RSN > pairwise=CCMP TKIP > group=CCMP TKIP > psk="psssst" > } > My scan data are: Cell 02 - Address: C0:3F:0E:BE:2B:44 Channel:3 Frequency:2.422 GHz (Channel 3) Quality=70/70 Signal level=-11 dBm Encryption key:on ESSID:"lwfdjf-n" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=00000226ec352cf9 Extra: Last beacon: 32ms ago IE: Unknown: 00086C7766646A662D6E IE: Unknown: 010882848B962430486C IE: Unknown: 030103 IE: Unknown: 2A0100 IE: Unknown: 2F0100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK IE: Unknown: 32040C121860 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK This AP is capable of 802.11n with 2.4 GHz rate up to 270 Mbps and HT40, which is the reason for channel 3. Larry ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-08 23:47 ` Rafał Miłecki 2011-06-09 0:27 ` Larry Finger @ 2011-06-11 7:53 ` Rafał Miłecki 2011-06-11 16:20 ` Rafał Miłecki 1 sibling, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-11 7:53 UTC (permalink / raw) To: b43-dev W dniu 9 czerwca 2011 01:47 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?: > BSS 00:23:69:c2:65:06 (on wlan0) > ? ? ? ?TSF: 665805184 usec (0d, 00:11:05) > ? ? ? ?freq: 2427 > ? ? ? ?beacon interval: 100 > ? ? ? ?capability: ESS Privacy ShortSlotTime (0x0411) > ? ? ? ?signal: -14.00 dBm > ? ? ? ?last seen: 778 ms ago > ? ? ? ?SSID: zajec_poznan_160 > ? ? ? ?Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 > ? ? ? ?DS Parameter set: channel 4 > ? ? ? ?ERP: <no flags> > ? ? ? ?Extended supported rates: 24.0 36.0 48.0 54.0 > ? ? ? ?RSN: ? ? * Version: 1 > ? ? ? ? ? ? ? ? * Group cipher: CCMP > ? ? ? ? ? ? ? ? * Pairwise ciphers: CCMP > ? ? ? ? ? ? ? ? * Authentication suites: PSK > ? ? ? ? ? ? ? ? * Capabilities: 16-PTKSA-RC (0x000c) > ? ? ? ?WMM: ? ?* Parameter version 1 > ? ? ? ? ? ? ? ?* BE: CW 15-1023, AIFSN 3 > ? ? ? ? ? ? ? ?* BK: CW 15-1023, AIFSN 7 > ? ? ? ? ? ? ? ?* VI: CW 7-15, AIFSN 2, TXOP 3008 usec > ? ? ? ? ? ? ? ?* VO: acm CW 3-7, AIFSN 2, TXOP 1504 usec > > network={ > ? ? ? ?ssid="zajec_poznan_160" > ? ? ? ?key_mgmt=WPA-PSK > ? ? ? ?proto=WPA RSN > ? ? ? ?pairwise=CCMP TKIP > ? ? ? ?group=CCMP TKIP > ? ? ? ?psk="psssst" > } In my parent's house I've the same router with the same OpenWRT version. Freq is also the same: BSS 00:23:69:a3:92:f0 (on wlan0) TSF: 3120501241 usec (0d, 00:52:00) freq: 2427 beacon interval: 100 capability: ESS Privacy ShortSlotTime (0x0411) signal: -61.00 dBm last seen: 843 ms ago SSID: zajec_160nl_openwrt Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 DS Parameter set: channel 4 ERP: Barker_Preamble_Mode Extended supported rates: 24.0 36.0 48.0 54.0 RSN: * Version: 1 * Group cipher: CCMP * Pairwise ciphers: CCMP * Authentication suites: PSK * Capabilities: 16-PTKSA-RC (0x000c) WMM: * Parameter version 1 * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec It connected just fine here. Weird. Maybe G?bor is right? Maybe we miss some calibration needed for the low distance with jamming? -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-11 7:53 ` Rafał Miłecki @ 2011-06-11 16:20 ` Rafał Miłecki 2011-06-11 17:36 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-11 16:20 UTC (permalink / raw) To: b43-dev W dniu 11 czerwca 2011 09:53 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?: > In my parent's house I've the same router with the same OpenWRT > version. Freq is also the same: > > (...) > > It connected just fine here. Weird. > > Maybe G?bor is right? Maybe we miss some calibration needed for the > low distance with jamming? I wanted to make some iperf tests so I connected keyboard and monitor. I could not connect anymore after this. My reaction? What a Terrible Failure. After experimenting, it appeared to be about direction of the antenna. Moving it by 90 degrees caused disconnection and reconnecting was not possible. Moving it back worked like a charm... well - kind of - because speed was still horrible. However at least connecting was working fine. So we may be lacking something important about calibration. But on the other hand, wl or ndiswrapper are not much better. Speed achieved with ndiswrapper can be 3Mb/s and 15Mb/s after 10 minutes (without touching anything). To make it even more ugly, PIO mode is almost not working for me. I can connect to the network (with antenna in the correct direction), but getting IP (dhcp) causes loosing authentication. Every time. After loosing connection taking interface down & up is required. I'm leaving this for now. Hope noone will ever meet card like mine. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-11 16:20 ` Rafał Miłecki @ 2011-06-11 17:36 ` Rafał Miłecki 2011-06-12 20:46 ` Rafał Miłecki 0 siblings, 1 reply; 16+ messages in thread From: Rafał Miłecki @ 2011-06-11 17:36 UTC (permalink / raw) To: b43-dev W dniu 11 czerwca 2011 18:20 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?: > To make it even more ugly, PIO mode is almost not working for me. I > can connect to the network (with antenna in the correct direction), > but getting IP (dhcp) causes loosing authentication. Every time. After > loosing connection taking interface down & up is required. > > I'm leaving this for now. Hope noone will ever meet card like mine. Not sure if I'll shout up. As I could not benchmark PIO on BCM4312 (14e4:4315), I decided to switch to BCM4311 (14e4:4312). Guess what. The same PIO issue! qos=0 workarounds pio issue on BCM4311 (14e4:4312). Not sure about BCM4312 yet. -- Rafa? ^ permalink raw reply [flat|nested] 16+ messages in thread
* Faulty 14e4:4315 (BCM4312)? 2011-06-11 17:36 ` Rafał Miłecki @ 2011-06-12 20:46 ` Rafał Miłecki 0 siblings, 0 replies; 16+ messages in thread From: Rafał Miłecki @ 2011-06-12 20:46 UTC (permalink / raw) To: b43-dev W dniu 11 czerwca 2011 19:36 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?: > W dniu 11 czerwca 2011 18:20 u?ytkownik Rafa? Mi?ecki > <zajec5@gmail.com> napisa?: >> To make it even more ugly, PIO mode is almost not working for me. I >> can connect to the network (with antenna in the correct direction), >> but getting IP (dhcp) causes loosing authentication. Every time. After >> loosing connection taking interface down & up is required. >> >> I'm leaving this for now. Hope noone will ever meet card like mine. > > Not sure if I'll shout up. > > As I could not benchmark PIO on BCM4312 (14e4:4315), I decided to > switch to BCM4311 (14e4:4312). Guess what. The same PIO issue! > > qos=0 workarounds pio issue on BCM4311 (14e4:4312). Not sure about BCM4312 yet. Same for my BCM4312. There is something wrong with QOS in PIO mode. Attached is dmesg with message for every TX. The first part is for qos=1, later is for qos=0. -- Rafa? -------------- next part -------------- [ 169.766050] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) [ 169.768723] b43-phy0 debug: b2062: Using crystal tab entry 19200 kHz. [ 171.154068] b43-phy0 debug: Chip initialized [ 171.154136] b43-phy0 debug: PIO initialized [ 171.154210] b43-phy0 debug: QoS enabled [ 171.163820] b43-phy0 debug: Wireless interface started [ 171.169096] b43-phy0 debug: Adding Interface type 2 [ 171.169592] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 171.360049] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.529042] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.598038] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.667036] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.736122] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.805041] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.874037] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 171.943037] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 172.012046] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 172.081039] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 172.150040] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 172.603208] wlan0: authenticate with 00:23:69:a3:92:f0 (try 1) [ 172.603231] [DBG] TX on PIO queue 3 (0x2D8); skb is len:30 data_len:0 priority:7 queue_mapping:0 [ 172.605296] wlan0: authenticated [ 172.605713] wlan0: associate with 00:23:69:a3:92:f0 (try 1) [ 172.605733] [DBG] TX on PIO queue 3 (0x2D8); skb is len:96 data_len:0 priority:7 queue_mapping:0 [ 172.608515] wlan0: RX AssocResp from 00:23:69:a3:92:f0 (capab=0x411 status=0 aid=1) [ 172.608519] wlan0: associated [ 172.609485] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 172.622855] [DBG] TX on PIO queue 1 (0x258); skb is len:155 data_len:0 priority:0 queue_mapping:2 [ 172.628257] [DBG] TX on PIO queue 1 (0x258); skb is len:133 data_len:0 priority:0 queue_mapping:2 [ 172.628381] b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 00:23:69:a3:92:f0 [ 172.628433] b43-phy0 debug: Using hardware based encryption for keyidx: 1, mac: ff:ff:ff:ff:ff:ff [ 173.708053] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 174.706051] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 175.706051] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 176.706046] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 176.919236] [DBG] TX on PIO queue 1 (0x258); skb is len:370 data_len:0 priority:0 queue_mapping:2 [ 177.706056] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 178.207064] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 178.708044] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 179.209056] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 179.710039] [DBG] TX on PIO queue 3 (0x2D8); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 179.922450] [DBG] TX on PIO queue 1 (0x258); skb is len:370 data_len:0 priority:0 queue_mapping:2 [ 180.211041] ieee80211 phy0: wlan0: No probe response from AP 00:23:69:a3:92:f0 after 500ms, disconnecting. [ 180.213041] b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:23:69:a3:92:f0 [ 180.217030] b43-phy0 debug: Disabling hardware based encryption for keyidx: 1, mac: ff:ff:ff:ff:ff:ff [ 180.217083] [DBG] TX on PIO queue 3 (0x2D8); skb is len:26 data_len:0 priority:7 queue_mapping:0 [ 180.217118] cfg80211: Calling CRDA to update world regulatory domain [ 180.230126] cfg80211: World regulatory domain updated: [ 180.230131] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 180.230136] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 180.230139] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 180.230143] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 180.230146] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 180.230150] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 180.487049] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 180.556036] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 180.625031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 180.694031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 180.863031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 180.932031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.001033] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.070041] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.139031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.208032] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.277031] [DBG] TX on PIO queue 3 (0x2D8); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 181.722499] wlan0: authenticate with 00:23:69:a3:92:f0 (try 1) [ 181.722520] [DBG] TX on PIO queue 3 (0x2D8); skb is len:30 data_len:0 priority:7 queue_mapping:0 [ 181.922034] wlan0: authenticate with 00:23:69:a3:92:f0 (try 2) [ 181.922055] [DBG] TX on PIO queue 3 (0x2D8); skb is len:30 data_len:0 priority:7 queue_mapping:0 [ 181.924340] b43-phy0 ERROR: PHY transmission error [ 181.925516] b43-phy0 ERROR: PHY transmission error [ 181.926696] b43-phy0 ERROR: PHY transmission error [ 181.927867] b43-phy0 ERROR: PHY transmission error [ 181.929040] b43-phy0 ERROR: PHY transmission error [ 181.930226] b43-phy0 ERROR: PHY transmission error [ 181.931389] b43-phy0 ERROR: PHY transmission error [ 181.932571] b43-phy0 ERROR: PHY transmission error [ 181.933786] b43-phy0 ERROR: PHY transmission error [ 181.934994] b43-phy0 ERROR: PHY transmission error [ 182.122033] wlan0: authenticate with 00:23:69:a3:92:f0 (try 3) [ 182.122055] [DBG] TX on PIO queue 3 (0x2D8); skb is len:30 data_len:0 priority:7 queue_mapping:0 [ 182.322028] wlan0: authentication with 00:23:69:a3:92:f0 timed out [ 184.668033] b43-phy0 debug: Removing Interface type 2 [ 184.668129] b43-phy0 debug: Wireless interface stopped [ 187.639590] b43-pci-bridge 0000:02:00.0: PCI INT A disabled [ 208.068049] b43-phy1: Loading firmware version 478.104 (2008-07-01 00:50:23) [ 208.070738] b43-phy1 debug: b2062: Using crystal tab entry 19200 kHz. [ 209.458072] b43-phy1 debug: Chip initialized [ 209.458145] b43-phy1 debug: PIO initialized [ 209.458158] b43-phy1 debug: QoS disabled [ 209.467813] b43-phy1 debug: Wireless interface started [ 209.473097] b43-phy1 debug: Adding Interface type 2 [ 209.473425] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 209.640050] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 209.809049] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 209.878037] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 209.947034] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.016062] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.085041] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.154034] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.223037] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.292036] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.361032] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.430030] [DBG] TX on PIO queue 1 (0x258); skb is len:45 data_len:0 priority:7 queue_mapping:0 [ 210.884198] wlan0: authenticate with 00:23:69:a3:92:f0 (try 1) [ 210.884220] [DBG] TX on PIO queue 1 (0x258); skb is len:30 data_len:0 priority:7 queue_mapping:0 [ 210.886259] wlan0: authenticated [ 210.886686] wlan0: associate with 00:23:69:a3:92:f0 (try 1) [ 210.886706] [DBG] TX on PIO queue 1 (0x258); skb is len:87 data_len:0 priority:7 queue_mapping:0 [ 210.889191] wlan0: RX AssocResp from 00:23:69:a3:92:f0 (capab=0x411 status=0 aid=1) [ 210.889195] wlan0: associated [ 210.889796] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 210.904481] [DBG] TX on PIO queue 1 (0x258); skb is len:153 data_len:0 priority:0 queue_mapping:0 [ 210.909875] [DBG] TX on PIO queue 1 (0x258); skb is len:131 data_len:0 priority:0 queue_mapping:0 [ 210.909997] b43-phy1 debug: Using hardware based encryption for keyidx: 0, mac: 00:23:69:a3:92:f0 [ 210.910361] b43-phy1 debug: Using hardware based encryption for keyidx: 1, mac: ff:ff:ff:ff:ff:ff [ 211.706050] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 212.706052] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 213.706050] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 214.706049] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 215.706039] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 215.844398] [DBG] TX on PIO queue 1 (0x258); skb is len:368 data_len:0 priority:0 queue_mapping:0 [ 215.855771] [DBG] TX on PIO queue 1 (0x258); skb is len:387 data_len:0 priority:0 queue_mapping:0 [ 215.871080] [DBG] TX on PIO queue 1 (0x258); skb is len:68 data_len:0 priority:0 queue_mapping:0 [ 216.071413] [DBG] TX on PIO queue 1 (0x258); skb is len:68 data_len:0 priority:0 queue_mapping:0 [ 216.271733] [DBG] TX on PIO queue 1 (0x258); skb is len:68 data_len:0 priority:0 queue_mapping:0 [ 216.472060] [DBG] TX on PIO queue 1 (0x258); skb is len:68 data_len:0 priority:0 queue_mapping:0 [ 216.672373] [DBG] TX on PIO queue 1 (0x258); skb is len:68 data_len:0 priority:0 queue_mapping:0 [ 216.706044] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 216.876136] [DBG] TX on PIO queue 1 (0x258); skb is len:80 data_len:0 priority:0 queue_mapping:0 [ 216.904171] [DBG] TX on PIO queue 1 (0x258); skb is len:329 data_len:0 priority:0 queue_mapping:0 [ 216.932513] [DBG] TX on PIO queue 1 (0x258); skb is len:452 data_len:0 priority:0 queue_mapping:0 [ 217.182430] [DBG] TX on PIO queue 1 (0x258); skb is len:452 data_len:0 priority:0 queue_mapping:0 [ 217.433694] [DBG] TX on PIO queue 1 (0x258); skb is len:452 data_len:0 priority:0 queue_mapping:0 [ 217.633647] [DBG] TX on PIO queue 1 (0x258); skb is len:416 data_len:0 priority:0 queue_mapping:0 [ 217.706052] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 217.910647] [DBG] TX on PIO queue 1 (0x258); skb is len:329 data_len:0 priority:0 queue_mapping:0 [ 218.640331] [DBG] TX on PIO queue 1 (0x258); skb is len:416 data_len:0 priority:0 queue_mapping:0 [ 218.706057] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 219.706049] [DBG] TX on PIO queue 1 (0x258); skb is len:64 data_len:0 priority:7 queue_mapping:0 [ 219.918588] [DBG] TX on PIO queue 1 (0x258); skb is len:488 data_len:0 priority:0 queue_mapping:0 [ 220.240309] wlan0: deauthenticating from 00:23:69:a3:92:f0 by local choice (reason=3) [ 220.242037] b43-phy1 debug: Disabling hardware based encryption for keyidx: 1, mac: ff:ff:ff:ff:ff:ff [ 220.242166] [DBG] TX on PIO queue 1 (0x258); skb is len:26 data_len:0 priority:7 queue_mapping:0 [ 220.244042] b43-phy1 debug: Disabling hardware based encryption for keyidx: 0, mac: 00:23:69:a3:92:f0 [ 220.246179] cfg80211: Calling CRDA to update world regulatory domain [ 220.257542] cfg80211: World regulatory domain updated: [ 220.257548] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 220.257553] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 220.257557] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 220.257560] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 220.257563] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 220.257567] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 220.284036] b43-phy1 debug: Removing Interface type 2 [ 220.284145] b43-phy1 debug: Wireless interface stopped [ 221.955593] b43-pci-bridge 0000:02:00.0: PCI INT A disabled ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2011-06-12 20:46 UTC | newest] Thread overview: 16+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-06-08 20:25 Faulty 14e4:4315 (BCM4312)? Rafał Miłecki 2011-06-08 20:37 ` Gábor Stefanik 2011-06-08 20:59 ` Rafał Miłecki 2011-06-08 20:59 ` Rafał Miłecki 2011-06-08 21:08 ` Gábor Stefanik 2011-06-08 21:19 ` Rafał Miłecki 2011-06-08 22:55 ` Rafał Miłecki 2011-06-08 23:05 ` Larry Finger 2011-06-08 23:14 ` Rafał Miłecki 2011-06-08 23:30 ` Larry Finger 2011-06-08 23:47 ` Rafał Miłecki 2011-06-09 0:27 ` Larry Finger 2011-06-11 7:53 ` Rafał Miłecki 2011-06-11 16:20 ` Rafał Miłecki 2011-06-11 17:36 ` Rafał Miłecki 2011-06-12 20:46 ` Rafał Miłecki
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).