Public bug reported: [Impact] The ASUS Zenbook A16 (UX3607OA) carries its main keyboard on an I2C-HID device with ID 0B05:4B42. Its Fn/media hotkeys use the ASUS vendor page on report 0x5a. Ubuntu 26.04 linux-nvidia and linux-nvidia-bos need the upstream hid-asus support for this device.
The affected mappings are: 0x85 -> KEY_CAMERA (Fn+F11, camera toggle) 0x86 -> KEY_PROG1 (Fn+F12, MyASUS key) 0x5f -> KEY_PROG2 (extra programmable key) The camera-toggle key sends its usage together with a companion state byte: 5a 85 01 or 5a 85 10. The 0x10 companion aliases the brightness- down vendor usage and can spuriously dim the panel. [Fix] Backport upstream commit 206107536018272a9c786fab74cdd90ee748ac2f (HID: asus: support the Zenbook A16 (UX3607OA) keyboard): https://github.com/torvalds/linux/commit/206107536018272a9c786fab74cdd90ee748ac2f The change adds the device match and key mappings, and filters camera companion slots before input mapping. The filter is gated to this keyboard. Downstream uses BIT(16) for the new quirk because BIT(15) is already used by QUIRK_ROG_NKEY_ID1ID2_INIT. Backport pull requests: https://github.com/NVIDIA/NV-Kernels/pull/637 https://github.com/NVIDIA/NV-Kernels/pull/638 ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Tags: fixed-upstream hw-specific kernel-bug resolute ** Description changed: [Impact] The ASUS Zenbook A16 (UX3607OA) carries its main keyboard on an I2C-HID device with ID 0B05:4B42. Its Fn/media hotkeys use the ASUS vendor page on report 0x5a. Ubuntu 26.04 linux-nvidia and linux-nvidia-bos need the upstream hid-asus support for this device. The affected mappings are: - 0x85 -> KEY_CAMERA (Fn+F11, camera toggle) - 0x86 -> KEY_PROG1 (Fn+F12, MyASUS key) - 0x5f -> KEY_PROG2 (extra programmable key) + 0x85 -> KEY_CAMERA (Fn+F11, camera toggle) + 0x86 -> KEY_PROG1 (Fn+F12, MyASUS key) + 0x5f -> KEY_PROG2 (extra programmable key) The camera-toggle key sends its usage together with a companion state byte: 5a 85 01 or 5a 85 10. The 0x10 companion aliases the brightness- down vendor usage and can spuriously dim the panel. [Fix] Backport upstream commit 206107536018272a9c786fab74cdd90ee748ac2f (HID: asus: support the Zenbook A16 (UX3607OA) keyboard): https://github.com/torvalds/linux/commit/206107536018272a9c786fab74cdd90ee748ac2f The change adds the device match and key mappings, and filters camera companion slots before input mapping. The filter is gated to this keyboard. Downstream uses BIT(16) for the new quirk because BIT(15) is already used by QUIRK_ROG_NKEY_ID1ID2_INIT. Backport pull requests: https://github.com/NVIDIA/NV-Kernels/pull/637 https://github.com/NVIDIA/NV-Kernels/pull/638 - - [Test Plan] - On an ASUS Zenbook A16 (UX3607OA), boot each affected kernel with the backport and inspect keyboard input events: - 1. Verify Fn+F11 produces KEY_CAMERA and does not spuriously lower panel brightness for either camera-toggle state. - 2. Verify Fn+F12 produces KEY_PROG1 and the extra programmable key produces KEY_PROG2. - 3. Verify ordinary keyboard input and brightness hotkeys still work. - - The device observations above come from the upstream commit and backport - descriptions. This report does not include hardware validation results. - - [Regression Potential] - The new device match and camera filter are specific to 0B05:4B42. The usage mappings are added to the shared ASUS vendor mapping, so other ASUS devices using these usages should be checked for unintended key events. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170055 Title: ASUS Zenbook A16 (UX3607OA) Fn/media keys need hid-asus support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2170055/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
