Problems with wi on 5.1-CURRENT

Kevin Oberman oberman at es.net
Wed Jun 18 14:16:13 PDT 2003


> From: "Robert Hulme" <rob at robhulme.com>
> Date: Wed, 18 Jun 2003 21:03:18 +0100
> Sender: owner-freebsd-current at freebsd.org
> 
> Hi,
> 
> Yesterday I sent in an email to freebsd-current about the problems with
> wi in 5.1-Current. There haven't been any replies to suggest anyone
> knows why this is happening, how to fix it, or anyone looking into
> fixing it.
> 
> Can someone please direct me as to which list (or which person) I should
> contact to make them aware of the problem?
> 
> I've checked the cvs entries @
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/wi/
> 
> All the recent changes were done by someone called 'imp'. Should I email
> this person? (if so what is there email address?)


Could you let us know EXACTLY how you are doing the configuration?
rc.conf or start_if.wi0? I use start_if.wi0 and it seems to work well.
With the exception of the key, could you post what you use to do the
configuration?

'imp' is M. Warner Losh who posts to both this list and mobile quite
often. He is the person primarily responsible for laptop work and
related stuff and is also core. Unfortunately, like everyone else, his
time is a bit limited.

I'm not sure that this will help you, but Warner is the one with the
non-disclosure specs for Prism chips, so he will almost certainly be
the one to get it fixed.

While I would not recommend running this way, could you try not
turning on WEP and see if the problem still occurs? This would, at
least, provide another data point.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634


More information about the freebsd-current mailing list