#859: Support for AR5006EG-based (PCI express) cards
---------------------------------+------------------------------------------
Reporter: Tupac | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: version 0.9.3
Component: madwifi: other | Version: v0.9.2
Resolution: fixed | Keywords: AR5006EG PCI Express
Patch_attached: 0 |
---------------------------------+------------------------------------------
Comment (by VladoK):
Hi, I've just tried an AR5006EG (168c:001c) card with latest madwifi (svn
r1971) and all I get is 'Hardware revision not supported' (HAL status 13)
error message together with some other weird messages about NMI and RAM
chips:
{{{
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (svn r1971)
ath_rate_sample: 1.2 (svn r1971)
ath_pci: 0.9.4.5 (svn r1971)
ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:0c:00.0 to 64
Uhhuh. NMI received for unknown reason a1 on CPU 0.
You probably have a hardware problem with your RAM chips
Dazed and confused, but trying to continue
wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL
status 13)
ACPI: PCI interrupt for device 0000:0c:00.0 disabled
}}}
So, some details:
* Card: !AzureWave AW-GE780, FCC-ID PPD-AR5BXB63
* System: Dell Latitude D420 (removed ipw3945 and inserted this card
instead), kill switch disabled, Coro Solo cpu
* Kernel: 2.6.19 preempt no-SMP, gcc 4.1.2
lspci:
{{{
0c:00.0 Ethernet controller: Atheros Communications, Inc. Unknown device
001c (rev 01)
Subsystem: Unknown device 1a3b:1026
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 17
Region 0: Memory at efdf0000 (64-bit, non-prefetchable) [disabled]
[size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
Address: 00000000 Data: 0000
Capabilities: [60] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
ExtTag-
Device: Latency L0s <512ns, L1 <64us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal-
Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port
0
Link: Latency L0s <512ns, L1 <64us
Link: ASPM Disabled RCB 128 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
Vector table: BAR=0 offset=00000000
PBA: BAR=0 offset=00000000
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
}}}
I don't like those 'RAM chips' related messages, never seen something like
that before (and there are no memory problems otherwise). Unfortunately, I
cannot test the card in different system since this one is the only one
with MiniPCIe slot available, and also I cannot change memory since it is
onboard, but it passed memtest86 without erros (with card inserted).
Have anyone experienced such problems with this card? Or could it possibly
be madwifi-unrelated problem?
Thanks
--
Ticket URL: <http://madwifi.org/ticket/859>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
