Date: Fri, 8 Mar 2002 13:25:03 -0800 From: "James Satterfield" <james@floondoon.com> To: "Brooks Davis" <brooks@one-eyed-alien.net> Cc: <stable@FreeBSD.ORG> Subject: Re: changes to wi ? Message-ID: <03a201c1c6e7$b64980e0$0feba8c0@sphynx> References: <20020307174706.A46627@shikima.mine.nu><3C87A851.5000904@tenebras.com><02dd01c1c647$06a52b30$0feba8c0@sphynx> <20020307.213047.55118321.imp@village.org> <034801c1c67a$c2b69560$0feba8c0@sphynx> <20020308112306.A3322@shikima.mine.nu> <20020308102139.A344@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Just to clarify. Is the file to edit if_wireg.h or if_wireg.c? I cannot find an if_wireg.c anywhere. James. ----- Original Message ----- From: "Brooks Davis" <brooks@one-eyed-alien.net> To: "Rasputin" <rasputin@shikima.mine.nu> Cc: "James Satterfield" <james@floondoon.com>; <stable@FreeBSD.ORG> Sent: Friday, March 08, 2002 10:21 AM Subject: Re: changes to wi ? This is diagnostic information. Failures represent a broken card or a driver bug. I'd rather find the right values then screw around with building sysctls to let people ignore their broken systems. Please try editing if_wireg.c and raising the value WI_DELAY (try 50 or 100 for starters) to see if this will go away. If that works, we can work back down toward a smaller value. If that doesn't work, you could also try raising WI_TIMEOUT as well, but it's hard to believe the card would take more then half a second to respond to a command. -- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?03a201c1c6e7$b64980e0$0feba8c0>