Date: Fri, 28 Jul 2006 12:00:13 -0400 From: John Baldwin <jhb@freebsd.org> To: Erik =?iso-8859-15?q?N=F8rgaard?= <norgaard@locolomo.org> Cc: Don Wilde <Don@silver-lynx.com>, freebsd-mobile@freebsd.org Subject: Re: Problem (maybe a solution) loading iwi firmware: firmware_get: failed to load firmware image iwi_bss Message-ID: <200607281200.14440.jhb@freebsd.org> In-Reply-To: <44CA2CA1.3040801@locolomo.org> References: <44C8D7FE.4080108@locolomo.org> <200607271739.48433.jhb@freebsd.org> <44CA2CA1.3040801@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 28 July 2006 11:26, Erik N=F8rgaard wrote: > John Baldwin wrote: > > On Thursday 27 July 2006 14:28, Erik N=F8rgaard wrote: > >> There is some development, I'm not sure if it has been imported into t= he > >> source tree yet, > >> > >> http://people.freebsd.org/~mlaier/new_iwi/ > >=20 > > Yes, it is in -current and I believe -stable now, and this just works f= ine=20 > > with the iwi-firmware-kmod port. > >=20 > > In short, upgrade to 6.1-stable, install the iwi-firmware-kmod port, an= d=20 > > everything should Just Work(tm). It does here on my laptop (albeit=20 running=20 > > 7-current). >=20 > 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. If it uses firmware_get() it qualifies as new_iwi for now. You should not= =20 have to explicitly load iwi_bss, firmware(9) will do that for you. > Note the interupt storm when the module is first loaded, but not the > second time. That's because it only logs a message once. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607281200.14440.jhb>