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

Using JetKVM attached to RPi Zero2W - repeated constant kernel messages relating to USB resets and storage device sr 0 resets #234

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

Originally created by @rtw819 on GitHub (May 1, 2025).

Background:
I have my new days-old JetKVM unit attached to a Raspberry Pi Zero2W via Mini HDMI and USB. The JetKVM is being powered externally and separately using the included USB-C Splitter with its own power supply, the data side of the splitter cable is attached to the RPi USB Hub for Keyboard/Mouse/etc. connectivity. The RPi has its own separate power supply as well. Pretty standard, right? The USB hub has a cable attached to a UPS since the purpose of the RPi is a remote Network UPS Tool (NUT) monitor for the UPS which you'll see in the RPi messages output below.

I consistently see -- every 1-2 minutes now -- a couple of kernel messages popping up on the Raspberry Pi:

<DateTime> <hostname> kernel: [ <uptime>] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
<DateTime> <hostname> kernel: [ <uptime>] sr 0:0:0:0: Power-on or device reset occurred

I'm guessing the USB resets and Storage Device resets logged every minute or two are NOT normal/expected? I don't believe this to be an RPi issue, since the RPi wasn't complaining until I connected the JetKVM.

This happened with both the original "as-shipped" firmware versions (couldn't find them), and still happens consistently with the latest updates:
App: 0.3.9
System: 0.2.3

Here's a snippet of the RPi's /var/log/messages file:

Apr 29 23:46:41 upsmon1 kernel: [  491.743962] vc4-drm soc:gpu: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x68 0x5
Apr 30 00:10:02 upsmon1 rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="371" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Apr 30 00:25:05 upsmon1 kernel: [ 2795.751271] vc4-drm soc:gpu: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x68 0x5
Apr 30 00:25:26 upsmon1 kernel: [ 2816.843298] Indeed it is in host mode hprt0 = 00021501
Apr 30 00:25:26 upsmon1 kernel: [ 2817.031103] usb 1-1: new high-speed USB device number 2 using dwc_otg
Apr 30 00:25:26 upsmon1 kernel: [ 2817.031257] Indeed it is in host mode hprt0 = 00001101
Apr 30 00:25:26 upsmon1 kernel: [ 2817.239632] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
Apr 30 00:25:26 upsmon1 kernel: [ 2817.239677] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Apr 30 00:25:26 upsmon1 kernel: [ 2817.239692] usb 1-1: Product: USB 2.0 Hub
Apr 30 00:25:26 upsmon1 kernel: [ 2817.240603] hub 1-1:1.0: USB hub found
Apr 30 00:25:26 upsmon1 kernel: [ 2817.240753] hub 1-1:1.0: 4 ports detected
Apr 30 00:25:27 upsmon1 kernel: [ 2817.631088] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Apr 30 00:25:27 upsmon1 kernel: [ 2817.832253] usb 1-1.1: New USB device found, idVendor=1d6b, idProduct=0044, bcdDevice= 0.40
Apr 30 00:25:27 upsmon1 kernel: [ 2817.832281] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 30 00:25:27 upsmon1 kernel: [ 2817.832296] usb 1-1.1: Product: JetKVM USB Emulation Device
Apr 30 00:25:27 upsmon1 kernel: [ 2817.832309] usb 1-1.1: Manufacturer: JetKVM
Apr 30 00:25:27 upsmon1 kernel: [ 2817.832322] usb 1-1.1: SerialNumber: ################
Apr 30 00:25:27 upsmon1 kernel: [ 2817.837018] input: JetKVM JetKVM USB Emulation Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1D6B:0044.0001/input/input1
Apr 30 00:25:27 upsmon1 kernel: [ 2817.896315] hid-generic 0003:1D6B:0044.0001: input,hidraw0: USB HID v1.01 Keyboard [JetKVM JetKVM USB Emulation Device] on usb-3f980000.usb-1.1/input0
Apr 30 00:25:27 upsmon1 kernel: [ 2817.900071] input: JetKVM JetKVM USB Emulation Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1:1.1/0003:1D6B:0044.0002/input/input2
Apr 30 00:25:27 upsmon1 kernel: [ 2817.900752] hid-generic 0003:1D6B:0044.0002: input,hidraw1: USB HID v1.01 Mouse [JetKVM JetKVM USB Emulation Device] on usb-3f980000.usb-1.1/input1
Apr 30 00:25:27 upsmon1 kernel: [ 2817.901778] usb-storage 1-1.1:1.2: USB Mass Storage device detected
Apr 30 00:25:27 upsmon1 kernel: [ 2817.902764] scsi host0: usb-storage 1-1.1:1.2
Apr 30 00:25:27 upsmon1 mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Apr 30 00:25:27 upsmon1 mtp-probe: bus: 1, device: 3 was not an MTP device
Apr 30 00:25:27 upsmon1 kernel: [ 2818.103137] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
Apr 30 00:25:28 upsmon1 kernel: [ 2818.329090] usb 1-1.3: New USB device found, idVendor=0764, idProduct=0601, bcdDevice= 2.00
Apr 30 00:25:28 upsmon1 kernel: [ 2818.329120] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Apr 30 00:25:28 upsmon1 kernel: [ 2818.329135] usb 1-1.3: Product: CP1500PFCLCDa
Apr 30 00:25:28 upsmon1 kernel: [ 2818.329148] usb 1-1.3: Manufacturer: CPS
Apr 30 00:25:28 upsmon1 kernel: [ 2818.329161] usb 1-1.3: SerialNumber: CXXNY#######
Apr 30 00:25:28 upsmon1 kernel: [ 2818.349125] hid-generic 0003:0764:0601.0003: hiddev96,hidraw2: USB HID v1.10 Device [CPS CP1500PFCLCDa] on usb-3f980000.usb-1.3/input0
Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 3 was not an MTP device
Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 30 00:25:28 upsmon1 kernel: [ 2818.531112] usb 1-1.4: new high-speed USB device number 5 using dwc_otg
Apr 30 00:25:28 upsmon1 kernel: [ 2818.732400] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=8152, bcdDevice=20.00
Apr 30 00:25:28 upsmon1 kernel: [ 2818.732448] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 30 00:25:28 upsmon1 kernel: [ 2818.732464] usb 1-1.4: Product: USB 10/100 LAN
Apr 30 00:25:28 upsmon1 kernel: [ 2818.732477] usb 1-1.4: Manufacturer: Realtek
Apr 30 00:25:28 upsmon1 kernel: [ 2818.732490] usb 1-1.4: SerialNumber: 00E04C360113
Apr 30 00:25:28 upsmon1 kernel: [ 2818.911146] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
Apr 30 00:25:28 upsmon1 kernel: [ 2818.919827] scsi 0:0:0:0: CD-ROM            JetKVM V irtual Media          PQ: 0 ANSI: 2
Apr 30 00:25:28 upsmon1 kernel: [ 2818.951491] scsi 0:0:0:0: Attached scsi generic sg0 type 5
Apr 30 00:25:28 upsmon1 kernel: [ 2818.969931] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:25:28 upsmon1 kernel: [ 2819.075793] sr 0:0:0:0: [sr0] scsi-1 drive
Apr 30 00:25:28 upsmon1 kernel: [ 2819.075823] cdrom: Uniform CD-ROM driver Revision: 3.20
Apr 30 00:25:28 upsmon1 kernel: [ 2819.141298] r8152 1-1.4:1.0: skip request firmware
Apr 30 00:25:28 upsmon1 kernel: [ 2819.172665] r8152 1-1.4:1.0 eth0: v1.12.13
Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 5 was not an MTP device
Apr 30 00:25:28 upsmon1 kernel: [ 2819.249556] usbcore: registered new interface driver cdc_ether
Apr 30 00:25:29 upsmon1 mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4"
Apr 30 00:25:29 upsmon1 mtp-probe: bus: 1, device: 5 was not an MTP device
Apr 30 00:25:29 upsmon1 kernel: [ 2819.338984] r8152 1-1.4:1.0 enx00e04c360113: renamed from eth0
Apr 30 00:26:30 upsmon1 kernel: [ 2880.703282] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:26:30 upsmon1 kernel: [ 2881.011622] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:27:31 upsmon1 kernel: [ 2942.135453] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:27:32 upsmon1 kernel: [ 2942.443908] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:28:33 upsmon1 kernel: [ 3003.583547] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:28:33 upsmon1 kernel: [ 3003.889276] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:29:34 upsmon1 kernel: [ 3065.015727] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:29:35 upsmon1 kernel: [ 3065.325049] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:30:36 upsmon1 kernel: [ 3126.455841] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:30:36 upsmon1 kernel: [ 3126.767305] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:31:37 upsmon1 kernel: [ 3187.899965] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:31:37 upsmon1 kernel: [ 3188.209530] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:32:41 upsmon1 kernel: [ 3251.384075] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:32:41 upsmon1 kernel: [ 3251.695140] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:33:42 upsmon1 kernel: [ 3312.824187] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:33:42 upsmon1 kernel: [ 3313.134063] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:34:44 upsmon1 kernel: [ 3374.264277] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
Apr 30 00:34:44 upsmon1 kernel: [ 3374.572938] sr 0:0:0:0: Power-on or device reset occurred
Apr 30 00:35:45 upsmon1 kernel: [ 3435.712349] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
###
...  After a couple JetKVM reboots...
...
###
May  1 21:10:59 upsmon1 kernel: [163950.427050] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:12:00 upsmon1 kernel: [164011.552905] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:12:01 upsmon1 kernel: [164011.862487] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:13:02 upsmon1 kernel: [164072.989118] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:13:02 upsmon1 kernel: [164073.298069] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:14:03 upsmon1 kernel: [164134.437288] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:14:04 upsmon1 kernel: [164134.639502] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:15:05 upsmon1 kernel: [164195.877526] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:15:05 upsmon1 kernel: [164196.185915] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:16:06 upsmon1 kernel: [164257.317707] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:16:07 upsmon1 kernel: [164257.624972] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:17:08 upsmon1 kernel: [164318.757923] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:17:08 upsmon1 kernel: [164319.067005] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:18:09 upsmon1 kernel: [164380.194153] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:18:09 upsmon1 kernel: [164380.502586] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:19:11 upsmon1 kernel: [164441.630352] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:19:11 upsmon1 kernel: [164441.938090] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:20:14 upsmon1 kernel: [164505.130588] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:20:14 upsmon1 kernel: [164505.440291] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:21:18 upsmon1 kernel: [164568.614764] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:21:18 upsmon1 kernel: [164568.922483] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:22:19 upsmon1 kernel: [164630.042994] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:22:19 upsmon1 kernel: [164630.351398] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:23:20 upsmon1 kernel: [164691.495168] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:23:21 upsmon1 kernel: [164691.803694] sr 0:0:0:0: Power-on or device reset occurred
May  1 21:24:22 upsmon1 kernel: [164752.927365] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg
May  1 21:24:22 upsmon1 kernel: [164753.235918] sr 0:0:0:0: Power-on or device reset occurred

Any thoughts? Suggestions? Thanks in advance!

Originally created by @rtw819 on GitHub (May 1, 2025). Background: I have my new days-old JetKVM unit attached to a Raspberry Pi Zero2W via Mini HDMI and USB. The JetKVM is being powered externally and separately using the included USB-C Splitter with its own power supply, the data side of the splitter cable is attached to the RPi USB Hub for Keyboard/Mouse/etc. connectivity. The RPi has its own separate power supply as well. Pretty standard, right? The USB hub has a cable attached to a UPS since the purpose of the RPi is a remote Network UPS Tool (NUT) monitor for the UPS which you'll see in the RPi messages output below. I consistently see -- every 1-2 minutes now -- a couple of kernel messages popping up on the Raspberry Pi: ``` <DateTime> <hostname> kernel: [ <uptime>] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg <DateTime> <hostname> kernel: [ <uptime>] sr 0:0:0:0: Power-on or device reset occurred ``` I'm guessing the USB resets and Storage Device resets logged every minute or two are NOT normal/expected? I don't believe this to be an RPi issue, since the RPi wasn't complaining until I connected the JetKVM. This happened with both the original "as-shipped" firmware versions (couldn't find them), and still happens consistently with the latest updates: App: 0.3.9 System: 0.2.3 Here's a snippet of the RPi's /var/log/messages file: ``` Apr 29 23:46:41 upsmon1 kernel: [ 491.743962] vc4-drm soc:gpu: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x68 0x5 Apr 30 00:10:02 upsmon1 rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="371" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Apr 30 00:25:05 upsmon1 kernel: [ 2795.751271] vc4-drm soc:gpu: [drm] User-defined mode not supported: "1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x68 0x5 Apr 30 00:25:26 upsmon1 kernel: [ 2816.843298] Indeed it is in host mode hprt0 = 00021501 Apr 30 00:25:26 upsmon1 kernel: [ 2817.031103] usb 1-1: new high-speed USB device number 2 using dwc_otg Apr 30 00:25:26 upsmon1 kernel: [ 2817.031257] Indeed it is in host mode hprt0 = 00001101 Apr 30 00:25:26 upsmon1 kernel: [ 2817.239632] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 Apr 30 00:25:26 upsmon1 kernel: [ 2817.239677] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Apr 30 00:25:26 upsmon1 kernel: [ 2817.239692] usb 1-1: Product: USB 2.0 Hub Apr 30 00:25:26 upsmon1 kernel: [ 2817.240603] hub 1-1:1.0: USB hub found Apr 30 00:25:26 upsmon1 kernel: [ 2817.240753] hub 1-1:1.0: 4 ports detected Apr 30 00:25:27 upsmon1 kernel: [ 2817.631088] usb 1-1.1: new high-speed USB device number 3 using dwc_otg Apr 30 00:25:27 upsmon1 kernel: [ 2817.832253] usb 1-1.1: New USB device found, idVendor=1d6b, idProduct=0044, bcdDevice= 0.40 Apr 30 00:25:27 upsmon1 kernel: [ 2817.832281] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 30 00:25:27 upsmon1 kernel: [ 2817.832296] usb 1-1.1: Product: JetKVM USB Emulation Device Apr 30 00:25:27 upsmon1 kernel: [ 2817.832309] usb 1-1.1: Manufacturer: JetKVM Apr 30 00:25:27 upsmon1 kernel: [ 2817.832322] usb 1-1.1: SerialNumber: ################ Apr 30 00:25:27 upsmon1 kernel: [ 2817.837018] input: JetKVM JetKVM USB Emulation Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:1D6B:0044.0001/input/input1 Apr 30 00:25:27 upsmon1 kernel: [ 2817.896315] hid-generic 0003:1D6B:0044.0001: input,hidraw0: USB HID v1.01 Keyboard [JetKVM JetKVM USB Emulation Device] on usb-3f980000.usb-1.1/input0 Apr 30 00:25:27 upsmon1 kernel: [ 2817.900071] input: JetKVM JetKVM USB Emulation Device as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1:1.1/0003:1D6B:0044.0002/input/input2 Apr 30 00:25:27 upsmon1 kernel: [ 2817.900752] hid-generic 0003:1D6B:0044.0002: input,hidraw1: USB HID v1.01 Mouse [JetKVM JetKVM USB Emulation Device] on usb-3f980000.usb-1.1/input1 Apr 30 00:25:27 upsmon1 kernel: [ 2817.901778] usb-storage 1-1.1:1.2: USB Mass Storage device detected Apr 30 00:25:27 upsmon1 kernel: [ 2817.902764] scsi host0: usb-storage 1-1.1:1.2 Apr 30 00:25:27 upsmon1 mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1" Apr 30 00:25:27 upsmon1 mtp-probe: bus: 1, device: 3 was not an MTP device Apr 30 00:25:27 upsmon1 kernel: [ 2818.103137] usb 1-1.3: new full-speed USB device number 4 using dwc_otg Apr 30 00:25:28 upsmon1 kernel: [ 2818.329090] usb 1-1.3: New USB device found, idVendor=0764, idProduct=0601, bcdDevice= 2.00 Apr 30 00:25:28 upsmon1 kernel: [ 2818.329120] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2 Apr 30 00:25:28 upsmon1 kernel: [ 2818.329135] usb 1-1.3: Product: CP1500PFCLCDa Apr 30 00:25:28 upsmon1 kernel: [ 2818.329148] usb 1-1.3: Manufacturer: CPS Apr 30 00:25:28 upsmon1 kernel: [ 2818.329161] usb 1-1.3: SerialNumber: CXXNY####### Apr 30 00:25:28 upsmon1 kernel: [ 2818.349125] hid-generic 0003:0764:0601.0003: hiddev96,hidraw2: USB HID v1.10 Device [CPS CP1500PFCLCDa] on usb-3f980000.usb-1.3/input0 Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1" Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 3 was not an MTP device Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3" Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 4 was not an MTP device Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3" Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 4 was not an MTP device Apr 30 00:25:28 upsmon1 kernel: [ 2818.531112] usb 1-1.4: new high-speed USB device number 5 using dwc_otg Apr 30 00:25:28 upsmon1 kernel: [ 2818.732400] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=8152, bcdDevice=20.00 Apr 30 00:25:28 upsmon1 kernel: [ 2818.732448] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 30 00:25:28 upsmon1 kernel: [ 2818.732464] usb 1-1.4: Product: USB 10/100 LAN Apr 30 00:25:28 upsmon1 kernel: [ 2818.732477] usb 1-1.4: Manufacturer: Realtek Apr 30 00:25:28 upsmon1 kernel: [ 2818.732490] usb 1-1.4: SerialNumber: 00E04C360113 Apr 30 00:25:28 upsmon1 kernel: [ 2818.911146] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg Apr 30 00:25:28 upsmon1 kernel: [ 2818.919827] scsi 0:0:0:0: CD-ROM JetKVM V irtual Media PQ: 0 ANSI: 2 Apr 30 00:25:28 upsmon1 kernel: [ 2818.951491] scsi 0:0:0:0: Attached scsi generic sg0 type 5 Apr 30 00:25:28 upsmon1 kernel: [ 2818.969931] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:25:28 upsmon1 kernel: [ 2819.075793] sr 0:0:0:0: [sr0] scsi-1 drive Apr 30 00:25:28 upsmon1 kernel: [ 2819.075823] cdrom: Uniform CD-ROM driver Revision: 3.20 Apr 30 00:25:28 upsmon1 kernel: [ 2819.141298] r8152 1-1.4:1.0: skip request firmware Apr 30 00:25:28 upsmon1 kernel: [ 2819.172665] r8152 1-1.4:1.0 eth0: v1.12.13 Apr 30 00:25:28 upsmon1 mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4" Apr 30 00:25:28 upsmon1 mtp-probe: bus: 1, device: 5 was not an MTP device Apr 30 00:25:28 upsmon1 kernel: [ 2819.249556] usbcore: registered new interface driver cdc_ether Apr 30 00:25:29 upsmon1 mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4" Apr 30 00:25:29 upsmon1 mtp-probe: bus: 1, device: 5 was not an MTP device Apr 30 00:25:29 upsmon1 kernel: [ 2819.338984] r8152 1-1.4:1.0 enx00e04c360113: renamed from eth0 Apr 30 00:26:30 upsmon1 kernel: [ 2880.703282] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:26:30 upsmon1 kernel: [ 2881.011622] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:27:31 upsmon1 kernel: [ 2942.135453] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:27:32 upsmon1 kernel: [ 2942.443908] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:28:33 upsmon1 kernel: [ 3003.583547] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:28:33 upsmon1 kernel: [ 3003.889276] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:29:34 upsmon1 kernel: [ 3065.015727] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:29:35 upsmon1 kernel: [ 3065.325049] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:30:36 upsmon1 kernel: [ 3126.455841] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:30:36 upsmon1 kernel: [ 3126.767305] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:31:37 upsmon1 kernel: [ 3187.899965] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:31:37 upsmon1 kernel: [ 3188.209530] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:32:41 upsmon1 kernel: [ 3251.384075] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:32:41 upsmon1 kernel: [ 3251.695140] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:33:42 upsmon1 kernel: [ 3312.824187] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:33:42 upsmon1 kernel: [ 3313.134063] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:34:44 upsmon1 kernel: [ 3374.264277] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg Apr 30 00:34:44 upsmon1 kernel: [ 3374.572938] sr 0:0:0:0: Power-on or device reset occurred Apr 30 00:35:45 upsmon1 kernel: [ 3435.712349] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg ### ... After a couple JetKVM reboots... ... ### May 1 21:10:59 upsmon1 kernel: [163950.427050] sr 0:0:0:0: Power-on or device reset occurred May 1 21:12:00 upsmon1 kernel: [164011.552905] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:12:01 upsmon1 kernel: [164011.862487] sr 0:0:0:0: Power-on or device reset occurred May 1 21:13:02 upsmon1 kernel: [164072.989118] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:13:02 upsmon1 kernel: [164073.298069] sr 0:0:0:0: Power-on or device reset occurred May 1 21:14:03 upsmon1 kernel: [164134.437288] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:14:04 upsmon1 kernel: [164134.639502] sr 0:0:0:0: Power-on or device reset occurred May 1 21:15:05 upsmon1 kernel: [164195.877526] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:15:05 upsmon1 kernel: [164196.185915] sr 0:0:0:0: Power-on or device reset occurred May 1 21:16:06 upsmon1 kernel: [164257.317707] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:16:07 upsmon1 kernel: [164257.624972] sr 0:0:0:0: Power-on or device reset occurred May 1 21:17:08 upsmon1 kernel: [164318.757923] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:17:08 upsmon1 kernel: [164319.067005] sr 0:0:0:0: Power-on or device reset occurred May 1 21:18:09 upsmon1 kernel: [164380.194153] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:18:09 upsmon1 kernel: [164380.502586] sr 0:0:0:0: Power-on or device reset occurred May 1 21:19:11 upsmon1 kernel: [164441.630352] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:19:11 upsmon1 kernel: [164441.938090] sr 0:0:0:0: Power-on or device reset occurred May 1 21:20:14 upsmon1 kernel: [164505.130588] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:20:14 upsmon1 kernel: [164505.440291] sr 0:0:0:0: Power-on or device reset occurred May 1 21:21:18 upsmon1 kernel: [164568.614764] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:21:18 upsmon1 kernel: [164568.922483] sr 0:0:0:0: Power-on or device reset occurred May 1 21:22:19 upsmon1 kernel: [164630.042994] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:22:19 upsmon1 kernel: [164630.351398] sr 0:0:0:0: Power-on or device reset occurred May 1 21:23:20 upsmon1 kernel: [164691.495168] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:23:21 upsmon1 kernel: [164691.803694] sr 0:0:0:0: Power-on or device reset occurred May 1 21:24:22 upsmon1 kernel: [164752.927365] usb 1-1.1: reset high-speed USB device number 6 using dwc_otg May 1 21:24:22 upsmon1 kernel: [164753.235918] sr 0:0:0:0: Power-on or device reset occurred ``` Any thoughts? Suggestions? Thanks in advance!
deekerman commented 2026-02-20 08:21:24 -05:00
Author
Owner
Copy link

@kotoko commented on GitHub (May 13, 2025):

I would suggest downloading latest ubuntu ISO and running ubuntu livecd on some spare laptop. Connect HDMI and USB from jetkvm to laptop and see if there is same problem. If there is, then maybe a cable or jetkvm (or power supply?) is a problem. If there is not, then maybe raspberry pi is a problem.

As fun fact - there are cheap devices that show how much power goes through usb-c cable. There are mostly to test what power delivery standard negotiates. If you suspect that maybe jetkvm does not get enough power you could consider buying something like that to verify. Example:
https://pl.aliexpress.com/item/1005006346907310.html?gatewayAdapt=glo2pol

@kotoko commented on GitHub (May 13, 2025): I would suggest downloading latest ubuntu ISO and running ubuntu livecd on some spare laptop. Connect HDMI and USB from jetkvm to laptop and see if there is same problem. If there is, then maybe a cable or jetkvm (or power supply?) is a problem. If there is not, then maybe raspberry pi is a problem. As fun fact - there are cheap devices that show how much power goes through usb-c cable. There are mostly to test what power delivery standard negotiates. If you suspect that maybe jetkvm does not get enough power you could consider buying something like that to verify. Example: https://pl.aliexpress.com/item/1005006346907310.html?gatewayAdapt=glo2pol
deekerman commented 2026-02-20 08:21:24 -05:00
Author
Owner
Copy link

@MrWoodward42 commented on GitHub (Jun 19, 2025):

@rtw819 I had a similar situation: JetKVM connected to Raspberry Pi 1B+ running Rasbian 10. Here's my assessment and workaround for the problem:

Near as I can tell, the JetKVM has the ability to emulate a mounted CD-ROM (or ISO) as a USB device. There is no ISO file selected, but the USB Mass Storage device feature is turned-on by default. Unfortunately, this feature appears to be malfunctioning with your RPiZero and my RPi1B+.

As a workaround, you can disable this feature by going into your JetKVM panel, click the [⚙ Settings] button, pick the [Hardware] menu option, and under the USB Device section there is a drop-down called Classes: Pick the Custom option and uncheck the Enable USB Mass Storage option and click [Update USB Classes] button to save your new settings.

This should get rid of the re-occurring error as it disables the USB Mass Storage feature of the JetKVM (which really is only needed for remotely bootstrapping a computer that has no OS.)

@MrWoodward42 commented on GitHub (Jun 19, 2025): @rtw819 I had a similar situation: JetKVM connected to Raspberry Pi 1B+ running Rasbian 10. Here's my assessment and workaround for the problem: Near as I can tell, the JetKVM has the ability to emulate a mounted CD-ROM (or ISO) as a USB device. There is no ISO file selected, but the USB Mass Storage device feature is turned-on by default. Unfortunately, this feature appears to be malfunctioning with your RPiZero and my RPi1B+. As a workaround, you can disable this feature by going into your JetKVM panel, click the `[⚙ Settings]` button, pick the `[Hardware]` menu option, and under the `USB Device` section there is a drop-down called `Classes`: Pick the `Custom` option and **uncheck** the `Enable USB Mass Storage` option and click `[Update USB Classes]` button to save your new settings. This should get rid of the re-occurring error as it disables the USB Mass Storage feature of the JetKVM (which really is only needed for remotely bootstrapping a computer that has no OS.)
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#234
No description provided.