From owner-freebsd-mobile@FreeBSD.ORG Fri Jul 28 16:10:43 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D46716A5BB; Fri, 28 Jul 2006 16:10:43 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED42943D53; Fri, 28 Jul 2006 16:10:40 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k6SGAdX0099838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jul 2006 09:10:40 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44CA36FF.9070404@errno.com> Date: Fri, 28 Jul 2006 09:10:39 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Erik_N=F8rgaard?= References: <44C8D7FE.4080108@locolomo.org> <44C905D3.4040208@locolomo.org> <200607271739.48433.jhb@freebsd.org> <44CA2CA1.3040801@locolomo.org> In-Reply-To: <44CA2CA1.3040801@locolomo.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Don Wilde , freebsd-mobile@freebsd.org Subject: Re: Problem (maybe a solution) loading iwi firmware: firmware_get: failed to load firmware image iwi_bss X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jul 2006 16:10:43 -0000 Erik Nørgaard wrote: > John Baldwin wrote: >> On Thursday 27 July 2006 14:28, Erik Nørgaard wrote: >>> There is some development, I'm not sure if it has been imported into the >>> source tree yet, >>> >>> http://people.freebsd.org/~mlaier/new_iwi/ >> Yes, it is in -current and I believe -stable now, and this just works fine >> with the iwi-firmware-kmod port. >> >> In short, upgrade to 6.1-stable, install the iwi-firmware-kmod port, and >> everything should Just Work(tm). It does here on my laptop (albeit running >> 7-current). > > The new_iwi has not been backported to -stable yet. I tried to use just > the iwi-firmware-kmod port, disabling dhcp on that interface and > configuring manually, loading modules in order: firmware, iwi_bss and > if_iwi. Either you've mis-typed the above or you are incorrect. From cvs log if_iwi.c: revision 1.8.2.7 date: 2006/07/11 00:00:29; author: mlaier; state: Exp; lines: +1525 -618 MFC iwi update: Sync with if_iwi.c 1.35, if_iwireg.h 1.12, if_iwivar.h 1.11 Lots of changes. This version now requires net/iwi-firmware-kmod so we also bump __FreeBSD_version to use in the port. That is, RELENG_6 has the revised iwi code and you must use the iwi-firmware-kmod port. > > Still, I can not get it working, output from dmesg: > > > iwi0: mem 0xb0107000-0xb0107fff irq 10 > at device 10.0 on pci6 > iwi0: Ethernet address: 00:16:6f:93:c9:75 > > This appears fine after I load if_iwi no further errors. But then > configuring with > > # ifconfig iwi0 10.35.4.64/24 ssid MYAP mode 11g channel 6 > > The following error appears: > > Interrupt storm detected on "irq5:"; throttling interrupt source > iwi0: timeout waiting for iwi_bss firmware initialization to complete > iwi0: could not load boot firmware iwi_bss > firmware_get: failed to load firmware image iwi_bss > iwi0: could not load firmware > > I do get the interface configured but with "no carrier". I unload and > reload if_iwi and configure again: > > iwi0: detached > iwi0: mem 0xb0107000-0xb0107fff irq 10 > at device 10.0 on pci6 > iwi0: Ethernet address: 00:16:6f:93:c9:75 > firmware_get: failed to load firmware image iwi_bss > iwi0: could not load firmware > > Note the interupt storm when the module is first loaded, but not the > second time. > > Why on irq 5 when the iwi0 is on irq 10? Looking at my devices, lspci -v > output below, there is an USB controler on irq 5 _and_ 10. Could some > with the iwi problems some how propagate? > > As seen below the bus is ICH6 based. > > Any hints? Thanks, Erik Figure out why you are not loading firmware properly. The firmware is packaged as normal loadable modules you can actually pre-load them using kldload. Check things loaded normally with kdlstat and/or check the console log msgs. My guess is you are not loading the correct firmware modules. I think there's a debugging knob/sysctl for firmware(9) but can't remember it off hand. I've wanted to include the firmware in the base system for a while so we can put all this firmware packaging stupidity behind us. It just requires having a click-thru agreement mechanism on first use or possibly just the intel README file in the directory. Sam