On Sun, Jul 05, 2009 at 08:31:05AM -0400, Bob Copeland wrote: Hi, > Try latest wireless-testing or 2.6.31-rc1; there may already be a fix > for your hardware thanks to recently added rfkill support. got around to give 2.6.30* more testing. LED now works nicely but that is about the only thing that works. Tried computers linked in Ad-Hoc mode with WEP. 2.6.30 and 2.6.31.1 work nicely on the other end. On the ath5k end it seems like 2.6.31 choked after resume from suspend or when interface was reconfigured. 2.6.31.1 does not work at all on this netbook. LED indicates activity but network does not get associated. "iwlist scan" does display available networks. After having tried 2.6.31.1 I have to cold-boot 2.6.30.x to get the ath5k working again, simple reboot does not do it. > > > Also, while the hotkey works how do query the current on/off status of it > > in Linux? > > There's the /dev/rfkill device (see http://git.sipsolutions.net/rfkill.git) > and I believe there are files under /sys/ as well which show the state but > I don't have the details handy (/sys/class/rfkill/xxx/state?). has that been merged into 2.6.31* ? The /sys/.../rfkill files are there but could not figure out anything that changes when hitting the hotkey. Besides, I would think the LED will indicate rfkill status? Richard -- 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
