I'm sorry to have taken so long to get back to y'all. It turns out I was wrong about madwifi, it does work with this chipset. Either I was mistaken in thinking that the device had been untouched up to the point I tried to load ath_pci, or a change in a 2.6.25.x point release fixed it. ath_info also works now. >> ath_info does not work: >> # ath_info df3f0000 It now says: Warning: Invalid EEPROM Magic number! -==Device Information==- MAC Version: 2424 (0xa0) MAC Revision: 5424 (0xa3) 5Ghz PHY Revision: SChip (0xa2) 2Ghz PHY Revision: SChip (0xa2) -==EEPROM Information==- EEPROM Version: 5.3 EEPROM Size: 4K Regulatory Domain: 0x62 -==== Capabilities ====- | 802.11a Support: yes | | 802.11b Support: yes | | 802.11g Support: yes | | RFKill Support: yes | | 32KHz Crystal: no | ======================== GPIO registers: CR 00018003 DO 00000000 DI 0000000a > This one looks interesting, plz use ndiswrapper for your card and use > mmiotrace to see > what windows driver does in your situation that makes the card work. Since it works now with madwifi, I am attaching mmiotrace runs for ath5k (latest compat-wireless driver, which still doesn't work) and madwifi. Please let me know if you still want to see traces for the windows driver. (The madwifi trace also includes a successful "iwlist wlan0 scan" operation; the ath5k trace obviously does not.) zw
Attachment:
cpu0.ath5k.gz
Description: GNU Zip compressed data
Attachment:
cpu0.madwifi.gz
Description: GNU Zip compressed data
