Comment 6 for bug 278800

@Dave:

I don't know if I can help but I'll jump in anyway.

I wonder if you are having a problem where the wireless device needs to be turned off in order to come back to life. Will one boot suffice to get your wireless working if you turn your computer off for a few seconds rather than just restart?

I also wonder if you are experiencing the following problem:

http://bugzilla.kernel.org/show_bug.cgi?id=12080

When this happens are you getting the changing bit-rates described by Superklaus?
========================

I see the changing bit rates and get the lost pings, but I don't get the hangs.

I'm also not getting the messages in the description--at least not during operation.

I wonder if there are actually two or three problems here. If so mine most closely matches Superklaus.

@Superklaus:

Off the web page:
http://wireless.kernel.org/en/users/Drivers/ath5k I found the command
[code] iwconfig wlan%d rate 11M [/code]

For me that becomes:
[code] sudo iwconfig wlan0 rate 11M [/code]

They mention on that page that the command is useful because of the current state of the experimental driver's rate control.

When I do this the rate stays at 11M, the 802.11 b rate, but that's better than 1M/bps and drop outs. I no longer have ping dropouts. Without this I get about 11% packet loss with an interruption every 10-20 seconds of about 2 seconds. This is enough to really get TCP agitated and my throughput crawls. With the command I'm in much better shape since I'd only see the drop in rate if copying files within my internal network.

Would you like to try this command and see if it helps?