Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Sep 2008 13:52:20 -0700
From:      Frank Mayhar <frank@exit.com>
To:        Lars Engels <lme@FreeBSD.org>
Cc:        Sam Leffler <sam@FreeBSD.org>, freebsd-mobile <freebsd-mobile@FreeBSD.org>
Subject:   Re: Atheros wireless problems.
Message-ID:  <1222635140.46610.0.camel@jill.exit.com>
In-Reply-To: <20080928134858.GO89204@e.0x20.net>
References:  <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> <20080928134858.GO89204@e.0x20.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2008-09-28 at 15:48 +0200, Lars Engels wrote:
> 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 today,
> > > > I installed it tonight and, well, problems.
> > > 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.
> > 
> > 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:
> > 
> 
> [...]
> 
> > 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.

How very very weird.  That worked.  Why might this be?  It's quite
clearly a driver/application problem of some kind...
-- 
Frank Mayhar frank@exit.com     http://www.exit.com/
Exit Consulting                 http://www.gpsclock.com/
                                http://www.exit.com/blog/frank/
                                http://www.zazzle.com/fmayhar*



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1222635140.46610.0.camel>