Talk:Framework Laptop 16

From ArchWiki
Latest comment: 27 November by Ratijas in topic Prevent waking up in backpack

Prevent waking up in backpack

> "You can disable keyboard and numpad module from waking your device using udev rules."


But wouldn't it also disable waking up when the laptop is open? If so, is there any way to adjust the rules to something like "disable-only-if-lid-is-closed"? I have no idea how this lid sensor works.

Also, the example rule would only work for a "Laptop 16 Keyboard Module - ANSI", but there are some more input modules available for this laptop, so it's worth mentioning it or just listing the rules for everything there: see https://usb-ids.gowdy.us/read/UD/32ac and https://github.com/FrameworkComputer/qmk_firmware/tree/framework16-keyboards/keyboards/framework Ratijas (talk) 09:58, 27 November 2024 (UTC)Reply

So far, I got this:
$ journalctl -ef
:...
:Nov 27 16:18:04 facility (udev-worker)[156337]: 1-4.2:1.0: /etc/udev/rules.d/90-disable-keyboard-wake.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-4/1-4.2/1-4.2:1.0/power/wakeup}="disabled", ignoring: No such file or directory
:Nov 27 16:18:04 facility (udev-worker)[156331]: 1-4.2:1.1: /etc/udev/rules.d/90-disable-keyboard-wake.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-4/1-4.2/1-4.2:1.1/power/wakeup}="disabled", ignoring: No such file or directory
:Nov 27 16:18:04 facility (udev-worker)[156293]: 1-4.2:1.3: /etc/udev/rules.d/90-disable-keyboard-wake.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-4/1-4.2/1-4.2:1.3/power/wakeup}="disabled", ignoring: No such file or directory
:Nov 27 16:18:04 facility (udev-worker)[156350]: 1-4.2:1.2: /etc/udev/rules.d/90-disable-keyboard-wake.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:08.1/0000:c5:00.3/usb1/1-4/1-4.2/1-4.2:1.2/power/wakeup}="disabled", ignoring: No such file or directory
:...
:
and indeed there are no files under those */power/ directories. Ratijas (talk) 11:24, 27 November 2024 (UTC)Reply
OK, so after triggering the rules AND reconnecting the input modules it does kinda work now: the keyboard and numpad modules won't wake up the laptop; but they stay on at all times along with their backlight which is clearly not ideal.
Also, the touchpad is not disabled by this method, and as soon as it will get flexed on by the display hard enough, the awoken keyboard would start typing random passwords in. Ratijas (talk) 11:33, 27 November 2024 (UTC)Reply