View Single Post
Old 12-22-2019, 06:42 PM   #10
Ricky D'Angelo
Fanatic
Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.Ricky D'Angelo ought to be getting tired of karma fortunes by now.
 
Ricky D'Angelo's Avatar
 
Posts: 537
Karma: 2495066
Join Date: Feb 2013
Location: Latin America
Device: Sony PRS-T1, PRS-T-2, PRS 350, PRS 950; Kobo Mini; Kindle PW3, Fire 10
Thumbs up

Quote:
Originally Posted by j.p.s View Post
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
Funny how one thing leads to another. I ran the command and although nothing connected I heard the dinging sound. Although I already swapped different cables I decided to swap out one more cable and it connected. Turns out the previous cables were charging cables. I never paid attention to these cables before but upon closer inspection there is a difference between a charging cable and the connecting cable. So, I went ahead and wrapped a piece of white tape around the charging cable to tell it apart from the connecting cable. Visually, it is also easier to tell apart because the usb section of the charging only cable is "thicker" than the narrower connecting cable. In the pic below the charging cable is connected to the amazon charger next to the "skinny" connecting cable. Running the linux command gave the following data:
Spoiler:
2673.574268] usb 2-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 2673.574270] usb 2-1.1: Product: xxxx
[ 2673.574272] usb 2-1.1: Manufacturer: Amazon
[ 2673.574273] usb 2-1.1: SerialNumber: xxxxxxxxxxxxxxxx
[ 2678.737309] usb 2-1.1: reset high-speed USB device number 9 using ehci-pci
[ 2678.933237] usb 2-1.1: reset high-speed USB device number 9 using ehci-pci
[ 2783.323716] usb 2-1.1: USB disconnect, device number 9
[ 2787.647141] usb 2-1.1: new high-speed USB device number 10 using ehci-pci
[ 2787.755989] usb 2-1.1: New USB device found, idVendor=1949, idProduct=0222, bcdDevice=ff.ff
[ 2787.755995] usb 2-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 2787.755999] usb 2-1.1: Product: xxxx
[ 2787.756002] usb 2-1.1: Manufacturer: Amazon
[ 2787.756006] usb 2-1.1: SerialNumber: xxxxxxxxxxxxxxxx

Attached Thumbnails
Click image for larger version

Name:	charger.jpg
Views:	196
Size:	22.5 KB
ID:	175817  

Last edited by Ricky D'Angelo; 12-22-2019 at 08:59 PM.
Ricky D'Angelo is offline   Reply With Quote