From owner-freebsd-current@FreeBSD.ORG Wed May 30 01:06:20 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4CE916A501 for ; Wed, 30 May 2007 01:06:20 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 49F5B13C46C for ; Wed, 30 May 2007 01:06:19 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from [127.0.0.1] (kevlo.org [220.128.136.52]) by ns.kevlo.org (8.13.8/8.13.8) with ESMTP id l4U199Rd004777; Wed, 30 May 2007 09:09:09 +0800 (CST) (envelope-from kevlo@kevlo.org) From: Kevin Lo To: "O. Hartmann" In-Reply-To: <465C108C.60507@zedat.fu-berlin.de> References: <465C108C.60507@zedat.fu-berlin.de> Content-Type: text/plain Date: Wed, 30 May 2007 09:05:51 +0800 Message-Id: <1180487151.6890.1.camel@monet> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: if_iwi: modul not built in CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2007 01:06:20 -0000 O. Hartmann wrote: > Hello, > this may be a boring question due to I missed the appropriate previous > message herein, > but on my 7.0 CURRENT/AMD64 from this week and today module 'if_iwi' and > friends isn't built automatically. > I tried this on a HP nx7300 notebook to get its WLAN adapter (Intel > 3945ABG WLAN module) running. Everything of the if_iwi module is in its > place and can be built properly, also the iwi_xbbs-stuff, but manually, > not automatically. Is there a special reason for this or just a typo in > one of the config files? > > Bytheway, the Intel Centrino Duo based WLAN 3945ABG seems not working > with the if_iwi module, it doesn't get recognized but can be seen via > 'pciconf -lvc'. You need the wpi(4) driver, not iwi(4): http://www.clearchain.com/wiki/Wpi > Thanks for your answers in advance, > Regards > Oliver Kevin