Let me see the entire set of messages that connecting the Kindle causes.
As in:
sudo dmesg -c
plug in Kindle
re-boot Kindle (with the cable plugged in for this test)
dmesg
Should look like this (without the re-boot in this case):
Code:
core2quad ~ $ dmesg
[563889.344015] usb 2-5: new high speed USB device number 21 using ehci_hcd
[563889.485245] scsi18 : usb-storage 2-5:1.0
[563890.485199] scsi 18:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
[563890.740273] sd 18:0:0:0: Attached scsi generic sg5 type 0
[563890.744449] sd 18:0:0:0: [sde] 2797568 512-byte logical blocks: (1.43 GB/1.33 GiB)
[563890.847343] sd 18:0:0:0: [sde] Write Protect is off
[563890.847349] sd 18:0:0:0: [sde] Mode Sense: 0f 00 00 00
[563890.957353] sd 18:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[563891.178413] sde: sde1
[563891.467408] sd 18:0:0:0: [sde] Attached SCSI removable disk
But let me see yours, including the re-boot.
If the USB storage does not appear momentarily (sometimes it does before it discovers the update file), this will require serial port access to fix.
If it does momentarily appear, then we may be able to force a way to fail the update process.