Asus Zenbook Duo 2025 (UX8406CA) keyboard issue on kernel 6.16.4-116.bazzite.fc42.x86_64

[marcofrancis]

Hi,
I just installed bazzite-asus:stable on my Asus Zenbook Duo 2025 (UX8406CA). Right now I have the kernel 6.16.4-116.bazzite.fc42.x86_64 and reading NeroReflex/asusctl#25 (comment) I thought that the fixes for the keyboard would have been incorporated since the message refers to 6.15, but I guess I was wrong. Right now the situation with the keyboard is the following:

• no backlight (neither when attached via usb nor when on BT)
• no function keys (neither when attached via usb nor when on BT)
• whenever the keyboard is disconnected the wifi is toggled off
• attaching the keyboard does nothing to the lower screen

Are these fixed in some newer version of the Bazzite kernel? Is it a problem of my 2025 version (vs 2024 version in the thread)?
Thank you!

[antheas]

whenever the keyboard is disconnected the wifi is toggled off

My bad on this I need to pull the fix I made haha.

As for the rest, can you give me some data? I will pull the new series and start adding fixes.

Start with:
lsusb

Then, if you can install hhd in a virtual environment and run sudo hhd.contrib evdev and sudo hhd.contrib hidraw and post the devices you see here.

See here: https://github.com/hhd-dev/hhd

[marcofrancis]

Oh wow, that's very responsive :D
So I got the following

1.lsusb

marco@bazzite:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 3277:0055 Shinetech USB2.0 FHD UVC WebCam
Bus 003 Device 004: ID 8087:0037 Intel Corp. 
Bus 003 Device 008: ID 0b05:1bf2 ASUSTek Computer, Inc. ASUS Zenbook Duo Keyboard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

2.hhd.contrib evdev

marco@bazzite:~$ sudo ~/.local/share/hhd/venv/bin/python -m hhd.contrib evdev
Available Devices with the Current Permissions
 - device /dev/input/event25, name "sof-hda-dsp HDMI/DP,pcm=5", phys "ALSA", uniq ""
 - device /dev/input/event24, name "sof-hda-dsp HDMI/DP,pcm=4", phys "ALSA", uniq ""
 - device /dev/input/event23, name "sof-hda-dsp HDMI/DP,pcm=3", phys "ALSA", uniq ""
 - device /dev/input/event22, name "sof-hda-dsp Headphone", phys "ALSA", uniq ""
 - device /dev/input/event21, name "Asus WMI hotkeys", phys "asus-nb-wmi/input0", uniq ""
 - device /dev/input/event20, name "PC Speaker", phys "isa0061/input0", uniq ""
 - device /dev/input/event19, name "Intel HID 5 button array", phys "", uniq ""
 - device /dev/input/event18, name "Intel HID events", phys "", uniq ""
 - device /dev/input/event17, name "Video Bus", phys "LNXVIDEO/video/input0", uniq ""
 - device /dev/input/event16, name "ELAN9008:00 04F3:4447 Touchpad", phys "i2c-ELAN9008:00", uniq ""
 - device /dev/input/event15, name "ELAN9008:00 04F3:4447 Stylus", phys "i2c-ELAN9008:00", uniq ""
 - device /dev/input/event14, name "ELAN9008:00 04F3:4447 UNKNOWN", phys "i2c-ELAN9008:00", uniq ""
 - device /dev/input/event13, name "ELAN9008:00 04F3:4447 UNKNOWN", phys "i2c-ELAN9008:00", uniq ""
 - device /dev/input/event12, name "ELAN9008:00 04F3:4447", phys "i2c-ELAN9008:00", uniq ""
 - device /dev/input/event11, name "ELAN9009:00 04F3:4448 Touchpad", phys "i2c-ELAN9009:00", uniq ""
 - device /dev/input/event10, name "ELAN9009:00 04F3:4448 Stylus", phys "i2c-ELAN9009:00", uniq ""
 - device /dev/input/event9, name "ELAN9009:00 04F3:4448 UNKNOWN", phys "i2c-ELAN9009:00", uniq ""
 - device /dev/input/event8, name "ELAN9009:00 04F3:4448 UNKNOWN", phys "i2c-ELAN9009:00", uniq ""
 - device /dev/input/event7, name "ELAN9009:00 04F3:4448", phys "i2c-ELAN9009:00", uniq ""
 - device /dev/input/event6, name "Primax Electronics Ltd. ASUS Zenbook Duo Keyboard Touchpad", phys "usb-0000:00:14.0-6/input5", uniq ""
 - device /dev/input/event5, name "Primax Electronics Ltd. ASUS Zenbook Duo Keyboard Mouse", phys "usb-0000:00:14.0-6/input5", uniq ""
 - device /dev/input/event4, name "Primax Electronics Ltd. ASUS Zenbook Duo Keyboard", phys "usb-0000:00:14.0-6/input3", uniq ""
 - device /dev/input/event3, name "Primax Electronics Ltd. ASUS Zenbook Duo Keyboard", phys "usb-0000:00:14.0-6/input0", uniq ""
 - device /dev/input/event2, name "AT Translated Set 2 keyboard", phys "isa0060/serio0/input0", uniq ""
 - device /dev/input/event1, name "Power Button", phys "PNP0C0C/button/input0", uniq ""
 - device /dev/input/event0, name "Lid Switch", phys "PNP0C0D/button/input0", uniq ""

Enter device path (/dev/input/event# or #):

3.hhd.contrib hidraw

marco@bazzite:~$ sudo ~/.local/share/hhd/venv/bin/python -m hhd.contrib hidraw
Available Devices with the Current Permissions
 - /dev/hidraw0  0b05:1bf2 Usage Page: 0x0001 Usage: 0x0006 Interface: 0 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw1  0b05:1bf2 Usage Page: 0xffe0 Usage: 0x0001 Interface: 1 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw2  0b05:1bf2 Usage Page: 0xff00 Usage: 0x0006 Interface: 2 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw3  0b05:1bf2 Usage Page: 0x000c Usage: 0x0001 Interface: 3 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw4  0b05:1bf2 Usage Page: 0xff31 Usage: 0x0076 Interface: 4 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw5  0b05:1bf2 Usage Page: 0x000d Usage: 0x000e Interface: 5 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw6  04f3:4448 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9009:00 04F3:4448'
 - /dev/hidraw7  04f3:4447 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9008:00 04F3:4447'

Enter device path (/dev/hidraw# or #):

[antheas]

This needs a kernel quirk:

 - /dev/hidraw4  0b05:1bf2 Usage Page: 0xff31 Usage: 0x0076 Interface: 4 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'

What bus is it connected with? Can you do Bluetooth? Just the hidraw command

[marcofrancis]

Sorry, not super experienced here. You mean re run the hidraw command with the keyboard connected via bluetooth? How do I find out which bus is it connected to?

[antheas]

You don't need to, because of lusb it's USB. Just repeat with Bluetooth

[marcofrancis]

Aaah got it.

hhd.contrib hidraw when BT

marco@bazzite:~$ sudo ~/.local/share/hhd/venv/bin/python -m hhd.contrib hidraw
[sudo] password for marco: 
Available Devices with the Current Permissions
 - /dev/hidraw0  0b05:1bf3 Usage Page: 0xff00 Usage: 0x0001 Interface: -1 Names: '': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw1  0b05:1bf3 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw6  04f3:4448 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9009:00 04F3:4448'
 - /dev/hidraw7  04f3:4447 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9008:00 04F3:4447'

Enter device path (/dev/hidraw# or #):

[antheas]

Enter 0 then paste what pops out. Bluetooth will be a bit more complicated

[marcofrancis]

Sure, here it is. Do you need the #1 as well?

hhd.contrib hidraw BT, #0

marco@bazzite:~$ sudo ~/.local/share/hhd/venv/bin/python -m hhd.contrib hidraw
Available Devices with the Current Permissions
 - /dev/hidraw0  0b05:1bf3 Usage Page: 0xff00 Usage: 0x0001 Interface: -1 Names: '': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw1  0b05:1bf3 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ASUS Zenbook Duo Keyboard'
 - /dev/hidraw6  04f3:4448 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9009:00 04F3:4448'
 - /dev/hidraw7  04f3:4447 Usage Page: 0x000d Usage: 0x000e Interface: -1 Names: '': 'ELAN9008:00 04F3:4447'

Enter device path (/dev/hidraw# or #): 0

Device Information:
 -                 path: b'/dev/hidraw0'
 -            vendor_id: 0x0b05
 -           product_id: 0x1bf3
 -        serial_number: fe:1a:da:f8:02:af
 -       release_number: 0x0000
 -  manufacturer_string:
 -       product_string: ASUS Zenbook Duo Keyboard
 -           usage_page: 0xff00
 -                usage: 0x0001
 -     interface_number: 0x-001

Device HID Descriptor:
0x05, 0x01,        // 000:  Usage Page (Vendor Usage Page 0x01)
0x09, 0x06,        // 002:  Usage (Vendor Usage 0x06)
0xa1, 0x01,        // 004:  Collection (Application)
0x85, 0x02,        // 006:   Report ID (2)
0x05, 0x07,        // 008:   Usage Page (Vendor Usage Page 0x07)
0x19, 0xe0,        // 00a:    .Usage Minimum (224)
0x29, 0xe7,        // 00c:    .Usage Maximum (231)
0x15, 0x00,        // 00e:    .Logical Minimum (0)
0x25, 0x01,        // 010:    .Logical Maximum (1)
0x75, 0x01,        // 012:    .Report Size (1)
0x95, 0x08,        // 014:    .Report Count (8)
0x81, 0x02,        // 016:   Input (Data,Var,Abs)
0x95, 0x01,        // 018:    .Report Count (1)
0x75, 0x08,        // 01a:    .Report Size (8)
0x81, 0x03,        // 01c:   Input (Cnst,Var,Abs)
0x95, 0x05,        // 01e:    .Report Count (5)
0x75, 0x01,        // 020:    .Report Size (1)
0x05, 0x08,        // 022:   Usage Page (Vendor Usage Page 0x08)
0x19, 0x01,        // 024:    .Usage Minimum (1)
0x29, 0x05,        // 026:    .Usage Maximum (5)
0x91, 0x02,        // 028:   Output (Data,Var,Abs)
0x95, 0x01,        // 02a:    .Report Count (1)
0x75, 0x03,        // 02c:    .Report Size (3)
0x91, 0x03,        // 02e:   Output (Cnst,Var,Abs)
0x95, 0x06,        // 030:    .Report Count (6)
0x75, 0x08,        // 032:    .Report Size (8)
0x15, 0x00,        // 034:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 036:    .Logical Maximum (255)
0x05, 0x07,        // 039:   Usage Page (Vendor Usage Page 0x07)
0x19, 0x00,        // 03b:    .Usage Minimum (0)
0x2a, 0xff, 0x00,  // 03d:    .Usage Maximum (255)
0x81, 0x00,        // 040:   Input (Data,Arr,Abs)
0xc0,              // 042:  End Collection
0x06, 0x00, 0xff,  // 043:  Usage Page (Vendor Usage Page 0xff00)
0x09, 0x06,        // 046:  Usage (Vendor Usage 0x06)
0xa1, 0x01,        // 048:  Collection (Application)
0x85, 0x0d,        // 04a:   Report ID (13)
0x09, 0x06,        // 04c:   Usage (Vendor Usage 0x06)
0x15, 0x00,        // 04e:    .Logical Minimum (0)
0x27, 0xff, 0xff, 0x00, 0x00, // 050:    .Logical Maximum (65535)
0x75, 0x20,        // 055:    .Report Size (32)
0x95, 0x01,        // 057:    .Report Count (1)
0xb1, 0x02,        // 059:   Feature (Data,Var,Abs)
0x85, 0xdd,        // 05b:   Report ID (221)
0x09, 0xdd,        // 05d:   Usage (Vendor Usage 0xdd)
0x15, 0x00,        // 05f:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 061:    .Logical Maximum (255)
0x75, 0x08,        // 064:    .Report Size (8)
0x95, 0x3f,        // 066:    .Report Count (63)
0x81, 0x02,        // 068:   Input (Data,Var,Abs)
0x85, 0xde,        // 06a:   Report ID (222)
0x09, 0xde,        // 06c:   Usage (Vendor Usage 0xde)
0x91, 0x02,        // 06e:   Output (Data,Var,Abs)
0xc0,              // 070:  End Collection
0x05, 0x0c,        // 071:  Usage Page (Vendor Usage Page 0x0c)
0x09, 0x01,        // 073:  Usage (Vendor Usage 0x01)
0xa1, 0x01,        // 075:  Collection (Application)
0x85, 0x03,        // 077:   Report ID (3)
0x19, 0x00,        // 079:    .Usage Minimum (0)
0x2a, 0xff, 0x02,  // 07b:    .Usage Maximum (767)
0x15, 0x00,        // 07e:    .Logical Minimum (0)
0x26, 0xff, 0x02,  // 080:    .Logical Maximum (767)
0x75, 0x18,        // 083:    .Report Size (24)
0x95, 0x01,        // 085:    .Report Count (1)
0x81, 0x00,        // 087:   Input (Data,Arr,Abs)
0xc0,              // 089:  End Collection
0x06, 0xe0, 0xff,  // 08a:  Usage Page (Vendor Usage Page 0xffe0)
0x09, 0x01,        // 08d:  Usage (Vendor Usage 0x01)
0xa1, 0x01,        // 08f:  Collection (Application)
0x85, 0x21,        // 091:   Report ID (33)
0x09, 0x00,        // 093:   Usage (Vendor Usage 0x00)
0x15, 0x00,        // 095:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 097:    .Logical Maximum (255)
0x75, 0x08,        // 09a:    .Report Size (8)
0x95, 0x3f,        // 09c:    .Report Count (63)
0x81, 0x02,        // 09e:   Input (Data,Var,Abs)
0x85, 0x20,        // 0a0:   Report ID (32)
0x09, 0x00,        // 0a2:   Usage (Vendor Usage 0x00)
0x91, 0x02,        // 0a4:   Output (Data,Var,Abs)
0xc0,              // 0a6:  End Collection
0x06, 0x31, 0xff,  // 0a7:  Usage Page (Vendor Usage Page 0xff31)
0x09, 0x76,        // 0aa:  Usage (Vendor Usage 0x76)
0xa1, 0x01,        // 0ac:  Collection (Application)
0x85, 0x5a,        // 0ae:   Report ID (90)
0x09, 0x76,        // 0b0:   Usage (Vendor Usage 0x76)
0x15, 0x00,        // 0b2:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 0b4:    .Logical Maximum (255)
0x75, 0x08,        // 0b7:    .Report Size (8)
0x95, 0x05,        // 0b9:    .Report Count (5)
0x81, 0x02,        // 0bb:   Input (Data,Var,Abs)
0x85, 0x5a,        // 0bd:   Report ID (90)
0x09, 0x76,        // 0bf:   Usage (Vendor Usage 0x76)
0x75, 0x08,        // 0c1:    .Report Size (8)
0x95, 0x0f,        // 0c3:    .Report Count (15)
0xb1, 0x02,        // 0c5:   Feature (Data,Var,Abs)
0xc0,              // 0c7:  End Collection
0x06, 0x00, 0xff,  // 0c8:  Usage Page (Vendor Usage Page 0xff00)
0x09, 0x01,        // 0cb:  Usage (Vendor Usage 0x01)
0xa1, 0x01,        // 0cd:  Collection (Application)
0x85, 0x42,        // 0cf:   Report ID (66)
0x09, 0x06,        // 0d1:   Usage (Vendor Usage 0x06)
0x15, 0x00,        // 0d3:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 0d5:    .Logical Maximum (255)
0x75, 0x08,        // 0d8:    .Report Size (8)
0x95, 0x03,        // 0da:    .Report Count (3)
0xb1, 0x02,        // 0dc:   Feature (Data,Var,Abs)
0x85, 0x43,        // 0de:   Report ID (67)
0x09, 0x06,        // 0e0:   Usage (Vendor Usage 0x06)
0x15, 0x00,        // 0e2:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 0e4:    .Logical Maximum (255)
0x75, 0x08,        // 0e7:    .Report Size (8)
0x95, 0x03,        // 0e9:    .Report Count (3)
0xb1, 0x02,        // 0eb:   Feature (Data,Var,Abs)
0x06, 0x00, 0xff,  // 0ed:   Usage Page (Vendor Usage Page 0xff00)
0x85, 0x41,        // 0f0:   Report ID (65)
0x09, 0x05,        // 0f2:   Usage (Vendor Usage 0x05)
0x15, 0x00,        // 0f4:    .Logical Minimum (0)
0x26, 0xff, 0x00,  // 0f6:    .Logical Maximum (255)
0x75, 0x08,        // 0f9:    .Report Size (8)
0x96, 0x00, 0x01,  // 0fb:    .Report Count (256)
0xb1, 0x02,        // 0fe:   Feature (Data,Var,Abs)
0xc0,              // 100:  End Collection

Selected device:
/dev/hidraw0  0b05:1bf3 Usage Page: 0xff00 Usage: 0x0001 Interface: -1 Names: '': 'ASUS Zenbook Duo Keyboard'

[antheas]

Thank you. You confirmed that 0b05:1bf3 (bluetooth) and 0b05:1bf2 (USB) need to be added to hid-asus with their respective protocols as ROG keyboards.

They both contain the application 0xff310076 with report ID 0x5A that is needed to control RGB and access vendor keys with Aura.

I will add them to the next kernel build. Keep in mind that you might need to wait for F43 to drop into testing.

[antheas]

Doing USB would be nice yes.

[antheas]

One more thing you should check under the current kernel is if KDE can see a four point brightness slider for the keyboard. If not, assuming the keyboard can be unavailable, this will need a quirk in the kernel too

[marcofrancis]

Doing USB would be nice yes.

So, shall I run hhd.contrib hidraw while keyboard is connected via USB OR while keyboard is on BT? Then select #1?

One more thing you should check under the current kernel is if KDE can see a four point brightness slider for the keyboard. If not, assuming the keyboard can be unavailable, this will need a quirk in the kernel too

Mmm, I do not have the slider neither in the Brightness and Colour nor in the Battery widgets. Any other place I should check?

[antheas]

Doing USB would be nice yes.

So, shall I run hhd.contrib hidraw while keyboard is connected via USB OR while keyboard is on BT? Then select #1?

You already did bluetooth. USB would be nice.

One more thing you should check under the current kernel is if KDE can see a four point brightness slider for the keyboard. If not, assuming the keyboard can be unavailable, this will need a quirk in the kernel too

Mmm, I do not have the slider neither in the Brightness and Colour nor in the Battery widgets. Any other place I should check?

This means that even if we add the quirk, if your system starts with the keyboard disconnected, keyboard brightness will not work as uPower will not pick it up. Therefore, we will need an additional patch for Duo models that enables the brightness slider on boot regardless of keyboard.

[marcofrancis]

Again, sorry if I'm being pedantic, but I don't want to give you the wrong data. So:

• I selected number # 0 while the keyboard was on bluetooth
• Do you want me to select number # 1 while the keyboard is on bluetooth OR do you want em to select number # 1 while the keyboard is connected via USB?

[antheas]

Order is random. For USB you want this one:

- /dev/hidraw4  0b05:1bf2 Usage Page: 0xff31 Usage: 0x0076 Interface: 4 Names: 'Primax Electronics Ltd.': 'ASUS Zenbook Duo Keyboard'

It might not be 4