> 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
>
> On Thu, Feb 14, 2013 at 10:47 PM, Ronald <ronald645@xxxxxxxxx> wrote:
>>> This e-mail is a follow-up as requested in this bug[1]. I will repost
>>> everything so far in this e-mail. Please CC me as I'm not subscribed
>>> to your list.
>>>
>>> We have acquired an e-reader which says: 'AV Autovision AV606'. I have
>>> confirmed with the distributer that it uses the usb-storage driver
>>> (not MTP). Did try that though, didn't work.
>>>
>>> Attached:
>>> [2] lsusb -v
>>> [3] kernel spew of v3.4 kernel the spawned sg[0-3] nodes all fail to mount
>>>
>>> Any direction, suggestion on how to proceed? I cannot provide more
>>> info as I don't know what to provide anymore. Please tell. Would like
>>> to use this e-reader with Linux. Otherwise an alternative OS is being
>>> preferred by it's daily users... :(
>>>
>>> I Would like to reassure you that I tested this with 3.8.0-rc7+ + the
>>> latest nouveau tree. These patches are not intrusive. I have v3.4
>>> kernel output here since I tried a liveCD (Gentoo based linux
>>> rescuecd). It's kernel seems to have more debug options enabled.
>>>
>>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=53891
>>> [2]: Attachment 'E-reader lsusb output.txt'
>>> [3]: Attachment 'E-reader dmesg output.txt'
>>
>> I attached a new document[1] with verbose USB logging while connecting
>> the E-reader. This is with today's kernel git + nouveau git of today
>> (v3.8-rc7+). It's pretty big btw...
>>
>> I also enabled verbose SCSI logging, but didn't see some of that come
>> back in the logs.
>
>
>
> --
> Matthew Dharm
> Maintainer, USB Mass Storage driver for Linux
--
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
