On Thu, May 15, 2008 at 12:45 PM, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote: > On Thu, May 15, 2008 at 10:41 AM, Zack Weinberg <zackw@xxxxxxxxx> wrote: >>> Interesting... can you confirm that madwifi also will not start from a cold >>> boot? >> >> Yes, madwifi will not start from a cold boot. > > Ugh, well that is not good. Does ndiswrapper work? I haven't tried it, but wireless does work under Windows (Vista, vendor installation). > Unless anyone > else has ideas, I would suggest capturing a trace using mmiotrace and > ndiswrapper to see what is going on. Someone on ath5k-devel list > might have a better idea. I don't know how to do that, can you point me at instructions? >> It's not hanging. The very first call to ath5k_hw_set_power(ah, >> AR5K_PM_AWAKE, true, 0); from ath5k_hw_nic_wakeup fails with -EIO, and >> the driver gives up. > > By 'hanging' I mean the register writes cease to do anything useful > and the card basically stops responding until you power off. Madwifi > will even give "Card didn't behave as expected" in this case Oh, okay. That is indeed the error message I'm getting from madwifi. zw -- 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
