Date: Thu, 10 Nov 2005 08:02:00 -0800 From: Sam Leffler <sam@errno.com> To: Bill Paul <wpaul@freebsd.org> Cc: Peter Carah <pete@altadena.net>, freebsd-mobile@freebsd.org Subject: Re: Broadcom wireless ndis 64 bit Message-ID: <43736EF8.9090601@errno.com> In-Reply-To: <20051110083413.96AF716A420@hub.freebsd.org> References: <20051110083413.96AF716A420@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Paul wrote: >>>I agree. Give it another try. >> >>Much better, but still no cigar. Module loads and recognizes the hardware. >>One time it left the blue light on, and said WPA (different from yours...), but >>no throughput. Since then it never really turns on. Dmesg excerpt from boot >>(with module preloaded) follows: > > > Whoa whoa whoa. Not so fast. > > First thing you should have done is "ifconfig ndis0 up" followed by "ifconfig > ndis0 scan" and then checked to see if it could detect any of your local > wireless networks. If "ifconfig ndis0 scan" shows nothing, then you're not > even ready to try wpa_supplicant yet. > > [..] > > >>..... >>after this the ONLY messages from this driver are the fpudna ones, and >>wpa_supplicant never actually got a connection. Once I plugged the ath0 card >>in *it* worked but ndis never did. >>Oh well... >>Are there any debug flags that might help here, and if so how? > > > When Sam Leffler tried the same driver earlier today, he too whined that > after loading the driver, no networks were visible. Then I asked him if > he had a magic "turn the radio on/off" button on his laptop. It turns > out he does, and once he used it to turn the radio on, everything worked > as expected. > > So does your laptop have a "turn the radio on/off" switch on it and did > you remember to use it to turn the radio on? Note that under XP the radio on/off led reflects the rfkill state but operating in emulation under freebsd it does not. That's what confused me. Given that the led does flash to reflect traffic it's unclear if the driver we forced into use for the part is not exactly the right one or if there's something not being emulated that caused the on-off operations to be dropped. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43736EF8.9090601>