On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote: > Pressing "Function key with symbol of computer sending signal" has no > effect. Which could be caused by the horrible state of keyboard. > When keyboard is needed, is an USB-attached keyboard needed. Usual use > case of the laptop is "headless server, server with SSH access".
I'm not sure what you mean by horrible state. > So I'm ask if > export KEYCODE=42 > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16 > could cause "wlan radio enable"? Or should KEYCODE be another magic number? FWIW my wifi hardware button's keycode is 246. But I would have thought the files to peruse might be: $ ls -GlgR /sys/class/rfkill/rfkill0/ /sys/class/rfkill/rfkill0/: total 0 lrwxrwxrwx 1 0 Jan 21 16:13 device -> ../../phy0 -r--r--r-- 1 4096 Jan 21 16:13 hard -r--r--r-- 1 4096 Jan 21 16:13 index -r--r--r-- 1 4096 Jan 21 16:13 name -r--r--r-- 1 4096 Jan 21 16:13 persistent drwxr-xr-x 2 0 Jan 21 16:13 power -rw-r--r-- 1 4096 Jan 21 16:13 soft -rw-r--r-- 1 4096 Jan 21 16:13 state lrwxrwxrwx 1 0 Jan 21 16:13 subsystem -> ../../../../../../../class/rfkill -r--r--r-- 1 4096 Jan 21 16:13 type -rw-r--r-- 1 4096 Jan 21 16:13 uevent /sys/class/rfkill/rfkill0/power: total 0 -rw-r--r-- 1 4096 Jan 21 16:14 async -rw-r--r-- 1 4096 Jan 21 16:14 autosuspend_delay_ms -rw-r--r-- 1 4096 Jan 21 16:14 control -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_kids -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_time -r--r--r-- 1 4096 Jan 21 16:14 runtime_enabled -r--r--r-- 1 4096 Jan 21 16:14 runtime_status -r--r--r-- 1 4096 Jan 21 16:14 runtime_suspended_time -r--r--r-- 1 4096 Jan 21 16:14 runtime_usage $ > What also would be helpfull, is knowning if > > echo 4242 > /devics/platform/laptop_chipset/input/input17 > > could change brightness (or another visible effect) Likewise: $ ls -GlgR /sys/class/backlight/intel_backlight/ /sys/class/backlight/intel_backlight/: total 0 -r--r--r-- 1 4096 Jan 21 16:19 actual_brightness -rw-r--r-- 1 4096 Jan 21 16:19 bl_power -rw-r--r-- 1 4096 Jan 18 21:57 brightness lrwxrwxrwx 1 0 Jan 21 16:19 device -> ../../card1-eDP-1 -r--r--r-- 1 4096 Jan 18 21:57 max_brightness drwxr-xr-x 2 0 Jan 21 16:19 power -r--r--r-- 1 4096 Jan 21 16:19 scale lrwxrwxrwx 1 0 Jan 18 21:57 subsystem -> ../../../../../../../class/backlight -r--r--r-- 1 4096 Jan 18 21:57 type -rw-r--r-- 1 4096 Jan 18 21:57 uevent /sys/class/backlight/intel_backlight/power: total 0 -rw-r--r-- 1 4096 Jan 21 16:19 async -rw-r--r-- 1 4096 Jan 21 16:19 autosuspend_delay_ms -rw-r--r-- 1 4096 Jan 21 16:19 control -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_kids -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_time -r--r--r-- 1 4096 Jan 21 16:19 runtime_enabled -r--r--r-- 1 4096 Jan 21 16:19 runtime_status -r--r--r-- 1 4096 Jan 21 16:19 runtime_suspended_time -r--r--r-- 1 4096 Jan 21 16:19 runtime_usage $ A recent thread on that starts at: https://lists.debian.org/debian-user/2023/10/msg00621.html with a nice algorithm in: https://lists.debian.org/debian-user/2023/10/msg00648.html Cheers, David.
