From owner-freebsd-wireless@freebsd.org Fri Nov 18 20:33:14 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04881C48203 for ; Fri, 18 Nov 2016 20:33:14 +0000 (UTC) (envelope-from andymenderunix@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD0E416A0 for ; Fri, 18 Nov 2016 20:33:13 +0000 (UTC) (envelope-from andymenderunix@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id 137so177486514vkl.0 for ; Fri, 18 Nov 2016 12:33:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3HqBIQiPuZjg0HfWYyf2adscLvNPe8j977JClp5017Q=; b=PIpAGOaO1VxeaNI98ZmkOYXNIUNQGpheRou3hMKvnwAIAm1yrUDMV2luxHI0er6FSM z0HA3xP3QYHeYM/ea98ZS7NAyff5DDc62OyzUrWCZiGD9yMGrpOY6QfLyqT9r798ctva MD4KBecPffklwNG1nSYBqZHPYXuYUkIFy9B2/WyiRsriWgWQbTumSVbNMN/lVYDng6+z rnNXJpsOJEC1q375eOGRjXnwmvvTT+U/VQQok1RoGIFBFYFDrfD9qARbI5thAOoLFm3L sAdHq4IIWJrRfiBNVt9bvM7pbX4qnjx1jrll1BbWVCG6SUSgXx5AnT6IjgTEPwkfnpVu CAfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3HqBIQiPuZjg0HfWYyf2adscLvNPe8j977JClp5017Q=; b=jBt7DKRl9+oX2oyZfa0D5JZ4ydpXOoA3ZE0qi/tLMDfnkoDiqbBppuraGBG3dp4/GM PnDHaHMt5WpBgorT9drHiCJLqC2Hkp3hMR55TxzT5eiGd0ZoTrLu+0oOz1Amm5pNYPR0 95sZSdIDT1K0tcBbMWIS8hadov6CnrH2VZCvcYHDWUdXhALuBAyjeqmrpBsrh/XI8o5b IppUv76gqLt3VMJbfu/w5ueGCj0L/5Q8T30Gq2saDDHS9zaU/E+fROdyArwDfvYU/Y2Z TnaYhVQQ+R5OnjsZgOz07rapLQUuJc+yrfx9V+FszD9+0kc5Qz029FwSY83IBxNw7sYs wrzg== X-Gm-Message-State: AKaTC00ywcmYHCE4DiHvFi6uOqzMZQl6IZ+mBm5fStcgb+Pw5+feks2CsHU3D0u6vbuHPhPxPb9tIjEYrN+/5A== X-Received: by 10.31.73.66 with SMTP id w63mr1079176vka.106.1479501192755; Fri, 18 Nov 2016 12:33:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.6.3 with HTTP; Fri, 18 Nov 2016 12:33:12 -0800 (PST) In-Reply-To: References: From: Andy Mender Date: Fri, 18 Nov 2016 21:33:12 +0100 Message-ID: Subject: Re: Broadcom BCM 43xx wireless chips To: Adrian Chadd , freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 20:33:14 -0000 Dear Adrian, I see, makes sense. I assumed bcm4322 and bcm4321 are similar. Trying to pull a higher Broadcom driver version for fwcutter will not cut it then (pun not intended)? I wanted to try it, just out of curiosity. Best regards, Andy On 18 November 2016 at 21:24, Adrian Chadd wrote: > 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 > 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 >> wrote: >> >>> there's a bwn firmware port you need to build. >>> >>> bwn-firmware-kmod >>> >>> -a >>> >>> >>> On 17 November 2016 at 22:35, Andy Mender >>> 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 >>>> 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 >>>>> 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 >>>>>> 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: 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 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" >>>>>> >>>>> >>>>> >>>> >>> >> >