NetBSD Problem Report #25928
Received: (qmail 12815 invoked by uid 605); 14 Jun 2004 20:26:27 -0000
Message-Id: <20040614202506.C9BCB11151@narn.netbsd.org>
Date: Mon, 14 Jun 2004 20:25:06 +0000 (UTC)
From: paul@plectere.com
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: paul@plectere.com
To: gnats-bugs@gnats.NetBSD.org
Subject: Atheros driver fails for D-Link DWL-AG530 PCI card
X-Send-Pr-Version: 3.95
>Number: 25928
>Notify-List: paul@plectere.com, dyoung@netbsd.org
>Category: kern
>Synopsis: ath driver fails with "unable to collect channel list from hal"
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: dyoung
>State: feedback
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Jun 14 20:27:00 +0000 2004
>Closed-Date:
>Last-Modified: Sat Dec 31 04:26:49 +0000 2022
>Originator: Paul Shupak
>Release: NetBSD 2.0F
>Organization:
>Environment:
System: NetBSD svcs 2.0F NetBSD 2.0F (SVCS) #208: Fri Jun 4 06:26:25 PDT 2004 ro
ot@svcs:/sys/arch/i386/compile/SVCS i386
Architecture: i386
Machine: i386
>Description:
When using a D-Link DWL-AG530, the Atheros contributed driver fails
with "unable to collect channel list from hal" during its initialization,
rendering the card unusable.
For anyone who can interpret the following data, it may be useful:
*** Relevant dmesg portion ***
ath0 at pci2 dev 13 function 0
ath0: interrupting at ioapic0 pin 21 (irq 11)
ath0: mac 5.9 phy 4.3 5ghz radio 3.6
ath0: unable to collect channel list from hal
*********************
A partial register and EEPROM dump using local tools (possibly
with mislabeled register names/functions) :
register state:
TXDP0 00000000 TXDP1 00000000 CR 00000000 RXDP 00000000
CFG 00000100 ISR 00000000 IMR 00000000 IER 00000000
BCR 00000000 TXCFG 00008015 RXCFG 00000005 MIBC 00000000
TOPS 00000008 RXNOFR 00000008 TXNOFR 00000010 RPGTO 00000000
RFCNT 0000001f MISC 00000000 RC 00000000 SCR 00000000
INTPEND 00000000 SFR 00000000 PCICFG 00000034 GPIOCR 00000000
SREV 00000059 STA_ID0 f5880d00 STA_ID1 0880103f BSS_ID0 ffffffff
BSS_ID1 0000ffff SLOT_TIM 00000000 TIME_OUT 08400840 RSSI_THR 00000700
RETRY_LM 128d93ab USEC 00000000 BEACON 00000000 CFP_PER 00000030
TIMER0 0007ffff TIMER1 01ffffff TIMER2 00000031 TIMER3 00000000
IFS0 fdfbfecf IFS1 dd9fbfff CFP_DUR 00000000 RX_FILTR 60875972
MCAST_0 fff7f7f8 MCAST_1 00000000 TXMASK0 00000001 TXMASK1 ffffc7ff
TRIGLEV 00000000 DIAG_SW 00000000 TSF_L32 00000000 TSF_U32 00000000
LAST_TST fffff5ef RETRYCNT 00000000 BACKOFF 00000000 NAV 00000000
RTS_OK 00000000 RTS_FAIL 00000000 ACK_FAIL 00000000 FCS_FAIL 00000000
BEAC_CNT 00000000
EEPROM Data:
0x0000: 70-8E 00-00 13-00 8C-16 00-02 01-00 00-00 01-50 p..............P
0x0008: 00-00 14-3A 86-11 0A-1C 00-01 00-00 C2-01 02-00 ...:............
0x0010: 06-C6 01-00 00-00 00-00 00-00 00-00 00-00 00-00 ................
0x0018: 00-00 00-00 00-00 00-00 00-00 00-00 00-00 10-3F ...............?
0x0020: F5-88 0D-00 00-00 00-00 00-00 00-00 00-00 00-00 ................
0x0028: 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 ................
0x0030: 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 ................
0x0038: 00-00 00-00 00-00 00-00 00-00 00-00 00-00 A5-5A ...............Z
0x0040: 00-00 00-00 13-03 43-49 53-20 04-71 02-12 00-04 ......CIS .q....
0x0048: 06-03 01-00 00-00 00-05 0E-41 B1-39 B5-1E 2D-4E .........A.9..-N
0x0050: 56-30 FF-FF 02-E9 00-07 06-01 00-00 00-01 00-15 V0..............
0x0058: 52-07 01-41 74-68 65-72 6F-73 20-43 6F-6D 6D-75 R..Atheros Commu
0x0060: 6E-69 63-61 74-69 6F-6E 73-2C 20-49 6E-63 2E-00 nications, Inc..
0x0068: 41-52 35-30 30-31 2D-30 30-30 30-2D 30-30 30-30 AR5001-0000-0000
0x0070: 00-57 69-72 65-6C 65-73 73-20 4C-41 4E-20 52-65 .Wireless LAN Re
0x0078: 66-65 72-65 6E-63 65-20 43-61 72-64 00-30 30-00 ference Card.00.
0x0080: FF-00 00-21 02-06 01-22 05-02 80-8D 5B-00 22-05 ...!..."....[.".
0x0088: 02-40 54-89 00-22 05-02 00-1B B7-00 22-05 02-80 .@T.."......"...
0x0090: A8-12 01-22 05-02 00-36 6E-01 22-05 02-00 51-25 ..."...6n."...Q%
0x0098: 02-22 05-02 00-6C DC-02 22-05 02-80 F9-37 03-22 ."...l.."....7."
0x00A0: 05-02 00-A2 4A-04 22-02 03-08 22-08 04-06 00-00 ....J."...".....
0x00A8: 04-7F 00-00 22-02 05-01 FF-00 00-00 00-00 00-00 ...."...........
0x00B0: 00-00 00-00 43-42 34-32 33-35 41-5F 39-39 39-39 ....CB4235A_9999
0x00B8: 61-30 00-00 00-00 00-00 00-00 00-00 00-00 00-F0 a0..............
0x00C0: 9B-D5 12-00 1A-80 08-40 07-1A 01-04 05-42 9B-01 .......@.....B..
0x00C8: 01-01 02-14 03-00 00-00 00-00 00-00 00-00 00-00 ................
0x00D0: 00-00 00-00 00-00 00-00 00-00 00-00 3C-2D 42-00 ............<-B.
0x00D8: 00-00 08-01 00-00 49-E0 92-24 0F-02 0E-00 CA-B0 ......I..$......
0x00E0: A3-21 22-40 01-00 0B-00 00-00 00-00 00-00 00-00 .!"@............
0x00E8: 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 ................
0x00F0: 00-00 00-00 00-00 00-00 78-28 52-00 20-08 48-81 ........x(R. .H.
0x00F8: 82-20 22-DA 1C-02 07-00 FF-B0 A3-01 12-40 01-00 . "..........@..
>How-To-Repeat:
Plug in a D-Link DWL-AG530 and boot a kernel with the ath driver.
>Fix:
Don't know, but after seeing a similar report for the DWL-AG520 on
sourceforge, I ported forward both of the 0.9.9.3 and 0.9.9.12/WPA HALs, but
found the same result, so simply updating won't fix it (the DWL-AG520 is
reported to work with 0.9.9.3 but not 0.9.9.12). It appears to be the
interpretation of the CountryCode/Regulatory Domain in the EEPROM that
causes the problems.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: kern-bug-people->dyoung
Responsible-Changed-By: dyoung
Responsible-Changed-When: Mon Jun 14 22:29:41 UTC 2004
Responsible-Changed-Why:
Looks like another one for me.
State-Changed-From-To: open->feedback
State-Changed-By: dyoung@netbsd.org
State-Changed-When: Sat, 23 Sep 2006 23:02:19 +0000
State-Changed-Why:
Do you still see this problem on -current?
From: Paul Shupak <paul@Plectere.com>
To: gnats-bugs@NetBSD.org
Cc: paul@Plectere.com
Subject: Re: kern/25928 (ath driver fails with "unable to collect channel list from hal")
Date: Sun, 24 Sep 2006 10:02:21 -0700 (PDT)
The symtoms are different, but the driver/HAL still fail. More
recent HALs assign part of the 4.9GHz band to the regulatory domain 0x18.
The correct frquencies are UNI-II and UNI-III minus channel 50 (see the
FCC notes for this - the sidebands are out-of-spec on channel 50; the
windows driver does *not* enforce this restriction). The UNI-I band does
not allow a device to have removable antenna(s) (i.e. channels 36-48).
Unless Atheros chooses to put in a fix for D-Link cards, the only
"real" fix is reprogramming the EEPROM (which then works very well, but
allows operation on illegal frequencies); Possibly a note could/should
be added to the man page simply saying that many D-Link cards are not
compatible with "ath" and the bug then closed.
Paul Shupak
State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 04 May 2008 02:52:21 +0000
State-Changed-Why:
feedback received.
State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 31 Dec 2022 04:26:49 +0000
State-Changed-Why:
Is this issue still current? All the ath stuff changed...
>Unformatted:
(Contact us)
$NetBSD: gnats-precook-prs,v 1.4 2018/12/21 14:20:20 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.