Your message dated Wed, 7 Oct 2026 13:47:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#1150188: linux-image-6.12.111: hid-asus fails N-KEY
init (-75), built-in keyboard dead on ASUS ROG Strix GL704GM (regression from
6.12.107)
has caused the Debian Bug report #1150188,
regarding linux-image-6.12.111: hid-asus fails N-KEY init (-75), built-in
keyboard dead on ASUS ROG Strix GL704GM (regression from 6.12.107)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1150188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150188
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:linux
Version: 6.12.111-1
Severity: important
Tags: regression
Since upgrading from 6.12.107-1 to 6.12.111-1, the built-in keyboard of an
ASUS ROG Strix GL704GM sends no key events at all. Booting 6.12.107-1 again
fixes it completely. The two kernels are installed side by side on the same
machine, nothing else changes, and the result is the same every time.
**Hardware**
- ASUS ROG Strix GL704GM (`Strix GL704GM_GL704GM`), BIOS GL704GM.301
(2018-09-14)
- The built-in keyboard is the internal USB device
`0b05:1866 ASUSTek Computer, Inc. N-KEY Device`, bound by `hid-asus`.
The PS/2 `AT Translated Set 2 keyboard` on serio0 carries no keys on this
model: IRQ 1 stays at its probe-time count while typing works on 6.12.107.
- Debian 13 (trixie) based, MX Linux 25.3, Debian kernel `6.12.111+deb13-amd64`
**Symptom on 6.12.111**
No key events reach the kernel from the built-in keyboard: none at the display
manager, on a VT, or in the desktop session. An evdev reader on the "Asus
Keyboard" input nodes sees nothing, and the Caps Lock LED doesn't toggle. USB
keyboards work normally. The internal keyboard works in GRUB and in Windows on
the same machine. The device is not runtime-suspended (`power/control=on`,
`runtime_status=active`).
**Kernel log, 6.12.111 (every boot, 7 of 7):**
```
asus 0003:0B05:1866.0002: input,hidraw1: USB HID v1.10 Keyboard
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input0
asus 0003:0B05:1866.0003: input,hidraw2: USB HID v1.10 Keyboard
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input1
asus 0003:0B05:1866.0004: Fixing up Asus N-Key report descriptor
asus 0003:0B05:1866.0004: Asus failed to request functions: -75
asus 0003:0B05:1866.0004: Failed to initialize backlight.
asus 0003:0B05:1866.0004: input,hiddev0,hidraw3: USB HID v1.10 Device
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input2
```
**Kernel log, 6.12.107 (every boot, keyboard works):**
```
asus 0003:0B05:1866.0004: input,hidraw2: USB HID v1.10 Keyboard
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input0
asus 0003:0B05:1866.0007: Fixing up Asus N-Key report descriptor
asus 0003:0B05:1866.0007: input,hiddev0,hidraw4: USB HID v1.10 Device
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input2
asus 0003:0B05:1866.0005: input,hidraw5: USB HID v1.10 Keyboard
[ASUSTeK Computer Inc. N-KEY Device] on usb-0000:00:14.0-10/input1
```
The new message is the functions request in the keyboard init path failing
with -EOVERFLOW (-75) on interface 2. After that the device stays silent,
which suggests the keyboard is never put into its reporting mode.
**Likely cause (not bisected)**
The only `hid-asus` changes between 6.12.107 and 6.12.111 are in 6.12.108:
- `HID: asus: simplify RGB init sequence`
- `HID: asus: fix missing hid_is_usb() check`
The first one changes the N-KEY init path, which is where the failure is
logged. I haven't bisected or tested a revert. I can test a patched kernel or
a revert if that helps.
**Workaround:** boot 6.12.107-1.
Further output (`lsusb -v -d 0b05:1866`, the hid report descriptor from
`/sys/kernel/debug/hid/0003:0B05:1866.*/rdesc`, full dmesg from either kernel)
is available on request.
--- End Message ---
--- Begin Message ---
This is a form message in response to your bug report.
The bug report appears to be a mixture of your own writing and
analysis generated by an LLM. This is not helpful to us, because it
is hard for us to understand which parts of the report are real
information about the problem and which are just statistically likely
text (and maybe "hallucination").
We cannot proceeed from such unreliable information. I am therefore
closing this bug report.
However, you may open a new bug report that does not include LLM-
generated explanations. You do not need to write a long report! Just
say what you know about the problem, and we can work with you and/or
upstream developers to debug it.
You should use the "reportbug" command or another program that runs
bug scripts on the affected system, if possible. Please read
<https://www.debian.org/Bugs/Reporting> if you have not previously
used it.
--- End Message ---
