From owner-freebsd-current@FreeBSD.ORG Thu Oct 28 12:36:19 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01CED10656AE for ; Thu, 28 Oct 2010 12:36:19 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7E87B8FC13 for ; Thu, 28 Oct 2010 12:36:18 +0000 (UTC) Received: by wyb42 with SMTP id 42so1805864wyb.13 for ; Thu, 28 Oct 2010 05:36:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=a/2CsiwxrOtLbldOI7j8UWinto6zTEjuHecXuiomDQo=; b=EvOQpoS+402/67XmrhzYnJSp5m8V9Qa0yGnpw++/EVebs1V52Y2yEK+qtvg3x4g4+M mcUxBYmRb8sPp40eDtyAXJoBl5a2DMaCR6apSGxqqgdFefmiqIlWDoZbIvDPEXy16w3l 9TDVlwq7kapg7QaOWRaVTkck4+pjC/7rkUPFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bGEcfHLNr4xdzQSsWP3S93uLIweBR8u0O2QRPDXw36lxo+LbnLgLLoFKWwc5r7Ybfh X+7h7205eyOLtJL2pYeQbuOzU0horv5+SaAvUmq7kHr/PdTaEuAcsFluxABn8+DKcMSG SWxj1iLsQyLQgQUSNmOdxHLf4LAFQ8brLUEM4= MIME-Version: 1.0 Received: by 10.216.158.140 with SMTP id q12mr131695wek.14.1288267631206; Thu, 28 Oct 2010 05:07:11 -0700 (PDT) Received: by 10.216.50.140 with HTTP; Thu, 28 Oct 2010 05:07:10 -0700 (PDT) In-Reply-To: <20101028063255.GA17624@current.Sisis.de> References: <20101025080705.GA33315@current.Sisis.de> <20101028063255.GA17624@current.Sisis.de> Date: Thu, 28 Oct 2010 12:07:10 +0000 Message-ID: From: Paul B Mahol To: Matthias Apitz Content-Type: text/plain; charset=ISO-8859-1 Cc: Alberto Villa , Scot Hetzel , current@freebsd.org Subject: Re: Broadcom BCM4310 USB Controller (Wifi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2010 12:36:19 -0000 On 10/28/10, Matthias Apitz wrote: > El dia Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel > escribio: > >> On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa wrote: >> > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol wrote: >> >> NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 >> >> driver. Note 5 vs 6 in driver name. >> >> Editing inf files will give you nothing. >> > >> > i've tried that driver, but apparently it doesn't support my card... >> > loading the .ko doesn't show anything... >> >> Where did you get your bcmwl5 driver? If you downloaded it from Acer, >> it should work. If you downloaded it from anywhere else then this >> might be why it didn't work for you. > > Following Scot's hint (thanks for this) I downloaded today morning the > WinXP x86 driver zip archive from www.Acer.com and built the bcmwl5_sys.ko > with > ndisgen(8). The system panics on early boot stages when the kmod was > pulled in via loader.conf. Newer drivers do that, I don't have solution. > > If the system is up, you can kldload the module fine and the interface > ndis0 appears and even the card gets associated with the AP (i.e. > wpa_supplicant(8) must work fine). > > The ifconfig(8) shows the interface as: > > ndis0: flags=8843 metric 0 mtu 2290 > ether 90:4c:e5:00:06:ce > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > > and the Wifi indicator light of the laptop is green. > > But: > > # dhclient ndis0 > ifconfig: ioctl (SIOCAIFADDR): Invalid argument > ndis0: not found > > and the same is with > > # ifconfig ndis0 192.168.2.200 > > All this is with a 8-CURRENT kernel/system as of May 2009. I will now build > a > USB key from HEAD and will continue testing. > On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. But note that such old CURRENT have few bugs in NDISulator. For example scan results are incomplete and scanning can trigger panic in some situations. If you use wpa_supplicant -Dndis you will never encounter such problems.