Date: Wed, 6 Mar 2002 21:27:33 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Dan Langille <dan@langille.org> Cc: stable@FreeBSD.ORG Subject: Re: wi0 problems under latest STABLE Message-ID: <20020306212733.A26094@Odin.AC.HMC.Edu> In-Reply-To: <20020307051444.EBC203F0E@bast.unixathome.org>; from dan@langille.org on Thu, Mar 07, 2002 at 12:14:41AM -0500 References: <20020307051444.EBC203F0E@bast.unixathome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Mar 07, 2002 at 12:14:41AM -0500, Dan Langille wrote: > I've just updated a my 4.5-STABLE laptop to the latest RELENG_4. It > contains a Lucent Orinoco card which turns up as wi0. It was working with > a STABLE dated Jan 28 2002. With the build from this evening's cvsup, I'm > getting time outs on wi0. > > This is the /etc/pccard.conf which I was using: > > [dan@laptop:~] $ less /etc/pccard.conf > # Lucent WaveLAN/IEEE > card "Lucent Technologies" "WaveLAN/IEEE" > config 0x1 "wi" ? > insert /etc/pccard_ether $device start > remove /etc/pccard_ether $device stop > > insert wicontrol -i $device -p 3 > insert wicontrol -i $device -k "4gRp1" > > What did I miss? > > Under the latest build, I get this: > > laptop /kernel: wi0: timeout in wi_cmd 11; event status 8000 > > If it's any help: > > wi0: <WaveLAN/IEEE 802.11> at port 0x240-0x27f irq 3 slot 0 on pccard0 > wi0: 802.11 address: 00:02:2d:0e:66:bd > wi0: using Lucent chip or unknown chip > > It doesn't seem to be affecting the traffic, it's just a repeating > message. If I don't use the above pccard.conf, the card doesn't seem to > work very well at all. It's fairly harmless (previously the command just failed without saying anything), it might be worth trying to raise the value of WI_DELAY in if_wireg.h. I'd suggest trying 100 and if that fixes it, lower it to see if you can find a better lower bound then 5. If that doesn't work, it might be worth trying to raise WI_TIMEOUT, but 500ms is a long time for a network adaptor. I'm not sure what you mean about not using the pccard.conf entry. The top part is exactly what is in /etc/defaults/pccard.conf and it won't work if you don't set your wep key and enable ad-hoc mode if that's how your network is configured. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8hvpEXY6L6fI4GtQRAjeWAJ4xXKZi4QzPEmefGQx7h7Iy/lbw8QCgwYru pU37Fv/75QQwEeOp9HnbHsc= =VRFg -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020306212733.A26094>