On Wed, Nov 30, 2011 at 2:14 PM, Renaud (Ron) Olgiati <renaud@olgiati-in-paraguay.org> wrote:
On Wednesday 30 Nov 2011 09:39 my mailbox was graced by a message from
Alejandro López who wrote:

> > Since last night the automounting through USB of a Kindle on my desktop
> > (mageia 1/KDE) mounts it as Read Only, making it impossible to load books
> > from the computer.

 > This usually happens when the filesystem is corrupted. Try a fsck on it.

root@localhost:/home/ron # fsck /dev/sdc1
Reclaimed 88 unused clusters (720896 bytes).
Free cluster summary wrong (352493 vs. really 352666)
1) Correct
2) Don't correct
? 1
Leaving file system unchanged.
/dev/sdc1: 481 files, 47608/400274 clusters

 
Why did fsck leave the file system unchanged if you said 1 (Correct)? Did it somehow misunderstood what you wanted? You could maybe try with the option -p to automatically fix any problem it finds, and avoid the question. Unluckily I have no other idea.

Alejandro.
 
root@localhost:/home/ron # dmesg
2:1:1: usb_set_interface failed
usb 1-4.2: new high speed USB device using ehci_hcd and address 25
usb 1-4.2: New USB device found, idVendor=1949, idProduct=0004
usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4.2: Product: Amazon Kindle
usb 1-4.2: Manufacturer: Amazon
usb 1-4.2: SerialNumber: B008A0A012250P0E
scsi18 : usb-storage 1-4.2:1.0
2:2:1: usb_set_interface failed
scsi 18:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
sd 18:0:0:0: Attached scsi generic sg3 type 0
sd 18:0:0:0: [sdc] 6410688 512-byte logical blocks: (3.28 GB/3.05 GiB)
sd 18:0:0:0: [sdc] Write Protect is off
sd 18:0:0:0: [sdc] Mode Sense: 0f 00 00 00
sd 18:0:0:0: [sdc] Assuming drive cache: write through
sd 18:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 18:0:0:0: [sdc] Assuming drive cache: write through
sd 18:0:0:0: [sdc] Attached SCSI removable disk
2:1:1: usb_set_interface failed
2:2:1: usb_set_interface failed


Do you have any old log file to verify whether this "usb_set_interface failed" message also happening when your kindle was correctly mounted in read-write mode?