From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 25 15:53:33 2008 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BEF81065688 for ; Thu, 25 Sep 2008 15:53:33 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0089B8FC23 for ; Thu, 25 Sep 2008 15:53:32 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8PFrJkR084643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Sep 2008 08:53:19 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48DBB3EF.3060909@freebsd.org> Date: Thu, 25 Sep 2008 08:53:19 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: frank@exit.com References: <1222317948.1740.10.camel@jill.exit.com> In-Reply-To: <1222317948.1740.10.camel@jill.exit.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-mobile Subject: Re: Atheros wireless problems. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2008 15:53:33 -0000 Frank Mayhar wrote: > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > believe) Atheros chipset in it; it's an a/b/g card. This is to use > while the chipset embedded in my laptop isn't supported. It came today, > I installed it tonight and, well, problems. > > I can get it to associate and, sometimes, even to get an IP address, but > as soon as I start trying to actually pass traffic on it, all hell > breaks loose. It starts timing out and the ath_hal starts complaining. > > Essential information: > > ath0@pci0:57:0:0: class=0x020000 card=0x3a631186 chip=0x0013168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet > ath0: flags=8843 metric 0 mtu 2290 > ether 00:13:46:11:6b:41 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:13:46:11:6b:41 > inet6 fe80::213:46ff:fe11:6b41%wlan0 prefixlen 64 scopeid 0x4 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid Unwired channel 1 (2412 Mhz 11g) bssid 00:1f:33:82:2f:6d > regdomain FCC indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF TKIP 2:128-bit txpower 18 bmiss 7 scanvalid 450 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS > wme burst ff roaming MANUAL > > >From the dmesg: > ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 5.9 phy 4.3 radio 3.6 > wlan0: Ethernet address: 00:13:46:11:6b:41 > > Then from /var/log/messages: > Sep 24 21:14:11 kernel: ath0: device timeout > Sep 24 21:14:11 kernel: ath0: ath_reset: unable to reset hardware; hal status 3230480741 > > I've also seen: > Sep 24 21:03:55 auton kernel: ath0: unable to reset hardware; hal status 3310983360 > Sep 24 21:02:35 auton kernel: ath0: unable to reset hardware; hal status 0 > > But it has only been those messages. I haven't yet tried turning on > bootverbose but I can if you would like. > > Any ideas? Any suggestions? As I sit here (using the wired em0 instead > of ath0) the lights on the card are happily blinking but it's not doing > anything at all. > The status codes look bogus. In 0.10.5.10 there is a code path through reset where status is not set if the chip is not brought out of low power mode. Why this might happen is beyond me (could be a cardbus problem) but if you initialize status to a known value before the hal calls that are failing this might confirm that as the problem. I've fixed the hal fwiw. Sam