From owner-freebsd-wireless@freebsd.org Fri Nov 18 20:24:29 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 A99ACC47CDA for ; Fri, 18 Nov 2016 20:24:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 6DA6E1053 for ; Fri, 18 Nov 2016 20:24:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x235.google.com with SMTP id j191so51466079ita.1 for ; Fri, 18 Nov 2016 12:24:29 -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 :cc; bh=52wKhmnVkd1jdCYzCnBSD2HnTHfS/vJ5g2IbdQ58LRQ=; b=LyphhDr8ZhMrIiAt9t9fn9oAd5qoxAV4RtFktao7bIs7SjJc0Z8v2MDSGfUs0oypLo WaTonPGN195gZfysqWFyxkwWfVH602AknZLlU3xQGjJ/rbl5tRI+6AFs757W206lYfGc 6Q7jjZy01eT8RsAqnxH/rZHI7UF01h3MfqNrMTIEX6Ci7hGkk3+Yq/bafLAdwIecq9U2 evq1VPDtWuStK3f/v0SBJ4SnQuIFFgMATyaERhrRPHSRoy5tvKfEgSwL8/M9UdHrayZk IW9f6y3Z4RYRbl5iGDLg5paQjgSMWs0wWqPvTg0h94kiTdcnr1qjesDPWuQNHGUkuhJm 3WmA== 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:cc; bh=52wKhmnVkd1jdCYzCnBSD2HnTHfS/vJ5g2IbdQ58LRQ=; b=Ln6fZb/X6WaRquc9LX3hqCaCnE0/S3Z5jNPwVpiOHQGG1XYu04P9MFFb6iJG+JIbt2 aHQZknYgx4HCqA4BXpaV7q8NvEsC9/nDF4jGXDIU9ULpqEgLC+BppmRf3+vpQ36bI0Hx TI4R+Raqag4U0trao2soObY3e/LgWij3JFkiLh68GwMHyB5QT7gdEumX4MXFL1nOCJIY 85I8vl6Zpm/NMTnqk0PTbMPMSKIKZdvTpZ3/oBKKMCf/Z+KoLAJmnGRzsGEYtG90vbk8 czi2HAY+yXK609Hhgvven1NPSKc8cGSlgD8qNMJ6HT/ZNSQ4oPoPtWQDMp/YrC3FITRy SKnA== X-Gm-Message-State: AKaTC01VhJ3B8sF3/5hdj2WPab9NojJzIKdVoH/k6WBqCg/Q/T9RYwrsEJNkC4dw5J3TcmfV9UDCAq2HzIr0wg== X-Received: by 10.107.136.86 with SMTP id k83mr1390141iod.99.1479500668753; Fri, 18 Nov 2016 12:24:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.39.134 with HTTP; Fri, 18 Nov 2016 12:24:27 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Fri, 18 Nov 2016 12:24:27 -0800 Message-ID: Subject: Re: Broadcom BCM 43xx wireless chips To: Andy Mender Cc: "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:24:29 -0000 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" >>>>> >>>> >>>> >>> >> >