Unfortunately, that didn't seem to work either. It does look like the Kindle is on usb1, but the ping still did not go through.
I tried rebooting the Pi, and then when I plugged the kindle in, "sudo dmesg -H" said something peculiar at the end:
Code:
[Jun26 20:41] usb usb1-port1: disabled by hub (EMI?), re-enabling...
[ +0.000061] usb 1-1: USB disconnect, device number 2
[ +0.007791] cdc_subset 1-1:1.1 usb1: unregister 'cdc_subset' usb-20980000.usb-1, Linux Device
[ +1.531992] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ +1.310018] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ +0.000166] usb usb1-port1: attempt power cycle
At this stage, trying to ifconfig usb1 returned
Code:
SIOCSIFADDR: No such device
usb1: ERROR while getting interface flags: No such device
and pinging it on usb0 didn't work either. I tried a couple of other cables too and nothing worked, and neither did rebooting the Kindle.
However, I rebooted the Pi once more and things are behaving differently:
Code:
[Jun26 20:54] usb 1-1: new high-speed USB device number 2 using dwc2
[ +0.265112] usb 1-1: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 3.25
[ +0.000046] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0.000022] usb 1-1: Product: RNDIS/Ethernet Gadget
[ +0.000021] usb 1-1: Manufacturer: Linux 2.6.31-rt11-lab126 with fsl-usb2-udc
[ +0.255479] cdc_ether 1-1:1.0 usb1: register 'cdc_ether' at usb-20980000.usb-1, CDC Ethernet Device, ee:49:00:00:00:00
[ +0.001743] usbcore: registered new interface driver cdc_ether
[ +0.012911] usbcore: registered new interface driver cdc_subset
[ +0.855560] IPv6: ADDRCONF(NETDEV_CHANGE): usb1: link becomes ready
Now, when I try to ssh into the Kindle (on usb1) instead of throwing "No route to host" it just hangs with no output and without returning to shell until I break. Ping won't show "Destination Host Unreachable" but it's not receiving any packets either.
Code:
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
--- 192.168.15.244 ping statistics ---
51 packets transmitted, 0 received, 100% packet loss, time 1041ms
I wonder why it's acting so inconsistent now...?