Veho Quinque MP5 player USB disk read capacity failed log messages

[PicKit2]

This Veho Quinque has 2 USB mass storage devices - the internal 4Gb and additional 2Gb on microSD card. May be its confused about two devices appearing. READ CAPACITY failed message will appear whether the 2Gb card is inserted on not. Can work OK on other platform - with both storage devices being recognised and read/write file transfer is successfull to both. Tried on Ubuntu 7.10 and 8.04. Not tried on 8.10. The messages below are from 7.10.
I was expecting the devices to be mounted as two mass storage drives.
Nothing happened when the device is plugged in.

Dec 16 19:03:11 desk kernel: [ 113.884000] usb 2-3: new high speed USB device using ehci_hcd and address 2
Dec 16 19:03:11 desk kernel: [ 114.016000] usb 2-3: configuration #1 chosen from 1 choice
Dec 16 19:03:11 desk kernel: [ 114.100000] usbcore: registered new interface driver libusual
Dec 16 19:03:11 desk kernel: [ 114.144000] Initializing USB Mass Storage driver...
Dec 16 19:03:11 desk kernel: [ 114.144000] scsi6 : SCSI emulation for USB Mass Storage devices
Dec 16 19:03:11 desk kernel: [ 114.144000] usbcore: registered new interface driver usb-storage
Dec 16 19:03:11 desk kernel: [ 114.144000] USB Mass Storage support registered.
Dec 16 19:03:16 desk kernel: [ 119.144000] scsi 6:0:0:0: Direct-Access RockChip USBDISK User 1.00 PQ: 0 ANSI: 0
Dec 16 19:03:16 desk kernel: [ 119.144000] scsi 6:0:0:1: Direct-Access RockChip USBDISK SD 1.00 PQ: 0 ANSI: 0
Dec 16 19:03:16 desk kernel: [ 119.148000] sd 6:0:0:0: [sdc] 7860224 512-byte hardware sectors (4024 MB)
Dec 16 19:03:16 desk kernel: [ 119.264000] usb 2-3: reset high speed USB device using ehci_hcd and address 2
Dec 16 19:03:17 desk kernel: [ 119.952000] usb 2-3: USB disconnect, address 2
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Write Protect is off
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] READ CAPACITY failed
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Sense not available.
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Write Protect is off
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] READ CAPACITY failed
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Sense not available.
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Write Protect is off
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: [sdc] Attached SCSI removable disk
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:0: Attached scsi generic sg2 type 0
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:1: [sdd] READ CAPACITY failed
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:1: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Dec 16 19:03:17 desk kernel: [ 119.952000] sd 6:0:0:1: [sdd] Sense not available.
Dec 16 19:03:17 desk kernel: [ 119.956000] sd 6:0:0:1: [sdd] Write Protect is off
Dec 16 19:03:17 desk kernel: [ 119.956000] sd 6:0:0:1: [sdd] Attached SCSI removable disk
Dec 16 19:03:17 desk kernel: [ 119.956000] sd 6:0:0:1: Attached scsi generic sg3 type 0

[IC Raibow (icrbow)]

This is somewhat old issue: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/58349

[Michele Mangili (mangilimic)]

Hello PicKit2!

Could you please tell us if this report is related to bug #58349 ? Thank you.

[kernel-janitor (kernel-janitor)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]