2007/11/26, Pavel Roskin <[EMAIL PROTECTED]>: > On Sat, 2007-11-24 at 15:45 +0200, Nick Kossifidis wrote: > > Hello ppl ;-) > > > > In order to get 5424/2424 pci-e cards working we need a full register > > dump (that means a dump when connected on an AP) from madwifi. > > I have a PCI-E card, but MadWifi won't work with it: > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:03:00.0 to 64 > Uhhuh. NMI received for unknown reason a1. > MadWifi: unable to attach hardware: 'Hardware revision not supported' (HAL > status 13) > You have some hardware problem, likely on the PCI bus. > Dazed and confused, but trying to continue > ACPI: PCI interrupt for device 0000:03:00.0 disabled > > Neither does ath_info work: > > # lspci -nv -s 03:00.0 > 03:00.0 0200: 168c:001c (rev 01) > Subsystem: 147b:1033 > Flags: bus master, fast devsel, latency 0, IRQ 17 > Memory at dfbf0000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [40] Power Management version 2 > Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- > Queue=0/0 Enable- > Capabilities: [60] Express Legacy Endpoint IRQ 0 > Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > > # ath_info dfbf0000 > Unable to read EEPROM Magic value! > > "Hardware revision not supported" suggests that NMI is not the issue. > > By the way, ath_info doesn't work with devices behind non-transparent > bridges, such as RouterBoard RB14. That may be the reason it's not > working, as the PCIe devices sit on a separate bus. Maybe we should > consider using it with libpciaccess. > > And that's what the current ath5k says about it: > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 > PCI: Setting latency timer of device 0000:03:00.0 to 64 > ath5k_hw_nic_wakeup: failed to resume the MAC Chip > ACPI: PCI interrupt for device 0000:03:00.0 disabled > ath5k_pci: probe of 0000:03:00.0 failed with error -5 > > If I could get ath_info to work, I could try to remove the subsystem ID. > I remember Atheros HAL doesn't like ABIT devices. >
That seems to be the problem also for another user, resently posted on linux-wireless (CCing Majo). Weird thing is that 5416 is also pci-e and i can at least read stuff etc from it (both with ath_info and ath5k), so bridge seems to be the problem. We need to see what's going on in pci_probe, maybe we need to tweak it a little. In Majo's case this is a dump from madwifi-trace... R:0x04004 = 0xffffffff - unknown W:0x04004 = 0xfffcffff - unknown R:0x04010 = 0xffffffff - unknown R:0x04004 = 0xffffffff - unknown W:0x04004 = 0xfffcffff - unknown R:0x04010 = 0xffffffff - unknown R:0x04004 = 0xffffffff - unknown W:0x04004 = 0xfffcffff - unknown That's why madwifi won't work either, it can't read anything from the card (so it tries to read srev and it gets 0xffffffff, so HAL returns unsupported revision). -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
