Bug 179847 - Update regdomain in ath drivers including 0x165
Summary: Update regdomain in ath drivers including 0x165
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords: needs-qa
Depends on:
Blocks:
 
Reported: 2013-06-22 19:00 UTC by josias
Modified: 2022-11-30 16:06 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description josias 2013-06-22 19:00:00 UTC
The Atheros Card from Maomifadacai Commodity Co., Ltd is a AR9220 + AR9223. (reference: http://www.wholesale-in-china.org/sell/tradelead-85438.html) not work on FreeBSD 10 Current. 

Debug:

ath0: <Atheros 9280> mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
ath0: [ITHREAD]
ar9280Attach: sc 0xc2178000 st 0x1 sh 0xcc7c6000
ar5416SetPowerMode: AWAKE -> AWAKE (set chip )
ar9280Attach: ID 0x832ff VERSION 0x2 TYPE 0x3 REVISION 0x2
ath_hal_v14EepromAttach Eeprom Magic = 0xa55a
ath_hal_v14EepromAttach Eeprom Version 14.19
v14EepromReadCTLInfo Numctls = 18
ar5416SetPowerMode: AWAKE -> AWAKE (set chip )
ar9280RfAttach: attach AR9280 radio
enableAniMIBCounters: Enable mib counters: OfdmPhyErrBase 0xbffe0c cckPhyErrBase 0xbfff38
ar9280Attach: return
getchannels: cc 0 regDmn 0xf0 mode 0xffffff ecm
isEepromValid: invalid regulatory domain/country code 0x165
getregstate: invalid EEPROM contents
ath0: ath_getchannels: unable to collect channel list from hal, status 12
ar5416Detach:
ar5416SetPowerMode: AWAKE -> AWAKE (set chip )
Detaching Ani
Disable MIB counters
ar5212SetPowerMode: AWAKE -> AWAKE (set chip )
ar5416SetPowerMode: AWAKE -> FULL-SLEEP (set chip )
device_attach: ath0 attach returned 22

Apparently is a problem with regdomain 0x165.

How-To-Repeat: Just insert the card in mini-pci slot and power on freebsd.
The error "device_attach: ath0 attach returned 22" will be displayed.
Turn on ath debug to show the complete information.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-06-22 21:20:18 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-wireless

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:42:38 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:35:43 UTC
Keyword: 

    patch
or  patch-ready

– in lieu of summary line prefix: 

    [patch]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2022-11-30 16:06:34 UTC
Comment #3 was the result of a batch edit that matched bugs with [patch] in the summary line. 

There is no patch with this report (also, as a keyword, patch is deprecated). 

Since more than nine years have passed: can josias, or anyone with knowledge of Wi-Fi in FreeBSD, tell whether this bug – reported against FreeBSD 10-CURRENT – is reproducible with 14.0-CURRENT?