Hi
[Please include the Debian bug address as well as we want to keep
track of the pgorgress and information on the bug]
On Tue, Jan 27, 2026 at 12:16:07AM +0000, Vicboom18 wrote:
> I used a Gigabyte G5 KC that also has Debian Trixie, the 2 *bad.log files
> are what's shown in the PC where the keyboard doesn't work while the
> *working.log files are what's shown in the laptop, in both cases the full
> dmesg log since the keyboard is connected and the lsusb executed after the
> dmesg.
> For what I could find the idVendor is 0x5566 ZXWMicroChip and the idProduct
> is 0x0008 ZXW-Keyboard.
> Plugging and unplugging several times does not work.
The full boot log would show more on the surrounding system so if you
can provide if for both the non working system and the working laptop
system can you please provide it still. I'm confused if they both run
trixie but work on one but not the other.
Can you please try the following testing patch please on the non
working system:
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index c4d85089d19b..7e6de2a27416 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -581,6 +581,9 @@ static const struct usb_device_id usb_quirk_list[] = {
/* VCOM device */
{ USB_DEVICE(0x4296, 0x7570), .driver_info =
USB_QUIRK_CONFIG_INTF_STRINGS },
+ /* ZXWMicroChip ZXW-Keyboard */
+ { USB_DEVICE(0x5566, 0x0008), .driver_info = USB_QUIRK_NO_LPM },
+
/* INTEL VALUE SSD */
{ USB_DEVICE(0x8086, 0xf1a5), .driver_info = USB_QUIRK_RESET_RESUME },
As the issue looks somehow similar to 181135bb20dc ("usb: add NO_LPM
quirk for Realforce 87U Keyboard").
To build and test a kernel with a patch applied on top see:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
If you struggle at any step with the above please let us know so we
might try to outline it smoother.
Regards,
Salvatore
