Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Jul 2003 05:31:50 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        brandt@fokus.fraunhofer.de
Cc:        FreeBSD-current@freebsd.org
Subject:   Re: Can't connect to wireless network with recent -CURRENT
Message-ID:  <20030703.053150.41960250.imp@bsdimp.com>
In-Reply-To: <20030703091732.F30117@beagle.fokus.fraunhofer.de>
References:  <20030703032544.GP29066@wantadilla.lemis.com> <20030703091732.F30117@beagle.fokus.fraunhofer.de>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030703091732.F30117@beagle.fokus.fraunhofer.de>
            Harti Brandt <brandt@fokus.fraunhofer.de> writes:
: I think the same problem was reported by Rob Holmes two weeks ago and by
: me (although with lesser detail) yesterday. I converted my kernel from
: OLDBUS to NEWBUS and now one out of four or five tries the card works, but
: this is really annoying. I have an Inspiron 8200 and an Avaya (that is a
: Lucent) card. I have found no solution until now.

The lucent problem is well known and has been known for a long time.
It was broken between 5.0 and 5.1 for some people with lucent cards
(not me and mine).  Enabling WITNESS seens to help, but that likely
means that it is a race that the overhead of WITNESS tickles in
certain ways.  Sam indicated he'd try to find some time to fix it.
There's something subtle going on with the lucent cards, and I've
given up trying to find it.  I just do't have the time.

Warner



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