Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Sep 2008 07:51:10 +0200
From:      Lars Engels <lme@FreeBSD.org>
To:        frank@exit.com
Cc:        Sam Leffler <sam@FreeBSD.org>, freebsd-mobile <freebsd-mobile@FreeBSD.org>
Subject:   Re: Atheros wireless problems.
Message-ID:  <20080929075110.8f6vo3zus08kwss0@0x20.net>
In-Reply-To: <1222635140.46610.0.camel@jill.exit.com>
References:  <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> <20080928134858.GO89204@e.0x20.net> <1222635140.46610.0.camel@jill.exit.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format and has been PGP signed.

--=_28kvy3pvvqv4
Content-Type: text/plain;
	charset=UTF-8;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Quoting Frank Mayhar <frank@exit.com>:

> 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  =20
>> came today,
>> > > > I installed it tonight and, well, problems.
>> > > The status codes look bogus.  In 0.10.5.10 there is a code path throu=
gh
>> > > 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 ra=
n
>> > 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...


I don't know. I brought this up some time ago but noone had a clue...
It would be nice to find out how to prevent hald probing the cardbus, =20
so you could insert the card before starting hald.

--=_28kvy3pvvqv4
Content-Type: application/pgp-signature
Content-Description: Digitale PGP-Unterschrift
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEABECAAYFAkjgbM4ACgkQKc512sD3afh2cACgkrnNXf0hek8fozB2eYrS7nyC
ad0AoJn3BnzTNj6WNZ4wf/Fp23cSdaUT
=cy3I
-----END PGP SIGNATURE-----

--=_28kvy3pvvqv4--




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