**** BEGIN LOGGING AT Sat Sep 29 03:00:01 2018 Sep 29 04:31:16 Sorry if somebody already answered this, but I can't seem to find my question in the logs: Sep 29 04:31:18 Hey folks, quick question. I have a beaglebone blue that has been having a high ping latency (~250ms) when pinged from an external device over the wifi interface. I have tried a couple of things including moving the BB closer to my wifi router without luck. Furthermore it seems that when I ping other devices from the BB Blue, the latencies are much closer to the expected range of roughly 8ms.  I haven't added much in terms of software t Sep 29 04:31:18 o the device yet, so memory doesn't seem to be an issue. Does anyone have any ideas of other things to try? I tried searching Google, but am not having much luck finding things. I am curious what ping latencies other people are seeing with their BB Blues. I am currently running the http://debian.beagleboard.org/images/bone-debian-9.4-iot-armhf-2018-06-17-4gb.img.xz image from the beagleboard website off of the eMMC. Sep 29 04:33:19 rehelmin: hmm, maybe a wifi powersaving thing acting up? Sep 29 04:33:50 try sudo iw dev wlan0 set power_save off Sep 29 04:35:53 zmatt: hmm. Doesn't seem to be any different. I did try a fresh install, and the latency does seem to be slightly improved with the latest 9.5 image, but I am still seeing around 75ms average on my LAN. Sep 29 04:36:20 I'd be curious what other people are seeing with their boards Sep 29 04:42:19 now that you mention it, I'm seeing something similar Sep 29 04:42:45 or wait, hold on I'm testing this right Sep 29 04:44:07 yeah I'm definitely getting much higher ping time for inbound pings Sep 29 04:45:11 interesting… The only reason I started looking into it was because 250ms was high enough to get a bit of delay in the typing through SSH. Sep 29 04:45:50 if I cause heavy traffic, the ping time goes way down to 1-2 ms Sep 29 04:45:57 so it's definitely something to do with powersaving Sep 29 04:46:46 iw dev wlan0 set power_save off seems to completely fix it for me Sep 29 04:46:57 let me try it again Sep 29 04:49:04 whats your txpower when you do iw dev wlan0 info? Sep 29 04:50:22 20.00 dBm Sep 29 04:51:25 same.. How did you cause heavy traffic? Is there a simple way to do that? Power save is turned off for me now too, but I am still seeing the same latency as before. Sep 29 04:51:30 I'm using firmware 8.9.0.0.76 btw, I don't know if that's different from the latest images Sep 29 04:51:58 using ping -q -A Sep 29 04:52:16 (to my laptop) Sep 29 04:53:36 ok, I am seeing the same thing where if I send a load of traffic the latency drops down to where I would expect it to be. Sep 29 04:56:12 out of curiosity, how did you get that version number? Sep 29 04:59:28 https://pastebin.com/raw/bTrQrSku Sep 29 04:59:55 wlcore: firmware booted (Rev 8.9.0.0.76) Sep 29 04:59:59 in kernel log Sep 29 05:01:36 hmm, latest is actually .79, maybe I should try that out Sep 29 05:02:23 I am apparently on an older version of firmware? wlcore: firmware booted (Rev 8.9.0.0.69) Sep 29 05:02:39 evidently Sep 29 05:03:51 Sorry for sounding naive, but how could that be? Are you on an alpha release of one of the debian images? I just downloaded the 9.5 version last night. Sep 29 05:04:08 or is the firmware separate from that? Sep 29 05:04:24 I'm not using those images as such Sep 29 05:04:29 ok Sep 29 05:05:02 and yeah you can find the firmware at git://git.ti.com/wilink8-wlan/wl18xx_fw Sep 29 05:08:05 zmatt: do you know of anywhere that I can read up on this stuff a bit more? I feel like I am in the realm of asking a bunch of dumb questions at this point. Sep 29 05:08:16 on which stuff? Sep 29 05:10:23 well for example, I was hoping for a readme in the git repo, but it looks like there is just a binary file. Not really sure where that should go. I'm also questioning whether there is any other firmware that is worth looking into updating. Sep 29 05:10:54 I just did a quick test of the latest firmware (8.9.0.0.79), it also seems to work and shows similar latency behaviour (high latency for inbound pings when the wifi is mostly idle and power_save is on, but otherwise decent) Sep 29 05:11:14 it goes in /lib/firmware/ti-connectivity Sep 29 05:11:26 ok Sep 29 05:17:27 I actually put the version in the file name and create a symlink to select which one to use, that makes it easier to switch: https://pastebin.com/raw/DEEjB4za (and similar for the wl18xx-conf.bin) Sep 29 05:19:30 updated firmware, similar to before where turning off the power save feature doesn't seem to bring the latency down but sending a bunch of traffic does. Sep 29 05:19:54 ¯\_(ツ)_/¯ Sep 29 05:20:54 ha, at least there is a workaround. You just have to make sure to send a lot of data. Sep 29 05:21:35 thanks for the help Sep 29 05:23:50 rehelmin: just in case, here's my ti-connectivity dir: https://liktaanjeneus.nl/ti-connectivity.tar.xz maybe the different config is somehow relevant Sep 29 05:24:57 I don't remember what the difference is between the mimo config and the c2pc-mimo config, or why I chose to use the latter Sep 29 05:25:16 (you almost certainly don't want any of the siso configs) Sep 29 05:27:46 copying the directory over now.. Sep 29 05:31:55 same same. Are you hooked up through the tethering feature or do you have the BBB connected through your wireless router like you would any other device? Sep 29 05:34:48 it is connected both via wifi and usb, and I've arranged to give the two different hostnames (and set the appropriate sysctl settings to ensure linux doesn't send arp replies on the wrong interface) Sep 29 05:35:29 the latter initially tripped me up... pinging the ip it had on wifi still ended up going via the usb interface Sep 29 05:36:14 brb Sep 29 05:36:19 k Sep 29 05:45:49 (btw, the arp issue only existed because I bridged the usb network interfaces to our LAN, which is the same LAN the wifi connects to. unless you create a similar setup you don't need to worry about it) Sep 29 05:47:11 ok. I'm not sure what I did, but I can't get the latency down at all now. I've tried reverting to where I started and now even when I do the ping -Q in a separate tab I am not getting the latency to come down. Sep 29 05:48:31 ping -q -A I should say Sep 29 05:51:14 zmatt: I take that back latencies are still coming down when doing the audible ping. I'll have to try working through this another day though. It's getting late over here. Thank you very much for the pointers. I appreciate the help. Sep 29 05:53:38 good luck :) Sep 29 15:41:23 Hi! I'm a new user of beaglebone Sep 29 15:41:55 After flashing a new image into the sdcard I can't enter into the board by ssh Sep 29 15:42:04 could anyone help me=? Sep 29 15:42:49 are you using the correct login and password? Sep 29 15:43:48 I don't know what i have done Sep 29 15:44:06 but some hours ago I entered in ssh Sep 29 15:44:14 now It doesn't appears in ethernet Sep 29 15:44:31 the board is turning the same sequence always with 2 leds Sep 29 15:44:42 uhh Sep 29 15:45:33 earlier you said you couldn't ssh after flashing a new image, now you're saying you were in fact able to log in but it stopped working? you're being quite unclear Sep 29 15:45:49 yes Sep 29 15:46:02 I were following these steps Sep 29 15:46:25 https://archlinuxarm.org/platforms/armv7/ti/beaglebone-black Sep 29 15:46:35 when asking for help, always clearly describe both the problem you're having and the sequence of steps leading up to it Sep 29 15:47:11 if you're a new user you should probably just stick to the default images from beagleboard.org Sep 29 15:47:33 and I think when I did the step 3 when emmc I have wipe the emmc system Sep 29 15:49:02 if you wiped eMMC it would still boot from sd card Sep 29 15:49:54 so just to be clear, you successfully created an sd card and booted the beaglebone from it, then proceeded to attempt to install onto eMMC and then... what? Sep 29 15:51:38 exactly Sep 29 15:52:13 then I have rebooted and the bbb have not init the ethernet Sep 29 15:53:53 what do you mean by "not init the ethernet" and why do you think this is the case? Sep 29 15:54:07 how are you trying to connect to the beaglebone? Sep 29 15:54:22 because I'm making ping to 192.168.7.2 and it doesn't answer Sep 29 15:54:34 why would it have that ip ? Sep 29 15:54:34 and also to 192.168.6.1 Sep 29 15:54:47 you're following instructions that apply to the standard debian images Sep 29 15:55:15 because I connected before to that ip with ssh Sep 29 15:55:26 when it was running Debian Sep 29 15:55:32 before you reflashed it to Arch Sep 29 15:55:57 ah Sep 29 15:56:05 so how could I solve this problem? Sep 29 15:56:37 reflash it to the latest recommended image from https://beagleboard.org/latest-images Sep 29 15:57:22 https://drive.google.com/file/d/1-G_ycCZLQ7pZLoBlxnBfZ2JnHFcYEQjP/view Sep 29 15:57:39 this is the sequence its showing Sep 29 15:57:45 Arch is a distro for advanced linux users, and moreover is rarely used on the beaglebone. if you use it you are expected to be able to get things like networking configured right yourself Sep 29 15:58:23 ok I will install it Sep 29 15:58:28 debian I mean Sep 29 15:58:45 one thing, it is possible to install nextcloud on this bbb Sep 29 15:58:46 ?? Sep 29 15:59:18 I have no idea what that is Sep 29 16:00:26 if it runs on ARM linux systems then presumably yes Sep 29 16:01:21 ok Sep 29 18:04:19 root@Beagle-X15:/etc# sensors Sep 29 18:04:20 -bash: sensors: command not found Sep 29 18:04:40 huh? I have a sensors3.conf file on this x15. Sep 29 18:05:00 it seems to have libsensors installed too. Sep 29 18:05:30 it's not complaining about either of those, the program itself isn't installed Sep 29 18:05:50 evidently Sep 29 18:05:55 sudo apt-get install lm-sensors Sep 29 18:06:07 ok...I'll rty it. Sep 29 18:06:30 this x15 is just laid out differently than what I'm used to in a linux. Sep 29 18:06:47 it's an adventure Sep 29 18:07:45 oh cool...it's installing via ipv6 too. Sep 29 18:08:28 if you have a working ipv6 connection then obviously it'll get used Sep 29 18:08:52 not all my devices are doing tht though. Sep 29 18:09:38 for instance....my leviton wall switches use ipv6 link local just fine. But they don't auto-address in the ipv6 global properly. Sep 29 18:09:45 odd Sep 29 18:09:51 however....... Sep 29 18:10:26 my 3 honeywell lyric thermostats do auto-address correctly in the 2001:blah:blah:blah space. Sep 29 18:10:31 that's actually quite bizarre... I'd expect either no ipv6 support at all or working ipv6 support Sep 29 18:11:11 the leviton switches do use ipv6...but only their link local addresses are used. Sep 29 18:11:29 they don't auto-concoct a global address. Sep 29 18:11:34 they just ignore router advertisements? Sep 29 18:11:48 I don't think they're smart enuff to do that. Sep 29 18:12:28 I know my router advertisements are good/configured right because the thermostats do the right thing. Sep 29 18:13:05 I can ping6 them on their global addresses just fine. Sep 29 18:13:05 or do they communicate on the local network only? because I'll admit that a link-local-only IPv6-only stack can be extremely simple, more so than an IPv4 stack Sep 29 18:13:27 or I guess it could just be an unfinished ipv6 stack Sep 29 18:14:05 implemented the base ipv6 proto and neighbour discovery and then decided "eh, fuck it" Sep 29 18:14:12 Evidently, you're correct that they just speak ipv6 mdns on the local link only. Sep 29 18:14:37 ah they don't connect to the internet at all? okay then it does make sense Sep 29 18:14:38 I see tons of it in etherape. Sep 29 18:15:27 it's kinda eye-opening that the honeywell thermos DO use global addresses....and they must phone home. Sep 29 18:15:55 IPv6 is very convenient for link-local since you don't need to implement anything at all to acquire an address since it derives from your MAC address Sep 29 18:17:03 (officially DAD (Duplicate Address Detection) is technically still required, but it's completely pointless to do so since a MAC-derived ipv6 address conflict also means you have a MAC-address conflict, which DAD isn't going to be able to deal with either) Sep 29 18:17:41 I see. Sep 29 18:18:29 different manufacturers have spotty adherence to the ipv6 thing....took etherape to show me what was going on Sep 29 18:18:46 it's congealing slowly though :) Sep 29 18:20:47 I'm gonna go kill the juice to the honeywell thermostats ... turn them back on and prove that they do or do not use the same address in the 2001: block. I bet they do. Sep 29 18:21:17 that means it's worthwhile to put in some ipv6 reverse lookuos. Sep 29 18:22:06 I once wrote a tiny stateless IPv6 "stack". UDP-only, and incapable of sending unicasts other than replies to the latest packet received (apart from that it could only multicast), but hey it was really simple :) Sep 29 18:22:25 and even worked with global addresses, it simply accepted any prefix Sep 29 18:23:26 if they use a MAC-derived interface identifier then you don't need to reboot them to check, it's easy enough to spot Sep 29 18:23:47 just check for the telltale ef:fe Sep 29 18:24:05 ff:fe Sep 29 18:25:58 or explicitly compare with their MAC address... https://pastebin.com/raw/xirgWGK1 Sep 29 22:23:48 Can anyone offer help to get my BBB booted? Sep 30 00:27:32 tchristle: don't ask for a personal assistant, just explain your problem or ask your question Sep 30 00:54:25 W/ the MotorCape, what would be a good way to power the BBBW w/ barrel jack? Sep 30 00:54:27 ... Sep 30 00:55:07 I am basically asking this question b/c there are no 5v, really, batteries that are supplied via barrel jack. Am I correct? Sep 30 00:55:41 Do I need a circuit or is there an odd part to purchase? Sep 30 00:56:41 switch? Sep 30 00:59:53 MOSFET switch? Sep 30 01:01:57 switching regulator? Sep 30 01:06:51 converters! Sep 30 01:07:10 DC-DC converters and circuits! Sep 30 01:08:47 These things are not cheap. Sep 30 01:09:46 $45.00 (MotorCape) + $15.00 (Switching Regulator) + S & H = priceless! Sep 30 01:12:57 debian Sep 30 01:51:12 Okay. Why did the MotorCape have 46v input maximum instead of 48 +/- 5%? Sep 30 01:52:08 because that's the spec of the L298 driver Sep 30 01:52:39 Oh!@ Sep 30 01:53:14 zmatt: Do not fret. There are way around that idea. Sep 30 01:53:29 That was almost English! Sep 30 01:55:01 I am looking for large, cheap DC-geared motors. Sep 30 01:55:06 Boring! Sep 30 02:24:35 Dudes (and ladies), I just scored a scooter tire w/ hub for $6.58! Sep 30 02:24:45 BBB boards! Sep 30 02:25:04 I cannot wait. Sep 30 02:31:38 I found some medical scooter motors, too. That is outrageous in cost. Sep 30 02:31:39 ... Sep 30 02:32:22 Fab. is going to be hard but the BBB must live on! **** ENDING LOGGING AT Sun Sep 30 03:00:00 2018