Re: Wi driver has WEP issues on both 5.0 and 5.1

2003-06-21 Thread Robert Watson
I've seen this on my older Wavelan card, but not my more recent PRISM card. If I run with WITNESS compiled in, I don't see it, which suggests a timing issue. This came up at USENIX a couple of times and I know Scott and Warner were discussing potential sources and fixes; Scott noticed there were

Re: Wi driver has WEP issues on both 5.0 and 5.1

2003-06-20 Thread Kevin Oberman
> Date: Sat, 21 Jun 2003 00:32:45 -0400 > From: BSDVault <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > A head up about the wi driver in FreeBSD 5.0 and 5.1. I have a netgear > MA-311 card that supports HostAP mode. The issue is that I get a busy bit > error. The exact error starts with th

Re: wi driver

2003-03-17 Thread M. Warner Losh
I've just committed the right fix for this (which is to nuke the bogus KASSERT). I have one or two other fixes in the pipe for lucent cards, but had hoped to get them 'perfect' rather than 'a lot better' before committing them. Since my time has been short, I'll go ahead and try to commit the 'be

Re: wi driver

2003-03-17 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> "Sam Leffler" <[EMAIL PROTECTED]> writes: : > * Alfred Perlstein <[EMAIL PROTECTED]> [030316 21:19] wrote: : > > um.. : > > : > ... : > 840 _FLAGS_OUTRANGE) { : > 841 WI_UNLOCK(sc); : > 842 return; : > 843

Re: wi driver

2003-03-16 Thread Sam Leffler
> * Alfred Perlstein <[EMAIL PROTECTED]> [030316 21:19] wrote: > > um.. > > > ... > 840 _FLAGS_OUTRANGE) { > 841 WI_UNLOCK(sc); > 842 return; > 843 } > 844 KASSERT((ifp->if_flags & IFF_OACTIVE) == 0, > 845 ("wi_

Re: wi driver

2003-03-16 Thread Alfred Perlstein
* Alfred Perlstein <[EMAIL PROTECTED]> [030316 21:19] wrote: > um.. > ... 840 _FLAGS_OUTRANGE) { 841 WI_UNLOCK(sc); 842 return; 843 } 844 KASSERT((ifp->if_flags & IFF_OACTIVE) == 0, 845 ("wi_start: if_flags %x\

RE: WI Driver issues, compile of kernel dies, after fidling it drops to db>

2002-04-12 Thread Jason
I hate replying to my own posts.. Anyways.. It appears The machine I was using as a test machine Either does not support pci 2.2 or is hosed (I'm voting for the latter as the bios seems to be losing its settings every so often)... So you can ignore the long winded issues I type below, sorr

Re: wi driver: firmware %i.%i problem?

2001-12-09 Thread Warner Losh
In message <[EMAIL PROTECTED]> Alfred Perlstein writes: : %i is because I lost a flamewar to get %i added to kernel printf, : it has been fixed. I was thinking of just committing the one line change and avoiding the flamewar :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubs

Re: wi driver: firmware %i.%i problem?

2001-12-09 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Alan Edmonds" writes: : I'm not sure if the %i is a problem the kernel printf or I didn't checkin the small patch to the kernel printf for %i support yet. Ignore it for now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current"

Re: wi driver: firmware %i.%i problem?

2001-12-08 Thread Alfred Perlstein
* Alan Edmonds <[EMAIL PROTECTED]> [011208 17:42] wrote: > > Here's a data point for you Warner. I have an Intel PRO 2011 > 802.11b adapter (Symbol Spectrum24 OEM) card. Works just fine > under -current and the wi driver. After a yesterday's rebuild > I noticed the wi driver displaying this on

Re: wi driver

1999-11-22 Thread Doug Ambrisko
Blaz Zupan writes: | I'm trying to make the wi (WaveLan) driver work in -current. It appears | that some changes to the pccard code have broken it (or that I can't find | out how to configure it correctly, although I have done it under 3.3 with | success). I have this in my config file: It needs