hiya, I think the 4322 is a newer PHY which we don't have support for yet (PHY-HT?). I think I tested the 4321 and that worked.
It's waiting for new bus code from landon, and then when that's done, I'll finish the PHY port and we can test. -adrian On 18 November 2016 at 12:12, Andy Mender <andymenderu...@gmail.com> wrote: > Dear Adrian, > > I specifically rebuild that port after upgrading my kernel. I'm afraid the > bcm4322 chip requires firmware that's not in the old Broadcom drivers that > are used as a source for fwcutter. On GNU/Linux systems I typically need > the 6.x series, while the port you mentioned uses the 5.x and 4.x drivers. > I checked the Makefile :). > > Best regards, > Andy > > On 18 November 2016 at 19:08, Adrian Chadd <adrian.ch...@gmail.com> wrote: > >> there's a bwn firmware port you need to build. >> >> bwn-firmware-kmod >> >> -a >> >> >> On 17 November 2016 at 22:35, Andy Mender <andymenderu...@gmail.com> >> wrote: >> >>> Hello, >>> >>> I recompiled the kernel and did a world rebuild to include the bwn code >>> we discussed last time. There is some progress - now the bwn module does >>> not complain that some features are missing. However, the firmware is >>> missing. I installed the /net/bwn-firmware-kmod, though that does not seem >>> to solve the problem. Below, the relevant snippet from dmesg: >>> >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: need multicast update callback >>> bwn0: ucode fw: ucode16_mimo >>> bwn_v4_ucode16_mimo: could not load firmware image, error 2 >>> bwn0: the fw file(bwn_v4_ucode16_mimo) not found >>> bwn0: ucode fw: ucode16_mimo >>> bwn-open_v4_ucode16_mimo: could not load firmware image, error 2 >>> bwn0: the fw file(bwn-open_v4_ucode16_mimo) not found >>> >>> Where should I get the correct firmware from and where should I put it? >>> >>> Best regards, >>> Andy >>> >>> On 17 November 2016 at 07:50, Andy Mender <andymenderu...@gmail.com> >>> wrote: >>> >>>> Dear Adrian, Ben, >>>> >>>> Bingo! That could've been it. I did NOT uncomment the lines you >>>> mentioned in /usr/src/sys/modules/bwn prior to recompiling the kernel. I'll >>>> try to rebuild the kernel with the lines added and write back with results. >>>> >>>> Hope it works! >>>> >>>> Best regards, >>>> Andy >>>> >>>> On 17 November 2016 at 07:44, Adrian Chadd <adrian.ch...@gmail.com> >>>> wrote: >>>> >>>>> 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 <andymenderu...@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 <woods...@gmail.com> wrote: >>>>> > >>>>> >> >>>>> >> On Wed., 16 Nov. 2016 at 8:09 pm, Andy Mender < >>>>> andymenderu...@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" >>>>> >>>> >>>> >>> >> > _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
