From owner-freebsd-ppc@FreeBSD.ORG Tue Dec 22 16:35:03 2009 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D67D106568F for ; Tue, 22 Dec 2009 16:35:03 +0000 (UTC) (envelope-from rob.wiers@googlemail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id C52B88FC17 for ; Tue, 22 Dec 2009 16:35:02 +0000 (UTC) Received: by fxm10 with SMTP id 10so3344230fxm.14 for ; Tue, 22 Dec 2009 08:35:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:mime-version:subject:date:references:x-mailer; bh=faeHTVbWWDCFjQkMnTG9sIPin/B1uOV8TC3sMDiMolw=; b=OjhCT+cHtEog5oJGOwvHY5+6mOUsx1KGd/q1ilNOoM3OcNGt0t+Q2tf5820+Wyi2II 9NNPv5TOVo1q5hcLjTEMdeauKwGB4oAlvssTBAXEdxp3ufenPd8lVVfsaYKMXYovNm5z DI6A5cIahH2ar2bEJZP4liNLSFM4myenOe1g0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:from:to:content-type:mime-version:subject:date :references:x-mailer; b=UiPq5h1Lwy41k/ur9QuK/OiR92wcTdsvJBZb6S3kWveyY3jhQCL+HSvRYDkikfAdN4 sGBQLns1ke9TAPSojqpa0igKccEQZEZHvjQ2iGtq83/zSTYM8qhaN4+7XxzBx0SUqEzB m3nSVs8CcHOstJrHCHhSMJLoc3XC9/XfiuGQc= Received: by 10.223.144.207 with SMTP id a15mr3271380fav.63.1261498047721; Tue, 22 Dec 2009 08:07:27 -0800 (PST) Received: from ?192.168.2.137? (f048048250.adsl.alicedsl.de [78.48.48.250]) by mx.google.com with ESMTPS id 1sm4998968fks.29.2009.12.22.08.07.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 08:07:26 -0800 (PST) Message-Id: From: Rob Wiers To: freebsd-ppc@freebsd.org Mime-Version: 1.0 (Apple Message framework v936) Date: Tue, 22 Dec 2009 17:07:25 +0100 References: <24D4D117-6252-4AB6-9A0C-5F5F1B3BF3FB@googlemail.com> X-Mailer: Apple Mail (2.936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Mac Mini G4 1.5GHz Broadcomm bwi BCM4318 problems X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 16:35:03 -0000 Trying to keep this thread on the mailing list as well.... Will reply to both next time around... > Subject: Re: Mac Mini G4 1.5GHz Broadcomm bwi BCM4318 problems > > Hello John, > > Thanks for replying. I'm wondering if this should go to the mailing > list as well? > > Just to make sure we've got everything clear: > 1. I boot with the bwi module available to the kernel > 2. The kernel recognises my BCM4318 device > 3. I login and attempt to use ifconfig (I did ifconfig bwi0 up scan > 4. The firmware kmod barfs with the error message I mentioned below. > > Now that we have that clear, the output of kgdb is attached here: > > > > > >> On Tuesday 22 December 2009 4:53:50 am Little Bhudda wrote: >>> Hello all, >>> >>> I am trying to get the Airport Extreme (Broadcom BCM4318) to work >>> under FreeBSD. This was working fine under Debian, but I'm having >>> some >>> problems getting it to work here. >>> >>> First of all, adding the line to /boot/loader.conf, as the bwi >>> man(4) >>> page says, did not give me the device. I tried to find the bwi >>> kernel >>> module, but couldn't find it. Maybe I was looking for the wrong >>> name? >>> >>> Then, I decided to go for option 2 and rebuilt the kernel with the >>> devices defined as mentioned in the bwi manpage. That went ok. I >>> also >>> built and installed the bwi-firmware-kmod as per the manpage's >>> instructions. >>> >>> When I boot, the device gets reconised, but the loading of the >>> firmware fails with the error message "cannot register image >>> bwi_v3_pcm5, firmware table full!" after which the MAC init fails. >>> >>> A copy of the relevant entries in the /var/log/messages is attached. >>> >>> Any help would be greatly appreciated. >> >> I suspect no one has tested bwi on ppc yet and that is why the >> module is not >> built by default. If you are successful in getting it working then >> it can be >> enabled by default easily enough by editing sys/modules/Makefile. >> The error >> message you are getting seems odd. The firmware table has room for >> 30 >> firmware images by default, and I find it hard to believe that you >> have over >> 30 firmware images. Can you fire up kgdb and run 'p >> firmware_table' and mail >> the output? >> >> -- >> John Baldwin >