On 27.12.2014 01:43, Ben Hutchings wrote: > On Sat, 2014-12-13 at 21:51 +0100, Lukasz Stelmach wrote: >> On 11.12.2014 21:57, Ben Hutchings wrote: >>> On Thu, 2014-12-11 at 19:28 +0100, Łukasz Stelmach wrote: >>>> Package: installation-reports >>>> Severity: important [...] >> That's strange, apparently the card has been prepared to be for >> Australians, who can use channel 13. >> >> --8<---------------cut here---------------start------------->8--- >> Dec 13 18:15:35 main-menu[392]: INFO: Menu item 'ethdetect' selected >> Dec 13 18:15:36 kernel: [ 112.707682] cfg80211: Calling CRDA to update world regulatory domain >> Dec 13 18:15:36 kernel: [ 112.716130] ath9k 0000:03:00.0: setting latency timer to 64 >> Dec 13 18:15:36 kernel: [ 112.723098] ath: EEPROM regdomain: 0x21 >> Dec 13 18:15:36 kernel: [ 112.723101] ath: EEPROM indicates we should expect a direct regpair map >> Dec 13 18:15:36 kernel: [ 112.723103] ath: Country alpha2 being used: AU >> Dec 13 18:15:36 kernel: [ 112.723104] ath: Regpair used: 0x21 >> Dec 13 18:15:36 kernel: [ 112.726937] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' >> Dec 13 18:15:36 kernel: [ 112.727445] Registered led device: ath9k-phy0 >> Dec 13 18:15:36 kernel: [ 112.727450] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xffffc90011a00000, irq=30 >> Dec 13 18:15:38 kernel: [ 115.279119] ADDRCONF(NETDEV_UP): wlan0: link is not ready >> Dec 13 18:15:40 main-menu[392]: INFO: Menu item 'netcfg' selected >> --8<---------------cut here---------------end--------------->8--- > > This driver uses a table of maximum TX power per channel in the wireless > controller's EEPROM. It looks like when the 'regpair' value is 0x21 > then it expects to find ETSI rules for the 2.4 GHz band, allowing use of > channel 13, but it might not. > > Does the interface work on channel 13 after installation? (And assuming > that you install crda.) Yes it does. -- Było mi bardzo miło. Twoje oczy lubią mnie >Łukasz< i to mnie zgubi (c)SNL
Attachment:
signature.asc
Description: OpenPGP digital signature