The integrated wireless chip works fine under normal conditions, monitor mode is supported out of the box, although injection is not.
# systemd-inhibit -what=handle-suspend-key sleep 1h KernelĪppending net.ifnames=0 to the kernel parameters is recommended if you are planning to use the installation for penetration-testing as the wireless adapter names will be quite long by default. Use this to inhibit the handling of the suspend key. It is a virtual, firmware-handled key and will be triggered when using an unmarked keybind, which would suspend your device. There is also a sleep button/suspend key. See nf(5) for more information on handling specific keys. Holding the physical shutdown button for more than three seconds will force the system to shutdown. The firmware will send many power button presses, so your machine will most likely only take a few seconds to power off because systemd kills the process/unit it is waiting for when the power button is pressed. This power button will be triggered when your device runs out of battery. The other detected power button seems to be a virtual, firmware-handled button. Pressing the power button should log an event. # stdbuf -o0 evemu-record /dev/input/event3 > event3 # systemd-inhibit -what=handle-power-key sleep 1h You can verify this by inhibiting the handling of the power button In this case, LNXPWRBN:00 ( /dev/input/event3) is the "real", physical power button. ├─/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 │ input:input5 "Acer Wireless Radio Control" This device has two detected power buttons and one sleep button. (Discuss in Talk:Acer Predator Helios 300) They seem to have been copied and pasted blindly from Dell Latitude 3500#Power buttons since it is cited as a reference in Help:Laptop page guidelines. Notes: This section and the next one duplicate the explanation of how to capture keys.