From owner-freebsd-current Fri Feb 21 14:11:59 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B73A237B401 for ; Fri, 21 Feb 2003 14:11:56 -0800 (PST) Received: from smak.uberduper.com (12-213-188-143.client.attbi.com [12.213.188.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 298E443F75 for ; Fri, 21 Feb 2003 14:11:56 -0800 (PST) (envelope-from james@uberduper.com) Received: from uberduper.com (unknown [208.33.24.5]) by smak.uberduper.com (Postfix) with ESMTP id F0D369B438; Fri, 21 Feb 2003 14:12:02 -0800 (PST) Message-ID: <3E56A4AE.3000700@uberduper.com> Date: Fri, 21 Feb 2003 14:14:06 -0800 From: James Satterfield User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030205 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maikel Verheijen Cc: current@FreeBSD.ORG Subject: Re: Wavelan problems References: <20030220083007.GA23886@myst.dohd.org> In-Reply-To: <20030220083007.GA23886@myst.dohd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a suggestion. Do not set media autoselect. Set it to DS/11Mbps mediaopt adhoc or something. This still gives me a TON of tx timeouts, but the card works. I've only had the problem you're seeing when I set media autoselect. James. Maikel Verheijen wrote: > Since I deleted the original email of Michael Bretterklieber, I can't > actually reply anymore :( > > This is what I would have replied: > > I can say nothing more than "me too", with a Lucent pC24E-H-ET, a generic > lucent silver card. > > Dmesg info: > wi0: at port 0x100-0x13f irq 11 function 0 config 1 on > pccard0 > wi0: 802.11 address: 00:02:2d:0c:e1:24 > wi0: using Lucent Technologies, WaveLAN/IEEE > wi0: Lucent Firmware: Station (7.28.1) > wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > And exact the same wicontrol output. > > I would like to add that, on enabeling the card (ifconfig wi0 up), my > machine practically freezes, and when I pull the card out, I got my machine > back most of the time... > > Dmesg info after doing "ifconfig wi0 up": > > wi0: timeout in wi_cmd 0x0002; event status 0x0080 > wi0: timeout in wi_cmd 0x0000; event status 0x0080 > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: wi_cmd: busy bit won't clear. > wi0: init failed > wi0: timeout in wi_seek to fc00/0 > wi0: timeout in wi_seek to fc81/0 > wi0: timeout in wi_seek to fc0c/0 > wi0: timeout in wi_seek to fc02/0 > wi0: timeout in wi_seek to fc03/0 > wi0: timeout in wi_seek to fc04/0 > wi0: timeout in wi_seek to fc01/0 > wi0: timeout in wi_seek to fc09/0 > wi0: timeout in wi_seek to fc07/0 > wi0: timeout in wi_seek to fc83/0 > wi0: timeout in wi_seek to fc06/0 > wi0: timeout in wi_seek to fc25/0 > wi0: timeout in wi_seek to fc84/0 > wi0: timeout in wi_seek to fc0e/0 > wi0: timeout in wi_seek to fc85/0 > wi0: timeout in wi_seek to fc20/0 > wi0: timeout in wi_seek to fc80/0 > wi0: wi_cmd: busy bit won't clear. > wi0: failed to allocate 2372 bytes on NIC > wi0: tx buffer allocation failed (error 12) > wi0: interface not running > wi0: wi_cmd: busy bit won't clear. > wi0: detached > > (got this after unplugging the wi-card, to un-freeze the card. > > Kind regards, > > > Maikel Verheijen > > > > Kind regards, > Maikel Verheijen > > USER, n.: > The word computer professionals use when they mean "idiot." > -- Dave Barry, "Claw Your Way to the Top" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message