>> Ronald -- >> >> A quick review on the verbose log shows a few interesting things: >> >> 1) The device claims to use the USB Mass Storage Class, so it should >> work with usb-storage. > > My thoughts exactly. However, I did see some 'lsusb -v' outputs on the > libmtp mailing list that also carry these value's. So I wanted to > confirm that it was indeed not an MTP device. > >> >> 2) The device identifies itself to the SCSI layer as "rockchip rk28 >> sdk demo" -- a string like that is not very encouraging to me in terms >> of believing this is a released and fully-tested prodcut. > > Yes, that is what bothered me as well. However, this product is > shipped with one of national's greatest newspapers around (Volkskrant) > as part of a package deal. You get 20 books plus an e-reader with a > subscription for the newspaper that lasts 6 months (at a reduced > price). > > Above statement does not in any way make the product 'more released > and fully-tested' but it was indeed deliberately shipped in this > fashion. Googling for this rockchip rk28 also yields results related > to Android devices?? This thing runs Linux btw... > >> >> 3) The device should appear as /dev/sdb according to the logs > > It did, once. There were no partitions. Manual does not mention an > initial format and I don't want to brick it. It did come up with > another device /dev/sdc. The size really roughly corresponds to what > the manual mentions. However, it contains four (bogus?) partitions, > one of them mentioning Novell Netware or something like that. Please > note, this is with a v3.4 kernel. Looks like behaviour varies across > kernel versions. Don't think this counts as a regression though... > > Disk /dev/sdc: 3426 MB, 3426746368 bytes > 106 heads, 62 sectors/track, 1018 cylinders, total 6692864 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x6f20736b > > This doesn't look like a partition table > Probably you selected the wrong device. > > Device Boot Start End Blocks Id System > /dev/sdc1 ? 778135908 1919645538 570754815+ 72 Unknown > /dev/sdc2 ? 168689522 2104717761 968014120 65 Novell Netware 386 > /dev/sdc3 ? 1869881465 3805909656 968014096 79 Unknown > /dev/sdc4 ? 0 3637226495 1818613248 d Unknown > > Mounting them does not work, the /dev/sdc* nodes are never created: > > mount: special device /dev/sdc1 does not exist > mount: special device /dev/sdc2 does not exist > mount: special device /dev/sdc3 does not exist > mount: special device /dev/sdc4 does not exist > > Furthermore: > > mount: /dev/sg0 is not a block device > mount: /dev/sg1 is not a block device > mount: /dev/sg2 is not a block device > mount: /dev/sg3 is not a block device > > >> >> 4) Something in your system is polling the device, waiting for it to >> become "ready". HOWEVER, the device is continually answering with >> "Not Ready: Medium not present" > > It has a seperate slot for inclusion of an SD card. But it contains > 4GB internal memory. I'm sorry, I should have mentioned this before I > guess. > > Thanks for your quick look! > >> >> Matt >> Just want to mention that I ran this by my neighbours. Works fine under Windows XP SP3. Two drives appear when connecting. Only after confirming the connection I can open one of these leading me to the internal memory. It is installed has a 'Mass Storage Device'. -- 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
