I’ll look into those, thank you!

(I currently set up my APL keymap via .Xmodmap with xmodmap, and setxkbmap for X11 terms, and with ‘loadkeys’ for console.)

Great info! I will try it when I decide to trial-run Wayland again, thank you!

(Some things I had read online suggested that Wayland did not use the x11 configs. If it does, that’s good news.)

As someone who hasn’t yet moved to Wayland, how good is support these days for alternate keyboard mappings? Is this something that each individual window manager needs to support, or does Wayland itself manage them?

Not just “international keyboard” support, but truly arbitrary keyboard/symbol mapping support. I muddle in programming with APL, which needs its own key mapping with Unicode symbols.

I recall KDE had its own mapping support which used some system APL layout but I’d rather not have key mappings tied to a specific window manager.

Keyboard media keys (Fn + F keys, eg. vol mute, +/-, brightness etc.) do NOT yet work in mainline kernel. There is some good work going on over here on github but it’s preliminary.

Also note kernel 6.10 broke the bottom display it would appear; I’m using kernel 6.13-rc4 currently.

NEW METHOD which avoids the udev ‘event storm’ caused by docking/undocking the keyboard

[/usr/local/bin/asusUX8406_kbdwatch]

#!/bin/bash

me=$(basename "$0")
laststate=2

while true; do
  sleep 3
  output=$(lsusb -d 0b05:1b2c)
  stat=$?
  if [ $stat == 1 ] && [ $laststate != 1 ]; then
    ## kbd removed, enable lower display
    laststate=1
    logger -p user.info "${me} KEYBOARD REMOVED"
    xrandr --auto && xrandr --output eDP-2 --below eDP-1
  elif [ $stat == 0 ] && [ $laststate != 0 ]; then
    ## kbd replaced, disable lower display
    laststate=0
    logger -p user.info "${me} KEYBOARD DOCKED"
    xrandr --output eDP-2 --off
  fi
done

Hook this up to your init system, or run from a nohup session redirected to /dev/null on login or session startup … for example, on my system I am member of group video, so installing it to /usr/local/bin and setting ownership to root:video and sudo chmod ug+rx allows it to be run on session login automatically.

We should do more than block them, they need to be teergrubed.