Hi,
I have been trying to get my ar9390 based wlan module to work as an AP
on my powerpc target. There seems to be some issues with AGC
calibration though. As soon as I start hostapd, I get the following:
ath9k 0000:01:00.0: mon.wlan0: Features changed: 0x00004800 -> 0x00004000
ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
Could not set interface mon.wlan0 flags: Input/output error
nl80211: Failed to set interface wlan0 into AP mode
nl80211 driver initialization failed.
ELOOP: remaining socket: sock=8 eloop_data=0x10219770
user_data=0x10219d18 handler=0x1002b8c0
ELOOP: remaining socket: sock=10 eloop_data=0x1021c0b8 user_data=(nil)
handler=0x100353e0
Further debugging revealed that the problem was AGC calibration that
didn't finish and that can be seen from the logs too:
ath: timeout (100000 us) on reg 0xa2c4: 0x00158dd9 & 0x00000001 != 0x00000000
I moved that module to x86 ubuntu 11.10 pc to see if it works there.
For my surprise it worked just fine. So it seems that there is
something related to powerpc platform. I'm using kernel 2.6.39 and
compat wireless drivers from november. Would it be possible that there
is some endianess stuff somewhere that isn't handled properly?
> Have you tried any other PCIe device behind such a bridge?
>
I have tested some gigabit ethernet cards an they work just fine. I
also tried another wlan card that has other atheros chip in it but
uses same ath9k driver. It works better, but that card too has
problems. Lots of phy and rx errors and poor throughput.
Hi again,
I still haven't been able to get this thing working. But I have made
some tests on other powerpc target (mpc8315 cpu versus mpc8321 cpu on
my own target) and I can tell that this problem doesn't seem to be
related to big endian environment. Ar9390 works just fine with
mpc8315. The difference between those two targets is that 8315 has
pcie bus whereas my own target's pcie bus is behind pci-to-pcie bridge
(PLX PEX8112).
Is anyone aware of any limitations or bugs related to using ar9390
behind pci-to-pcie bridge? All help is really appreciated.
2011/11/29 wireless newbie <[email protected]>:
> Hi,
>
> I have been trying to get my ar9390 based wlan module to work as an AP
> on my powerpc target. There seems to be some issues with AGC
> calibration though. As soon as I start hostapd, I get the following:
>
> ath9k 0000:01:00.0: mon.wlan0: Features changed: 0x00004800 -> 0x00004000
> ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
> Could not set interface mon.wlan0 flags: Input/output error
> nl80211: Failed to set interface wlan0 into AP mode
> nl80211 driver initialization failed.
> ELOOP: remaining socket: sock=8 eloop_data=0x10219770
> user_data=0x10219d18 handler=0x1002b8c0
> ELOOP: remaining socket: sock=10 eloop_data=0x1021c0b8 user_data=(nil)
> handler=0x100353e0
>
> Further debugging revealed that the problem was AGC calibration that
> didn't finish and that can be seen from the logs too:
>
> ath: timeout (100000 us) on reg 0xa2c4: 0x00158dd9 & 0x00000001 != 0x00000000
>
> I moved that module to x86 ubuntu 11.10 pc to see if it works there.
> For my surprise it worked just fine. So it seems that there is
> something related to powerpc platform. I'm using kernel 2.6.39 and
> compat wireless drivers from november. Would it be possible that there
> is some endianess stuff somewhere that isn't handled properly?
This sounds like "noise spurs all over the place."
AGC calibration failing can be because of this.
Can you do a channel survey, or something? Felix, what can he do to
inspect the channel busy % ?
Adrian
Is it this bad behaved in 5ghz mode?
adrian
On 23 December 2011 01:03, wireless newbie <[email protected]> wrote:
>> iw wlan0 survey dump
>
> Here is what I got. Looks like its busy most of the time, doesn't it?
>
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2412 MHz
> ? ? ? ?channel active time: ? ? ? ? ? ?139291 ms
> ? ? ? ?channel busy time: ? ? ? ? ? ? ?135849 ms
> ? ? ? ?channel receive time: ? ? ? ? ? 0 ms
> ? ? ? ?channel transmit time: ? ? ? ? ?0 ms
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2417 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2422 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2427 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2432 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2437 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2442 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2447 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2452 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2457 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2462 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5180 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5200 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5220 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5240 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5745 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5765 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5785 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5805 MHz
> Survey data from wlan0
> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5825 MHz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
On 2011-12-22 12:11 PM, wireless newbie wrote:
> I still haven't been able to get this thing working. But I have made
> some tests on other powerpc target (mpc8315 cpu versus mpc8321 cpu on
> my own target) and I can tell that this problem doesn't seem to be
> related to big endian environment. Ar9390 works just fine with
> mpc8315. The difference between those two targets is that 8315 has
> pcie bus whereas my own target's pcie bus is behind pci-to-pcie bridge
> (PLX PEX8112).
>
> Is anyone aware of any limitations or bugs related to using ar9390
> behind pci-to-pcie bridge? All help is really appreciated.
Have you tried any other PCIe device behind such a bridge?
Maybe you should also check the ASPM settings, though I don't know
enough to give you details on that. It's been covered in various threads
on linux-wireless.
- Felix
On 2011-12-23 7:45 AM, Adrian Chadd wrote:
> This sounds like "noise spurs all over the place."
>
> AGC calibration failing can be because of this.
>
> Can you do a channel survey, or something? Felix, what can he do to
> inspect the channel busy % ?
iw wlan0 survey dump
> iw wlan0 survey dump
Here is what I got. Looks like its busy most of the time, doesn't it?
Survey data from wlan0
frequency: 2412 MHz
channel active time: 139291 ms
channel busy time: 135849 ms
channel receive time: 0 ms
channel transmit time: 0 ms
Survey data from wlan0
frequency: 2417 MHz
Survey data from wlan0
frequency: 2422 MHz
Survey data from wlan0
frequency: 2427 MHz
Survey data from wlan0
frequency: 2432 MHz
Survey data from wlan0
frequency: 2437 MHz
Survey data from wlan0
frequency: 2442 MHz
Survey data from wlan0
frequency: 2447 MHz
Survey data from wlan0
frequency: 2452 MHz
Survey data from wlan0
frequency: 2457 MHz
Survey data from wlan0
frequency: 2462 MHz
Survey data from wlan0
frequency: 5180 MHz
Survey data from wlan0
frequency: 5200 MHz
Survey data from wlan0
frequency: 5220 MHz
Survey data from wlan0
frequency: 5240 MHz
Survey data from wlan0
frequency: 5745 MHz
Survey data from wlan0
frequency: 5765 MHz
Survey data from wlan0
frequency: 5785 MHz
Survey data from wlan0
frequency: 5805 MHz
Survey data from wlan0
frequency: 5825 MHz
Hi,
I tried 5ghz by changing hw_mode to 'a' and channel to 40. Still I get
the same error:
ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
That frequency makes me wonder if the change has really any affect?
2011/12/23 Adrian Chadd <[email protected]>:
> Is it this bad behaved in 5ghz mode?
>
>
> adrian
>
> On 23 December 2011 01:03, wireless newbie <[email protected]> wrote:
>>> iw wlan0 survey dump
>>
>> Here is what I got. Looks like its busy most of the time, doesn't it?
>>
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2412 MHz
>> ? ? ? ?channel active time: ? ? ? ? ? ?139291 ms
>> ? ? ? ?channel busy time: ? ? ? ? ? ? ?135849 ms
>> ? ? ? ?channel receive time: ? ? ? ? ? 0 ms
>> ? ? ? ?channel transmit time: ? ? ? ? ?0 ms
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2417 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2422 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2427 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2432 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2437 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2442 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2447 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2452 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2457 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?2462 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5180 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5200 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5220 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5240 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5745 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5765 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5785 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5805 MHz
>> Survey data from wlan0
>> ? ? ? ?frequency: ? ? ? ? ? ? ? ? ? ? ?5825 MHz
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html