**** BEGIN LOGGING AT Fri Jun 02 03:00:02 2017
Jun 02 03:00:05 <austin> Haha it's all good.
Jun 02 03:00:12 <austin> I think i'm gonna give up for the night
Jun 02 03:00:18 <Set_> Oh...I know. use TightVNC Viewer.
Jun 02 03:00:46 <Set_> You can get to the bone's OS in real time.
Jun 02 03:01:22 <Set_> I am sorry.
Jun 02 03:01:30 <Set_> I failed trying to teach again.
Jun 02 03:02:06 <Set_> Oh snap. Try this. ssh root@192.168.7.2 at the cmd line
Jun 02 03:02:14 <austin> haha thanks man,
Jun 02 03:02:21 <austin> doesn't work
Jun 02 03:02:24 <Set_> No?
Jun 02 03:02:30 <austin> nope
Jun 02 03:02:31 <Set_> Damn. That is odd.
Jun 02 03:02:41 <Set_> Let me try one more thing. Please.
Jun 02 03:02:41 <austin> gonna go dig up an ethernet cable and try another way tomororw
Jun 02 03:02:44 <austin> thanks for trying.
Jun 02 03:02:45 <austin> Oh ok sure.
Jun 02 03:03:00 <Set_> Okay. Please hold. I am going to type one more thing.
Jun 02 03:03:22 <austin> sure thing
Jun 02 03:03:47 <Set_> Maybe sudo ssh debian@192.168.7.2
Jun 02 03:04:39 <austin> Doesn't work either.
Jun 02 03:05:17 <austin> It's a hardware issue I think.  My OS doesn't even recognize that there could be a network over the USB
Jun 02 03:05:54 <austin> So I can see the storage from running fdisk. I can lsusb and see my device.  I can't in anyway see usb as a network interface.
Jun 02 03:06:02 <Set_> Hey...get a Ethernet cable and type in sudo ssh debian@192.168.7.2
Jun 02 03:06:10 <Set_> I am serious. I got mine booted and working now.
Jun 02 03:06:17 <austin> lol cool!
Jun 02 03:06:28 <austin> I'm at school and need to get home.  will try when I get there.
Jun 02 03:06:31 <austin> Thanks for your help.
Jun 02 03:06:44 <Set_> Okay.
Jun 02 03:06:49 <Set_> Godspeed!
Jun 02 03:06:50 <austin> Cheers!
Jun 02 03:26:25 <Set_> It is hard to believe that I forgot everything so quickly. Sheesh.
Jun 02 03:26:42 <Set_> On my end, I was losing it.
Jun 02 04:02:43 <stormbytes> zmatt if you feel like translating this bit of ruby code into async-javascript I'd love to see it. I've been racking my brains out for weeks trying to get this async paradign... https://pastebin.com/aKZ73QgQ
Jun 02 07:23:26 <Orange_> Hi, I have a couple issues with getting into root of BBB. The password options don't work. Does anyone know how to override this? I tried re-flashing the board to reset it. I put all my steps in this justpasteit link (shows more steps main goal is getting internet-over-USB working) https://justpaste.it/17fb1
Jun 02 07:26:30 <tbr> you mean you can't log in as root via SSH?
Jun 02 07:26:35 <tbr> that's a security feature
Jun 02 07:26:57 <Orange_> Yeah, is this not an option?
Jun 02 07:27:01 <tbr> you're *strongly* discouraged from disabling that
Jun 02 07:27:20 <tbr> the preferred workflow is: log in as user, use sudo
Jun 02 07:27:39 <Orange_> Alright, so would I do "sudo ssh ..." ?
Jun 02 07:27:44 <tbr> no
Jun 02 07:27:57 <tbr> you'd do "ssh debian@beagleboneIP" and *then* sudo
Jun 02 07:28:42 <tbr> obviously you should change the password for the debian user to something secure.
Jun 02 07:29:44 <Orange_> I will do that soon, thanks. I'm trying sudo right now
Jun 02 07:34:55 <Orange_> I tried "ssh debian@beaglebone<IP address of BBB>" but operation timed out
Jun 02 07:39:03 <tbr> "ssh debian@<IP address of BBB>"
Jun 02 07:39:08 <tbr> obviously
Jun 02 07:39:33 <tbr> "ssh debian@beaglebone.local" should work too according to your paste
Jun 02 07:42:29 <Orange_> whoops! so ssh debian@<IP address of BBB> connected refused. Now tried "ssh debian@beaglebone.local" password "tempted" then "sudo apt-get update" and it looks like it's actually downloading. Thank You!!!
Jun 02 07:42:41 <Orange_> *temppwd
Jun 02 07:48:48 <Orange_> Everything's set. internet-over-USB works great. Thanks again tbr!
Jun 02 10:50:55 * zmatt looks at stormbytes' pastebin...
Jun 02 10:51:10 <zmatt> stdout, stderr, status = Open3.capture3("ls /dev/*usb*")
Jun 02 10:51:12 <zmatt> ewwww
Jun 02 11:00:01 <ver|laptop> niiiice XD
Jun 02 11:07:02 <zmatt> it's kinda amazing how many things are wrong in one tiny expression
Jun 02 11:30:46 <desperate_dude> hello everybody
Jun 02 11:31:40 <desperate_dude> so, i wanna have a beaglebone black image set up on a usb drive (self powered) and i want the board to boot from USB instead of sd or internal mmc
Jun 02 11:31:52 <desperate_dude> can anyone tell me how i do that?
Jun 02 11:32:39 <freemor> if you hang out long enough someone should.
Jun 02 11:33:05 <freemor> this channel tends to go in runs depending on who is about
Jun 02 11:33:14 <ver|laptop> check out bbblfs .. although it needs some tweaks
Jun 02 11:33:26 <desperate_dude> i mean, i found some stuff from people who have apparently done it before, but the files they were modifying do not exist on my image that i am using
Jun 02 11:33:27 <ver|laptop> its designed for flashing, but should get you started
Jun 02 11:33:42 <ver|laptop> prepare for a lot of reverse-engineering :D
Jun 02 11:33:45 <LetoThe2nd> basically reading up on the sysboot pins in the srm should be enough, given a thumb drive containing a proper image
Jun 02 11:35:19 <desperate_dude> it doesnt even need to be automatic boot or anything. would be enough if i just could manually boot usb via J1 commands
Jun 02 11:35:30 <zmatt> ver|laptop: I don't see how bbblfs is useful here
Jun 02 11:35:36 <ver|laptop> zmatt: it was just a thought.
Jun 02 11:35:39 <LetoThe2nd> zmatt: neither me.
Jun 02 11:35:49 <ver|laptop> but .. depending on your level of expertise .. you can go to silicon or .. not .. :)
Jun 02 11:36:03 <zmatt> desperate_dude: I don't know if the usual u-boot is built with usb host support
Jun 02 11:36:23 <LetoThe2nd> desperate_dude: you can either do it in software, adding some clever scripting to uboot. or just read up in the srm if the SoC itself can boot from usb, and then act accorcdingly.
Jun 02 11:36:29 <zmatt> it can't
Jun 02 11:36:31 <desperate_dude> it would be a great help to just know where i find u boot on my image
Jun 02 11:36:35 <ver|laptop> zmatt: LetoThe2nd: somehow you gotta get the processor to look at usb, and bootstrap from there .. this system doesn't have a BIOS ;)
Jun 02 11:36:37 <zmatt> you'll need u-boot on eMMC or μSD
Jun 02 11:36:45 <desperate_dude> boot/uboot/ is empty on the image i use
Jun 02 11:36:57 <zmatt> that's an obsolete directory, you can toss it
Jun 02 11:37:00 <LetoThe2nd> ver|laptop: *sigh* i repat: one has to read up in the srm if usb host mode is supported.
Jun 02 11:37:23 <zmatt> LetoThe2nd: I saved one the effort: 13:36 < zmatt> it can't
Jun 02 11:37:23 <ver|laptop> oh I'm thinking the USB-OTG port . NOT the HOST port.. my bad. Sorry.
Jun 02 11:37:28 <ver|laptop> easy mistake.
Jun 02 11:38:15 <ver|laptop> too much blood in the caffeine stream today :((
Jun 02 11:38:16 <zmatt> desperate_dude: u-boot does support booting from an usb drive, but I don't know if that has been enabled at compile-time
Jun 02 11:38:34 <LetoThe2nd> zmatt: well then its just uboot + some scripting.
Jun 02 11:38:34 <ver|laptop> zmatt: you've never recompiled a uboot yet? I guess not ...
Jun 02 11:38:37 * zmatt sends ver|laptop a few grams of caffeine powder
Jun 02 11:38:42 <zmatt> ver|laptop: lol yes
Jun 02 11:38:45 <ver|laptop> zmatt: intravenous, preferably :D
Jun 02 11:38:48 <desperate_dude> so, i basically would need to recompile the kernel?
Jun 02 11:38:53 <zmatt> desperate_dude: no
Jun 02 11:39:13 <desperate_dude> ok?
Jun 02 11:39:22 <ver|laptop> desperate_dude: uboot is like a bIos .. its a 'sub-kernel'
Jun 02 11:39:26 <zmatt> recompile u-boot, *if* support for usb drives is not already enabled
Jun 02 11:39:47 <zmatt> it's not a 'sub-kernel', it's a bootloader... i.e. indeed like BIOS
Jun 02 11:39:50 <desperate_dude> ok, but where is uboot?
Jun 02 11:40:25 <zmatt> desperate_dude: on eMMC, sectors 256 and above
Jun 02 11:40:41 <zmatt> (before the partition that contains the linux filesystem)
Jun 02 11:40:48 <desperate_dude> OH
Jun 02 11:41:02 <desperate_dude> so i was a total idiot when i looked for it in the filesystem
Jun 02 11:41:21 <zmatt> well, it's kinda understandable :)
Jun 02 11:41:47 <zmatt> but finding a file on the root filesystem requires being able to understand ext4 filesystems
Jun 02 11:42:01 <zmatt> and this is something the RBL (ROM bootloader) cannot do
Jun 02 11:42:38 <zmatt> the boot process actually happens in several stages:
Jun 02 11:43:05 <zmatt> 1. initial execution is in the ROM bootloader baked into the AM335x
Jun 02 11:43:38 <desperate_dude> makes sense
Jun 02 11:44:09 <zmatt> it performs basic initialization of the AM335x and then tries to find a program to execute in various places
Jun 02 11:44:49 <zmatt> which places depends on the values of "sysboot" bits 0-4
Jun 02 11:44:54 <desperate_dude> thats where the pins come into play that tell the chip where to look for an image, isnt it?
Jun 02 11:45:26 <zmatt> yes, sysboot is an array of 16 bits which are the values of the LCD_DATA0-15 pins right after power-on-reset
Jun 02 11:45:53 <desperate_dude> i see
Jun 02 11:46:18 <zmatt> (they also configure things like the frequency of the main oscillator)
Jun 02 11:47:12 <zmatt> by default the resistors on the BBB pull sysboot 0..4 to {0,0,1,1,1}
Jun 02 11:47:27 <zmatt> which makes ROM use the boot order { mmc1, mmc0, uart0, usb0 }
Jun 02 11:47:35 <zmatt> usb here is not what you're thinking
Jun 02 11:47:57 <desperate_dude> actually it should be the mini usb
Jun 02 11:47:59 <desperate_dude> isnt it?
Jun 02 11:48:12 <zmatt> yes, it will appear as usb network device (RNDIS) and then perform netboot via that
Jun 02 11:49:06 <zmatt> if you hold the S2 button pressed, you pull sysboot2 low.  the boot order is then { spi0, mmc0, usb0, uart0 }
Jun 02 11:49:12 <zmatt> mmc0 is μSD, mmc1 is eMMC
Jun 02 11:49:17 <zmatt> anyway
Jun 02 11:49:35 <desperate_dude> ok, hold on a minute. if i solder a miniusb to a usb drive and plug that in with an image, it should work, right?
Jun 02 11:49:40 <zmatt> no
Jun 02 11:49:53 <zmatt> again, the BBB doesn't act as host, it acts as a device
Jun 02 11:50:02 <zmatt> specifically it will appear as an usb networking device
Jun 02 11:50:13 <desperate_dude> so i need to reconfigure the client to host
Jun 02 11:50:32 <zmatt> and then perform netboot over that, exactly as it would via ethernet (which is another option if you configure sysboot different)
Jun 02 11:51:02 <zmatt> acting as a host and loading stuff from an usb driver requires totally different code
Jun 02 11:51:17 <zmatt> and this is still ROM we're talking about, so there's nothing you can change at this point yet
Jun 02 11:51:30 <desperate_dude> oh
Jun 02 11:51:41 <zmatt> so ROM needs to find *something* on eMMC (or μSD as fallback)
Jun 02 11:52:10 <zmatt> that something is u-boot, or rather its "SPL", Secondary Program Loader
Jun 02 11:52:30 <desperate_dude> ok, so you are saying the uboot needs to exist still on sd or mmc
Jun 02 11:52:35 <zmatt> yes
Jun 02 11:52:37 <desperate_dude> but only the uboot?
Jun 02 11:53:41 <zmatt> yes.  for example, when you "boot from μSD", what typically happens is that u-boot is loaded from eMMC (which it is first in the boot order considered by ROM), but then u-boot will load the kernel from μSD
Jun 02 11:54:00 <desperate_dude> is that also the case when i manually interrupt the boot process and select a boot manually?
Jun 02 11:54:04 <desperate_dude> via J1
Jun 02 11:54:21 <desperate_dude> actually, i am not sure at what stage that interrupts.
Jun 02 11:54:26 <zmatt> you're interacting with u-boot there
Jun 02 11:54:35 <zmatt> it'll actually have printed "u-boot" already too
Jun 02 11:54:37 <zmatt> somewhere
Jun 02 11:56:35 <zmatt> twice actually
Jun 02 11:56:55 <zmatt> the first message after boot is something like   U-Boot SPL <version> (<build date>)
Jun 02 11:57:03 <zmatt> that's when the SPL has started
Jun 02 11:57:36 <zmatt> shortly after that is  U-Boot <version> (<build date>)   when the full u-boot has started
Jun 02 11:58:12 <zmatt> then it will do platform initialization, and gives you a chance to interrupt boot before it executes its boot script
Jun 02 11:59:04 <desperate_dude> the usbboot command i see when i cammand help is not working without doing the changes to uboot first tho, right?
Jun 02 11:59:31 <zmatt> ah so support for usbboot has been compiled in? good
Jun 02 11:59:58 <desperate_dude> i am not sure. it looks like it, since there are some scripts and tools related to usb images
Jun 02 12:00:15 <desperate_dude> but it didnt appear to be working when i tried them
Jun 02 12:01:19 <zmatt> u-boot commands are not always very obvious
Jun 02 12:01:33 <desperate_dude> yeah, i noticed.
Jun 02 12:01:58 <zmatt>  CONFIG_USB_MUSB_HOST=y
Jun 02 12:02:05 <zmatt> ok
Jun 02 12:02:09 <desperate_dude> i mean i think it tried to boot via usb, but it just said data abort and reset itself
Jun 02 12:02:11 <zmatt> so support should be compiled in
Jun 02 12:02:22 <zmatt> which version of u-boot are you using?
Jun 02 12:02:36 <desperate_dude> good question, lemme check
Jun 02 12:03:40 <zmatt> if you have older than v2017.05 you may want to upgrade first
Jun 02 12:04:06 <zmatt> but, I gotto go, will be back later
Jun 02 12:04:41 <desperate_dude> alrighty
Jun 02 12:07:28 <desperate_dude> its an older version 2016.11
Jun 02 12:13:16 <anhira> hello
Jun 02 12:14:11 <anhira> i'm woking with the bbb and i have one problem with the analog inputs. I have installed Ubuntu 16.04 and the kernel is 4.4.x
Jun 02 12:14:29 <anhira> the question is i can't read values under 0.8 0.9 V
Jun 02 12:15:40 <anhira> i don't know why because when i configured the analog input for the first time i read correct values
Jun 02 12:16:29 <anhira> maybe if the voltage under this pins are bigger than 1.8v can damage the analog port
Jun 02 12:17:10 <anhira> i'm try with other pcb and I have the same values
Jun 02 12:17:33 <anhira> anybody can help me please?
Jun 02 12:17:43 <desperate_dude> but you should still see values from the adc fifo
Jun 02 12:18:27 <desperate_dude> what exactly do you mean you cant read values under 0.8?
Jun 02 12:18:31 <anhira> I read the value from the file: in_voltage0_raw
Jun 02 12:19:05 <desperate_dude> oh, i never used the adc that way. i always used the hardware registers to use em
Jun 02 12:19:09 <anhira> yes if i put for example 0.4V the adc show the value of 0.8V
Jun 02 12:19:44 <anhira> and how i can read the value from the adc fifo?
Jun 02 12:20:17 <anhira> you use some O.S. or you program directly from the TI AM335x
Jun 02 12:20:31 <desperate_dude> you need to get access to the hardware register so you dont get a segmentation fault and then just read the value of a pointer that points to the hardware adress
Jun 02 12:22:52 <desperate_dude> if you can use the pru, that can access the adc register and can read the values into shared ram. it should also be much faster than using the main cpu, which would probably not be able to exceed like 10khz adc frequency
Jun 02 12:24:09 <desperate_dude> anyways, it would be interesting to know if the adc register itself also has an incorrect value stored, or if it is an error in the driver that translates the value into the file.
Jun 02 12:25:03 <anhira> ok thanks I'm gonna try this, because it's a bit strange this, first i thought that can be configuration problem, but maybe would be hardware problem
Jun 02 12:26:11 <desperate_dude> a bug i know can occur is that the adc stops and leaves the value unchanged if there is a valtage peak or something.
Jun 02 12:26:25 <desperate_dude> then the value stays the same until you reset the adc
Jun 02 12:27:13 <anhira> no i think that this is not the problem because if the voltage range is [0.9..1.8V] the values from the adc are corrects
Jun 02 12:27:29 <anhira> is the  low range
Jun 02 12:27:44 <desperate_dude> the range should be 0 to 1.8, if i remember correctly
Jun 02 12:27:49 <anhira> yes
Jun 02 12:30:22 <anhira> i changed the input to all the rest analog pins from AIN0 and all the same
Jun 02 12:30:41 <anhira> :(
Jun 02 12:30:58 <desperate_dude> and if you change it back above 0.9 its working immediatly correctly again?
Jun 02 12:32:43 <anhira> yes the values from the adc stopped around 2074 but if the value it's bigger than 2074 the read it's good, up 4095
Jun 02 12:33:09 <anhira> but if i try to put values under 0.8V the value from the adc it's always 2074
Jun 02 12:33:26 <desperate_dude> that doesnt make any sense to me
Jun 02 12:33:58 <anhira> if i connect directly the pin AIN0 to GND the value readed from adc is 0
Jun 02 12:34:02 <desperate_dude> i know for a fact 2074 is not he lower limit, because i read lower values b4
Jun 02 12:34:34 <anhira> it's like the input has a pull up
Jun 02 12:34:42 <anhira> o fixed this value
Jun 02 12:35:13 <desperate_dude> i dont think they do
Jun 02 12:35:38 <desperate_dude> far as i know, the adc pins cant be reconfigured like other gpios
Jun 02 12:36:15 <anhira> exactly this pins are exclusive for the AD
Jun 02 12:36:30 <anhira> it's very strange this case
Jun 02 12:36:38 <desperate_dude> so, wait, you plug ain0 to gnd and its 0 now?
Jun 02 12:36:49 <anhira> yes
Jun 02 12:37:20 <desperate_dude> are you sure the hardware is correctly configured then?
Jun 02 12:37:53 <desperate_dude> did you meassure the voltage on the input with a different instrument too?
Jun 02 12:38:05 <desperate_dude> from beaglebone black ground as a reference?
Jun 02 12:38:43 <anhira> yes with multimeter, and the voltage from 0 to 0.8V it's always the same
Jun 02 12:39:05 <anhira> only when i force one zero connected to GND is when the AD reads '0'
Jun 02 12:39:15 <desperate_dude> can you meassure with your multimeter from gnd to adc ground?
Jun 02 12:39:24 <anhira> ok
Jun 02 12:41:47 <anhira> 0V
Jun 02 12:43:09 <desperate_dude> what are you using as a test voltage to meassure?
Jun 02 12:43:13 <anhira> i have connected GND with Analog GND through a ferrite
Jun 02 12:43:27 <desperate_dude> ok
Jun 02 12:43:54 <anhira> its a pH meter
Jun 02 12:44:20 <anhira> and i have the output from the amplifier operational connected to AIN0
Jun 02 12:44:40 <anhira> and i have the range limited to 0V_1.8V
Jun 02 12:44:51 <desperate_dude> and whats the source voltages of it?
Jun 02 12:45:52 <desperate_dude> if you input ground to the opamp, what do you meassure on its output?
Jun 02 12:48:41 <anhira> the same 0.8
Jun 02 12:49:51 <anhira> with the pin on air the output is 0 but if i connected to the pin AIN0 the output change to 0.8 if the voltage of the op amp is under this value.
Jun 02 12:50:05 <anhira> it's like something force this value
Jun 02 12:50:28 <desperate_dude> i highly suspect a bug in your op amp circuit
Jun 02 12:50:42 <anhira> maybe
Jun 02 12:51:12 <anhira> thank you very much for your interest but i need to go to launch maybe after we can continue
Jun 02 12:51:17 <anhira> thank you again
Jun 02 12:51:20 <anhira> bye
Jun 02 12:51:30 <desperate_dude> no problem, have fun
Jun 02 15:35:45 <sspiff2> I'm having some trouble getting wifi going on BBBW: 'connmanctl technologies' does not list wifi and wlan0 is not in 'ifconfig -a'.  I spent some time googling, but can't find these symptoms.  Any advice?
Jun 02 16:14:57 <zmatt> sspiff2: some BBBWs have misprogrammed EEPROM, which makes u-boot unable to recognize it as a beaglebone black wireless
Jun 02 16:15:58 <zmatt> sspiff2: try: perl -pe 's/\0/\n/g' /proc/device-tree/model
Jun 02 16:17:22 <zmatt> or
Jun 02 16:17:23 <zmatt> sudo head -c 28 /sys/bus/i2c/devices/0-0050/eeprom | hexdump -C
Jun 02 16:19:35 <sspiff2> Thanks zmatt!  Yes, I finally found a forum post a few minutes ago and I think that is my problem.  'dmesg | grep Baseboard' shows the board ident as 'A335BNLT,,'.
Jun 02 16:21:25 <sspiff2> I added 'dtb=am335x-boneblack-wireless.dtb' to /boot/uEnv.txt and now wifi seems to be working (well, almost, it can't find my network, but finds my neighbor's).
Jun 02 21:16:08 <Orange_> Hi, I have a question about internet-over-USB for BBB and for getting the date to update. I accomplished these two tasks yesterday and documented all my work. I logged into BBB today and as expected the date was off since no battery. I then  repeated the steps to update the date, but it wouldn't work and "sudo apt-get update" wouldnt work. I re-flashed the board erasing all saved code and now "sudo apt-get update" works, but the dat
Jun 02 21:17:15 <zmatt> Orange_: your text was too long and got truncated:  now "sudo apt-get update" works, but the dat
Jun 02 21:18:05 <Orange_> It's strange because I followed the steps exactly as I did them yesterday but now it doesn't work. Also, I am wondering if there is code I can save in "nano ~/.profile" such that I don't have to worry about setting anything up when I turn on BBB?
Jun 02 21:18:23 <Orange_> This link shows my steps https://justpaste.it/17g4r
Jun 02 21:34:58 <Set_> dpkg-reconfigure tzdata
Jun 02 21:35:54 <Set_> Orange: use this ^
Jun 02 21:40:40 <Orange_> Set_, trying this right now
Jun 02 21:42:03 <Set_> Okay.
Jun 02 21:42:09 <Set_> You will see a set of instructions.
Jun 02 21:42:19 <Set_> America is one and US is another.
Jun 02 21:42:30 <Set_> Pick US and the timezone you are in.
Jun 02 21:42:32 <Set_> This should help.
Jun 02 21:46:01 <Set_> Or you can lie about it if necessary.
Jun 02 21:49:55 <Set_> Orange_: I am off. Enjoy!
Jun 02 21:50:00 <Orange_> Yeah, manually set the time? I'm taking long srry screen in terminal is giving some issues at the moment
Jun 02 21:50:07 <Orange_> Ahh, okay, well thanks for your help!
Jun 02 21:50:12 <Orange_> Set_
Jun 02 21:50:14 <Set_> No issue. Have a good day.
Jun 02 21:50:19 <Orange_> You as well!
Jun 02 22:00:51 <Orange_> Hi, one last question: is it normal that after a successful execution of "apt-get update" the first time, for it to return "Err" and "failure to fetch" in later attempts?
Jun 02 22:03:36 <ayjay_t_> i think that error is normally because of a poor internet connection
Jun 02 22:12:05 <Orange_> That could be. What I've noticed is that "apt-get update" works great when board was just flashed, but then it has these errors when I do the update again, sitting close to my wifi router for both times
Jun 02 23:45:43 <ayjay_t_> Are you using wifi?
Jun 03 02:31:39 <Nickst> Hey! Any BBB enthusiasts online?
**** ENDING LOGGING AT Sat Jun 03 03:00:01 2017