> Next, use lsinput to identify the input device named "Eee PC WMI hotkeys" or something similar, which will be associated with
> some input/event<n> device. Then run 'sudo input-events <n>' and press the wlan hotkey. Does input-events output KEY_WLAN
> events when you press the hotkey?
No... the hotkeys appear as event7, but when I press Fn+F2 repeatedly, input-events shows nothing and eventually exits after timing out.
> Please also attach /var/log/syslog and the output of dmesg after wireless has stopped working. Thanks!
I've attached a tarball that contains syslog, dmesg after the wifi stops working, and the output of rfkill showing the block on and off.
As I mentioned before, even when rfkill shows the softblock off and Enable Wireless is checked in the Networking indicator menu, the wi-fi device on this EeePC won't come back on until I've done a full reboot.
> Next, use lsinput to identify the input device named "Eee PC WMI hotkeys" or something similar, which will be associated with
> some input/event<n> device. Then run 'sudo input-events <n>' and press the wlan hotkey. Does input-events output KEY_WLAN
> events when you press the hotkey?
No... the hotkeys appear as event7, but when I press Fn+F2 repeatedly, input-events shows nothing and eventually exits after timing out.
> Please also attach /var/log/syslog and the output of dmesg after wireless has stopped working. Thanks!
I've attached a tarball that contains syslog, dmesg after the wifi stops working, and the output of rfkill showing the block on and off.
As I mentioned before, even when rfkill shows the softblock off and Enable Wireless is checked in the Networking indicator menu, the wi-fi device on this EeePC won't come back on until I've done a full reboot.