Date: Wed, 16 Nov 2016 22:44:52 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Andy Mender <andymenderunix@gmail.com> Cc: Ben Woods <woodsb02@gmail.com>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Broadcom BCM 43xx wireless chips Message-ID: <CAJ-VmonDnMT7TBLDbBvyDft2B4EUJyXOZfnOwZLBozKViKiK1w@mail.gmail.com> In-Reply-To: <CAHVfhuff3U=0-5SxSLekmGQ0QpxjzuHcy8Xn_iqNxRF9TVP=DA@mail.gmail.com> References: <CAHVfhueFRSdYfh1AJYUf52yceUhttMaUP88LXUV9AYZQrZyCpg@mail.gmail.com> <CAOc73CCdNmyzShnxvmDXdmzEVT77b07yM2U7VJLPeyJL=EXS8w@mail.gmail.com> <CAHVfhuff3U=0-5SxSLekmGQ0QpxjzuHcy8Xn_iqNxRF9TVP=DA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, Something's wrong with that compilation. Check modules/bwn/Makefile and make sure you uncommented the bwn n_phy source files. -adrian On 16 November 2016 at 22:38, Andy Mender <andymenderunix@gmail.com> wrote: > Dear Adrian, Ben, > > sysctl.net.wlan.devices returns only the urtwn0 interface (from a TP-LINK > USB dongle I use to get any connection). > > Below, please find the output of "dmesg | grep bwn": > andy@mb-2008:~ % dmesg | grep bwn > link_elf_obj: symbol bwn_nphy_op_allocate undefined > KLD file if_bwn.ko - could not finalize loading > siba_bwn0: <Broadcom BCM4322 802.11a/b/g/n Wireless> mem > 0xd3100000-0xd3103fff at device 0.0 on pci3 > siba_bwn0: warn: multiple PCI(E) cores > siba_bwn0: unsupported coreid (USB 2.0 Device) > siba_bwn0: unsupported coreid (unknown) > siba_bwn0: unsupported coreid (Internal Memory) > > How should I proceed? > > Best regards, > Andy > > On 16 November 2016 at 23:35, Ben Woods <woodsb02@gmail.com> wrote: > >> >> On Wed., 16 Nov. 2016 at 8:09 pm, Andy Mender <andymenderunix@gmail.com> >> wrote: >> >>> Dear Adrian, >>> >>> I set the mentioned option (BWN_GPL_PHY just below the bwn driver) in the >>> kernel config file and recompiled the STABLE kernel. >>> Now the additional message about BWN_GPL_PHY is gone, but there is some >>> 2-3 >>> features listed as unsupported. The driver gets attached to the network >>> card as siba_bwn0, but no interface is created by ifconfig. >>> >>> What should be the name of the interface in /etc/rc.conf - siba_bwn0 or >>> bwn0? >>> >>> Otherwise, paradox added a link to some Broadcom device datasheets from >>> Cypress: http://www.cypress.com/search/all?f[0]=meta_type% >>> 3Atechnical_documents&f[1]=resource_meta_type%3A575&f[2]= >>> field_related_products%3A110101 >>> >>> I had a quick look and although bcm4321 and bcm4322 are not on the list, >>> bcm4318, bcm4319 and bcm4325 are. Might be relevant to further testing and >>> writing drivers in general. >>> >>> Best regards, >>> Andy >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@ >>> freebsd.org" >>> >> >> Hi Andy, >> >> Since 11.0-RELEASE FreeBSD no longer shows the parent interface for >> wireless devices in ifconfig. It will only show the cloned wlan0 device >> once it is created. >> >> To determine which wireless devices are available to clone to a wlan0 >> interface, use the following command: >> $ sysctl net.wlan.devices >> >> Once you have found the wireless device, set it up using the normal method: >> https://www.freebsd.org/doc/handbook/network-wireless.html >> >> Good luck! >> >> Regards, >> Ben >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonDnMT7TBLDbBvyDft2B4EUJyXOZfnOwZLBozKViKiK1w>