As per steps above, I was actually booting Dwarf/Laptop, and then connecting cable… and it wasn’t working. Re-verified now, that letting Dwarf boot (USB cable disconnected), and then plugging in is not working here.
What I don’t really understand is how ping
works to 192.168.51.1
, and nmap can see the various open ports (22,80 and 8081), but pointing a browser to 192.168.51.1
doesn’t work, and neither does SSH-ing in via port 22…
Does the cdc
probe error logically explain that?
(Also, is there any easy place to share diffs (in the git diff sense) with yee? I’m diffing dmesg
output to just strip to the interesting parts - would be nice to easily share them?)
Full boot, then connect USB cable dmesg
output: Dwarf USB 1st Connect After Full Boot - Pastebin.com
Multiple-replugs without rebooting MOD: Dwarf USB Multi Replugs - Pastebin.com
On the full-boot, then connect dmesg output, notice this
+[ 2033.824517] cdc_subset: probe of 1-1:2.0 failed with error -22
+[ 2033.825805] cdc_subset 1-1:2.1 usb0: register 'cdc_subset' at usb-0000:00:14.0-1, Linux Device, d2:1a:ac:66:58:46
+[ 2033.825860] usbcore: registered new interface driver cdc_subset
bit in particular - the cdc probe error occurs, but it does register a new interface for cdc_subset
.
In the multi-replug case, it does this instead
+[ 2603.078512] cdc_subset: probe of 1-2:2.0 failed with error -22
+[ 2603.079979] rndis_host 1-2:2.0 usb0: register 'rndis_host' at usb-0000:00:14.0-2, RNDIS device, 3a:b4:a2:a4:af:5c
which has the cdc_subset
error, but then does NOT register a cdc interface.
So indeed it seems like 1st plug vs re-plugs does make a difference here. Perhaps this was already known - just stating my findings/learnings.
I’ll try on a Windows machine, and see how that goes, -Harry