From owner-freebsd-current@FreeBSD.ORG  Mon Dec  8 09:42:48 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 7732A16A4CE; Mon,  8 Dec 2003 09:42:48 -0800 (PST)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2EABB43FD7; Mon,  8 Dec 2003 09:42:45 -0800 (PST)
	(envelope-from sam@errno.com)
Received: from 66.127.85.91 ([66.127.85.91])
	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hB8HgiHQ037538
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Mon, 8 Dec 2003 09:42:44 -0800 (PST)
	(envelope-from sam@errno.com)
From: Sam Leffler <sam@errno.com>
Organization: Errno Consulting
To: Erwin Lansing <erwin@freebsd.org>, current@freebsd.org
Date: Mon, 8 Dec 2003 09:45:49 -0800
User-Agent: KMail/1.5.3
References: <20031208162637.GB70065@droso.net>
In-Reply-To: <20031208162637.GB70065@droso.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200312080945.49054.sam@errno.com>
Subject: Re: Status of wi(4)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2003 17:42:48 -0000

On Monday 08 December 2003 08:26 am, Erwin Lansing wrote:
> Some time ago, I've seen some traffic about problems with wi(4). I've
> been on holiday for most of November, just to find my fine working
> Netgear MA401 no longer functional on 5.2-RC. AFAIKS initialization
> fails (see below). Are there still known oustanding issues with wi ?
>
> -erwin
>
> wi0: <NETGEAR MA401 Wireless PC Card> at port 0x100-0x13f irq 11
> function 0 config 1 on pccard0
> wi0: 801.11 address: 00:30:ab:11:69:a5
> wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.A
> wi0: Intersil Firmware: Primary (0.3.0), Station (0.8.3)
> wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> wi0: timeout in wi_cmd 0x0002; event status 0x0008
> wi0: timeout in wi_cmd 0x0000; event status 0x0008
> wi0: wi_cmd: busy bit won't clear.
> wi0: init failed
> wi0: failed to allocate 2372 bytes on NIC
> wi0: tx buffer allocation failed (error 12)
> wi0: interface not running

My MA401 w/ later station firmware (1.3.4) works fine.  The previous wi 
problems were with Lucent cards and appear to have been resolved.

	Sam