Date: Mon, 1 May 2006 00:20:42 +0200 From: Max Laier <max@love2party.net> To: freebsd-current@freebsd.org Cc: rmgls@wanadoo.fr Subject: Re: iwi driver Message-ID: <200605010020.50468.max@love2party.net> In-Reply-To: <4454F7AC.3070904@errno.com> References: <20060430125904.E7BF47000091@mwinf1306.wanadoo.fr> <4454F7AC.3070904@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart8229981.CS7TTfcPKH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 30 April 2006 19:45, Sam Leffler wrote: > rmgls@wanadoo.fr wrote: > > hello all, > > > > since the last update dated > > Sat Apr 29, (on current), > > the iwi driver does not work: > > cannot change any achannel, and no association! > > the old version of the driver works. > > > > ... > > ;* Copyright Sam Leffler */ > > > > previous: > > /* $FreeBSD: src/sys/dev/iwi/if_iwi.c,v 1.27 2006/01/29 12:03:03 damien > > Exp $ */ > > > > the nic is seated onboard of a s5 Sony laptop. > > dmesg: > > ... > > firmware_get: failed to load firmware image iwi_bss > > iwi0: could not load firmware > > > > ... > > > > firmware_get: failed to load firmware image iwi_bss > > iwi0: could not load firmware > > > > pciconf -lv > > iwi0@pci6:11:0: class=3D0x028000 card=3D0x27538086 chip=3D0x42208086 re= v=3D0x05 > > hdr=3D0x00 vendor =3D 'Intel Corporation' > > device =3D 'PRO/Wireless 2200BG Network Connection' > > class =3D network > > > > Please can you tell me something to do about this? > > The firmware image file could not be loaded; verify it is present and > named properly. The driver in cvs will accept either 2.4 or 3.x rev > image formats so if you get the filename right it should just work. > Unfortunately there was a period of time where the driver in cvs would > only accept rev 3.0 firmware then the names associated with the firmware > changed, etc. As a result some people have bogus firmware files on > their system. > > When in doubt you can pre-load the firmware with kldload. Unfortunately > firmware(9) doesn't have any debug msgs to show things like firmware > images being registered. This would be useful for cases like this. Here is a small patch to build a "debug.firmware" sysctl. Should give:=20 "iwi_bss/300/191142" for the latest firmware from net/iwi-firmware-kmod Any comments on the patch? Will commit shortly otherwise. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart8229981.CS7TTfcPKH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEVThCXyyEoT62BG0RAlN9AJ44jkMSaooH0yvhP3Leo8eSp0AUDgCdFzpS Sb5vOrn6QCPNbcbvAtASFuI= =uceu -----END PGP SIGNATURE----- --nextPart8229981.CS7TTfcPKH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605010020.50468.max>