Re: No probe response from AP address after 500ms, disconnecting.
On Thu, Mar 18, 2010 at 12:26:32AM +, Chris Vine ch...@cvine.freeserve.co.uk wrote: I suggest you add to this thread in linux-acpi (and lkml), that you can reproduce the problem, and it might then get some attention: http://marc.info/?l=linux-kernelm=126879129905898w=2 . Done. Out of interest, if you revert to 2.6.32 do you find your CMOS has been reset so that the wireless is permanently off? That happens to me intermittently. How do I check if there was a CMOS reset? I just see that once I did a suspend to disk, ifconfig eth0 up / iwlist eth0 scan does not work with the same error codes as yours. Did you tried to bisect it? I did not have time to do it yesterday but I might tonight. State your hardware when doing so (what is it?). I mentioned it @ lkml, it's an S12 netbook as well. Thanks. pgpXk2vDTr5Gj.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
Hi, I recently upgraded to 2.6.33, then 2.6.34-rc1, but both have the same bugs: 1) The earlier mentioned problem is still there, the b43 driver disconnects if no WPA is used by the AP. (This is not an issue with the binary broadcom 'wl' driver.) 2) The wireless card seems not to be functional after suspend to disk: # iwlist eth0 scan eth0 Failed to read scan data : Invalid argument And this is with b43 and wl, 2.6.33 and 2.6.34-rc1. If I downgrade to 2.6.32, both work after hibernation. Is this a known issue? Also, is there a bugtracker where I should report these errors? Or should I simply use http://bugzilla.kernel.org? Thanks! pgp3FAcMN74rP.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
On Fri, Jan 15, 2010 at 04:51:33AM +0100, Peter Stuge pe...@stuge.se wrote:
Should I include a section for the linksys (which has no encryption)
AP as well? if yes, what should it look like?
Yes, otherwise I don't think wpa_supplicant will do anything.
network={
ssid=linksys
key_mgmt=NONE
}
It could help to run it in foreground - you should see disconnect and
reauth then.
OK, when I add this, wpa_supplicant authenticates with the wpa ap on
startup. That's fine, but when I do an iwconfig eth0 essid linksys,
the wpa_supplicant stdout is:
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:1b:2f:51:25:70 (SSID='wpa ap' freq=2462 MHz)
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1b:2f:51:25:70
WPA: Key negotiation completed with 00:1b:2f:51:25:70 [PTK=CCMP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:1b:2f:51:25:70 completed (reauth) [id=0
id_str=]
The dmesg diff is:
--- a 2010-01-15 14:13:47.951510823 +0100
+++ b 2010-01-15 14:13:54.064510826 +0100
@@ -709,3 +709,11 @@
eth0: RX AssocResp from 00:1b:2f:51:25:70 (capab=0x431 status=0 aid=2)
eth0: associated
eth0: no IPv6 routers present
+eth0: deauthenticating from 00:1b:2f:51:25:70 by local choice (reason=3)
+eth0: direct probe to AP 00:1b:2f:51:25:70 (try 1)
+eth0: direct probe responded
+eth0: authenticate with AP 00:1b:2f:51:25:70 (try 1)
+eth0: authenticated
+eth0: associate with AP 00:1b:2f:51:25:70 (try 1)
+eth0: RX AssocResp from 00:1b:2f:51:25:70 (capab=0x431 status=0 aid=2)
+eth0: associated
The MAC you see is the wpa ap one, so basically I can't switch to the
linksys AP. (The MAC of the linksys AP - 00:12:17:D3:87:F5 - doesn't
show up in either outputs.)
pgpOw8Coak4D3.pgp
Description: PGP signature
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
On Fri, Jan 15, 2010 at 11:08:19AM +0100, Rafał Miłecki zaj...@gmail.com wrote: By 2.6.33, you mean that I should give 2.6.33-rc4 a try? That's right. You can try wireless-testing as well, currently it contains same LP-PHY support level as 33-rc4. How do I see what's improved? I just upgraded, and the only thing I could think of is to try iwconfig eth0 power off, but that's still not supported: # iwconfig eth0 power off Error for wireless request Set Power Management (8B2C) : SET failed on device eth0 ; Operation not supported. # uname -r 2.6.33-rc4 Thanks. pgpzvIL9Dw3jJ.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
On Fri, Jan 15, 2010 at 02:16:37PM +0100, Miklos Vajna vmik...@frugalware.org wrote: The MAC you see is the wpa ap one, so basically I can't switch to the linksys AP. (The MAC of the linksys AP - 00:12:17:D3:87:F5 - doesn't show up in either outputs.) I just tried what happens when the wpa ap is not available, just the linksys one. It still can't associate, but at least the MAC of the linksys shows up in the wpa_supplicant output: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:12:17:d3:87:f5 (SSID='linksys' freq=2462 MHz) Associated with 00:12:17:d3:87:f5 CTRL-EVENT-CONNECTED - Connection to 00:12:17:d3:87:f5 completed (reauth) [id=1 id_str=] So it's like: it's avilable for about 5 secs, then it goes down for 2, and this loops forever. :/ Again, this is with 2.6.33-rc4. Now my hope is that wireless-testing has some changes which are not in 2.6.33-rc4 and that solves this issue, but I'll wait for your experience first. :) Thanks, Miklos pgpuJtdSCENw5.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
On Sat, Jan 16, 2010 at 05:49:48AM +0100, Peter Stuge pe...@stuge.se wrote: Please let me know if that helped (which git repo, which branch?). It did not help. I merged git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-testing.git master into my kernel, and have posted a message about it to the ath9k list. :( OK, for now I think I'll just live with the binary driver (http://www.broadcom.com/docs/linux_sta/hybrid-portsrc-x86_64-v5.10.91.9.3.tar.gz), I hate to use external modules, but that one at least works fine for me. pgpm7XwZJCYUI.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
No probe response from AP address after 500ms, disconnecting.
Hi, I tried asking on #bcm-users, then found the wiki where it's suggested to report to this list, so I'm doing so. Sorry for the noise on IRC. A description of the problem at hand: My card works fine when I use it with WPA, however when I try to use it without any encryption (actually the provider uses MAC-based filtering, but that's not important), then after the iwconfig eth0 essid essid, iwconfig shows the MAC of the AP, and after about 5 secs iwconfig says it's Not-Associated. If I run iwconfig eth0 essid again, then it's usable again for ~5 secs and so on. When the AP goes unassociated, I see this in dmesg: No probe response from AP 00:12:17:d3:87:f5 after 500ms, disconnecting. When it happens: It happens only in case not using encryption. An other laptop with ipw2200 driver works fine, so I guess this will be a b43 or firmware problem. The same card works under Windows XP as well, so I guess it's not a hardware problem. How to reproduce: Run iwconfig eth0 essid essid, wait ~5 secs and run iwconfig again. Result: it's unassociated. Expected: to show the MAC of the AP, etc. $ uname -a Linux s12 2.6.32-fw2 #1 SMP PREEMPT Sat Dec 19 13:56:14 CET 2009 x86_64 GNU/Linux $ sudo lspci -vvn|grep 43 -A7 00:00.4 0600: 1106:4353 Subsystem: 17aa:3889 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes 00:00.5 0800: 1106:5353 (prog-if 20 [IO(X)-APIC]) Subsystem: 17aa:388a -- 02:00.0 0280: 14e4:4315 (rev 01) Subsystem: 14e4:04b5 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 28 Region 0: Memory at f520 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 -- Kernel driver in use: b43-pci-bridge Kernel modules: ssb dmesg: http://frugalware.org/~vmiklos/files/dmesg-s12 Wlan configuration, authentication/encryption type: b43 from vanilla kernel, no encryption. Firmware is installed as described at http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp kernel is a distro-packaged vanilla 2.6.32.1. Any ideas? Thanks! pgpkGdUyIEjyK.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: No probe response from AP address after 500ms, disconnecting.
On Fri, Jan 15, 2010 at 03:36:54AM +0100, Gábor Stefanik netrolller...@gmail.com wrote: 14E4:4315 is an LP-PHY (specifically, for most people,, it is the LP-PHY), for which 2.6.32 contains no calibration support, so performance/range problems can be expected. 2.6.33 should have improvements (part of calibration done), and 2.6.34 will (if I have time to do it) have full calibration support. What does calibration support mean? By performance problem I mean that after iwconfig eth0 essid it's working for ~5sec, and then it's down till the next iwconfig eth0 essid, so it's basically unusable. :/ By 2.6.33, you mean that I should give 2.6.33-rc4 a try? Thanks! pgpe7JV4HJ7ay.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
