On Tue, 8 May 2012, Jesse Feddema wrote: > Hi, > > My sister's Yarvik PMP400 MP4 player refuses to stay connected on any > kernel version and on any computer I try. The player is not broken and Actually it is -- or at least, buggy. > should not require special drivers, as it works with Windows 7 without > installation of third party software or drivers. Using kernel That's because Windows does not follow the USB mass storage protocol properly. > 3.4.0-rc6, here is some dmesg output illustrating the problem: > > ===== dmesg output ===== > [ 1764.765492] usb 2-1.1: new high-speed USB device number 5 using ehci_hcd > [ 1764.859858] scsi8 : usb-storage 2-1.1:1.0 > [ 1765.857389] scsi 8:0:0:0: Direct-Access Maxm Media Player > 4GB 1.00 PQ: 0 ANSI: 0 > [ 1765.858135] scsi 8:0:0:1: Direct-Access Maxm Media Player > 4GB 1.00 PQ: 0 ANSI: 0 > [ 1765.860585] sd 8:0:0:0: Attached scsi generic sg2 type 0 > [ 1765.861296] sd 8:0:0:1: Attached scsi generic sg3 type 0 > [ 1765.862402] sd 8:0:0:0: [sdb] 7774208 512-byte logical blocks: > (3.98 GB/3.70 GiB) > [ 1765.880965] usb 2-1.1: USB disconnect, device number 5 > [ 1765.887956] sd 8:0:0:0: [sdb] Write Protect is off > [ 1765.887967] sd 8:0:0:0: [sdb] Mode Sense: 03 00 00 00 > [ 1765.888008] sd 8:0:0:1: [sdc] Attached SCSI removable disk > [ 1765.888048] sd 8:0:0:0: [sdb] Asking for cache data failed > [ 1765.888059] sd 8:0:0:0: [sdb] Assuming drive cache: write through > [ 1765.888622] sd 8:0:0:0: [sdb] Attached SCSI removable disk > ===== end of dmesg output ===== > > As you can see, the device exposes two scsi disks. One of them is the > internal memory (4GB), the other I think is supposed to give access to > the MicroSD slot in the device. I have only tried connecting the > player without a MicroSD card inserted. Also, you can see that the > device disconnects just over a second after it is connected, and even > before sdb is properly initialized. It doesn't show up in lsusb after > this disconnect, and the screen of the device shows, after a brief > moment of displaying a "connected" icon, a "charging without being > connected" icon. > > I was able to obtain lsusb -vvv output by running the command during > the brief time the device is connected: Good, that helped. > Also, I captured usbmon output, which is available at > http://pastebin.com/ENUYujJy (I hope there isn't any noise in it, I'm > a little new at this). I'd be very grateful if you could help me find > a way to get this device to work with Linux :). Feel free to ask me > for additional (debugging) output. Your usbmon trace was very useful. It showed that the player has a nasty bug; it doesn't use the correct command tag in its responses. The patch below will tell the usb-storage driver to ignore the bug; hopefully it will solve your problem. If it doesn't, please post another usbmon trace. Alan Stern Index: usb-3.4/drivers/usb/storage/unusual_devs.h =================================================================== --- usb-3.4.orig/drivers/usb/storage/unusual_devs.h +++ usb-3.4/drivers/usb/storage/unusual_devs.h @@ -1885,6 +1885,13 @@ UNUSUAL_DEV( 0x1652, 0x6600, 0x0201, 0x USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_IGNORE_RESIDUE ), +/* Reported by Jesse Feddema <jdfeddema@xxxxxxxxx> */ +UNUSUAL_DEV( 0x177f, 0x0400, 0x0000, 0x0000, + "Yarvik", + "PMP400", + USB_SC_DEVICE, USB_PR_DEVICE, NULL, + US_FL_BULK_IGNORE_TAG ), + /* Reported by Hans de Goede <hdegoede@xxxxxxxxxx> * These Appotech controllers are found in Picture Frames, they provide a * (buggy) emulation of a cdrom drive which contains the windows software -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html