Walter Zambotti Posted 6 hours ago Posted 6 hours ago (edited) I have been trying to diagnose a QHYCCD camera problem on a N2 running INDI server. Everything appears to work fine but after several minutes the device fails to respond. The device is only supported by QHY on a true USB3 slot. Looking on other forums USB and cable stability are a common problem with these QHY devices so falling onto the wrong USB bus would definitely be a problem. However looking at lsusb I can see the device has dropped onto the wrong USB bus: $ lsusb Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:3217 Canon, Inc. Canon Digital Camera Bus 001 Device 008: ID 1618:0716 QHYCCD QHY715U3G20-20230106 Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] Bus 001 Device 004: ID 0483:5740 STMicroelectronics Virtual COM Port Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The QHYCCD is showing up on USB bus 1 (which I'm sure is the USB2 480M) Confirmed here by lsusb -ttv $ lsusb -ttv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 1: Dev 4, If 0, Class=Communications, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 1: Dev 4, If 1, Class=CDC Data, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter |__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M ID 1618:0716 |__ Port 2: Dev 2, If 0, Class=Imaging, Driver=usbfs, 480M ID 04a9:3217 Canon, Inc. I'm running the Armbian version of Ubuntu 22.04 with kernel 6.12.22 Linux odroidn2-1 6.12.22-current-meson64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux. Further : This only occurs if the USB3 device is connected during boot. If the same USB3 device is plugged in well after boot it is correctly detected as a HIGH speed USB device. I'm looking for any ideas on forcing this device to be detected as a high speed USB3 device during boot time. So I don;t have to keep remembering to unplug and plug it back in. Also posted in the Odroid and INDI forums. Walter Zambotti N2 - 22.04 Armbian xfce desktop N2+ - CoreElec KODI Edited 6 hours ago by Walter Zambotti 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.