Hi Bryan,

Bryan Phillippe wrote:
> I'm somewhat new to Linux wireless, and have begun to use it for a
> project at work.  I've had a few of problems, some of which I've
> solved and others that I'm still fighting with.

I think you'll also have more problems.


> My project has been to update an ARM-based Linux WAP from an older
> version of Linux to 2.6.35-ish.  I know this is not the latest
> version, but it's what I'm working with presently - perhaps the
> best place for me to start is to get a recommendation on which
> version of the ath9k driver I should use, and any patches you
> believe are essential.

This mailing list sees email from people working for Atheros, but
they will basically not help unless you are running latest git code.

They also help less with older hardware. There seems to be a strong
focus on the very latest x86 platforms, so PCI-only chip on ARM is
somewhat of a bad starting position. (Atheros of course wants you to
use their SoCs instead.)


> I'll work on migrating my project to that version.

I'd start by using very latest git.


> The problems that I'm still seeing are:

For the record I've tried to use similar generation hardware as you,
I was on AR5416, but I gave up. After giving up I was motivated to
try again, but at that point my PCI bus master had broken. I have new
hardware now but too many other construction projects at the moment.


> 1.) I still see "ath: Failed to stop TX DMA. Resetting hardware!" a
> lot when using Windows 7 clients and MacBook Air clients.  Happens
> more with more network load.  I also sometimes see "ath: Failed to
> stop TX DMA in 100 msec after killing last frame".

I've gotten my share of DMA error messages. My gut feeling then was
that they were due to bad driver code, but I have been convinced by
members of the list that the driver is by now fairly good, so I guess
that instead it may be because of the ath9k driver being firmware bug
incompatible with Windows drivers where presumably everything works
great.


> 2.) I see this message occasionally from hostapd, for both Windows
> and Mac clients:

hostapd should probably also be git code to get help.


> 3.) Performance and ability to stay associated is intermittent

This was exactly my problem, although I was operating as STA. I had
severe problems with AR5416. By the time I got to use AR9220 much I
quickly had the broken bus master.

I'll try my luck with AR9380 next, although it is quickly becoming
too old as well.


//Peter
_______________________________________________
ath9k-devel mailing list
[email protected]
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to