KOA2 KOA2 USB mount

[j.p.s]

Prior to KOA2, my various kindles between K2 and KV show up as a drive with a single partition. The KOA2 shows up as an unparitioned drive. Don't know if that is why the KOA2 does not show up for Calibre as I don't use Calibre to move files around.

[knc1]

Originally Posted by j.p.s

Prior to KOA2, my various kindles between K2 and KV show up as a drive with a single partition. The KOA2 shows up as an unparitioned drive. Don't know if that is why the KOA2 does not show up for Calibre as I don't use Calibre to move files around.

That is wrong, re-boot it.
If the start-up code doesn't fix it, return it as defective.

(The partitioning and formatting has special options set that only after-market Windows tools can get correct.)

[j.p.s]

Originally Posted by knc1

That is wrong, re-boot it.
If the start-up code doesn't fix it, return it as defective.

(The partitioning and formatting has special options set that only after-market Windows tools can get correct.)

I'll give that a go, but why did it have a documents directory that I was able to put books in and read?

It was turned on and set up with no access to cellular or wifi and the first thing I did after setup was put it in airplane mode, if that matters.

[knc1]

Originally Posted by j.p.s

I'll give that a go, but why did it have a documents directory that I was able to put books in and read?

It was turned on and set up with no access to cellular or wifi and the first thing I did after setup was put it in airplane mode, if that matters.

Well, if it had a directory on it, then it wasn't as you described.
I was assuming your description was correct.

[j.p.s]

Originally Posted by knc1

Well, if it had a directory on it, then it wasn't as you described.
I was assuming your description was correct.

Maybe I am not using correct terminology. Below are the dmesg outputs after connection to KOA2 oand KV respectively. The former is consistant with my experience when an unpartitioned storage device is attached, the latter when a device that has been partitioned device has been attached. Of course, the device or a partition has to be formatted in order to be mounted. Both my KOA2 and KV can be mounted, the KOA2 mounts without specifying a partition, e.g. mount -t auto /dev/sdb /media/usb and files show up.

KOA2 connected to laptop USB:

dmesg | tail
[8892124.411746] usb 3-1: Product: Internal Storage
[8892124.411747] usb 3-1: SerialNumber: G000S1xxxxxxxxxx
[8892124.412476] usb-storage 3-1:1.0: USB Mass Storage device detected
[8892124.412617] scsi24 : usb-storage 3-1:1.0
[8892125.410382] scsi 24:0:0:0: Direct-Access Kindle Internal Storage 0401 PQ: 0 ANSI: 2
[8892125.410723] sd 24:0:0:0: Attached scsi generic sg2 type 0
[8892125.411931] sd 24:0:0:0: [sdb] Attached SCSI removable disk
[8892127.626910] sd 24:0:0:0: [sdb] 57280429 512-byte logical blocks: (29.3 GB/27.3 GiB)
[8892127.839181] sd 24:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[8892128.080591] sdb:

KV connected to laptop USB:

dmesg | tail
[8892412.531631] usb 3-1: Manufacturer: Amazon
[8892412.531633] usb 3-1: SerialNumber: B05409xxxxxxxxxx
[8892412.534529] usb-storage 3-1:1.0: USB Mass Storage device detected
[8892412.534624] scsi25 : usb-storage 3-1:1.0
[8892413.533516] scsi 25:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
[8892413.533724] sd 25:0:0:0: Attached scsi generic sg2 type 0
[8892413.542462] sd 25:0:0:0: [sdb] Attached SCSI removable disk
[8892415.793764] sd 25:0:0:0: [sdb] 6385664 512-byte logical blocks: (3.26 GB/3.04 GiB)
[8892416.010499] sd 25:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[8892416.231544] sdb: sdb1

[knc1]

What OS on your laptop?

If that is Linux -
Then it just looks like your missing a u-dev rule.

For each case in your last post, do:

 
lsusb

and post.

I am betting that you will find that the KOA has a new (newer than your udev database) vendor/device pair.

(And most likely that is because of the partial support for Android. I.E: So external USB detection can tell the difference between Amazon/Linux and Google/Linux.)

PS: If you use the code-/code tag pair, the mono-spaced stuff will hold together much better.

[j.p.s]

Originally Posted by knc1

What OS on your laptop?

If that is Linux -
Then it just looks like your missing a u-dev rule.

For each case in your last post, do:

 
lsusb

and post.

I am betting that you will find that the KOA has a new (newer than your udev database) vendor/device pair.

(And most likely that is because of the partial support for Android. I.E: So external USB detection can tell the difference between Amazon/Linux and Google/Linux.)

PS: If you use the code-/code tag pair, the mono-spaced stuff will hold together much better.

uname -a
Linux lcw530 3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/issue
Ubuntu 14.04.2 LTS \n \l

diff lsusbkv.txt lsusbkoa2.txt 
11c11
< Bus 003 Device 023: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
---
> Bus 003 Device 025: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite

Restarting KVOA2 did not change anything.

lsusb out attached.

[knc1]

So my guess was wrong.

What is missing on the KOA2 dmesg case is where file system discovery is run by the kernel.
It does the hardware discovery, just not the file system discovery.
I don't know why your Linux install does not do that for the KOA2.
But that is most likely something to do with Ubuntu's kernel hardware discovery, not the Kindle.
The place to find out about it would be on one of the Ubuntu user forums.

But the only thing lacking is the auto-mount feature of your Ubuntu GUI for the KOA2.
If you can still mount it yourself, then use it like that until somebody finds the answer.

If they can give you an answer, then please share it with us here.

[j.p.s]

Originally Posted by knc1

So my guess was wrong.

What is missing on the KOA2 dmesg case is where file system discovery is run by the kernel.
It does the hardware discovery, just not the file system discovery.
I don't know why your Linux install does not do that for the KOA2.
But that is most likely something to do with Ubuntu's kernel hardware discovery, not the Kindle.
The place to find out about it would be on one of the Ubuntu user forums.

But the only thing lacking is the auto-mount feature of your Ubuntu GUI for the KOA2.
If you can still mount it yourself, then use it like that until somebody finds the answer.

If they can give you an answer, then please share it with us here.

The same thing happens on my Debian Jessie workstation, so it is not an ubuntu thing.

I never enable automount when I set up a system, and disable it when I encounter it, if possible.