From owner-freebsd-mobile@FreeBSD.ORG Thu Sep 15 04:46:28 2005 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 435E416A41F for ; Thu, 15 Sep 2005 04:46:28 +0000 (GMT) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: from luftpost.plosh.net (luftpost.plosh.net [204.152.186.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0427143D46 for ; Thu, 15 Sep 2005 04:46:27 +0000 (GMT) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: by luftpost.plosh.net (Postfix, from userid 1001) id CDAAA32606; Wed, 14 Sep 2005 21:51:47 -0700 (PDT) Received: from dhcp-6.sql1.plosh.net (c-24-4-233-31.hsd1.ca.comcast.net [24.4.233.31]) by luftpost.plosh.net (tmda-ofmipd) with ESMTP; Wed, 14 Sep 2005 21:51:45 -0700 (PDT) To: freebsd-mobile@freebsd.org Date: Wed, 14 Sep 2005 21:46:29 -0700 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2429083.JluRdIT0Uq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200509142146.42969.plosher@plosh.net> From: Peter Losher X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Subject: Best way to load iwi firmware for wpa_supplicant? 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: Thu, 15 Sep 2005 04:46:28 -0000 --nextPart2429083.JluRdIT0Uq Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I now have a Dell Inspiron 700m w/ a integrated iwi chipset, which is=20 detected just fine, and works w/ WEP keys etc. with the iwi firmware=20 loaded from the local/rc.d script. dmesg below: =2D=3D- % dmesg | grep iwi iwi0: mem 0xe0206000-0xe0206fff irq 10 at=20 device 1.0 on pci2 iwi0: Ethernet address: 00:12:f0:a2:bf:98 =2D=3D- However, I need to get the firmware loaded before wpa_supplicant starts=20 for those WPA networks I attach to. (which is why I still have a ath0=20 card sitting around) Right now, the preferred method seems to be having a=20 local/etc/devd/iwi.conf defined like so: =2D=3D- % more /usr/local/etc/devd/iwi.conf # devd configuration file for the iwi driver. # This file downloads the firmware on attach and starts up dhclient=20 # if configured. # attach 100 { device-name "iwi0"; action "/usr/local/sbin/iwicontrol -i iwi0=20 =2Dd /usr/local/share/iwi-firmware/ -m bss"; }; # Try to start dhclient when the link comes up. =20 # Only devices that are configured to support DHCP will actually # run it. No link down rule exists because dhclient automatically exits # when the link goes down. # notify 100 { match "system" "IFNET"; match "subsystem" "iwi0"; match "type" "LINK_UP"; action "/etc/rc.d/dhclient start iwi0"; }; =2D=3D- Yet when the system boots I get a error when wpa_supplicant starts up: =2D=3D- iwi0: Please load firmware =2D=3D- Is what I have defined in iwi.conf enough, or am I missing a piece here? Best Wishes - Peter =2D-=20 [ http://www.plosh.net/ ] - "Earth Halted: Please reboot to continue" --nextPart2429083.JluRdIT0Uq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDKPyyuffIhmkXw7kRAgctAKCTVatChs7TpUO3RLMuoO59Qv4LJQCfQgEa IsWBIXn50ejAWGi7s8tKc5Y= =BZnw -----END PGP SIGNATURE----- --nextPart2429083.JluRdIT0Uq--