From owner-freebsd-net@FreeBSD.ORG Mon Jan 31 13:53:13 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A951106566C for ; Mon, 31 Jan 2011 13:53:13 +0000 (UTC) (envelope-from frase@frase.id.au) Received: from bacardi.wooloowin.frase.id.au (60-242-254-5.static.tpgi.com.au [60.242.254.5]) by mx1.freebsd.org (Postfix) with ESMTP id 68B558FC1A for ; Mon, 31 Jan 2011 13:53:11 +0000 (UTC) Received: from bacardi.wooloowin.frase.id.au (localhost [127.0.0.1]) by bacardi.wooloowin.frase.id.au (8.14.4/8.14.4) with ESMTP id p0VDE2Ze006763 for ; Mon, 31 Jan 2011 23:14:02 +1000 (EST) (envelope-from frase@frase.id.au) Received: (from Fraser@localhost) by bacardi.wooloowin.frase.id.au (8.14.4/8.14.4/Submit) id p0VDE1UD006680 for net@freebsd.org; Mon, 31 Jan 2011 23:14:01 +1000 (EST) (envelope-from frase@frase.id.au) X-Authentication-Warning: bacardi.wooloowin.frase.id.au: Fraser set sender to frase@frase.id.au using -f Date: Mon, 31 Jan 2011 23:14:01 +1000 From: Fraser Tweedale To: net@freebsd.org Message-ID: <20110131131400.GA71793@bacardi.wooloowin.frase.id.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: bwn(4) support for BCM4322 (MacBook WiFi) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 13:53:13 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I might be fighting a losing battle, but any advice on getting the Broadcom BCM4322 802.11a/b/g/n working? This chip is found in Apple's MacBook and probably elsewhere. I'm currently running amd64 8.2-RC2. As best as I can see, HEAD has nothing that RELENG_8_2 doesn't have, as far as bwn(4) is concerned. As per the bwn(4) man page, I installed the net/bwn-firmware-kmod port. The firmware failed to load, giving a "firmware table full" error. Seems that others had this issue. Bumping the firmware table size FIRMWARE_MAX in sys/kern/subr_firmware.c was the suggested workaround; both modules provided by the port - bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko - now load without error. Loading if_bwn.ko yeilds the following on console: siba_bwn0: mem 0x93100000-0x93103fff irq 18 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) siba_bwn0: unknown chipid 0x4322 for PLL & PMU init bwn0 on siba_bwn0 bwn0: unsupported PHY type (4) device_attach: bwn0 attach returned 6 siba_bwn0 appears in devinfo(8) output but bwn(4) is nowhere to be found. Any suggestions on how to get the card working? Regards, Fraser --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAk1GtZgACgkQPw/2FZbemTXi9wCgrWjhCEmD2YBE8yqIGZ389FQd +P8AnRk1YzjV5l2Jolb1SX+UdAQenwOZ =H8se -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--