From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:43:55 2004 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 B213E16A4CE; Sun, 11 Jan 2004 15:43:55 -0800 (PST) Received: from mail.tel.fer.hr (zg04-053.dialin.iskon.hr [213.191.137.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4BD643D31; Sun, 11 Jan 2004 15:43:52 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from 192.168.200.114 (marko@dhcp14.katoda.net [192.168.200.114]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i0BNgKi3012106; Mon, 12 Jan 2004 00:42:40 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: freebsd-mobile@freebsd.org, Peter Radcliffe Date: Mon, 12 Jan 2004 00:42:50 +0100 User-Agent: KMail/1.5.4 References: <20040111003426.E0EF55D08@ptavv.es.net> <20040111.142357.50578253.imp@bsdimp.com> <20040111220050.GA839@pir.net> In-Reply-To: <20040111220050.GA839@pir.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401120042.50744.zec@tel.fer.hr> cc: freebsd-net@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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: Sun, 11 Jan 2004 23:43:55 -0000 On Sunday 11 January 2004 23:00, Peter Radcliffe wrote: > "M. Warner Losh" probably said: > > You really really really want to be using 1.4.5 firmware. Older > > firmware is known to be buggy. > > I've got newer firmware but no way to actually upgrade it. IBM > doesn;t supply a meanthod to upgrade to anythig newer than I have > installed... > > Got an installer ? On my Prism 2.5 mini-PCI card I managed to upgrade the firmware to 1.1.1 / 1.7.4 using the utilities found here: http://linux.junsun.net/intersil-prism/ First of all, you'll have to boot a M$ OS and install the winupdate utility. Next, in the NIC driver disable the "firmware download" option, as it temporarily loads a new firmware in the NIC RAM, which seems to prevent firmware updates to flash to succeed. You'll have to shut down the machine in order to force a full reset of the NIC. I was kind of paranosic in choosing the appropriate primary / station code, but have latter learned that the "winupdate" utility was smart enough to prevent me from flashing the card with an unappropriate code. Good luck, Marko