From owner-freebsd-hardware@FreeBSD.ORG Sun Feb 27 03:00:27 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BFAD16A4CE for ; Sun, 27 Feb 2005 03:00:27 +0000 (GMT) Received: from neptune.atopia.net (neptune.atopia.net [209.128.231.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5240343D49 for ; Sun, 27 Feb 2005 03:00:27 +0000 (GMT) (envelope-from dcp1990@neptune.atopia.net) Received: by neptune.atopia.net (Postfix, from userid 1034) id 024994240; Sat, 26 Feb 2005 22:00:26 -0500 (EST) Date: Sat, 26 Feb 2005 22:00:26 -0500 From: Dan Ponte To: freebsd-hardware@freebsd.org Message-ID: <20050227030026.GA95336@neptune.atopia.net> Mail-Followup-To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: wi(4) and prism2.5 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 03:00:27 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I have a box running 5.3-RELEASE and have a Linksys WMP11 prism2.5 card. A couple of weeks ago, I had noticed lots of wi0: device timeout errors in my dmesg, and decided to finally do something about it. So, I ended up sticking the card in a windows machine and upgrading the firmware to the following: wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.2) This fixed the device timeout errors (which caused the entire card to lock up until a reboot), but then I started seeing lots of the following in my dmesg: wi0: timeout in wi_seek to 13d/0 =2E..repeat 15 times... wi0: timeout in wi_seek to 13d/0 wi0: timeout in wi_cmd 0x010b; event status 0xa000 wi0: xmit failed wi0: timeout in wi_seek to 128/0 =2E..repeat 3 times... wi0: record read mismatch, rid=3Dfd4f, got=3Dfd43 wi0: record read mismatch, rid=3Dfd43, got=3Dfd4f =2E..repeat 10 times I notice I only have problems when I start using high-traffic applications such as P2P apps. Now, I cannot even do a wicontrol(8) to check signal strength; all I get is "SIOCGWAVELAN: Input/output error", but the card otherwise works fine. I've googled all over for what causes these problems and what can be done to possibly rectify them. I'm also looking for a way to fix the wicontrol problem without a reboot every time. Thanks for your time (a long post, I know), -Dan --=20 Dan Ponte http://www.theamigan.net/ When asked by an anthropologist what the Indians called America before the white men came, an Indian said simply "Ours." -- Vine Deloria, Jr. --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD4DBQFCITfK8dUD8SpKFR8RAu0oAKDj/KgCOc8lz3H+IsP9LaTVq5h5QwCXfOOJ GZwxFEOub2UEl4BKw1+4gA== =/3Pq -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--