Modify

Opened 5 years ago

Closed 4 years ago

#13064 closed defect (fixed)

[ath9k][orion][WRT350n v2]: wrong rx_chainmask disables wireless

Reported by: paxmanpwnz@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

On my WRT350n v2 2.0 the wireless is always down if rx_chainmask has the default value of 0x00000005; i.e. Luci shows that wireless is enabled and I can scan for networks - in luci or via shell (iw ... scan) - but AP (mode master) is always down (scan for network on laptop doesn't find it) and STA (client mode) can't connect to selected AP, it forever loops with "authenticating->direct probe to ... (3x)->authentication time out" cycle. Dmesg and kernel log haven't got any error messages that I can see.

I found out that I can bring up AP and connect to other AP with STA if I set rx_chainmask manually to 0x00000007:

echo 0x00000007 > /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask

writing it again with the default value didn't help. Maybe because this is the value in eeprom data (tx_chainmasks are the same):

root@OpenWrt:/# cat /sys/kernel/debug/ieee80211/phy0/ath9k/base_eeprom 
       Major Version :         14
       Minor Version :          2
            Checksum :      37089
              Length :       3256
          RegDomain1 :         55
          RegDomain2 :          0
             TX Mask :          7
             RX Mask :          7
          Allow 5GHz :          0
          Allow 2GHz :          1
   Disable 2GHz HT20 :          0
   Disable 2GHz HT40 :          0
   Disable 5Ghz HT20 :          0
   Disable 5Ghz HT40 :          0
          Big Endian :          0
   Cal Bin Major Ver :          0
   Cal Bin Minor Ver :          3
       Cal Bin Build :          4
 OpenLoop Power Ctrl :          0
          MacAddress : 00:XX:XX:XX:XX:7e

?

If I power cycle the router with chainmask set manually, the rx_chainmask is again the default (0x0...5) value and wireless is down again.
The workaround is to put

echo 0x00000007 > /sys/kernel/debug/ieee80211/phy0/ath9k/rx_chainmask

in /etc/rc.local and now wireless is up and running when the router starts.

I'm using custom compiled Barrier Breaker r35759 with Atheros debug enabled. Doesn't matter which hostapd, wpa_supplicant package (mini, full, ...) is installed, the result is the same.

Attaching wireless (wireless client, AFAIK) and network settings.

Attachments (2)

wireless (647 bytes) - added by paxmanpwnz@… 5 years ago.
wireless config
network (604 bytes) - added by paxmanpwnz@… 5 years ago.
network config

Download all attachments as: .zip

Change History (5)

Changed 5 years ago by paxmanpwnz@…

wireless config

Changed 5 years ago by paxmanpwnz@…

network config

comment:1 Changed 4 years ago by Petri

Thank you for this post! This helped me to solve the same problem for Linksys WRT350N v2.
I'm using firmware version 12.09.

comment:2 Changed 4 years ago by paxmanpwnz@…

In Chaos Calmer r41936 this problem seems to be fixed.

comment:3 Changed 4 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.