From owner-freebsd-mobile@FreeBSD.ORG Wed May 28 09:13:38 2003 Return-Path: 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 3418B37B401 for ; Wed, 28 May 2003 09:13:38 -0700 (PDT) Received: from fnord.ir.bbn.com (FNORD.IR.BBN.com [192.1.100.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4316243F3F for ; Wed, 28 May 2003 09:13:37 -0700 (PDT) (envelope-from gdt@ir.bbn.com) Received: by fnord.ir.bbn.com (Postfix, from userid 10853) id 69523228C; Wed, 28 May 2003 12:13:36 -0400 (EDT) To: freebsd-mobile@freebsd.org References: <20030528073415.GA23028@speedy.unibe.ch> <20030528143847.GA4804@pir.net> From: Greg Troxel Date: 28 May 2003 12:13:36 -0400 In-Reply-To: <20030528143847.GA4804@pir.net> Message-ID: Lines: 56 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: ibm minipci wlan firmware X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 16:13:38 -0000 > I am now in the process of updating and reinstalling my T30 and > noticed a firmware for that card from Feb.25 2003 (v1.04.09.02). > Is it safe to update the firmware or did anyone run into problems? The IBM release notes say that 1.04.09 and 1.04.09.02 have the same firmware and are just an updated loader. So if you have 1.04.09 you probably don't need to update. I presume this is 'station' firmware rather than 'primary' firmware. I have a T30 running netbsd 1.6.1 (I know this is a freebsd list but I suspect most issues are similar). wi0 at pci2 dev 2 function 0: Intersil Prism2.5 Wireless Lan wi0: interrupting at irq 11 wi0: 802.11 address [redacted] wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) wi0: timeout in wi_seek to 13b/0; last status 813b wi0: timeout in wi_seek to 13b/44; last status 813b which seems to work fine modulo occasional timeouts above and wi0: device timeout wi0: command timed out, cmd=0x2 wi0: wi_cmd: BUSY did not clear, cmd=0x0 wi0: init failed wi0: timeout in wi_seek to fce0/0; last status 800b wi0: device timeout wi0: command timed out, cmd=0x2 wi0: wi_cmd: BUSY did not clear, cmd=0x0 wi0: init failed wi0: device timeout wi0: command timed out, cmd=0x2 wi0: device timeout wi0: command timed out, cmd=0x2 wi0: device timeout wi0: command timed out, cmd=0x2 wi0: command timed out, cmd=0x10b wi0: xmit failed wi0: device timeout wi0: command timed out, cmd=0x2 wi0: wi_cmd: BUSY did not clear, cmd=0x0 wi0: init failed wi0: timeout in wi_seek to fce0/0; last status 800b wi0: timeout in wi_seek to fc07/0; last status 800b wi0: timeout in wi_seek to fc00/0; last status 800b wi0: timeout in wi_seek to fc83/0; last status 800b wi0: timeout in wi_seek to fc84/0; last status 800b wi0: timeout in wi_seek to fc06/0; last status 800b wi0: timeout in wi_seek to fc09/0; last status 800b wi0: timeout in wi_seek to fc0c/0; last status 800b In general it works fine, and it recovers from these problems without any intervention. Greg Troxel