From owner-freebsd-drivers@FreeBSD.ORG  Thu Feb  1 17:21:58 2007
Return-Path: <owner-freebsd-drivers@FreeBSD.ORG>
X-Original-To: freebsd-drivers@freebsd.org
Delivered-To: freebsd-drivers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8C25516A400
	for <freebsd-drivers@freebsd.org>; Thu,  1 Feb 2007 17:21:58 +0000 (UTC)
	(envelope-from sam@errno.com)
Received: from ebb.errno.com (ebb.errno.com [69.12.149.25])
	by mx1.freebsd.org (Postfix) with ESMTP id 1DBF713C442
	for <freebsd-drivers@freebsd.org>; Thu,  1 Feb 2007 17:21:58 +0000 (UTC)
	(envelope-from sam@errno.com)
Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248])
	(authenticated bits=0)
	by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l11HLh6c099344
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 1 Feb 2007 09:21:44 -0800 (PST) (envelope-from sam@errno.com)
Message-ID: <45C221A7.80908@errno.com>
Date: Thu, 01 Feb 2007 09:21:43 -0800
From: Sam Leffler <sam@errno.com>
User-Agent: Thunderbird 1.5.0.8 (X11/20061115)
MIME-Version: 1.0
To: Benjamin Close <Benjamin.Close@clearchain.com>
References: <459E6477.2010508@clearchain.com>		<499c70c0701201038w6960174n3006ffd525f17bf6@mail.gmail.com>		<20070124204443.GA1107@bsdmon.com>	<45B9F697.1090402@clearchain.com>		<20070127101900.GB1099@bsdmon.com>		<11167f520701271114j66f82398h83c43885b9d25e12@mail.gmail.com>		<45C0B271.4040100@clearchain.com>
	<45C0B33B.9000807@FreeBSD.org>		<11167f520702010148w4cb84122r6412c2d8eebade74@mail.gmail.com>		<499c70c0702010153u65eda1fj67057753e5ccf800@mail.gmail.com>	<11167f520702010158x48534ab3jaae3d2b0be3d8417@mail.gmail.com>
	<45C1CD68.8090904@clearchain.com>
In-Reply-To: <45C1CD68.8090904@clearchain.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Sam Fourman Jr." <sfourman@gmail.com>, freebsd-drivers@freebsd.org
Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
X-BeenThere: freebsd-drivers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Writing device drivers for FreeBSD <freebsd-drivers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>, 
	<mailto:freebsd-drivers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-drivers>
List-Post: <mailto:freebsd-drivers@freebsd.org>
List-Help: <mailto:freebsd-drivers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-drivers>,
	<mailto:freebsd-drivers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2007 17:21:58 -0000

Benjamin Close wrote:
> This is normal, I turned debugging on in this driver so I could get some
> better error reports.
> The driver is constantly scanning looking for a host in which to
> associated. When it finds one it will stop scanning.
> Looking at the log messages....
> 
> You can see that a beacon is found on channel 3, 4,  5, 6 & 7 - note the
> rx intr occurring with a tstamp
> 802.11 actually spreads across 3 channels so you looking at it you
> probably have 2 wireless devices near by on different channels.
> 
> The thing we need to find out is why the driver never associated with
> either.
> Can you please install the wlandebug command and run:
> 
> wlandebug -i wpi0 0xffffff
> 
> then bring the device up.
> 
> Instructions are in the README.
> Then send me the results

Better is wlandebug -i wpi0 scan+auth+assoc.

	Sam