Bug 41002 - ath5k ignores settings in ieee80211_regdom
Summary: ath5k ignores settings in ieee80211_regdom
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-12 07:06 UTC by Cijoml Cijomlovic Cijomlov
Modified: 2012-08-30 10:27 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.39.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Cijoml Cijomlovic Cijomlov 2011-08-12 07:06:08 UTC
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11
ath5k 0000:01:05.0: PCI INT A -> Link[LNKE] -> GSI 11 (level, low) -> IRQ 11
ath5k 0000:01:05.0: registered as 'phy0'
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ WHY!? I am NOT in US!!!

ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ath: Regpair used: 0x3a
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)

list of /etc/modprobe.d/ - i.e. channel 13 should be enabled
options cfg80211 ieee80211_regdom="EU"

notas:/home/cijoml# iwlist wlan0 channel
wlan0     32 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 36 : 5.18 GHz
          Channel 37 : 5.185 GHz
          Channel 38 : 5.19 GHz
          Channel 39 : 5.195 GHz
          Channel 40 : 5.2 GHz
          Channel 41 : 5.205 GHz
          Channel 42 : 5.21 GHz
          Channel 43 : 5.215 GHz
          Channel 44 : 5.22 GHz
          Channel 45 : 5.225 GHz
          Channel 46 : 5.23 GHz
          Channel 47 : 5.235 GHz
          Channel 48 : 5.24 GHz
          Channel 149 : 5.745 GHz
          Channel 150 : 5.75 GHz
          Channel 151 : 5.755 GHz
          Channel 152 : 5.76 GHz
          Channel 153 : 5.765 GHz
          Channel 154 : 5.77 GHz
          Channel 155 : 5.775 GHz
          Channel 156 : 5.78 GHz

But channel 13 is missing!!! Marked blocking since I can't network since our company network operates at channel 13. In Windows channel 13 is enabled automatically and card works!
Comment 1 John W. Linville 2011-08-12 13:36:56 UTC
The dmesg output is fairly plain -- the EEPROM on your device is set to default, and default maps to the US according to Atheros customs.

Regarding ieee80211_regdom, there is no "EU" domain and there hasn't been one for some time.  You would need to use a code appropriate to the country you are in.  But in this case your driver is overriding any such setting based on the EEPROM info.
Comment 2 Cijoml Cijomlovic Cijomlov 2011-08-12 15:57:53 UTC
It is stupid behaviour - Windows drivers allow for channel 13 and don't bother about EEPROM settings. I simply want same behaviour as in windows. This is unresolved bug. Sorry. Card is bought from official seller at Czech market since it must work in Czech republic at all the channels allowed in Czech republic.
Comment 3 John W. Linville 2011-08-12 16:58:50 UTC
Please don't play childish games with the bug status.  If you want to complain, complain to the vendor that improperly programmed the EEPROM.
Comment 4 Cijoml Cijomlovic Cijomlov 2011-08-17 05:56:57 UTC
I really must reopen this - yesterday I visited official service center of Atheros here in Czech  republic. They upgraded firmware in my card to latest version, but it still say US region. They told me, that there is not special firmware for EU users.

SO I REQUEST WORKAROUND SAME WE HAVE FOR CRIPPLED BIOSes...

Note You need to log in before you can comment on or make changes to this bug.