From owner-freebsd-stable@FreeBSD.ORG Fri Oct 29 09:04:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4252A1065695 for ; Fri, 29 Oct 2010 09:04:23 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id D43BC8FC17 for ; Fri, 29 Oct 2010 09:04:22 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id E9B0AE7746; Fri, 29 Oct 2010 10:04:21 +0100 (BST) Received: from unknown (client-81-107-142-135.midd.adsl.virginmedia.com [81.107.142.135]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Fri, 29 Oct 2010 10:04:21 +0100 (BST) Date: Fri, 29 Oct 2010 10:04:14 +0100 From: Bruce Cran To: Message-ID: <20101029100414.00001337@unknown> In-Reply-To: References: X-Mailer: Claws Mail 3.7.6 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Intel PRO/Wireless 6050 in 8.1-RELEASE Problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2010 09:04:23 -0000 On Fri, 29 Oct 2010 02:32:52 -0600 wrote: > I've installed FreeBSD 8.1-RELEASE on a Dell Latitude E6410. Most > hardware works just fine, but I'm having a hell of a time with the > wifi. Everytime I try to associate with an access point, my terminal > replies with: > > jarvis# wpa_supplicant -i iwn0 -c /etc/wpa_supplicant.conf > ioctl[SIOCG80211, op 98, len 32]: Invalid argument > Failed to initialize driver interface > ELOOP: remaining socket: sock=4 eloop_data=0x28406140 > user_data=0x2840d040 handler=0x8069f70 I'm sure it's not the cause of the problem, but shouldn't you be running wpa_supplicant on the wlan0 interface, not the underlying iwn0? -- Bruce Cran