Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM in Oracular

Bug #2089113 reported by Mitchell Augustin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Mitchell Augustin
Oracular
Fix Released
Medium
Mitchell Augustin

Bug Description

SRU Justification:

[ Impact ]

The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.

[ Test Plan ]

I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.

[ Fix ]

On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.

[ Where problems could occur ]

I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.

[ Changes since v1 of this patch set ]

A patch series that fixes this is already upstream: https://<email address hidden>/

Corrected patch format issues

Luke D. Jones (1):
  hid-asus: use hid for brightness control on keyboard

 drivers/hid/hid-asus.c | 7 +++++
 drivers/platform/x86/asus-wmi.c | 3 +-
 include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
 3 files changed, 45 insertions(+), 1 deletion(-)

CVE References

affects: linux-nvidia-6.2 (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
assignee: nobody → Mitchell Augustin (mitchellaugustin)
Revision history for this message
Mitchell Augustin (mitchellaugustin) wrote :

SRU request submitted to kernel-team mailing list ([SRU][Oracular][PATCH 0/1] hid-asus: use hid for brightness control)

Changed in linux (Ubuntu):
status: Confirmed → In Progress
description: updated
tags: added: oracular
Agathe Porte (gagath)
Changed in linux (Ubuntu Oracular):
status: New → In Progress
assignee: nobody → Mitchell Augustin (mitchellaugustin)
Changed in linux (Ubuntu Oracular):
status: In Progress → Fix Committed
importance: Undecided → Medium
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.11.0-17.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-oracular-linux' to 'verification-done-oracular-linux'. If the problem still exists, change the tag 'verification-needed-oracular-linux' to 'verification-failed-oracular-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-oracular-linux-v2 verification-needed-oracular-linux
tags: added: verification-done-oracular-linux
removed: verification-needed-oracular-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-intel/6.11.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-oracular-linux-intel' to 'verification-done-oracular-linux-intel'. If the problem still exists, change the tag 'verification-needed-oracular-linux-intel' to 'verification-failed-oracular-linux-intel'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-oracular-linux-intel-v2 verification-needed-oracular-linux-intel
Changed in linux (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (254.6 KiB)

This bug was fixed in the package linux - 6.11.0-18.18

---------------
linux (6.11.0-18.18) oracular; urgency=medium

  * CVE-2025-0927
    - SAUCE: fs: hfs/hfsplus: add key_len boundary check to hfs_bnode_read_key

linux (6.11.0-17.17) oracular; urgency=medium

  * oracular/linux: 6.11.0-17.17 -proposed tracker (LP: #2093643)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon (LP: #2091744)
    - [Packaging] disable hv-kvp-daemon if needed

  * Backport "netkit: Add option for scrubbing skb meta data" to 6.8
    (LP: #2091184)
    - netkit: Add option for scrubbing skb meta data

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
    - Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x

  * oracular: ubuntu_boot lib/dynamic_queue_limits.c:99! (LP: #2089684)
    - virtio_net: correct netdev_tx_reset_queue() invocation point
    - virtio_ring: add a func argument 'recycle_done' to virtqueue_resize()
    - virtio_net: ensure netdev_tx_reset_queue is called on tx ring resize

  * Failed to probe for OVTI02C1: chip id mismatch: 560243!=0 (LP: #2090932)
    - SAUCE: ACPI: scan: Update HID for new platform

  * Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported
    features (-110)" (LP: #2085485)
    - Bluetooth: btintel_pcie: Add recovery mechanism

  * Poor bluetooth performance on Lenovo X13s (LP: #2089357)
    - SAUCE: Bluetooth: qca: Support downloading board ID specific NVM for WCN6855

  * vfio_pci soft lockup on VM start while using PCIe passthrough (LP: #2089306)
    - SAUCE: Revert "mm: use rwsem assertion macros for mmap_lock"
    - SAUCE: Revert "vfio/pci: Insert full vma on mmap'd MMIO fault"
    - SAUCE: Revert "vfio/pci: Use unmap_mapping_range()"

  * Oracular update: v6.11.11 upstream stable release (LP: #2091655)
    - wifi: mac80211: Fix setting txpower with emulate_chanctx
    - wifi: cfg80211: Add wiphy_delayed_work_pending()
    - wifi: mac80211: Convert color collision detection to wiphy work
    - wifi: radiotap: Avoid -Wflex-array-member-not-at-end warnings
    - spi: stm32: fix missing device mode capability in stm32mp25
    - ASoC: codecs: rt5640: Always disable IRQs from rt5640_cancel_work()
    - ASoC: Intel: bytcr_rt5640: Add support for non ACPI instantiated codec
    - ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet
    - ASoC: Intel: sst: Support LPE0F28 ACPI HID
    - wifi: iwlwifi: mvm: Use the sync timepoint API in suspend
    - wifi: iwlwifi: mvm: SAR table alignment
    - mac80211: fix user-power when emulating chanctx
    - usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver
    - usb: typec: use cleanup facility for 'altmodes_node'
    - selftests/watchdog-test: Fix system accidentally reset after watchdog-test
    - ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13
    - ASoC: codecs: wcd937x: ...

Changed in linux (Ubuntu Oracular):
status: Fix Committed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Update Released

The verification of the Stable Release Update for linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-6.11/6.11.0-1011.11~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp-6.11' to 'verification-done-noble-linux-gcp-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-6.11' to 'verification-failed-noble-linux-gcp-6.11'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-gcp-6.11-v2 verification-needed-noble-linux-gcp-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.11/6.11.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-6.11' to 'verification-done-noble-linux-nvidia-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-6.11' to 'verification-failed-noble-linux-nvidia-6.11'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-nvidia-6.11-v2 verification-needed-noble-linux-nvidia-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.11/6.11.0-1012.12~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-6.11' to 'verification-done-noble-linux-azure-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-6.11' to 'verification-failed-noble-linux-azure-6.11'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-azure-6.11-v2 verification-needed-noble-linux-azure-6.11
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.