From owner-freebsd-wireless@freebsd.org Fri Nov 18 18:08:30 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 18472C487EC for ; Fri, 18 Nov 2016 18:08:30 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 C45FF13C1 for ; Fri, 18 Nov 2016 18:08:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x231.google.com with SMTP id j191so45158370ita.1 for ; Fri, 18 Nov 2016 10:08: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=cVmJVguFZONiKL1KNlUt6N+VQ5x8faF2P2uf+Jb8NTE=; b=oxuutAfCNocOMmMT/kMhpo7C99I4IXZ3DjM967r5b4BncCrLeENZhWioew09fa857J Fm6ow55nO6qIgiloOtzGZNuu2Y2Xq8AdZtsYag0o1Az6uweZd2R+NyGyrFUcSE51P4ar Dbx1u39XjFYIpou2Gy+fssrwcUaWhg1LOx9M60XFaw1vfe3Hj5JauvD2Kmyzm/c/1E47 mxR/Q9sf4oRsG7Ra7FYzRUhLQQMznul9qMSH9weYQXjRlFM1z5JYxXW2Pn1ypvdvcaXE Vp/aOjXq4kuCohe4LhTYw3X3WROqppaxVmwShUNA3qUkgbSyPMQvCQsj8ccpxntnl2J0 hLPQ== 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=cVmJVguFZONiKL1KNlUt6N+VQ5x8faF2P2uf+Jb8NTE=; b=hhTik+zcB/xz65/sn778PdLMcc964q0UUgNRc0lhxUMDda8UBqRP966dylc4zsyj/e P+1Sk3lvOU2qo4pzYJU3r4xcAAf85F5KOy5MoG/vDTV+KHUN19Zh6/aC787TbrD/8xI/ dH0D7yvySCWcHz0NSXO5c4sf0zURC37+RtOJpvs53dH9sjOsxCwuJRbjj083AoAQEIab aKD+Hql9UoSijXHYGlEFtNWPm01IN0WdD9zIa3xhxo+9T1zKGmPWLfi/e9ZZ5b4m9N65 wlVRckUXftegu69hjK0w548PJCUokcI4O0kI3mPVqHg625klc9ekcgRUgdfvgWd0Mpyv fPRw== X-Gm-Message-State: AKaTC03zpZnIAIN9fnACRtusjWyxB2OGb4OuE9GQYwB0a8iMDYAWfQqlF5QlaQALJFezSl3CSitEAdBCGzn8JQ== X-Received: by 10.107.36.144 with SMTP id k138mr891247iok.177.1479492509194; Fri, 18 Nov 2016 10:08:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.39.134 with HTTP; Fri, 18 Nov 2016 10:08:28 -0800 (PST) In-Reply-To: References: From: Adrian Chadd Date: Fri, 18 Nov 2016 10:08:28 -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 18:08:30 -0000 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" >>> >> >> >