----------------------------------------
> Subject: RE: More on ASUS WL-138G V2
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: [email protected]
> Date: Sun, 23 Mar 2008 13:31:23 +0100
>
>
>> ...I'd be fairly sure that I shouldn't see this either ;
>>
>> wlan0: authenticate with AP 00:1e:2a:61:7d:2c
>> phy3: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a
>> A1=00:1e:2a:61:7d:2c A2=00:1b:fc:61:15:e1 A3=00:1e:2a:61:7d:2c
>> wlan0: authenticate with AP 00:1e:2a:61:7d:2c
>> phy3: TX to low-level driver (len=30) FC=0x00b0 DUR=0x013a
>> A1=00:1e:2a:61:7d:2c A2=00:1b:fc:61:15:e1 A3=00:1e:2a:61:7d:2c
>> wlan0: authentication with AP 00:1e:2a:61:7d:2c timed out
>
> For one you should turn off low-level debugging ;)
>
> But the timeouts are another matter.
>
>> ....on the other hand, if RX packets = 0 on the interface and that's
>> true, then I probably would expect to see something like that...
>
> Not entirely sure those stats are kept properly, but I think they are.
>
....okay...
[snip]...
>
> No, it's more likely a transmission bug. Can you enable b43 debugfs,
> mount debugfs, and check the output of
> cat /debug/b43/phy*/txstat
>
.....all ready to go, mounted it and saw...
[EMAIL PROTECTED]:~# cat /debug/b43/phy*/txstat
Nothing transmitted, yet.
That situation did not change -- 5minutes of low level gibberish in dmesg (like
the above ;) and /debug/b43/phy*/txstat did NOT change...
That's not good, is it?.....Next?...
Kind regards,
Donald
>
> johannes
_________________________________________________________________
Fashion, beauty, health, relationship advice and horoscopes.
http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=873&referral=MarchHotmailTagline&URL=http://lifestyle.ninemsn.com.au/?ocid=T003HOT40A0710G
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
