Menu
▾
▴
#9 TX error 0x10 Pre3
closed
nobody
None
5
2006-07-26
2003-10-16
Anonymous
No
I am having issues with with 0.2.0-pre3 where the card
will stay up for quite a while and then drop off of
service with "TX Error the Distance may be to far." I
have installed on redhat 9 kernel 2.4.20. The machine
is currently located right next to my WAP so I know
that the distance isn't to far. The only way to clear
issue is to stop_net and start_net. iwconfig wlan0
shows that the signal strength is 64/100 and SNR =
0/100 and SIR = 100/100. I have used most of the
default settings other than IP address changed.
Logged In: YES
user_id=132674
Did 0.2.0pre4 work? (or does it lock up the box?)
It has quite some changes which might fix that.
Else just wait for the next version...
Logged In: NO
0.2.0pre4 locked up the box.
Logged In: NO
0.2.0pre4 locked up the box.
Logged In: YES
user_id=132674
The reporter could try out 0.2.0pre5 now to check whether it
works now ;-)
(or just wait some more)
pre5 is MUCH more solid than pre4 (although there's still at
least one remaining corner case where it locks up the box)
Logged In: YES
user_id=132674
Hmm, I have a similar recent report which might indicate
that there indeed is a real problem here.
Please retry with a recent version (e.g. the
pre6_plus_fixes_6 tar)
and post some logs.
Thanks!
Logged In: YES
user_id=832108
I'm getting this same problem with RH9 and 0.2.0-pre6 (dwl-
650+)
Logged In: NO
I have got the same problem with 0.2.0pre6-1 (DWL-520+)
Logged In: NO
I use 0.2.0pre5 (DWL-520+), I have that freakin' "tx error
occured (error 0x10)!! (maybe the distance is too high!)"
massage allways when I try to connect to anywhere...
The connection is perfect, but I always get this stupid
massage.
How could I turn it off?
Logged In: NO
Any higher than 0.2.0pre5 is not working for me (DWL-520+,
2.4.25 kernel) ...
Logged In: YES
user_id=132674
You're lucky for having added another blurb. Otherwise I'd
have smashed you to pieces for daring to use a driver
version that is more than 4 months old! ;-)
Anyway, error 0x10 is MSDU timeout, which has been fixed a
long time ago.
What doesn't work with current versions? Logs, please.
(please use http://lisas.de/~andi/acx100/\)
Thanks!
Logged In: YES
user_id=132674
Closing, for repeated lack of replies and anonymous report.
Should be working now anyway.