starred/kvm
1
0
Fork 0
mirror of https://github.com/jetkvm/kvm.git synced 2026-03-02 22:58:00 -05:00
Code Issues 252 Projects Packages Wiki Activity

USB not detected if not present at startup #95

New issue
Open
opened 2026-02-20 08:20:16 -05:00 by deekerman · 15 comments
deekerman commented 2026-02-20 08:20:16 -05:00
Owner
Copy link

Originally created by @Nyarumi on GitHub (Feb 1, 2025).

Originally assigned to: @IDisposable on GitHub.

App: 0.3.4
System: 0.2.0

My JetKVM does not recognize the USB connection if it's already powered on before the USB is connected. For example, if I power on the device using the RJ-11 jack from the ATX module and then plug in the USB, it never recognizes it. But, if I power it on using the USB first it works just fine. Strangely, shutting down the PC and then turning it back on re-establishes the USB link just fine, but simply unplugging and replugging it back in does not. I'm unsure if this is the intended behavior, but it doesn't seem like that would make much sense.

Originally created by @Nyarumi on GitHub (Feb 1, 2025). Originally assigned to: @IDisposable on GitHub. App: 0.3.4 System: 0.2.0 My JetKVM does not recognize the USB connection if it's already powered on before the USB is connected. For example, if I power on the device using the RJ-11 jack from the ATX module and then plug in the USB, it never recognizes it. But, if I power it on using the USB first it works just fine. Strangely, shutting down the PC and then turning it back on re-establishes the USB link just fine, but simply unplugging and replugging it back in does not. I'm unsure if this is the intended behavior, but it doesn't seem like that would make much sense.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@azfoxd commented on GitHub (Feb 4, 2025):

Thanks for the issue. Could be related to #41 as well.

@azfoxd commented on GitHub (Feb 4, 2025): Thanks for the issue. Could be related to #41 as well.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@caplam commented on GitHub (Apr 17, 2025):

I have the exact same bug when using the dc power extension.
App: 0.3.9
System: 0.2.3

@caplam commented on GitHub (Apr 17, 2025): I have the exact same bug when using the dc power extension. App: 0.3.9 System: 0.2.3
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@IITYWYBMAB commented on GitHub (Apr 23, 2025):

Having this problem often as well, although it manifests a bit differently. I am fully remote (overseas) with no remote power on this machine currently, so I have to call in remote hands to power cycle the device at my colocation rack. I've had to do this several times. I've tried warm booting the machine and rebooting the KVM remotely, neither get's the USB to connect. It just spins "connecting" forever.

System: NUC Gen 13 i7
Plugged directly into USB for Power (which does work) and connectivity on USBC port.
Debian 11.2 Bookworm

Thanks for looking into this!

@IITYWYBMAB commented on GitHub (Apr 23, 2025): Having this problem often as well, although it manifests a bit differently. I am fully remote (overseas) with no remote power on this machine currently, so I have to call in remote hands to power cycle the device at my colocation rack. I've had to do this several times. I've tried warm booting the machine and rebooting the KVM remotely, neither get's the USB to connect. It just spins "connecting" forever. System: NUC Gen 13 i7 Plugged directly into USB for Power (which does work) and connectivity on USBC port. Debian 11.2 Bookworm Thanks for looking into this!
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@DevSecNinja commented on GitHub (May 19, 2025):

I have the same or a similar problem. I need to fully shutdown my server, disconnect JetKVM from both power + data, let JetKVM boot up and then start the server for USB to work.

@DevSecNinja commented on GitHub (May 19, 2025): I have the same or a similar problem. I need to fully shutdown my server, disconnect JetKVM from both power + data, let JetKVM boot up and then start the server for USB to work.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@th3voic3 commented on GitHub (May 20, 2025):

What works for me right now just as a workaround is enabling ssh and then logging onto the jetkvm and issuing a reboot. After a reboot everything works. For keyboard input it is often enough to go to hardware in the web interface and updating the USB identifier. For mouse to work I have to reboot the Jetkvm

@th3voic3 commented on GitHub (May 20, 2025): What works for me right now just as a workaround is enabling ssh and then logging onto the jetkvm and issuing a reboot. After a reboot everything works. For keyboard input it is often enough to go to hardware in the web interface and updating the USB identifier. For mouse to work I have to reboot the Jetkvm
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@IITYWYBMAB commented on GitHub (Jun 17, 2025):

Seems to be more stable now, perhaps I'm just getting lucky?

@IITYWYBMAB commented on GitHub (Jun 17, 2025): Seems to be more stable now, perhaps I'm just getting lucky?
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@indy-scott commented on GitHub (Jul 25, 2025):

Confirmed with the DC power extension being used. I have the same issue as many that if I power off the server while maintaining power to the JetKVM when I turn on the server USB no longer connects. As stated, I have to turn on the server then SSH into the JetKVM and reboot to get things working again.

@indy-scott commented on GitHub (Jul 25, 2025): Confirmed with the DC power extension being used. I have the same issue as many that if I power off the server while maintaining power to the JetKVM when I turn on the server USB no longer connects. As stated, I have to turn on the server then SSH into the JetKVM and reboot to get things working again.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@x-cubed commented on GitHub (Sep 3, 2025):

I've seen the same problem with the DC power extension in use, with the following errors showing in the Linux console of the connected computer:

Image

Following the suggestions above about rebooting to fix it, I went into Settings -> Advanced -> Troubleshooting Mode -> Disable USB Emulation, then Enable USB Emulation, and the JetKVM showed USB as connected again, and the Linux console responded to keyboard input.

Somehow the USB emulation isn't starting up correctly when powered from the RJ11 jack.

@x-cubed commented on GitHub (Sep 3, 2025): I've seen the same problem with the DC power extension in use, with the following errors showing in the Linux console of the connected computer: <img width="538" height="113" alt="Image" src="https://github.com/user-attachments/assets/5ad7ac38-c3d2-4894-a44d-ad9bee603201" /> Following the suggestions above about rebooting to fix it, I went into *Settings* -> *Advanced* -> *Troubleshooting Mode* -> *Disable USB Emulation*, then *Enable USB Emulation*, and the JetKVM showed USB as connected again, and the Linux console responded to keyboard input. Somehow the USB emulation isn't starting up correctly when powered from the RJ11 jack.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@AdrianFletcher commented on GitHub (Sep 14, 2025):

Just adding another voice to this one. Thanks @x-cubed as your suggestion fixed it for me as well. I have this issue when using the ATX extension powered over the RJ-11.

Disabling and re-enabling the USB Emulation fixed it.

@AdrianFletcher commented on GitHub (Sep 14, 2025): Just adding another voice to this one. Thanks @x-cubed as your suggestion fixed it for me as well. I have this issue when using the ATX extension powered over the RJ-11. Disabling and re-enabling the USB Emulation fixed it.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@RobVerduijn commented on GitHub (Nov 7, 2025):

I experienced this today with my 2 new jetkvm devices, both have the dc-power-control extension.

I started them , updated them and gave them a testrun
app: 0.4.8
system: 0.2.5

the keyboard/mouse didn't work

The workaround fixed this:

  • disconnect 12v from dc-power-control
  • disconnect usb
  • reconnect usb
  • wait for jetkvm to initialize
  • connect 12v

and keyboard/mouse worked

@RobVerduijn commented on GitHub (Nov 7, 2025): I experienced this today with my 2 new jetkvm devices, both have the dc-power-control extension. I started them , updated them and gave them a testrun app: 0.4.8 system: 0.2.5 the keyboard/mouse didn't work The workaround fixed this: - disconnect 12v from dc-power-control - disconnect usb - reconnect usb - wait for jetkvm to initialize - connect 12v and keyboard/mouse worked
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@julianrichen commented on GitHub (Nov 10, 2025):

Same as others above.

App: 0.4.8
System: 0.2.5

I have a JetKVM + DC Power Control Extension. The DC Power Control has 12V/3A DC input, which powers a mini PC via the DC Out and then RJ11 power to JetKVM. USB-C-to-USB-A cable from JetKVM to mini PC doesn't seem to work. I don't get any error, but when I unplug/plug the USB cable i get:

[58.709907] usb 1-3: new high-speed USB device number 9 using xhci_hcd
[58.821951] usb 1-3: device descriptor read/64, error -71
[59.836942] usb 1-3: device descriptor read/64, error -71
[59.252889] usb 1-3: new high-speed USB device number 10 using xhci_hcd
[59.364937] usb 1-3: device descriptor read/64, error -71
[59.581918] usb 1-3: device descriptor read/64, error -71
[59.685032] usb usb1-port3: attempt power cycle
[60.063843] usb 1-3: new high-speed USB device number 11 using xhci_hcd
[60.064019] usb 1-3: Device not responding to setup address.
[60.269016] usb 1-3: Device not responding to setup address.
[60.476821] usb 1-3: device not accepting address 11, error -71
[60.588858] usb 1-3: new high-speed USB device number 12 using xhci_hcd
[60.589028] usb 1-3: Device not responding to setup address.
[60.797009] usb 1-3: Device not responding to setup address.
[61.004793] usb 1-3: device not accepting address 12, error -71
[61.005086] usb usb1-port3: unable to enumerate USB device

Trying what @x-cubed recommended under Settings -> Advanced -> Troubleshooting Mode -> Disable USB Emulation, then Enable USB Emulation does seem to resolve it; until you lose power to the DC Extension.

I can power cycle the device either via systemctl reboot/systemctl poweroff or the DC Power Control extension and usb continues to work. It's only when I unplug and/or lose power completely to the DC Power Control Extension itself either by unpluging the DC input or losing power externally does it require me to redo the workaround above.

Likely not important by for reference:

Hardware: GMKtec Nucbox G3 Mini PC
OS: Fedora-IOT 42.2

@julianrichen commented on GitHub (Nov 10, 2025): Same as others above. App: 0.4.8 System: 0.2.5 I have a JetKVM + DC Power Control Extension. The DC Power Control has 12V/3A DC input, which powers a mini PC via the DC Out and then RJ11 power to JetKVM. USB-C-to-USB-A cable from JetKVM to mini PC doesn't seem to work. I don't get any error, but when I unplug/plug the USB cable i get: ``` [58.709907] usb 1-3: new high-speed USB device number 9 using xhci_hcd [58.821951] usb 1-3: device descriptor read/64, error -71 [59.836942] usb 1-3: device descriptor read/64, error -71 [59.252889] usb 1-3: new high-speed USB device number 10 using xhci_hcd [59.364937] usb 1-3: device descriptor read/64, error -71 [59.581918] usb 1-3: device descriptor read/64, error -71 [59.685032] usb usb1-port3: attempt power cycle [60.063843] usb 1-3: new high-speed USB device number 11 using xhci_hcd [60.064019] usb 1-3: Device not responding to setup address. [60.269016] usb 1-3: Device not responding to setup address. [60.476821] usb 1-3: device not accepting address 11, error -71 [60.588858] usb 1-3: new high-speed USB device number 12 using xhci_hcd [60.589028] usb 1-3: Device not responding to setup address. [60.797009] usb 1-3: Device not responding to setup address. [61.004793] usb 1-3: device not accepting address 12, error -71 [61.005086] usb usb1-port3: unable to enumerate USB device ``` Trying what @x-cubed recommended under Settings -> Advanced -> Troubleshooting Mode -> Disable USB Emulation, then Enable USB Emulation does seem to resolve it; until you lose power to the DC Extension. I can power cycle the device either via `systemctl reboot`/`systemctl poweroff` or the DC Power Control extension and usb continues to work. It's only when I unplug and/or lose power completely to the DC Power Control Extension itself either by unpluging the DC input or losing power externally does it require me to redo the workaround above. Likely not important by for reference: Hardware: GMKtec Nucbox G3 Mini PC OS: Fedora-IOT 42.2
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@ym commented on GitHub (Nov 14, 2025):

We can confirm that we have been able to reproduce this issue, and we are currently working on it.

@ym commented on GitHub (Nov 14, 2025): We can confirm that we have been able to reproduce this issue, and we are currently working on it.
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@netandreus commented on GitHub (Jan 29, 2026):

Have the same issue, guys :(

USB: Disconnected
PC: Minisforum MS-01
OS: VMWare ESXi 8.0.3
JetKVM app: 0.5.2
JetKVM System: 0.2.7

Can't use keyboard and mouse.

Image
@netandreus commented on GitHub (Jan 29, 2026): Have the same issue, guys :( USB: Disconnected PC: Minisforum MS-01 OS: VMWare ESXi 8.0.3 JetKVM app: 0.5.2 JetKVM System: 0.2.7 Can't use keyboard and mouse. <img width="1517" height="1233" alt="Image" src="https://github.com/user-attachments/assets/e30fef57-d94b-4332-84f5-68f58bd621bf" />
deekerman commented 2026-02-20 08:20:17 -05:00
Author
Owner
Copy link

@netandreus commented on GitHub (Feb 2, 2026):

Fixed for me either connect second usb-c <-> usb-a cable to splitter and PC or to connect with single usb-c <-> usb-a cable without using a splitter.

@netandreus commented on GitHub (Feb 2, 2026): Fixed for me either connect second usb-c <-> usb-a cable to splitter and PC or to connect with single usb-c <-> usb-a cable without using a splitter.
deekerman commented 2026-02-20 08:20:18 -05:00
Author
Owner
Copy link

@gentslava commented on GitHub (Feb 15, 2026):

Same issue there. USB connection is not established until jetkvm is rebooted.
For any USB port.

App: 0.5.3
System: 0.2.7

Server logs:

2026-02-16T06:41:51.791975+07:00 home kernel: usb 1-4: new high-speed USB device number 2 using xhci_hcd
2026-02-16T06:41:51.791979+07:00 home kernel: usb 1-4: device descriptor read/64, error -71
2026-02-16T06:41:51.791979+07:00 home kernel: usb 1-4: device descriptor read/64, error -71
2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: new high-speed USB device number 3 using xhci_hcd
2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: device descriptor read/64, error -71
2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: device descriptor read/64, error -71
2026-02-16T06:41:51.792093+07:00 home kernel: usb usb1-port4: attempt power cycle
2026-02-16T06:41:51.792114+07:00 home kernel: usb 1-4: new high-speed USB device number 4 using xhci_hcd
2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: Device not responding to setup address.
2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: Device not responding to setup address.
2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: device not accepting address 4, error -71
2026-02-16T06:41:51.792118+07:00 home kernel: usb 1-4: new high-speed USB device number 5 using xhci_hcd
2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: Device not responding to setup address.
2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: Device not responding to setup address.
2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: device not accepting address 5, error -71
2026-02-16T06:41:51.792119+07:00 home kernel: usb usb1-port4: unable to enumerate USB device
...
2026-02-16T06:42:44.509838+07:00 home kernel: usb 1-2: new high-speed USB device number 19 using xhci_hcd
2026-02-16T06:42:44.624854+07:00 home kernel: usb 1-2: device descriptor read/64, error -71
2026-02-16T06:42:44.842826+07:00 home kernel: usb 1-2: device descriptor read/64, error -71
2026-02-16T06:42:45.064895+07:00 home kernel: usb 1-2: new high-speed USB device number 20 using xhci_hcd
2026-02-16T06:42:45.179842+07:00 home kernel: usb 1-2: device descriptor read/64, error -71
2026-02-16T06:42:45.401826+07:00 home kernel: usb 1-2: device descriptor read/64, error -71
2026-02-16T06:42:45.510855+07:00 home kernel: usb usb1-port2: attempt power cycle
2026-02-16T06:42:45.899854+07:00 home kernel: usb 1-2: new high-speed USB device number 21 using xhci_hcd
2026-02-16T06:42:45.899874+07:00 home kernel: usb 1-2: Device not responding to setup address.
2026-02-16T06:42:46.102844+07:00 home kernel: usb 1-2: Device not responding to setup address.
2026-02-16T06:42:46.310887+07:00 home kernel: usb 1-2: device not accepting address 21, error -71
2026-02-16T06:42:46.425850+07:00 home kernel: usb 1-2: new high-speed USB device number 22 using xhci_hcd
2026-02-16T06:42:46.425863+07:00 home kernel: usb 1-2: Device not responding to setup address.
2026-02-16T06:42:46.630828+07:00 home kernel: usb 1-2: Device not responding to setup address.
2026-02-16T06:42:46.839832+07:00 home kernel: usb 1-2: device not accepting address 22, error -71
2026-02-16T06:42:46.839849+07:00 home kernel: usb usb1-port2: unable to enumerate USB device
...
2026-02-16T07:02:51.502617+07:00 home kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
2026-02-16T07:02:51.502617+07:00 home kernel: usb 1-1: device descriptor read/64, error -71
2026-02-16T07:02:51.502618+07:00 home kernel: usb 1-1: device descriptor read/64, error -71
2026-02-16T07:02:51.502687+07:00 home kernel: usb 1-1: new high-speed USB device number 3 using xhci_hcd
2026-02-16T07:02:51.502687+07:00 home kernel: usb 1-1: device descriptor read/64, error -71
2026-02-16T07:02:51.502690+07:00 home kernel: usb 1-1: device descriptor read/64, error -71
2026-02-16T07:02:51.502690+07:00 home kernel: usb usb1-port1: attempt power cycle
2026-02-16T07:02:51.502708+07:00 home kernel: usb 1-1: new high-speed USB device number 4 using xhci_hcd
2026-02-16T07:02:51.502709+07:00 home kernel: usb 1-1: Device not responding to setup address.
2026-02-16T07:02:51.502709+07:00 home kernel: usb 1-1: Device not responding to setup address.
2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: device not accepting address 4, error -71
2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: new high-speed USB device number 5 using xhci_hcd
2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: Device not responding to setup address.
2026-02-16T07:02:51.502713+07:00 home kernel: usb 1-1: Device not responding to setup address.
2026-02-16T07:02:51.502713+07:00 home kernel: usb 1-1: device not accepting address 5, error -71
2026-02-16T07:02:51.502713+07:00 home kernel: usb usb1-port1: unable to enumerate USB device

After rebooting JetKVM, logs appeared:

2026-02-16T07:03:07.422205+07:00 home kernel: usb 1-1: new high-speed USB device number 8 using xhci_hcd
2026-02-16T07:03:07.554225+07:00 home kernel: usb 1-1: New USB device found, idVendor=1d6b, idProduct=0104, bcdDevice= 1.00
2026-02-16T07:03:07.554241+07:00 home kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2026-02-16T07:03:07.554242+07:00 home kernel: usb 1-1: Product: USB Emulation Device
2026-02-16T07:03:07.554243+07:00 home kernel: usb 1-1: Manufacturer: JetKVM
2026-02-16T07:03:07.593617+07:00 home kernel: usb-storage 1-1:1.3: USB Mass Storage device detected
2026-02-16T07:03:07.593617+07:00 home kernel: scsi host0: usb-storage 1-1:1.3
2026-02-16T07:03:07.600202+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.0/0003:1D6B:0104.0001/input/input8
2026-02-16T07:03:07.653246+07:00 home kernel: hid-generic 0003:1D6B:0104.0001: input,hidraw0: USB HID v1.01 Keyboard [JetKVM USB Emulation Device] on usb-0000:c6:00.3-1/input0
2026-02-16T07:03:07.653265+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.1/0003:1D6B:0104.0002/input/input9
2026-02-16T07:03:07.689500+07:00 home kernel: hid-generic 0003:1D6B:0104.0002: input,hidraw1: USB HID v1.01 Mouse [JetKVM USB Emulation Device] on usb-0000:c6:00.3-1/input1
2026-02-16T07:03:07.689514+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.2/0003:1D6B:0104.0003/input/input10
@gentslava commented on GitHub (Feb 15, 2026): Same issue there. USB connection is not established until jetkvm is rebooted. For any USB port. App: 0.5.3 System: 0.2.7 Server logs: ``` 2026-02-16T06:41:51.791975+07:00 home kernel: usb 1-4: new high-speed USB device number 2 using xhci_hcd 2026-02-16T06:41:51.791979+07:00 home kernel: usb 1-4: device descriptor read/64, error -71 2026-02-16T06:41:51.791979+07:00 home kernel: usb 1-4: device descriptor read/64, error -71 2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: new high-speed USB device number 3 using xhci_hcd 2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: device descriptor read/64, error -71 2026-02-16T06:41:51.792089+07:00 home kernel: usb 1-4: device descriptor read/64, error -71 2026-02-16T06:41:51.792093+07:00 home kernel: usb usb1-port4: attempt power cycle 2026-02-16T06:41:51.792114+07:00 home kernel: usb 1-4: new high-speed USB device number 4 using xhci_hcd 2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: Device not responding to setup address. 2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: Device not responding to setup address. 2026-02-16T06:41:51.792115+07:00 home kernel: usb 1-4: device not accepting address 4, error -71 2026-02-16T06:41:51.792118+07:00 home kernel: usb 1-4: new high-speed USB device number 5 using xhci_hcd 2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: Device not responding to setup address. 2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: Device not responding to setup address. 2026-02-16T06:41:51.792119+07:00 home kernel: usb 1-4: device not accepting address 5, error -71 2026-02-16T06:41:51.792119+07:00 home kernel: usb usb1-port4: unable to enumerate USB device ... 2026-02-16T06:42:44.509838+07:00 home kernel: usb 1-2: new high-speed USB device number 19 using xhci_hcd 2026-02-16T06:42:44.624854+07:00 home kernel: usb 1-2: device descriptor read/64, error -71 2026-02-16T06:42:44.842826+07:00 home kernel: usb 1-2: device descriptor read/64, error -71 2026-02-16T06:42:45.064895+07:00 home kernel: usb 1-2: new high-speed USB device number 20 using xhci_hcd 2026-02-16T06:42:45.179842+07:00 home kernel: usb 1-2: device descriptor read/64, error -71 2026-02-16T06:42:45.401826+07:00 home kernel: usb 1-2: device descriptor read/64, error -71 2026-02-16T06:42:45.510855+07:00 home kernel: usb usb1-port2: attempt power cycle 2026-02-16T06:42:45.899854+07:00 home kernel: usb 1-2: new high-speed USB device number 21 using xhci_hcd 2026-02-16T06:42:45.899874+07:00 home kernel: usb 1-2: Device not responding to setup address. 2026-02-16T06:42:46.102844+07:00 home kernel: usb 1-2: Device not responding to setup address. 2026-02-16T06:42:46.310887+07:00 home kernel: usb 1-2: device not accepting address 21, error -71 2026-02-16T06:42:46.425850+07:00 home kernel: usb 1-2: new high-speed USB device number 22 using xhci_hcd 2026-02-16T06:42:46.425863+07:00 home kernel: usb 1-2: Device not responding to setup address. 2026-02-16T06:42:46.630828+07:00 home kernel: usb 1-2: Device not responding to setup address. 2026-02-16T06:42:46.839832+07:00 home kernel: usb 1-2: device not accepting address 22, error -71 2026-02-16T06:42:46.839849+07:00 home kernel: usb usb1-port2: unable to enumerate USB device ... 2026-02-16T07:02:51.502617+07:00 home kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd 2026-02-16T07:02:51.502617+07:00 home kernel: usb 1-1: device descriptor read/64, error -71 2026-02-16T07:02:51.502618+07:00 home kernel: usb 1-1: device descriptor read/64, error -71 2026-02-16T07:02:51.502687+07:00 home kernel: usb 1-1: new high-speed USB device number 3 using xhci_hcd 2026-02-16T07:02:51.502687+07:00 home kernel: usb 1-1: device descriptor read/64, error -71 2026-02-16T07:02:51.502690+07:00 home kernel: usb 1-1: device descriptor read/64, error -71 2026-02-16T07:02:51.502690+07:00 home kernel: usb usb1-port1: attempt power cycle 2026-02-16T07:02:51.502708+07:00 home kernel: usb 1-1: new high-speed USB device number 4 using xhci_hcd 2026-02-16T07:02:51.502709+07:00 home kernel: usb 1-1: Device not responding to setup address. 2026-02-16T07:02:51.502709+07:00 home kernel: usb 1-1: Device not responding to setup address. 2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: device not accepting address 4, error -71 2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: new high-speed USB device number 5 using xhci_hcd 2026-02-16T07:02:51.502712+07:00 home kernel: usb 1-1: Device not responding to setup address. 2026-02-16T07:02:51.502713+07:00 home kernel: usb 1-1: Device not responding to setup address. 2026-02-16T07:02:51.502713+07:00 home kernel: usb 1-1: device not accepting address 5, error -71 2026-02-16T07:02:51.502713+07:00 home kernel: usb usb1-port1: unable to enumerate USB device ``` After rebooting JetKVM, logs appeared: ``` 2026-02-16T07:03:07.422205+07:00 home kernel: usb 1-1: new high-speed USB device number 8 using xhci_hcd 2026-02-16T07:03:07.554225+07:00 home kernel: usb 1-1: New USB device found, idVendor=1d6b, idProduct=0104, bcdDevice= 1.00 2026-02-16T07:03:07.554241+07:00 home kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2026-02-16T07:03:07.554242+07:00 home kernel: usb 1-1: Product: USB Emulation Device 2026-02-16T07:03:07.554243+07:00 home kernel: usb 1-1: Manufacturer: JetKVM 2026-02-16T07:03:07.593617+07:00 home kernel: usb-storage 1-1:1.3: USB Mass Storage device detected 2026-02-16T07:03:07.593617+07:00 home kernel: scsi host0: usb-storage 1-1:1.3 2026-02-16T07:03:07.600202+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.0/0003:1D6B:0104.0001/input/input8 2026-02-16T07:03:07.653246+07:00 home kernel: hid-generic 0003:1D6B:0104.0001: input,hidraw0: USB HID v1.01 Keyboard [JetKVM USB Emulation Device] on usb-0000:c6:00.3-1/input0 2026-02-16T07:03:07.653265+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.1/0003:1D6B:0104.0002/input/input9 2026-02-16T07:03:07.689500+07:00 home kernel: hid-generic 0003:1D6B:0104.0002: input,hidraw1: USB HID v1.01 Mouse [JetKVM USB Emulation Device] on usb-0000:c6:00.3-1/input1 2026-02-16T07:03:07.689514+07:00 home kernel: input: JetKVM USB Emulation Device as /devices/pci0000:00/0000:00:08.1/0000:c6:00.3/usb1/1-1/1-1:1.2/0003:1D6B:0104.0003/input/input10 ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
dependabot/npm_and_yarn/ui/vitejs/plugin-react-swc-4.2.3
dependabot/npm_and_yarn/ui/vite-tsconfig-paths-6.1.1
dependabot/npm_and_yarn/ui/framer-motion-12.34.3
dependabot/npm_and_yarn/ui/tailwind-merge-3.5.0
dependabot/npm_and_yarn/ui/multi-d88693a43a
dependabot/go_modules/github.com/pion/webrtc/v4-4.2.9
dependabot/npm_and_yarn/ui/inlang/cli-3.1.6
dependabot/npm_and_yarn/ui/eslint-plugin-react-refresh-0.5.2
dependabot/go_modules/golang.org/x/sys-0.41.0
dependabot/go_modules/golang.org/x/crypto-0.48.0
dependabot/npm_and_yarn/ui/zustand-5.0.11
dependabot/go_modules/github.com/prometheus/procfs-0.20.1
dependabot/npm_and_yarn/ui/inlang/sdk-2.7.0
dependabot/go_modules/github.com/gin-gonic/gin-1.12.0
dependabot/go_modules/golang.org/x/net-0.51.0
dependabot/github_actions/actions/upload-artifact-7
dependabot/npm_and_yarn/ui/npm_and_yarn-e66adb831b
feat/signed-releases
dependabot/go_modules/github.com/prometheus/common-0.67.5
fix/ipv6-readiness
fix/failsafe-tolerance
fix/failscafe-tolerance
debug/native-logs
fix/retry-sleep-mode-check
copilot/add-copilot-instructions-file
chore/es-lint-redux
fix/deploy-cloud-app
release-cloud-app/0.4.9
release-cloud-app/0.4.8
release-cloud-app/0.4.5
release-cloud-app/0.4.4
release-cloud-app/0.4.3
release-cloud-app/0.4.2
release-cloud-app/0.4.1
release-cloud-app/0.4.0
release-cloud-app/0.3.9
release-cloud-app/0.3.8
fix/prevent-video-restart-loop
fix/en-as-default
backports/ota-und-cgo
e2e-tests
release/049
feat/audio-support-metrics
fix/usb-gadget-init-rebind
feat/lldp
feat/usb-reset
feat/audio-support
fix/hdmi-mutex
main
feat/auto-reload-fe
feat/jsonrpc-typings
feat/ocr
chore/show-codec
chore/golangci-lint-additional
refactor/jsonrpc-kbd
misc/0.4.6-with-old-deps
feat/static-ip-ui
cursor/refactor-uselocation-to-prevent-re-renders-f026
cursor/remove-uselocation-from-devices-id-tsx-7751
chore/eslint-prettier-setup
feat/tls-config
feat/metrics-optin
feat/tls
release/0.5.4-dev202602080922
release/0.5.3
release/0.5.3-dev202602061404
release/0.5.3-dev202601281951
release/0.5.2-dev202601071426
release/0.5.2
release/0.5.2-dev202601070105
release/0.5.2-dev202601070032
release/0.5.2-dev202601061215
release/0.5.2-dev202601051816
release/0.5.2-dev202512291946
release/0.5.1-dev202512211114
release/0.5.1
release/0.5.1-dev202512181840
release/0.5.1-dev202512181609
release/0.5.1-dev202512181144
release/0.5.0-dev202512051510
release/0.5.0
0.5.0-dev202511271013
0.5.0-dev202511271020
release/0.5.0-dev202511211223
release/0.5.0-dev20251120
release/0.4.9
release/0.4.8
release/0.4.7
challenge-base
release/0.4.6
release/0.4.5
release/0.4.5-rc2
release/0.4.5-rc1
release/0.4.4
release/0.4.3
release/0.4.2
release/0.4.1
release/0.4.0
release/0.3.9
release/0.3.8
Labels
Clear labels   
component/keyboard-layout

   
component: cloud

   
component: device screen

   
component: extensions

   
component: hid/keyboard

   
component: hid/mouse

   
component: network

   
component: timesync

   
component: ui

   
component: updater

   
component: usb

   
component: usb/hid

   
component: usb/storage

   
component: video

   
component: webrtc

   
component: webserver

   
need-more-details

   
status: working-in-progress

   
wontfix
No labels
component/keyboard-layout
component: cloud
component: device screen
component: extensions
component: hid/keyboard
component: hid/mouse
component: network
component: timesync
component: ui
component: updater
component: usb
component: usb/hid
component: usb/storage
component: video
component: webrtc
component: webserver
need-more-details
status: working-in-progress
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/kvm#95
No description provided.