View Single Post
Old 12-22-2019, 12:53 PM   #9
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,814
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by Ricky D'Angelo View Post
Running the command, sudo cat /var/log/syslog.1 | grep usb, in ubuntu terminal gave me the following usb data log files.


No idea what that means but my kindle still doesn't connect although the battery bar indicates it's charging. I started up calibre and the kindle isn't recognized either.

I agree that the workaround is to send files to the kindle wirelessly or via direct download from the paperwhite experimental browser.
The best approach in linux is to use the dmesg command, which may or may not require sudo in front. I just did the following with my K4NT and an older laptop running an older ubuntu:
Code:
#comment initial baseline dmesg output
dmesg > dmesg_init.txt
#comment connect kindle with USB then get next dmesg
dmesg > dmesg_conn.txt
#comment disconnect kindle from USB then get next dmesg
dmesg > dmesg_disc.txt
#comment get new part after connect
diff dmesg_init.txt dmesg_conn.txt
#comment get new part after disconnect
diff dmesg_conn.txt dmesg_disc.txt
Ignore diff output lines starting with "<"

New part after connect:
Spoiler:

2165a2152,2171
> [14087610.879315] usb 3-1: new high-speed USB device number 14 using xhci_hcd
> [14087615.877512] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
> [14087616.081451] usb 3-1: Device not responding to set address.
> [14087616.285365] usb 3-1: device not accepting address 14, error -71
> [14087616.581370] usb 3-1: new high-speed USB device number 16 using xhci_hcd
> [14087616.612426] usb 3-1: New USB device found, idVendor=1949, idProduct=0004
> [14087616.612434] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [14087616.612438] usb 3-1: Product: Amazon Kindle
> [14087616.612441] usb 3-1: Manufacturer: Amazon
> [14087616.612444] usb 3-1: SerialNumber: B00E150xxxxxxxxx
> [14087616.621866] usb-storage 3-1:1.0: USB Mass Storage device detected
> [14087616.622091] scsi38 : usb-storage 3-1:1.0
> [14087617.623137] scsi 38:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
> [14087617.623637] sd 38:0:0:0: Attached scsi generic sg2 type 0
> [14087617.628972] sd 38:0:0:0: [sdb] 2854912 512-byte logical blocks: (1.46 GB/1.36 GiB)
> [14087617.740109] sd 38:0:0:0: [sdb] Write Protect is off
> [14087617.740117] sd 38:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> [14087617.849914] sd 38:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [14087618.071243] sdb: sdb1
> [14087618.299928] sd 38:0:0:0: [sdb] Attached SCSI removable disk

So Kindle detected as USB Mass Storage device as sdb with
single partition sdb1

New part after disconnect.
Spoiler:

2171a2170,2173
> [14087669.881824] usb 3-1: USB disconnect, device number 16
> [14087669.883137] sd 38:0:0:0: [sdb] Synchronizing SCSI cache
> [14087669.883266] sd 38:0:0:0: [sdb]
> [14087669.883272] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

Last edited by j.p.s; 12-22-2019 at 01:01 PM.
j.p.s is offline   Reply With Quote