[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Kelly Hogan]

Hi all,

I'm trying to get the UBNT AirRouter to work with latest ath9k and am
finding that it is failing in the ath9k_hw_wait with a timeout fail.

The ah structure appears to return it as a 9860 but 0x58d21 as the reg
value.    The and with AR_PHY_AGC_CONTROL of 1 obviously returns
0x58d21

debug output when trying to bring up the device.

ath: ah->misc_mode 0x4
ath: timeout (100000 us) on reg 0x9860: 0x00058d21 & 0x00000001 != 0x00000000
ath: offset calibration failed to complete in 1ms; noisy environment?
ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)

By resetting AR_PHY_AGC_CONTROL to 0x00000000 the above errors go
away, but still no ability to see traffic on any of the interfaces.

I dont understand fully the structures, so any pointers into how to
configure this radio would be appreciated.

Thanks!

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Mohammed Shafi]

On Mon, Jul 18, 2011 at 3:46 AM, Kelly Hogan <kshogan@bluemesh.net> wrote:
> Hi all,
>
> I'm trying to get the UBNT AirRouter to work with latest ath9k and am
> finding that it is failing in the ath9k_hw_wait with a timeout fail.
>
> The ah structure appears to return it as a 9860 but 0x58d21 as the reg
> value. ? ?The and with AR_PHY_AGC_CONTROL of 1 obviously returns
> 0x58d21
>
> debug output when trying to bring up the device.
>
> ath: ah->misc_mode 0x4
> ath: timeout (100000 us) on reg 0x9860: 0x00058d21 & 0x00000001 != 0x00000000
> ath: offset calibration failed to complete in 1ms; noisy environment?
> ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)

can you please test, does this message appears even in a clean environment ?

>
> By resetting AR_PHY_AGC_CONTROL to 0x00000000 the above errors go
> away, but still no ability to see traffic on any of the interfaces.
>
> I dont understand fully the structures, so any pointers into how to
> configure this radio would be appreciated.
>
> Thanks!
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Felix Fietkau]

On 2011-07-18 12:16 AM, Kelly Hogan wrote:
> Hi all,
>
> I'm trying to get the UBNT AirRouter to work with latest ath9k and am
> finding that it is failing in the ath9k_hw_wait with a timeout fail.
>
> The ah structure appears to return it as a 9860 but 0x58d21 as the reg
> value.    The and with AR_PHY_AGC_CONTROL of 1 obviously returns
> 0x58d21
>
> debug output when trying to bring up the device.
>
> ath: ah->misc_mode 0x4
> ath: timeout (100000 us) on reg 0x9860: 0x00058d21&  0x00000001 != 0x00000000
> ath: offset calibration failed to complete in 1ms; noisy environment?
> ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
>
> By resetting AR_PHY_AGC_CONTROL to 0x00000000 the above errors go
> away, but still no ability to see traffic on any of the interfaces.
>
> I dont understand fully the structures, so any pointers into how to
> configure this radio would be appreciated.
What kind of wifi chip does this device have? AR9280 or AR9287?
What is the value of
/sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask and tx_chainmask?

- Felix

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Kelly Hogan]

Yes, clean environment reports same error.  Device is 9285, nearly
exactly same as UBNT bullet M.    I popped the AR_PHY_TIMEOUT to
100000 just to see if it was slow.

root at OpenWrt:/# dmesg | grep phy
Determined physical RAM map:
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=72
root at OpenWrt:/# dmesg | grep ath
\ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
Registered led device: ath9k-phy0

iw list shows:

root at OpenWrt:/# iw list
Wiphy phy0
        Band 1:
                Capabilities: 0x11ce
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT RX MCS rate indexes supported: 0-15
                TX unequal modulation not supported
                HT TX Max spatial streams: 1
                HT TX MCS rate indexes supported may differ
                Frequencies:
                        * 2412 MHz [1] (27.0 dBm)
                        * 2417 MHz [2] (27.0 dBm)
                        * 2422 MHz [3] (27.0 dBm)
                        * 2427 MHz [4] (27.0 dBm)
                        * 2432 MHz [5] (27.0 dBm)
                        * 2437 MHz [6] (27.0 dBm)
                        * 2442 MHz [7] (27.0 dBm)
                        * 2447 MHz [8] (27.0 dBm)
                        * 2452 MHz [9] (27.0 dBm)
                        * 2457 MHz [10] (27.0 dBm)
                        * 2462 MHz [11] (27.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        Coverage class: 0 (up to 0m)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * new_beacon
                 * new_station
                 * new_mpath
                 * set_mesh_params
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * action
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * connect
                 * disconnect
        Supported TX frame types:
                 * IBSS: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050
0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * managed: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050
0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * AP: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050
0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * AP/VLAN: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050
0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
                 * mesh point: 0x0000 0x0010 0x0020 0x0030 0x0040
0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0
0x00f0
                 * P2P-client: 0x0000 0x0010 0x0020 0x0030 0x0040
0x0050 0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0
0x00f0
                 * P2P-GO: 0x0000 0x0010 0x0020 0x0030 0x0040 0x0050
0x0060 0x0070 0x0080 0x0090 0x00a0 0x00b0 0x00c0 0x00d0 0x00e0 0x00f0
        Supported RX frame types:
                 * IBSS: 0x00d0
                 * managed: 0x0040 0x00d0
                 * AP: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                 * AP/VLAN: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0
                 * mesh point: 0x00b0 0x00c0 0x00d0
                 * P2P-client: 0x0040 0x00d0
                 * P2P-GO: 0x0000 0x0020 0x0040 0x00a0 0x00b0 0x00c0 0x00d0




On Mon, Jul 18, 2011 at 12:40 AM, Mohammed Shafi
<shafi.wireless@gmail.com> wrote:
> On Mon, Jul 18, 2011 at 3:46 AM, Kelly Hogan <kshogan@bluemesh.net> wrote:
>> Hi all,
>>
>> I'm trying to get the UBNT AirRouter to work with latest ath9k and am
>> finding that it is failing in the ath9k_hw_wait with a timeout fail.
>>
>> The ah structure appears to return it as a 9860 but 0x58d21 as the reg
>> value. ? ?The and with AR_PHY_AGC_CONTROL of 1 obviously returns
>> 0x58d21
>>
>> debug output when trying to bring up the device.
>>
>> ath: ah->misc_mode 0x4
>> ath: timeout (100000 us) on reg 0x9860: 0x00058d21 & 0x00000001 != 0x00000000
>> ath: offset calibration failed to complete in 1ms; noisy environment?
>> ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
>
> can you please test, does this message appears even in a clean environment ?
>
>>
>> By resetting AR_PHY_AGC_CONTROL to 0x00000000 the above errors go
>> away, but still no ability to see traffic on any of the interfaces.
>>
>> I dont understand fully the structures, so any pointers into how to
>> configure this radio would be appreciated.
>>
>> Thanks!
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
>
> --
> shafi
>

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Kelly Hogan]

Thanks for the response!

This is a 9285 and similar to the UBNT Bullet M radio I believe.

root at OpenWrt:/# dmesg | grep phy
Determined physical RAM map:
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=72
root at OpenWrt:/# dmesg | grep ath
\ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
Registered led device: ath9k-phy0

root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat rx_chainmask
0x00000003
root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat tx_chainmask
0x00000001



On Mon, Jul 18, 2011 at 12:40 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> On 2011-07-18 12:16 AM, Kelly Hogan wrote:
>>
>> Hi all,
>>
>> I'm trying to get the UBNT AirRouter to work with latest ath9k and am
>> finding that it is failing in the ath9k_hw_wait with a timeout fail.
>>
>> The ah structure appears to return it as a 9860 but 0x58d21 as the reg
>> value. ? ?The and with AR_PHY_AGC_CONTROL of 1 obviously returns
>> 0x58d21
>>
>> debug output when trying to bring up the device.
>>
>> ath: ah->misc_mode 0x4
>> ath: timeout (100000 us) on reg 0x9860: 0x00058d21& ?0x00000001 !=
>> 0x00000000
>> ath: offset calibration failed to complete in 1ms; noisy environment?
>> ath: Unable to reset hardware; reset status -5 (freq 2412 MHz)
>>
>> By resetting AR_PHY_AGC_CONTROL to 0x00000000 the above errors go
>> away, but still no ability to see traffic on any of the interfaces.
>>
>> I dont understand fully the structures, so any pointers into how to
>> configure this radio would be appreciated.
>
> What kind of wifi chip does this device have? AR9280 or AR9287?
> What is the value of
> /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask and tx_chainmask?
>
> - Felix
>

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Felix Fietkau]

On 2011-07-18 6:02 PM, Kelly Hogan wrote:
> Thanks for the response!
>
> This is a 9285 and similar to the UBNT Bullet M radio I believe.
>
> root at OpenWrt:/# dmesg | grep phy
> Determined physical RAM map:
> ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> Registered led device: ath9k-phy0
> ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=72
> root at OpenWrt:/# dmesg | grep ath
> \ath: EEPROM regdomain: 0x0
> ath: EEPROM indicates default country code should be used
> ath: doing EEPROM country->regdmn map search
> ath: country maps to regdmn code: 0x3a
> ath: Country alpha2 being used: US
> ath: Regpair used: 0x3a
> Registered led device: ath9k-phy0
>
> root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat rx_chainmask
> 0x00000003
> root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat tx_chainmask
> 0x00000001
I'm pretty sure that explains your problems - the rx chainmask is wrong.
The AR9285 chipset is single-stream and thus cannot have a chainmask of 
3 (which would imply dual-stream MIMO Rx).

Try echo 1 > rx_chainmask, and then restart wifi.
If that fixes the issue for you, I'll make a patch to make ath9k 
validate the chainmask settings from the EEPROM and fix them if they're 
wrong.

- Felix

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Outback Dingo]

Try echo 1 > rx_chainmask, and then restart wifi.

> If that fixes the issue for you, I'll make a patch to make ath9k
> validate the chainmask settings from the EEPROM and fix them if they're
> wrong.


Yes, confirmed this does bring up wireless on the AP Ubiquiti AirRouter




> - Felix
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110718/b054fae2/attachment.htm 

[ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?

[Adrian Chadd]

.. so Ubiquiti shipped the units with bad chainmask settings?

Can someone do a dump and see what the rcchainmask field is (Not
rxchainmask, r_c_ chainmask.)

Thanks,


adrian

On 19 July 2011 09:46, Outback Dingo <outbackdingo@gmail.com> wrote:
> Try echo 1 > rx_chainmask, and then restart wifi.
>>
>> If that fixes the issue for you, I'll make a patch to make ath9k
>> validate the chainmask settings from the EEPROM and fix them if they're
>> wrong.
>
> Yes, confirmed this does bring up wireless on the AP?Ubiquiti AirRouter
>
>
>>
>> - Felix
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>