Dear Maintainer,

   * What led up to the situation?
Connecting a Krom Kreator keyboard to any USB port on the system
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
- Tried different USB ports (USB 2.0, USB 3.0, front panel, rear I/O)
- Tried through USB hubs (powered and unpowered)
- Tried different USB quirks via kernel parameters
   * What was the outcome of this action?
Same problem persists: "usb *: unable to read config index 0 descriptor/start: -32"
The keyboard fails to enumerate and is unusable in Linux.
Previously it showed error -71 but after some update it changed to -32
   * What outcome did you expect instead?
Keyboard should enumerate and work normally as it does in BIOS and Windows.

=== dmesg output when keyboard connected ===
[10832.805157] usb 5-1.2: new full-speed USB device number 16 using xhci_hcd
[10838.070073] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10838.070082] usb 5-1.2: chopping to 0 config(s)
[10838.070086] usb 5-1.2: can't read configurations, error -32
[10838.165080] usb 5-1.2: new full-speed USB device number 17 using xhci_hcd
[10843.445780] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10843.445790] usb 5-1.2: chopping to 0 config(s)
[10843.445794] usb 5-1.2: can't read configurations, error -32
[10843.446086] usb 5-1-port2: attempt power cycle
[10844.029144] usb 5-1.2: new full-speed USB device number 18 using xhci_hcd
[10849.077690] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10849.077698] usb 5-1.2: chopping to 0 config(s)
[10849.077701] usb 5-1.2: can't read configurations, error -32
[10849.149121] usb 5-1.2: new full-speed USB device number 19 using xhci_hcd
[10854.197667] usb 5-1.2: unable to read config index 0 descriptor/start: -32
[10854.197675] usb 5-1.2: chopping to 0 config(s)
[10854.197678] usb 5-1.2: can't read configurations, error -32
[10854.197837] usb 5-1-port2: unable to enumerate USB device

=== lsusb -t output ===
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
    |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 003: Dev 004, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    |__ Port 005: Dev 005, If 0, Class=Vendor Specific Class, Driver=[none], 12M
    |__ Port 005: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 006: Dev 006, If 0, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 1, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 2, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 006: Dev 006, If 3, Class=Application Specific Interface, Driver=[none], 480M
    |__ Port 008: Dev 007, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/5p, 480M
        |__ Port 004: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 003: Dev 005, If 0, Class=Communications, Driver=cdc_ether, 480M
            |__ Port 003: Dev 005, If 1, Class=CDC Data, Driver=cdc_ether, 480M
            |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 003: Dev 007, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 005: Dev 004, If 0, Class=Billboard, Driver=[none], 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/:  Bus 009.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 10000M

=== Additional information ===
-The keyboard works perfectly in BIOS/UEFI and Windows 10/11
-Keyboard does not work in this specific system, probably due to an xhci_hcd issue on the A620 chipset

Hi,

Can you please attach the keyboard and the provide the *full* kernel
log, I'm interested to see the idVendor, and idProduct.

Please do as well provide a verbose output of lsusb for the device in
a moment it is seen.

If you do several plugging/unpuggling cycles, does it sometimes work
correctly?

Regards,
Salvatore

Hi

[Please include the Debian bug address as well as we want to keep
track of the pgorgress and information on the bug]
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

Hi,

Well yes, I know it is reported there in Debian.

let me phrase it differently. I won't provide private support, that is
please *always* include the Debian BTS email address as well in the
replies, so others in the team are aware as well of the progress.

Thank you. So I see in the one variant it seems to recocnize correctly
the keyboard. So we should still try to quirk before forwarding your
report to upstream.

I need here the full context. As

set +e; QUILT_PC=.pc quilt unapplied --quiltrc - >/dev/null && echo 'Patch series not fully applied'; test $? -eq 1
Patch series not fully applied


I think you need to massage a bit the patch yet for context in
6.12.63. I will see if I can provide you a test kernel to test it more
reasily.

For context of the bug I will attach your 3 provided log to the bug.

Regards,
Salvatore

Hi,

here we go, can you please test it with the (unofficial!) kernel
provided in
https://people.debian.org/~carnil/tmp/linux/1126149/
and report back if that resolves the issue?

Regards,
Salvatore

Hi,

[adding back the BTS bug]

Thanks for reporting back.

Regards,
Salvatore