From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 28 13:49:01 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 8B6681065689; Sun, 28 Sep 2008 13:49:01 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.ipv6.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 1BD258FC1D; Sun, 28 Sep 2008 13:49:00 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 743EC3A6BC; Sun, 28 Sep 2008 15:48:58 +0200 (CEST) Date: Sun, 28 Sep 2008 15:48:58 +0200 From: Lars Engels To: Frank Mayhar Message-ID: <20080928134858.GO89204@e.0x20.net> References: <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2" Content-Disposition: inline In-Reply-To: <1222560406.89800.10.camel@jill.exit.com> X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: Sam Leffler , freebsd-mobile Subject: Re: Atheros wireless problems. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2008 13:49:01 -0000 --lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 27, 2008 at 05:06:46PM -0700, Frank Mayhar wrote: > On Thu, 2008-09-25 at 08:53 -0700, Sam Leffler wrote: > > 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 tod= ay, > > > I installed it tonight and, well, problems. > > The status codes look bogus. In 0.10.5.10 there is a code path through= =20 > > reset where status is not set if the chip is not brought out of low=20 > > power mode. Why this might happen is beyond me (could be a cardbus=20 > > problem) but if you initialize status to a known value before the hal= =20 > > calls that are failing this might confirm that as the problem. I've=20 > > fixed the hal fwiw. >=20 > That's definitely not the problem, it seems. I modified the driver to > zero 'status' in each of the routines that emit the message. When I ran > it today, it emitted the 'device timeout' and 'unable to reset hardware' > messages: >=20 [...] > Anything else I might try? Are you running hald? I have the same error messages and can work around that problem by inserting the wireless card after hald is started. --lEGEL1/lMxI0MVQ2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjfi0oACgkQKc512sD3afibuACdGCzzR7Z9NwBQHpQArdj8pB7h XEoAniGgY6JxmtPwrOIeBmGPYQ01Az+Z =gUX9 -----END PGP SIGNATURE----- --lEGEL1/lMxI0MVQ2--