Re: PCI 802.11b w/NetBSD 1.6

A lot of people report this problem. I am not able to reproduce it,
myself. Maybe it is because I test on much slower computers.

Be sure that you are using the latest ic/wi.c (1.109) and pci/if_wi_pci.c
(1.16), since I have recently fixed bugs in both.

Dave

On Mon, Jan 27, 2003 at 05:14:18PM +0900, Shingo WATANABE / ?$BEOJU ?$B?-8c wrote:
> hello.
> 
> At Fri, 24 Jan 2003 00:43:09 +0000 (UTC),
> Alan Post <[email protected]> wrote:
> 
> > Can anyone recommend a good PCI 802.11b card for use with NetBSD 1.6?
> > Just as a client, not as an access point.
> > 
> > Should I be running NetBSD-current instead, to get support of more
> > cards?
> 
> I'm using ThinkPad X30 with NetBSD-current(1.6M) and having same
> problem. :-(
> 
> 
> 
> > I picked up a Netgear MA311, and the kernel recognizes it:
> 
> wi0 is attached as following:
> 
> wi0 at pci1 dev 2 function 0: Intersil Prism2.5 Wireless Lan
> wi0: interrupting at irq 11
> wi0: 802.11 address 00:05:3c:06:32:c9
> wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
> wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9)
> wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> 
> 
> > Unfortunately, when I try to actually send data on it, the
> > driver spews errors:
> 
> I have same trouble in sending *large* data.
> When I send small data (ex. ssh ...), it works without problem.
> As far as I know it happens only when I use "wi at pci".
> 
> 
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: command timed out, cmd=0x10b, arg=0x127
> wi0: xmit failed
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: timeout in wi_seek to 127/0
> wi0: bad alloc 127 != 13c, cur 1 nxt 1
> wi0: timeout in wi_seek to 151/0
> wi0: timeout in wi_seek to 151/0
> wi0: device timeout
> wi0: timeout in wi_seek to 151/0
> wi0: timeout in wi_seek to 151/0
> wi0: command timed out, cmd=0x121, arg=0xfce0
> 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 fc82/0
> wi0: timeout in wi_seek to fc06/0
> wi0: timeout in wi_seek to fc2d/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 fc2a/0
> wi0: timeout in wi_seek to fc28/0
> wi0: timeout in wi_seek to fc80/0
> wi0: command timed out, cmd=0xa, arg=0x944
> wi0: failed to allocate 2372 bytes on NIC
> wi0: tx buffer allocation failed
> wi0: interface not running
> wi0: wi_cmd: BUSY did not clear, cmd=0x2, prev=0x8000
> wi0: timeout in wi_seek to fc80/0
> wi0: timeout in wi_seek to fc85/0
> wi0: wi_cmd: BUSY did not clear, cmd=0x2, prev=0x8000
> wi0: wi_cmd: BUSY did not clear, cmd=0x0, prev=0x8000
> wi0: wi_cmd: BUSY did not clear, cmd=0x0, prev=0x8000
> wi0: wi_cmd: BUSY did not clear, cmd=0x0, prev=0x8000
> wi0: wi_cmd: BUSY did not clear, cmd=0x0, prev=0x8000
> wi0: wi_cmd: BUSY did not clear, cmd=0x0, prev=0x8000
> --
> *bsd wireless list, a bawug thing <http://www.bawug.org/>
> [un]subscribe: http://lists.bawug.org/mailman/listinfo/bsd-wireless/

-- 
David Young             OJC Technologies
[email protected]      Engineering from the Right Brain
                        Urbana, IL * (217) 278-3933
--
*bsd wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/bsd-wireless/