Date: Thu, 14 Jun 2007 09:14:23 -0700 From: Sam Leffler <sam@errno.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: ath device appears broken Message-ID: <4671695F.7090202@errno.com> In-Reply-To: <20070614061339.GA96199@troutmask.apl.washington.edu> References: <20070614043216.GA90909@troutmask.apl.washington.edu> <4670C6F1.9060301@errno.com> <20070614044805.GA91084@troutmask.apl.washington.edu> <4670CCA4.3040200@errno.com> <20070614061339.GA96199@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > On Wed, Jun 13, 2007 at 10:05:40PM -0700, Sam Leffler wrote: >> Steve Kargl wrote: >>> I can't find anything relevent at the moment. The 20070610 entry >>> states: >>> Users must also, for the moment, kldload the wlan_scan_sta and/or >>> wlan_scan_ap modules if they use modules for wireless support. >>> >>> I don't use modules nor compile them. Perhaps, a sentence is >>> missing that should direct people that don't use module to update >>> their kernel config file? >> Thanks, I'll add more explanation. Short answer is the scanning support >> is now broken out into separate modules that you must either load or >> specify in your kernel config file. wlan_scan_sta for sta mode >> operation. wlan_sta_ap for ap mode operation. This is comparable to >> how ciphers are split out into modules. > > OK. I've added all the wlan_* devices to my config > and the kernel boots and my script now runs. > > Thanks for responding so quickly. > > PS: I seem to get a periodic "ath0: device timeout" message > on the console. I doesn't seem to cause any problems (e.g., > long pauses). > No idea. I suspect there's a race in the tx done processing that makes the driver think there is a timeout when one is not present. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4671695F.7090202>