From owner-freebsd-net@FreeBSD.ORG Wed Mar 15 15:16:21 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F3B16A41F for ; Wed, 15 Mar 2006 15:16:21 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 615EF43D48 for ; Wed, 15 Mar 2006 15:16:21 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.187] ([10.0.0.187]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k2FFGKo7012141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Mar 2006 07:16:20 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <44182FC4.7050200@errno.com> Date: Wed, 15 Mar 2006 07:16:20 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5 (X11/20060209) MIME-Version: 1.0 To: Joseph Vella References: <200603052102.24881.max@love2party.net> <200603150712.32783.satyam@sklinks.com> In-Reply-To: <200603150712.32783.satyam@sklinks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Max Laier Subject: Re: New version of iwi(4) - Call for testers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 15:16:21 -0000 Joseph Vella wrote: > On Sunday 05 March 2006 12:02, Max Laier wrote: >> All, >> >> there have been a lot of problem reports with iwi(4) lately. Can everybody >> who does have problems with it please take a look at: >> >> http://people.freebsd.org/~mlaier/new_iwi/ >> >> There is a new version of the driver (converted to use firmware(9)). It >> includes some fundamental changes that greatly help stability and >> performance. There are, however, still some instabilities with it. >> >> I'd appreciate if you could give it a try and report back. If it breaks >> (device timeout, connection stall, etc. ...) you could help us a great deal >> if you set "sysctl debug.iwi=3" and include the console output at the time > of >> the failure. If you don't see something interesting there, you might want > to >> increase debug.iwi even further, but that will be *very* chatty. >> >> Thanks in advance. >> >> -- > > How do you tell which firmware you have? > (just to double check, this would be for my Intel 2915 right?) > There is no tool presently to dump the firmware rev. The driver will reject any unsuitable firwmare image it can detect. Yes it will work on a 2915. Sam