Date: Tue, 07 Jul 2009 12:08:22 +0200 From: Michael Gmelin <freebsdusb@bindone.de> To: Aragon Gouveia <aragon@phat.za.net> Cc: freebsd-net@freebsd.org Subject: Re: iwn(4) doesn't like hardware RF switches Message-ID: <4A531E96.4060005@bindone.de> In-Reply-To: <4A52C132.5080106@phat.za.net> References: <4A52C132.5080106@phat.za.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Aragon Gouveia wrote: > Hi, > > Is it just me, or does the iwn driver in -CURRENT not play well with > hardware RF switches on notebooks? For me the only resemblence of an > event I see is when I switch off RF - the kernel sends a log to syslog. > wpa_supplicant doesn't pick it up, and neither does devd. The result > is that I can't keep wpa_supplicant running and let it reassociate when > I turn off/on, and neither can I start/stop wpa_supplicant from devd > when I turn on/off. > > I guess I could leave the RF switch on and just bind a key shortcut in > Xorg to start/stop wpa_supplicant, but a standard approach would be > nice... :) > > > Thanks, > Aragon > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" I can confirm this behaviour (+ sometimes iwn gets totally confused by that). What laptop are you using?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A531E96.4060005>