Closed chelmuth closed 6 months ago
Based on the findings in #5041, the following lines in the Linux log look suspicious and hint UAS may be the cause of this issue too.
[Wed Aug 31 15:27:42 2022] usbcore: registered new interface driver usb-storage
[Wed Aug 31 15:27:42 2022] scsi host4: uas
[Wed Aug 31 15:27:42 2022] usbcore: registered new interface driver uas
Let's close this issue as duplicate of the more generic "usb: USB passthrough breaks UAS #5041".
The device
04e8:61f5
seems to be initialized correctly when plugged except the following string descriptor errors in the host driver.The USB storage driver successfully reads the first blocks of the device and, thus, the partition table is parsed correctly. Subsequent usage in Inspect and e2fsck also worked.
Further, if the device is passed to a Linux VM in VirtualBox, the guest fails to initialize the device. This stems from the fact, that the device is
USB_SPEED_SUPER_PLUS
, which is currently not supported in the USB session and qemu-usb as well. Clamping the speed toUSB_SPEED_SUPER
in repos/dde_linux/src/lib/lx_emul/usb.c did not suffice to make it work but resulted in other errors.