Public bug reported:

## Summary
After BIOS update to version FX608JHR.309 (2026-01-28), the Super key stopped
working on Linux. The asus_wmi driver receives scancode 0x4f but has no mapping
for it, logging "Unknown key code 0x4f".

## Hardware
- Model: ASUS TUF Gaming F16 FX608JHR
- BIOS: FX608JHR.309 (2026-01-28)

## Software
- OS: Ubuntu 24.04
- Kernels tested: 6.14.0-37 and 6.17.0-22 (both affected)
- asusd: v6.1.21

## Root Cause
BIOS 309 added a new WMI event in the DSDT ACPI table:

    Case (0x31)          <- WMI internal event
    {
        If (ATKP)
        {
            ^^^ATKD.IANE (0x4F)   <- scancode sent to asus_wmi
        }
    }

The scancode 0x4F is not present in the asus_wmi/asus_nb_wmi keymap,
resulting in:

    asus_wmi: Unknown key code 0x4f

## Evidence
dmesg:
    [22.271983] asus_wmi: Unknown key code 0x4f

evtest /dev/input/event8 (Asus WMI hotkeys):
    Event: type 4 (EV_MSC), code 4 (MSC_SCAN), value 4f
    Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
    Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0

Note: The key is emitted as instant down+up (~10 microseconds apart),
making it impossible to use as a modifier key even with userspace remapping.

## Expected Behavior
Scancode 0x4f should map to KEY_LEFTMETA (Super/Windows key).

## Proposed Fix
Add the following entry to the asus_nb_wmi keymap in
drivers/platform/x86/asus-nb-wmi.c:

    { KE_KEY, 0x4F, { KEY_LEFTMETA } },

## Additional Notes
The key generates instant down+up events (not sustained hold), which suggests
the BIOS may need to be fixed as well to properly report key hold state.
A BIOS fix would be needed for modifier combinations (Super+L, Super+arrows)
to work correctly.
EOF

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.17.0-23-generic 6.17.0-23.23~24.04.1
ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13
Uname: Linux 6.17.0-23-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  admilson   5074 F.... wireplumber
 /dev/snd/controlC0:  admilson   5074 F.... wireplumber
 /dev/snd/seq:        admilson   5070 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May  5 12:31:51 2026
InstallationDate: Installed on 2025-11-23 (163 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 
(20250805.1)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F16 FX608JHR_FX608JHR
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-23-generic 
root=UUID=480ae6c2-abb4-447f-a413-8693b2fa1e99 ro quiet splash 
mem_sleep_default=deep nvidia-drm.modeset=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.17.0-23-generic N/A
 linux-backports-modules-6.17.0-23-generic  N/A
 linux-firmware                             20240318.git3b128b60-0ubuntu2.27
SourcePackage: linux-hwe-6.17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2025
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX608JHR.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX608JHR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.7
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX608JHR.309:bd11/03/2025:br5.27:efr3.7:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF16FX608JHR_FX608JHR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX608JHR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS TUF Gaming F16
dmi.product.name: ASUS TUF Gaming F16 FX608JHR_FX608JHR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux-hwe-6.17 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug noble

** Description changed:

- # Coletar tudo em um arquivo
- cat > ~/asus-super-key-bug-report.txt << 'EOF'
- === Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16 FX608JHR 
===
+ === Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16
+ FX608JHR ===
  
  ## Summary
  After BIOS update to version FX608JHR.309 (2026-01-28), the Super key stopped
  working on Linux. The asus_wmi driver receives scancode 0x4f but has no 
mapping
  for it, logging "Unknown key code 0x4f".
  
  ## Hardware
  - Model: ASUS TUF Gaming F16 FX608JHR
  - BIOS: FX608JHR.309 (2026-01-28)
  
  ## Software
  - OS: Ubuntu 24.04
  - Kernels tested: 6.14.0-37 and 6.17.0-22 (both affected)
  - asusd: v6.1.21
  
  ## Root Cause
  BIOS 309 added a new WMI event in the DSDT ACPI table:
  
-     Case (0x31)          <- WMI internal event
-     {
-         If (ATKP)
-         {
-             ^^^ATKD.IANE (0x4F)   <- scancode sent to asus_wmi
-         }
-     }
+     Case (0x31)          <- WMI internal event
+     {
+         If (ATKP)
+         {
+             ^^^ATKD.IANE (0x4F)   <- scancode sent to asus_wmi
+         }
+     }
  
  The scancode 0x4F is not present in the asus_wmi/asus_nb_wmi keymap,
  resulting in:
  
-     asus_wmi: Unknown key code 0x4f
+     asus_wmi: Unknown key code 0x4f
  
  ## Evidence
  dmesg:
-     [22.271983] asus_wmi: Unknown key code 0x4f
+     [22.271983] asus_wmi: Unknown key code 0x4f
  
  evtest /dev/input/event8 (Asus WMI hotkeys):
-     Event: type 4 (EV_MSC), code 4 (MSC_SCAN), value 4f
-     Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
-     Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
+     Event: type 4 (EV_MSC), code 4 (MSC_SCAN), value 4f
+     Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
+     Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
  
  Note: The key is emitted as instant down+up (~10 microseconds apart),
  making it impossible to use as a modifier key even with userspace remapping.
  
  ## Expected Behavior
  Scancode 0x4f should map to KEY_LEFTMETA (Super/Windows key).
  
  ## Proposed Fix
  Add the following entry to the asus_nb_wmi keymap in
  drivers/platform/x86/asus-nb-wmi.c:
  
-     { KE_KEY, 0x4F, { KEY_LEFTMETA } },
+     { KE_KEY, 0x4F, { KEY_LEFTMETA } },
  
  ## Additional Notes
  The key generates instant down+up events (not sustained hold), which suggests
  the BIOS may need to be fixed as well to properly report key hold state.
  A BIOS fix would be needed for modifier combinations (Super+L, Super+arrows)
  to work correctly.
  EOF
  
  echo "Bug report salvo em ~/asus-super-key-bug-report.txt"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.17.0-23-generic 6.17.0-23.23~24.04.1
  ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13
  Uname: Linux 6.17.0-23-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
-  USER        PID ACCESS COMMAND
-  /dev/snd/controlC1:  admilson   5074 F.... wireplumber
-  /dev/snd/controlC0:  admilson   5074 F.... wireplumber
-  /dev/snd/seq:        admilson   5070 F.... pipewire
+  USER        PID ACCESS COMMAND
+  /dev/snd/controlC1:  admilson   5074 F.... wireplumber
+  /dev/snd/controlC0:  admilson   5074 F.... wireplumber
+  /dev/snd/seq:        admilson   5070 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 12:31:51 2026
  InstallationDate: Installed on 2025-11-23 (163 days ago)
  InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 
(20250805.1)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F16 FX608JHR_FX608JHR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-23-generic 
root=UUID=480ae6c2-abb4-447f-a413-8693b2fa1e99 ro quiet splash 
mem_sleep_default=deep nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-6.17.0-23-generic N/A
-  linux-backports-modules-6.17.0-23-generic  N/A
-  linux-firmware                             20240318.git3b128b60-0ubuntu2.27
+  linux-restricted-modules-6.17.0-23-generic N/A
+  linux-backports-modules-6.17.0-23-generic  N/A
+  linux-firmware                             20240318.git3b128b60-0ubuntu2.27
  SourcePackage: linux-hwe-6.17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2025
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX608JHR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX608JHR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX608JHR.309:bd11/03/2025:br5.27:efr3.7:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF16FX608JHR_FX608JHR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX608JHR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F16
  dmi.product.name: ASUS TUF Gaming F16 FX608JHR_FX608JHR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Summary changed:

- Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16 FX608JHR 
+ asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16 FX608JHR

** Description changed:

- === Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16
- FX608JHR ===
- 
  ## Summary
  After BIOS update to version FX608JHR.309 (2026-01-28), the Super key stopped
  working on Linux. The asus_wmi driver receives scancode 0x4f but has no 
mapping
  for it, logging "Unknown key code 0x4f".
  
  ## Hardware
  - Model: ASUS TUF Gaming F16 FX608JHR
  - BIOS: FX608JHR.309 (2026-01-28)
  
  ## Software
  - OS: Ubuntu 24.04
  - Kernels tested: 6.14.0-37 and 6.17.0-22 (both affected)
  - asusd: v6.1.21
  
  ## Root Cause
  BIOS 309 added a new WMI event in the DSDT ACPI table:
  
      Case (0x31)          <- WMI internal event
      {
          If (ATKP)
          {
              ^^^ATKD.IANE (0x4F)   <- scancode sent to asus_wmi
          }
      }
  
  The scancode 0x4F is not present in the asus_wmi/asus_nb_wmi keymap,
  resulting in:
  
      asus_wmi: Unknown key code 0x4f
  
  ## Evidence
  dmesg:
      [22.271983] asus_wmi: Unknown key code 0x4f
  
  evtest /dev/input/event8 (Asus WMI hotkeys):
      Event: type 4 (EV_MSC), code 4 (MSC_SCAN), value 4f
      Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
      Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
  
  Note: The key is emitted as instant down+up (~10 microseconds apart),
  making it impossible to use as a modifier key even with userspace remapping.
  
  ## Expected Behavior
  Scancode 0x4f should map to KEY_LEFTMETA (Super/Windows key).
  
  ## Proposed Fix
  Add the following entry to the asus_nb_wmi keymap in
  drivers/platform/x86/asus-nb-wmi.c:
  
      { KE_KEY, 0x4F, { KEY_LEFTMETA } },
  
  ## Additional Notes
  The key generates instant down+up events (not sustained hold), which suggests
  the BIOS may need to be fixed as well to properly report key hold state.
  A BIOS fix would be needed for modifier combinations (Super+L, Super+arrows)
  to work correctly.
  EOF
  
  echo "Bug report salvo em ~/asus-super-key-bug-report.txt"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.17.0-23-generic 6.17.0-23.23~24.04.1
  ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13
  Uname: Linux 6.17.0-23-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  admilson   5074 F.... wireplumber
   /dev/snd/controlC0:  admilson   5074 F.... wireplumber
   /dev/snd/seq:        admilson   5070 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 12:31:51 2026
  InstallationDate: Installed on 2025-11-23 (163 days ago)
  InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 
(20250805.1)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F16 FX608JHR_FX608JHR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-23-generic 
root=UUID=480ae6c2-abb4-447f-a413-8693b2fa1e99 ro quiet splash 
mem_sleep_default=deep nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.17.0-23-generic N/A
   linux-backports-modules-6.17.0-23-generic  N/A
   linux-firmware                             20240318.git3b128b60-0ubuntu2.27
  SourcePackage: linux-hwe-6.17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2025
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX608JHR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX608JHR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX608JHR.309:bd11/03/2025:br5.27:efr3.7:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF16FX608JHR_FX608JHR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX608JHR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F16
  dmi.product.name: ASUS TUF Gaming F16 FX608JHR_FX608JHR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Summary changed:

- asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16 FX608JHR
+ Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16 FX608JHR

** Description changed:

  ## Summary
  After BIOS update to version FX608JHR.309 (2026-01-28), the Super key stopped
  working on Linux. The asus_wmi driver receives scancode 0x4f but has no 
mapping
  for it, logging "Unknown key code 0x4f".
  
  ## Hardware
  - Model: ASUS TUF Gaming F16 FX608JHR
  - BIOS: FX608JHR.309 (2026-01-28)
  
  ## Software
  - OS: Ubuntu 24.04
  - Kernels tested: 6.14.0-37 and 6.17.0-22 (both affected)
  - asusd: v6.1.21
  
  ## Root Cause
  BIOS 309 added a new WMI event in the DSDT ACPI table:
  
      Case (0x31)          <- WMI internal event
      {
          If (ATKP)
          {
              ^^^ATKD.IANE (0x4F)   <- scancode sent to asus_wmi
          }
      }
  
  The scancode 0x4F is not present in the asus_wmi/asus_nb_wmi keymap,
  resulting in:
  
      asus_wmi: Unknown key code 0x4f
  
  ## Evidence
  dmesg:
      [22.271983] asus_wmi: Unknown key code 0x4f
  
  evtest /dev/input/event8 (Asus WMI hotkeys):
      Event: type 4 (EV_MSC), code 4 (MSC_SCAN), value 4f
      Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
      Event: type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
  
  Note: The key is emitted as instant down+up (~10 microseconds apart),
  making it impossible to use as a modifier key even with userspace remapping.
  
  ## Expected Behavior
  Scancode 0x4f should map to KEY_LEFTMETA (Super/Windows key).
  
  ## Proposed Fix
  Add the following entry to the asus_nb_wmi keymap in
  drivers/platform/x86/asus-nb-wmi.c:
  
      { KE_KEY, 0x4F, { KEY_LEFTMETA } },
  
  ## Additional Notes
  The key generates instant down+up events (not sustained hold), which suggests
  the BIOS may need to be fixed as well to properly report key hold state.
  A BIOS fix would be needed for modifier combinations (Super+L, Super+arrows)
  to work correctly.
  EOF
  
- echo "Bug report salvo em ~/asus-super-key-bug-report.txt"
- 
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.17.0-23-generic 6.17.0-23.23~24.04.1
  ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13
  Uname: Linux 6.17.0-23-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  admilson   5074 F.... wireplumber
   /dev/snd/controlC0:  admilson   5074 F.... wireplumber
   /dev/snd/seq:        admilson   5070 F.... pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  5 12:31:51 2026
  InstallationDate: Installed on 2025-11-23 (163 days ago)
  InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 
(20250805.1)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F16 FX608JHR_FX608JHR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-23-generic 
root=UUID=480ae6c2-abb4-447f-a413-8693b2fa1e99 ro quiet splash 
mem_sleep_default=deep nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.17.0-23-generic N/A
   linux-backports-modules-6.17.0-23-generic  N/A
   linux-firmware                             20240318.git3b128b60-0ubuntu2.27
  SourcePackage: linux-hwe-6.17
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2025
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FX608JHR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX608JHR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.7
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX608JHR.309:bd11/03/2025:br5.27:efr3.7:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF16FX608JHR_FX608JHR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX608JHR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming F16
  dmi.product.name: ASUS TUF Gaming F16 FX608JHR_FX608JHR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2151215

Title:
  Bug Report: asus_wmi Unknown key code 0x4f - ASUS TUF Gaming F16
  FX608JHR

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.17/+bug/2151215/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to