Date: Tue, 24 Feb 2004 11:39:34 -0600 From: "Adam M Ryan" <adam@powersurge.net> To: "'Kevin Oberman'" <oberman@es.net> Cc: freebsd-mobile@freebsd.org Subject: RE: How to upgrade firmware on PCMCIA card. Message-ID: <20040224173740.A2D9118F382@pop4.cfu.net> In-Reply-To: <20040224172930.1648A5D07@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The question is more or less how to obtain the firmware and how to apply it to the card. Are there some utilities that I need to do this or can it be from fbsd. Also where I can get this firmware update? Thanks Adam -----Original Message----- From: Kevin Oberman [mailto:oberman@es.net] Sent: Tuesday, February 24, 2004 11:30 AM To: Adam M Ryan Cc: freebsd-mobile@freebsd.org Subject: Re: How to upgrade firmware on PCMCIA card. > From: "Adam M Ryan" <adam@powersurge.net> > Date: Mon, 23 Feb 2004 23:41:57 -0600 > Sender: owner-freebsd-mobile@freebsd.org > > > Here is the error: > > kernel: wi0: device timeout > kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8000 > kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8000 > kernel: wi0: wi_cmd: busy bit won't clear. > kernel: wi0: wi_cmd: busy bit won't clear. > kernel: wi0: init failed > kernel: wi0: wi_cmd: busy bit won't clear. > last message repeated 19 times > kernel: wi0: failed to allocate 2372 bytes on NIC > kernel: wi0: tx buffer allocation failed (error 12) > kernel: wi0: interface not running > > Found this: http://www.freebsd.org/cgi/query-pr.cgi?pr=53927 > Fix > Update WLAN card firmware. > from > wi0: Intersil Firmware: Primary (1.0.5), Station (1.3.4) to > wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) > > > > I know I need to update the firmware, but I really don't know how. > > Linksys wpc11 v3 > Frebsd 5.2.1 > > If anyone could give me a hand it would be great, linksys site wasn't too > much help. It's likely that 1.4.9 is not new enough to do the job. I believe that 1.7.4 is the current station level and I believe that this is the revision you need to resolve the issue. There is a work-around submitted by Marko Zec that involves adding to short delays to the driver after the reset. This has resolved the issue for me. The patch was posted to this list on January 10. Note that the line numbers may not match the driver you have, but searching for the string "set in the event status register." should find the spots. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040224173740.A2D9118F382>