[Bug] Keyboard works when connected to laptop, but not through dock (modelh, thinkpad thunderbolt 3 workstation dock)
#23.825 aperta il 29 mag 2024
Metriche repository
- Star
- (20.368 star)
- Metriche merge PR
- (Merge medio 20g 9h) (27 PR mergiate in 30 g)
Descrizione
Describe the Bug
I'm using an IBM Model M keyboard, upgraded with the modelh controller from keebd.
The keyboard works perfectly fine when attached directly to any of my 3 laptops (archlinux thinkpad p1g2, windows11 thinkpad x1 carbon gen 8, windows11 t490s) but does not work when attached through my thinkpad thunderbolt 3 workstation dock gen2.
Attaching the keyboard directly to the laptop results in the following dmesg output: ` [10388.938531] usb 1-2: new full-speed USB device number 25 using xhci_hcd [10389.081163] usb 1-2: New USB device found, idVendor=1eaf, idProduct=0003, bcdDevice= 2.01 [10389.081166] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10389.081168] usb 1-2: Product: Maple 003 [10389.081168] usb 1-2: Manufacturer: LeafLabs [10389.081169] usb 1-2: SerialNumber: LLM 003 [10390.451680] usb 1-2: USB disconnect, device number 25 [10390.775181] usb 1-2: new full-speed USB device number 26 using xhci_hcd [10390.916535] usb 1-2: New USB device found, idVendor=feed, idProduct=b155, bcdDevice= 1.00 [10390.916539] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [10390.916541] usb 1-2: Product: Model M [10390.916542] usb 1-2: Manufacturer: IBM [10390.918142] input: IBM Model M as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:FEED:B155.0019/input/input47 [10390.972071] hid-generic 0003:FEED:B155.0019: input,hidraw2: USB HID v1.11 Keyboard [IBM Model M] on usb-0000:00:14.0-2/input0 [10390.973047] input: IBM Model M System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:FEED:B155.001A/input/input48 [10391.028550] input: IBM Model M Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:FEED:B155.001A/input/input49 [10391.028630] hid-generic 0003:FEED:B155.001A: input,hidraw3: USB HID v1.11 Device [IBM Model M] on usb-0000:00:14.0-2/input1 [10391.571392] audit: type=1326 audit(1717014109.109:20): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=22467 comm="qmk_id" exe="/usr/lib/udev/qmk_id" sig=31 arch=c000003e syscall=67 compat=0 ip=0x79b44dbec1ab code=0x80000000 [10391.572936] audit: type=1326 audit(1717014109.113:21): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=22473 comm="qmk_id" exe="/usr/lib/udev/qmk_id" sig=31 arch=c000003e syscall=67 compat=0 ip=0x79ef376c01ab code=0x80000000
`
And connecting the keyboard to the dock results in the following:
`
[10415.288333] usb 3-2.1.3: new low-speed USB device number 31 using xhci_hcd [10415.415233] usb 3-2.1.3: device descriptor read/64, error -32 [10415.648606] usb 3-2.1.3: device descriptor read/64, error -32 [10415.878582] usb 3-2.1.3: new low-speed USB device number 32 using xhci_hcd [10416.004928] usb 3-2.1.3: device descriptor read/64, error -32 [10416.238404] usb 3-2.1.3: device descriptor read/64, error -32 [10416.345138] usb 3-2.1-port3: attempt power cycle `
The dock has the latest firmware installed, and I have built and flashed the latest version of QMK to the controller, resulting in no change so far. I have also tried disabling NKRO and mouse keys by adding a rules.mk file in the relevant directory, but make reported that both were already disabled in the jsonfile, so nothing changed from that either.
I'm hoping it's possible i could tweak something in the firmware that may allow the dock to recognize this controller, and would really appreciate some pointers - this is my first QMK based controller, and internet search results including "qmk" and "dock" are very few.
Keyboard Used
ibm/model_m/modelh
Link to product page (if applicable)
https://keebd.com/products/model-h-usb-controller-upgrade-ibm-model-m
Operating System
archlinux, windows11
qmk doctor Output
not relevant
Is AutoHotKey / Karabiner installed
- AutoHotKey (Windows)
- Karabiner (macOS)
Other keyboard-related software installed
No response
Additional Context
No response