From owner-freebsd-current@FreeBSD.ORG  Wed Nov 19 15:02:00 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E3FF016A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 19 Nov 2003 15:02:00 -0800 (PST)
Received: from perrin.nxad.com (internal.nxad.com [69.1.70.251])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6B28443FD7
	for <freebsd-current@freebsd.org>;
	Wed, 19 Nov 2003 15:01:59 -0800 (PST)	(envelope-from sean@nxad.com)
Received: by perrin.nxad.com (Postfix, from userid 1001)
	id 5C71C2106A; Wed, 19 Nov 2003 15:01:19 -0800 (PST)
Date: Wed, 19 Nov 2003 15:01:19 -0800
From: Sean Chittenden <sean@chittenden.org>
To: Ryan Sommers <ryans@gamersimpact.com>
Message-ID: <20031119230118.GA6899@perrin.nxad.com>
References: <20031119223948.61677.qmail@neuroflux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031119223948.61677.qmail@neuroflux.com>
X-PGP-Key: finger seanc@FreeBSD.org
X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0  83A6 DD99 E31F BC84 B341
X-Web-Homepage: http://sean.chittenden.org/
User-Agent: Mutt/1.5.4i
cc: freebsd-current@freebsd.org
Subject: Re: DStumbler / BSD-AirTools Error with new Wi code?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Nov 2003 23:02:01 -0000

> I have been getting the following error when attempting to use dstumbler 
> with 5.1-RELEASE-p10: 
> 
> error: unable to ioctl device socket: Invalid argument 
> 
> After much searching around newsgroups/mailing lists it looks like the 
> Wi(4) code was changed and dstumbler never got updated. I found one patch 
> that supposedly fixed support on some cards, however, it didn't seem to 
> work on mine. Has anyone worked on this in -current? Or does anyone know of 
> patches that aren't in CVS yet that might work? 

I just updated it yesterday.  Update to 0.3 and things should work:

dstumbler wi0 -o

-sc

-- 
Sean Chittenden