Return-path: Received: from nf-out-0910.google.com ([64.233.182.191]:43662 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751008AbYEOQxF (ORCPT ); Thu, 15 May 2008 12:53:05 -0400 Received: by nf-out-0910.google.com with SMTP id d3so207261nfc.21 for ; Thu, 15 May 2008 09:53:03 -0700 (PDT) Message-ID: (sfid-20080515_185318_110595_CCB57149) Date: Thu, 15 May 2008 12:53:03 -0400 From: "Zack Weinberg" To: "Bob Copeland" Subject: Re: Getting ath5k driver working with Thinkpad T61 [168c:1014] Cc: linux-wireless@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 References: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, May 15, 2008 at 12:45 PM, Bob Copeland wrote: > On Thu, May 15, 2008 at 10:41 AM, Zack Weinberg 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