On Mon, 2008-12-15 at 09:53 -0200, Henrique de Moraes Holschuh wrote: > On Sun, 14 Dec 2008, Dan Williams wrote: > > On Sat, 2008-12-13 at 11:28 -0200, Henrique de Moraes Holschuh wrote: > > > On Sat, 13 Dec 2008, Tony Vroon wrote: > > > > > What is the WLAN driver involved? Is it rfkill-aware? > > > > > > > > The driver is iwlagn, which does indeed notice that it is killed. > > > > This information does not reach NetworkManager. Relevant log > > > > entries: Dec 12 00:59:01 amalthea iwlagn: Radio Frequency Kill > > > > Switch is On: Dec 12 00:59:01 amalthea Kill switch must be turned > > > > off for wireless networking to work. > > > > > > Then, it is just a matter of time for it to be working correctly. In > > > fact, it might already be if you use wireless-testing and latest > > > network manager. > > > > If HAL's killswitch support doesn't know about the kernel killswitch > > device, or it cannot get the state of the killswitch, then certainly > > NetworkManager isn't going to know about it. > > I see. I have added "up-to-date HAL also required" to my mental list of > stuff needed in userspace. I plan to beat the shit out of the hal killswitch support pretty soon. AFAIK it still doesn't know about softblock, which is part of the whole reason for the rfkill rewrite in 2.6.26 anyway. It also doesn't yet (AFAIK) support uevents from killswitches either, which sucks. Dan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
