From owner-freebsd-current@FreeBSD.ORG Thu Oct 28 07:33:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1AD816A4CE for ; Thu, 28 Oct 2004 07:33:18 +0000 (GMT) Received: from hobbit.neveragain.de (neveragain.de [217.69.76.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E11C943D31 for ; Thu, 28 Oct 2004 07:33:17 +0000 (GMT) (envelope-from amf@hobbit.neveragain.de) Received: from hobbit.neveragain.de (amf@localhost [127.0.0.1]) i9S7XGkJ015031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Oct 2004 09:33:17 +0200 Received: (from amf@localhost) by hobbit.neveragain.de (8.13.1/8.13.1/Submit) id i9S7XGTU015030; Thu, 28 Oct 2004 09:33:16 +0200 Date: Thu, 28 Oct 2004 09:33:16 +0200 From: Dennis Koegel To: Yamamoto Shigeru Message-ID: <20041028073316.GA14639@neveragain.de> References: <20041028.115737.55780539.shigeru@iij.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041028.115737.55780539.shigeru@iij.ad.jp> X-PGP-KeyID: 0D73E19A User-Agent: Mutt/1.5.6+20040722i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (hobbit.neveragain.de [127.0.0.1]); Thu, 28 Oct 2004 09:33:17 +0200 (CEST) cc: freebsd-current@freebsd.org Subject: Re: who is test Intel PRO/Wireless 2100/2200BG/2915ABG? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 28 Oct 2004 07:33:18 -0000 Hi, On Thu, Oct 28, 2004 at 11:57:37AM +0900, Yamamoto Shigeru wrote: > I find a Intel PRO/Wireless 2100/2200BG/2915ABG for *BSD at > http://damien.bergamini.free.fr/ipw/ [...] > Does anyone test it? I have a Thinkpad X31 with ipw; used 1.2 before and now using 1.4. I don't need it that often, but it works pretty good so far. The only problem I encountered is a deadlock when loading the firmware from within X11. Loading it on the console while X11 is running doesn't make problems though. Didn't investigate further ... - D.