On Wed, Feb 06, 2008 at 11:42:40AM +0100, Jiri Slaby wrote: > On 02/05/2008 11:57 PM, Tino Keitel wrote: > > Hi, > > > > I tried the current git (9ef9dc69d4167276c04590d67ee55de8380bc1ad) and > > got the following error message from ath5k: > > > > ath5k_pci 0000:02:00.0: registered as 'phy0' > > ath5k phy0: failed to resume the MAC Chip > > ath5k_pci: probe of 0000:02:00.0 failed with error -5 > > We failed to resume after a hardware reset here for a whole second. Is there any > version of ath5k which worked for you (is this a regression)? I cannot speak for Tino, but my ath5k never worked in MacBook -- it failed the same way, and I believe the hardware was the same. My understanding was that it was a known bug with PCIE devices, but I got that out of reading list archives. > > > Here is the lspci -vnn output: > > > > 02:00.0 Ethernet controller [0200]: Atheros Communications, Inc. > > AR5006EG 802.11 b/g Wireless PCI Express Adapter [168c:001c] (rev 01) > > Subsystem: Apple Computer Inc. Unknown device [106b:0086] > > Flags: fast devsel, IRQ 17 > > Memory at 90100000 (64-bit, non-prefetchable) [disabled] > > [size=64K] > > Capabilities: [40] Power Management version 2 > > Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- > > Queue=0/0 Enable- > > Capabilities: [60] Express Legacy Endpoint, MSI 00 > > Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 > > Capabilities: [100] Advanced Error Reporting <?> > > Capabilities: [140] Virtual Channel <?> > > Kernel modules: ath5k > > > > The same device works with madwifi: > > > > ath_rate_sample: 1.2 (svn r3339) > > MadWifi: ath_attach: Switching per-packet transmit power control off > > wifi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps > > 24Mbps 36Mbps 48Mbps 54Mbps > > wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > > wifi0: H/W encryption support: WEP AES AES_CCM TKIP > > wifi0: ath_announce: Use hw queue 1 for WME_AC_BE traffic > > wifi0: ath_announce: Use hw queue 0 for WME_AC_BK traffic > > wifi0: ath_announce: Use hw queue 2 for WME_AC_VI traffic > > wifi0: ath_announce: Use hw queue 3 for WME_AC_VO traffic > > wifi0: ath_announce: Use hw queue 8 for CAB traffic > > wifi0: ath_announce: Use hw queue 9 for beacons > > ath_pci: wifi0: Atheros 5424/2424: mem=0x90100000, irq=17 > > > > I can also set the interface up and use iwlist ath0 scan. > > Hmm, I guess madwif-old-openhal doesn't work either. > > I suspect ath5k_hw_nic_wakeup being called before setting ah_single_chip in > ath5k_hw_attach. Could you test the attached patch? I cannot, as my MacBook is now broken. -- Joseph Fannin jfannin@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
