I've just become the "proud" owner of a Ruizu brand MP3 player.
It mounts as a storage device on Linux (Linux Mint 22.2) just fine, and I can copy files over to it:
However I think the device itself is in some way behaving rudely. If I just plug it in to a FreeBSD 14.3 system (I've tried two), the device itself sits there resetting every minute or so, with the following logs:
I'm tempted to just return the thing for a refund, but was wondering if anyone else has experienced this, and/or is more experienced than me at debugging USB issues? It looks like it's not returning descriptors etc. when queried. But why, then, should this work fine on Linux?
It mounts as a storage device on Linux (Linux Mint 22.2) just fine, and I can copy files over to it:
Code:
[ 791.762244] usb 5-1: new high-speed USB device number 3 using xhci_hcd
[ 791.893847] usb 5-1: New USB device found, idVendor=10d6, idProduct=1101, bcdDevice= 1.00
[ 791.893857] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 791.893859] usb 5-1: Product: HS USB FlashDisk
[ 791.893861] usb 5-1: Manufacturer: ACTIONS
[ 791.893864] usb 5-1: SerialNumber: CA4512482ADF0FEEEE
[ 791.973293] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 791.973521] scsi host0: usb-storage 5-1:1.0
[ 791.973651] usbcore: registered new interface driver usb-storage
[ 793.003258] scsi 0:0:0:0: Direct-Access ACTIONS USB DISK FOB 2.0 0 PQ: 0 ANSI: 0 CCS
[ 793.003855] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 793.004993] sd 0:0:0:0: [sda] 65388544 1024-byte logical blocks: (67.0 GB/62.4 GiB)
[ 793.005128] sd 0:0:0:0: [sda] Write Protect is off
[ 793.005131] sd 0:0:0:0: [sda] Mode Sense: 00 c0 00 00
[ 793.005248] sd 0:0:0:0: [sda] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 793.007876] sda:
[ 793.008014] sd 0:0:0:0: [sda] Attached SCSI removable disk
However I think the device itself is in some way behaving rudely. If I just plug it in to a FreeBSD 14.3 system (I've tried two), the device itself sits there resetting every minute or so, with the following logs:
Code:
usb_msc_auto_quirk: UQ_MSC_NO_SYNC_CACHE set for USB mass storage device ACTIONS HS USB FlashDisk (0x10d6:0x1101)
usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_ALLOW set for USB mass storage device ACTIONS HS USB FlashDisk (0x10d6:0x1101)
usb_msc_auto_quirk: UQ_MSC_NO_TEST_UNIT_READY set for USB mass storage device ACTIONS HS USB FlashDisk (0x10d6:0x1101)
usb_msc_auto_quirk: UQ_MSC_NO_START_STOP set for USB mass storage device ACTIONS HS USB FlashDisk (0x10d6:0x1101)
usbd_req_re_enumerate: addr=1, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_SHORT_XFER
usbd_req_re_enumerate: addr=1, set address failed! (USB_ERR_IOERROR, ignored)
usbd_setup_device_desc: getting device descriptor at addr 1 failed, USB_ERR_IOERROR
usb_alloc_device: Failure selecting configuration index 0:USB_ERR_IOERROR, port 1, addr 1 (ignored)
ugen2.2: <ACTIONS HS USB FlashDisk> at usbus2
ugen2.2: <ACTIONS HS USB FlashDisk> at usbus2 (disconnected)
I'm tempted to just return the thing for a refund, but was wondering if anyone else has experienced this, and/or is more experienced than me at debugging USB issues? It looks like it's not returning descriptors etc. when queried. But why, then, should this work fine on Linux?
