alesya-h / zenbook-duo-2024-ux8406ma-linux

automatic screen on/off, brightness sync, battery limiter
BSD 2-Clause "Simplified" License
53 stars 13 forks source link

Key "wlan" no more registering event on kb attach/detach #14

Open dolphin-evorobey opened 2 months ago

dolphin-evorobey commented 2 months ago

today it stops recognize. no event when i try to rebind hotkey action, also nothin catched with sudo showkey -k

what i changed - yesterday i played with grub entries, but i reverted them all already now it GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

and im installed latest libwacom from Debian repos. and playing with libwacom configs.

any ideas? dont know what to try....

bitodt commented 2 months ago

This kernel patch disables the wlan-on-attach/detach. Also, read this:

The patch for the wireless disconnecting after connecting the keyboard has been included in Linux 6.11, which should be released as a new stable kernel soon. However, I haven’t tested this kernel to see if any other issues come up.

So if you recently upgraded your linux kernel to 6.11+, you should not receive a wlan event on keyboard attach/detach. What kernel version do you run? You can see this with uname -a

SchoeningStud commented 2 months ago

If you had the automatic screen toggle set up using WLAN key as trigger, This might be an alternative solution: #15

dolphin-evorobey commented 1 month ago

bitodt thx, i checked, really - i missed that i vahe kernel upgrade this day, my kernel 6.10.12-x64v3-xanmod1 , looks like this patch already included there.. SchoeningStud looks like it what i want! thx mate

NaScha commented 1 month ago

@dolphin-evorobey Have you got this run what @SchoeningStud adviced? I changed my duo file accordingly, the display watcher starts, but nothing happens to the screens. I am with Kernel 6.11

And what happens if you manually call "duo toggle"? In my case nothing. As far as I understood WLAN key event is only for attaching / detaching keyboard, but at least, manual toggling should work, shouldn't it?

SchoeningStud commented 1 month ago

@NaScha The Problem might be, that the newest patch introduced a non-existent third monitor, which keeps the duo normal command from being run as I just copied the duo set-displays command in watch-displays.

I solved this for me by adding multi monitor support via #16 on my machine and removing the monitor check from watch-displays.

The "duo toggle" command may be broken, as it doesn't do anything for me either, but as long as "duo normal" works, this should be a problem.

NaScha commented 1 month ago

@SchoeningStud Tried as you adviced and watch-displays now works, but 2 new problems:

Using the 2 variables from this Pull-Request +eDP_TOP="eDP-1" +eDP_BOTTOM="eDP-2" duo set-tablet-mapping is broken.

Removing these variables and change all occurances to according eDP-x I can call duo set-tablet-mapping, but then, duo watch-rotation is broken. I can come to book mode, but not back to laptop-mode, i. e. I am stuck now in vertical mode and can not get back to horizontal mode. Fortunately, rebooting the machine brings me back to horizontal mode. The error is the following - any way to fix that?

duo watch-rotation Executing both command: gnome-monitor-config set -LM eDP-1 -m 2880x1800@120.000 -s 1.74757 -x 0 -y 0 -t right -LM eDP-2 -m 2880x1800@120.000 -s 1.74757 -x 0 -y 1030 -t right -p :::: ../src/gmc-display-config.c:691 cc_display_logical_monitor_config_add_monitor() - :::: ../src/gmc-display-config.c:691 cc_display_logical_monitor_config_add_monitor() - Logical monitor [ 2880x1800+0+0 ], scale = 1.74757 Monitor [ eDP-1 ] 2880x1800@120 Logical monitor [ 2880x1800+0+1030 ], PRIMARY, scale = 1.74757 Monitor [ eDP-2 ] 2880x1800@120 [(0, 0, 1.7475727796554565, uint32 3, false, [('eDP-1', '2880x1800@120.000', @a{sv} {})]), (0, 1030, 1.7475727796554565, 3, true, [('eDP-2', '2880x1800@120.000', {})])] Failed to set configuration: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent

// Edit - sry, I have to correct myself: After having rebooted the machine, everything is broken - duo watch-displays stopped working, too, with the following error:

duo watch-displays Setting up watches. Watches established. /dev/bus/usb/003/ ATTRIB 010 Executing top command: gnome-monitor-config set -LM eDP-1 -m 2880x1800@120.000 -s 1.74757 -x 120 -y 0 -t normal -p :::: ../src/gmc-display-config.c:691 cc_display_logical_monitor_config_add_monitor() - Logical monitor [ 2880x1800+120+0 ], PRIMARY, scale = 1.74757 Monitor [ eDP-1 ] 2880x1800@120 [(120, 0, 1.7475727796554565, uint32 0, true, [('eDP-1', '2880x1800@120.000', @a{sv} {})])] Failed to set configuration: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors positions are offset Setting up watches. Watches established. /dev/bus/usb/003/ ATTRIB 010 Executing top command: gnome-monitor-config set -LM eDP-1 -m 2880x1800@120.000 -s 1.74757 -x 120 -y 0 -t normal -p :::: ../src/gmc-display-config.c:691 cc_display_logical_monitor_config_add_monitor() - Logical monitor [ 2880x1800+120+0 ], PRIMARY, scale = 1.74757 Monitor [ eDP-1 ] 2880x1800@120 [(120, 0, 1.7475727796554565, uint32 0, true, [('eDP-1', '2880x1800@120.000', @a{sv} {})])] Failed to set configuration: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors positions are offset Setting up watches. Watches established.

undingen commented 1 month ago

I think I had the same "Logical monitors position are offset" when I used it initially on ubuntu 24.10 beta. This change fixed the problem for me y_offset=1800 unfortunately for some reason my display reports that it can't get scaled to 175%..

SchoeningStud commented 1 month ago

@NaScha This was caused by an offset in the x coordinate in the top monitor in "duo left-up", which wasn't corrected for in any of the other commands. The fix I'm using is here, also this adapts all commands for multi monitor use.

NaScha commented 1 month ago

@SchoeningStud Your fix works like a charm! Now I have back all the functionality I need:

Thank you for having fixed so quickly.

Also added the keyboard_light extension to your fixed file content - great so far! Looking forward to F-Keys function what will come with newer Kernels.

SchoeningStud commented 1 month ago

@NaScha

The tablet mapping solved itself for me, I believe it was the GNOME 46 update.

For the second ond third point, if you are on nixos, here I have uploaded the part in the configuration.nix which creates the systemd services for automatic screen toggle, rotation and brightness syncronisation. I you are not on nixos, you would need to translate them to usual .service files.