On Fri, 2009-03-27 at 16:04 +0200, Nick Kossifidis wrote:
> Nice catch ;-)
I just realized that ath5k worked when I was in Russia a week ago
because I was setting the country code correctly, and there is no 5 GHz
band in Russia. But in the US, ath5k fails to scan! That's why ath5k
"broke" when
2009/3/27 Pavel Roskin :
> On Thu, 2009-03-26 at 03:47 +0200, Nick Kossifidis wrote:
>
>> That's weird, I've tested this with my 5413 and it works just fine. It
>> seems that 5424 (pci-e version of 5413) still has some issues. Have
>> you tried monitor mode ?
>
> I have reduced the patch to the clo
On Thu, 2009-03-26 at 03:47 +0200, Nick Kossifidis wrote:
> That's weird, I've tested this with my 5413 and it works just fine. It
> seems that 5424 (pci-e version of 5413) still has some issues. Have
> you tried monitor mode ?
I have reduced the patch to the clock setting in ath5k_hw_nic_wakeup(
Quoting Nick Kossifidis :
> That's weird, I've tested this with my 5413 and it works just fine. It
> seems that 5424 (pci-e version of 5413) still has some issues. Have
> you tried monitor mode ?
The monitor mode is fine.
I also looked at the probe requests and probe responses and could not
fi
2009/3/26 Pavel Roskin :
> Hello!
>
> AR5414 fails to scan most of the time starting with the revision
> 94f2e0d6234991d0c10d458f6f378934efbdf6d6 "ath5k: Update reset code"
>
> I have about 18 APs in the range. With the latest kernel, the scan
> results are usually empty. I tried reverting parts
Hello!
AR5414 fails to scan most of the time starting with the revision
94f2e0d6234991d0c10d458f6f378934efbdf6d6 "ath5k: Update reset code"
I have about 18 APs in the range. With the latest kernel, the scan
results are usually empty. I tried reverting parts of the patch, as it
cannot be cleanly
