Date: Thu, 2 Mar 2017 23:34:11 -0500 From: Baho Utot <baho-utot@columbus.rr.com> To: freebsd-questions@freebsd.org Subject: Re: Firmware Message-ID: <0299093b-0dc4-5ee1-8810-971c51fe8044@columbus.rr.com> In-Reply-To: <58B8A303.1050701@SDF.org> References: <dce97bd5-4f0f-49c6-380c-18170af1105f@columbus.rr.com> <58B889FA.6060006@SDF.org> <e6ac5459-9906-12c6-2556-54f24eb49705@columbus.rr.com> <58B8A303.1050701@SDF.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/2/2017 5:56 PM, Cary wrote: > Baho Utot wrote: >> >> On 03/02/17 16:09, Cary wrote: >>> To build a driver for bcm43XX ndisgen(8) is worth a try. If you have not seen it >>> before, here is a post that gives a quick summary. >>> http://blog.cochard.me/2012/10/using-bcm4313-wireless-chip-under.html >>> >>> >>> >> Thanks I will have a look at it. >> >> I have /boot/modules/bwn_v4_lp_ucode.ko and >> /boot/modules/bwn_v4_ucode.ko >> >> But dmesg says that the firmware cannot be found and it then gives me the >> following: >> bwn0: warn: firmware state (28713) >> >> I am looking at the site you posted now. >> >> Thanks >> >> > What I've found is that the native FreeBSD driver for your wlan interface may > work. Unfortunately, it does not support secure encryption. Only WEP is supported. > I am not following you here, are you saying that there is a native freebsd driver for the BCM4311? If so can you point me to it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0299093b-0dc4-5ee1-8810-971c51fe8044>