Date: Thu, 28 Oct 2010 12:07:10 +0000 From: Paul B Mahol <onemda@gmail.com> To: Matthias Apitz <guru@unixarea.de> Cc: Alberto Villa <avilla@freebsd.org>, Scot Hetzel <swhetzel@gmail.com>, current@freebsd.org Subject: Re: Broadcom BCM4310 USB Controller (Wifi) Message-ID: <AANLkTi=ROfLOUnm5rqAQ6YoLxqkaw6kFPCJxbzjhp0Kf@mail.gmail.com> In-Reply-To: <20101028063255.GA17624@current.Sisis.de> References: <20101025080705.GA33315@current.Sisis.de> <AANLkTi=65roV5vxX54dHOsmcND6BgoUQiEsGq6skYagL@mail.gmail.com> <AANLkTim8PavYF60cnYQge5hzjzg4LFbXWj5vzz0uSikY@mail.gmail.com> <AANLkTi=cJXqV9S0DZ%2BYhqP9_LD9B1o7t13rPCcohE7op@mail.gmail.com> <AANLkTikXWWpnhJmcYLi3aSp3vRndCpP4dv2%2BxyM5RKP2@mail.gmail.com> <AANLkTikq6Ktf_pyTpq2bvmPpr0-0nkqyR3KWZA0j7Oe5@mail.gmail.com> <AANLkTi=8E_Kk1qc0LD3jVtw=sNAjJ4on45crbA1vvPRj@mail.gmail.com> <AANLkTi=0_KLrpAyd1cNiOz=njmFk7XiCLcDiaBApLWrU@mail.gmail.com> <20101028063255.GA17624@current.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/28/10, Matthias Apitz <guru@unixarea.de> 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 <avilla@freebsd.org> wrote: >> > On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol <onemda@gmail.com> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=ROfLOUnm5rqAQ6YoLxqkaw6kFPCJxbzjhp0Kf>