Re: [Madwifi-users] AR5213: Does not send faster than 18Mbps
Status: Beta
Brought to you by:
otaku
From: Jerry <mr...@st...> - 2005-10-18 12:26:18
|
Hello! Well, as sad as it is, I have found the driver to be slow too. In the = same=20 or next room (hooking to a hardware AP) I have seem up to 23Mbs = throughput,=20 but if there is any noise at all (and/or distance), this drops to = nothing=20 quickly. I have used onoe and amrr (and the sample), and they all = basically=20 act the same. There is no software re-transmission, only hardware=20 re-transmit, this has been said in the list many times. These same cards in windows, kisk ass (at least my CM9 does), so it has = to=20 be a driver issue, and it has been acknowledged as such. I am (impatiently) waiting for the new code as well. I know the cards = can,=20 as I have used StarOS and Mikrotik, and they seem to work more like one=20 would expect the card to... We just need to be patient. Jerryf > Ouch, this su**s. What does iwlist bitrate say? E.g.: > wcc:~# iwlist ath0 bit > ath0 12 available bit-rates : > 1 Mb/s > 2 Mb/s > 5.5 Mb/s > 11 Mb/s > 6 Mb/s > 9 Mb/s > 12 Mb/s > 18 Mb/s > 24 Mb/s > 36 Mb/s > 48 Mb/s > 54 Mb/s > Current Bit Rate:9 Mb/s > Are all the bitrates listed? If so, I can't imagine how the driver = could=20 > be at fault and would point to the HAL. Unless there's a problem at = the=20 > receiving end or in the negotiation with the receiving end. Not sure = how=20 > to troubleshoot that, unless there's a debug message during the=20 > association phase that lists the available bit rates of the peer. > TvE > > Evan Jones wrote: >> On Oct 17, 2005, at 10:41, Thorsten von Eicken wrote: >> >>> Are you using 'sample' rate control? If not, do so. Then check the=20 >>> values in /proc/sys/dev/athX/rate and see what the rate control says = >>> about packet successes at higher bit rates. >> >> >> The information in these files, when using the "sample" rate control=20 >> verifies our experiments when using the raw interface: All the packet = >> transmissions at higher bit rates fail. Here is the contents of one = of=20 >> the files: >> >> blackbox rate # more stats_1600 >> 00:02:6f:21:df:eb >> rate tt/perfect failed/pkts avg_tries last_tx >> 6 2560/2560 0/ 0 1.00 - >> 9 1848/1848 0/ 0 1.00 - >> 12 1480/1480 0/ 0 1.00 - >> * 18 1124/1124 0/ 23 1.00 205.147 >> 24 1873/ 940 6/ 6 3.00 205.851 >> 36 1842/ 764 5/ 5 3.00 205.58 >> 48 1360/ 672 3/ 3 3.00 267.972 >> 54 1323/ 644 3/ 3 3.00 269.897 >> >> >> At this point, I'm hoping that this oft-rumoured "new" code will=20 >> magically fix something. >> >> Evan Jones >> >> --=20 >> Evan Jones >> http://evanjones.ca/ >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, = discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users >=20 |