**** BEGIN LOGGING AT Mon Nov 27 03:00:01 2017 Nov 27 16:37:54 zmatt: Are the drivers available through Windows Update or something? Or are you referring to whether the drivers are sufficiently signed (hence a later image would be more likely to have correct signatures) Nov 27 16:39:20 Btw I have had no wifi issues with my BBB Wireless ever since I turned off power management. Still haven't entirely nailed down how to completely disable it at start up but it's nice to have something to blame it on Nov 27 17:57:02 what could be causing my ethernet from not accessing Internet? I can only connect over USB now (was working on Friday). I've changed cables. When I do ifconfig I see eth0 but pinging google fails with, "Temporary failure in name resolution" Nov 27 17:58:07 MathOnNapkins: I don't know the full details, I suspect they just tweaked some usb descriptors to make windows automatically use their own driver, but I've never investigated since I don't really care Nov 27 17:58:21 what could be causing my ethernet from not accessing Internet? I can only connect over USB now (was working on Friday). I've changed cables. When I do ifconfig I see eth0 but pinging google fails with, "Temporary failure in name resolution" Nov 27 17:58:36 when I ping google.com's IP address (216.58.216.142) I get, "Destination Host Unreachable" so I don't think it's a DSN issue Nov 27 17:59:01 MathOnNapkins: I also realized that it might actually also apply to older versions of windows, not sure... the "since windows 10" thing I was thinking of is for usb serial, not RNDIS Nov 27 17:59:14 windsur__: can you show the output of "ip addr" Nov 27 17:59:25 (using pastebin.com or similar site) Nov 27 17:59:37 zmatt just the eth0 part? Nov 27 17:59:51 should suffice Nov 27 18:00:19 zmatt https://pastebin.com/8dDqNi1J Nov 27 18:00:41 it's not able to obtain an ip address Nov 27 18:00:50 so that's my router's fault maybe? Nov 27 18:01:17 could be Nov 27 18:01:36 what part of that paste did you glean that from? Nov 27 18:02:23 inet 169.254.*.*/16 is a self-assigned link-local address Nov 27 18:02:38 (which is a fallback for when dhcp fails) Nov 27 18:02:49 zmatt ok. thanks Nov 27 18:20:09 zmatt ok. thanks Nov 27 18:20:24 zmatt ok. thanks Nov 27 18:20:34 sorry, wrong window Nov 27 18:20:51 I can't even ping my router's IP. Nov 27 18:21:25 I'm at a loss, I wonder if the ethernet port got damaged somehow from static or somethig Nov 27 18:23:02 sudo shutdown -h now Nov 27 18:23:05 fack sorry Nov 27 18:27:32 windsur__: doesn't seem likely since it seems to be reporting link up Nov 27 18:27:42 you can't ping anything if you don't have an ip Nov 27 18:27:54 zmatt ah ok Nov 27 18:28:42 try checking the link statistics using: ip -s link show eth0 Nov 27 18:29:03 the RX statistics should show if any packets are being received at all Nov 27 18:31:11 * windsur__ zmatt thanks, I see https://pastebin.com/BJTkmFHv Nov 27 18:31:38 the bytes I see would be over eth0, not my usb? Nov 27 18:31:44 you're clearly receiving packets, so the port seems to be working fine from a hardware perspective Nov 27 18:31:54 ok, getting somewhere I guess Nov 27 18:33:53 my laptop is connected over wifi, not lan so I can't compare that Nov 27 18:35:18 you can try monitoring dhcp traffic on the beaglebone using: sudo tcpdump -e -i eth0 -l -n -p -t udp port bootps Nov 27 18:35:23 then plug in ethernet Nov 27 18:36:07 don't have tcpdump apparently Nov 27 18:36:17 I'd get it if I had internet :P Nov 27 18:36:23 heh Nov 27 18:37:17 alternatively, you can try manually configuring an ip in the range used on your network... be sure to avoid using one that's already in use ;) Nov 27 18:38:18 for example: ip addr add 10.0.0.123/24 dev eth0 Nov 27 18:38:42 yeah ok Nov 27 18:38:46 is that temporary? Nov 27 18:38:56 if you can ping the router then, you can proceed to add a default route using ip route add default via 10.0.0.1 (or whatever the router ip is) Nov 27 18:38:59 yes Nov 27 18:39:35 it's already based on the assumption the network manager you're using (probably connman) doesn't mind or mess with it Nov 27 18:40:36 brb Nov 27 18:48:59 zmatt I added an IP and can ping myself but that's all Nov 27 18:50:14 yeah obviously you can ping yourself if you manually configure an ip... those packets don't even involve the actual ethernet interface Nov 27 18:53:37 just shows I added the IP ok Nov 27 18:53:54 but yeah, I understand that's not a measure of eth connectivity Nov 27 18:54:08 so weird Nov 27 18:54:17 maybe I need to go find another lan to try this on Nov 27 18:58:21 or another device with an ethernet port Nov 27 18:58:30 true Nov 27 19:05:01 tried assigning a static IP via router config for eth0 mac address. No luck there either Nov 27 23:39:35 hi there. I’m following the instructions here https://github.com/beagleboard/pocketbeagle/wiki/FAQ#How_do_I_get_additional_USB_connections to add a usb connection to my pocketbeagle. I’d like the PocketBeagle to act as the host on this additional port so I can plug in a USB device such as a wifi or ethernet adapter. I think I’ve wired it up ok but when I run `lsusb` I get the following output: Nov 27 23:39:59 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Nov 27 23:39:59 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Nov 27 23:40:22 sorry that was supposed to be all one message Nov 27 23:41:59 anyway it lists two USB items but both are “Linux Foundation 2.0 root hub”, this suggests my PocketBeagle is configured as the USB client in on both USB ports, right? So perhaps I need to do some configuration to have the PocketBeagle act as the USB host on USB1? Nov 28 02:17:04 I am using some moisture sensor and licking my finger to get different readings. Yes...you read that correctly. Nov 28 02:17:34 You can program this thing just like a TMP36 but w/out all the math. Nov 28 02:17:36 Yea boy! Nov 28 02:18:49 ... Nov 28 02:19:04 I have no idea on what to use it for just yet but wait. I am sure I will come up w/ ideas. **** ENDING LOGGING AT Tue Nov 28 03:00:01 2017