**** BEGIN LOGGING AT Mon Apr 02 03:00:03 2018 Apr 02 03:19:53 FL4SHK: interesting.. there are lots of graphical applications that don't require accelleration Apr 02 03:27:44 Hey? Are there any barrel jack to battery set ups for the BBBlue? Apr 02 03:28:35 12v preferably...Am I even "allowed" to input 12v into the barrel jack? Apr 02 03:31:38 For instance...I would hardwire some battery leads to the barrel jack. Then, I could plug in the barrel jack into the BBBlue. Apr 02 03:31:39 Right? Apr 02 03:32:02 Or is that jack just for a battery charger? Apr 02 03:51:14 I saw 5v, 2A but is this correct for battery supply? Apr 02 04:28:57 I will wait until tomorrow. Easter! Apr 02 06:42:04 FL4SHK: getting the gpu drivers working is not hard but also not trivial. it requires some minor kernel patches, an out-of-tree kernel module, and userspace libs. it only provides OpenGL ES and ES 2, either without windowing system (DRM and GBM backends) or with wayland (haven't tested that myself yet), no X11 support Apr 02 06:42:38 if you're still interested after knowing these restrictions I can point you to the necessary ingredients Apr 02 06:43:22 (the userspace libs are closed-source) Apr 02 07:42:07 hey guys, i'm looking to create an inventory box with rfid tags and bagle, i want to build an api that will send information to a server when the tags are taken out / placed in the box... anyone can give me some advice(links)? Apr 02 08:31:45 pathrocle: there are some limitations to your idea. The most simple and cheap tags can be only read from close range, so whoever takes things out or puts things back would need to touch a reader with the tag. Apr 02 08:32:24 I think there are some 800/900MHz tags that might be suitable for reading from further away, but are probably a bit more expensive Apr 02 08:33:18 its not a personal project Apr 02 08:33:20 other than that it's rather simple, you interface with the reader, usually over UART, I²C or SPI and process things in software Apr 02 08:33:29 i don't know if money is so big of a difference Apr 02 08:33:49 then there are commercial solutions for this available off the shelf Apr 02 08:36:38 Hi Greetings!!! Apr 02 08:37:47 We are planning to use beagle board X15 in our projects. Apr 02 08:38:09 What is the warenty we get while we are purchasing? Apr 02 09:05:42 hi Apr 02 09:06:49 tbr do you know any commercial one? Apr 02 09:17:05 Jero_: you will need to ask the selling party, this may differ. Apr 02 09:21:20 pathrocle: I've seen small active tags attached to servers and other hardware in the office, I don't recall the brand though Apr 02 09:52:56 any1 there? Apr 02 09:53:09 nope, 200 people in here are an illusioin Apr 02 09:53:12 http://www.catb.org/esr/faqs/smart-questions.html Apr 02 09:53:16 :-) Apr 02 09:53:52 tbr: Be nice! Apr 02 09:54:04 trying to download latest debian image. Very slow, around 30 kB/s. Is the the usual? Apr 02 09:54:22 this Apr 02 09:54:50 sorry, new to IRC Apr 02 09:55:04 Ben__: that's rather on the slow side of things Apr 02 09:56:10 Ben__: from the official page? Apr 02 09:57:22 yes, from https://beagleboard.org/latest-images Apr 02 09:58:30 I think that's all coming out of amazon's cloud Apr 02 09:58:48 maybe you're unlucky and got a slow route to them? Apr 02 10:00:29 thanks, i will try again later Apr 02 10:02:58 i'm following udemy EmbeddedLinuxBBB training. Anyone with experience from this course? Apr 02 10:04:13 no, but I hope it's kept up to date, else you might get some outdated instructions and be confused. :-/ Apr 02 10:05:31 so far I have managed! It is very software-centric (boot, linux kernel, busybox, buildroot, etc.). I'm no good at electronics, so this suits me fine. Apr 02 10:08:08 also, i'm looking for an entrylevel digital oscilloscope. WIlling to pay around USD500 max. Would much appriciate suggestion/s Apr 02 10:19:57 beaglelogic ? :) Apr 02 10:20:25 ah, no patience Apr 02 13:26:15 zmatt: yeah I'm up for that Apr 02 13:26:46 I could use Wayland I guess Apr 02 13:27:38 okay. patches: https://github.com/dutchanddutch/bb-kernel/tree/am33x-v4.14/patches/drivers/ti/sgx Apr 02 13:29:04 Can I use this with a different OS From the stock one? I'm assuming so, but I'll need to switch from the default kernel. Apr 02 13:29:12 Using Arch Linux ARM Here. Apr 02 13:29:54 yeah I saw. I've never tried a vanilla linux kernel on beaglebone, but I presume these patches should apply to them too Apr 02 13:30:08 Oh do I need the bb-kernel then? Apr 02 13:30:11 I don't mind non-vanilla kernel Apr 02 13:30:22 Also this still applies to BBB, yes? Apr 02 13:30:33 we use rcn's 4.14-bone kernel series with some custom patches and custom config Apr 02 13:30:52 that's what's produced by our dutchanddutch/bb-kernel repo Apr 02 13:31:05 Alright, then I'll grab that. Can I cross compile the kernel? Apr 02 13:31:28 I'm not sure if you want our kernel config though Apr 02 13:31:33 Oh, alright. Apr 02 13:31:43 that's what rcn's bb-kernel repo does Apr 02 13:32:16 copy system.sh.sample to system.sh and adjust contents to taste Apr 02 13:32:47 then you can run ./build_deb.sh to build a debian package or ./build_kernel.sh to build a tarball Apr 02 13:33:15 Tarball most likely. Apr 02 13:33:40 it'll download a cross-toolchain (if necessary), check out the right linux branch, apply patches, give you an chance to tweak the kernel config, cross-compiles it, and builds tarball/package Apr 02 13:34:02 That should be pretty good. Apr 02 13:34:24 Is it alright with you if I come back to this later? Not sure if later today but probably. Apr 02 13:34:27 rcn's kernel config is probably more appropriate than ours... I've disabled quite a bit simply because we didn't need it (to reduce startup time) Apr 02 13:34:39 Alright Apr 02 13:35:12 after checking out our branch, you can revert the kernel config by doing git checkout 4.14.30-bone14 -- patches/defconfig Apr 02 13:36:17 alternatively you can grab rcn's bb-kernel and cherry-pick just our commit for the sgx drivers (2133fc92389b) Apr 02 13:36:43 not sure why rcn hasn't integrated it, I did mail him that I got the drivers working on 4.14 Apr 02 13:38:01 once you have the kernel, here are the drivers for it: https://github.com/mvduin/omap5-sgx-ddk-linux Apr 02 13:38:54 it has a build script you can use as inspiration (but it hardcodes some paths and builds a debian package, so you'll need to tweak it regardless) Apr 02 14:59:14 Anyone using adc here? I'm trying to achieve a decent sampling rate (close to the specified 200 khz) but can't figure out how. I set up the buffer according to http://processors.wiki.ti.com/index.php/Linux_Core_ADC_Users_Guide and it works no problem, but nowhere close to the expected speed: running `cat /dev/iio\:device0 | pv > /dev/null` gives just ~14 Kb/s speed. Increasing buffer size for iio doesn't help. Apr 02 15:00:02 it's possible a low samplerate has been configured in DT Apr 02 15:01:23 yep https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/BB-ADC-00A0.dts#L37-L40 Apr 02 15:01:41 16x averaging, and a considerable open delay Apr 02 15:02:02 (why on earth would anyone would open delay instead of increasing the sample time? o.O ) Apr 02 15:02:08 *would anyone use Apr 02 15:02:24 hm, I don't think I have any .dts files now Apr 02 15:02:36 sudo find / -iname '*dts*' is empty Apr 02 15:02:47 dts are sources for dtb and dtbo files Apr 02 15:02:56 ah, sure Apr 02 15:11:14 it's also not that easy to find up-to-date instructions (and to be sure they are up-to-date!) Apr 02 15:11:14 as I understand currently overlays are handled by u-boot and not kernel, so kernel is kinda independent from dts compilation? Apr 02 15:11:33 and all the scripts needed are in that repo Apr 02 15:11:56 overlays are now loaded by u-boot yes. that doesn't really have anything to do with dts compilation Apr 02 15:13:53 main dtb files are typically compiled and packaged along with the kernel (since some parts of the main dts can be dependent on kernel version), although there's the https://github.com/RobertCNelson/dtb-rebuilder repository to make it easy to rebuild dtb files without having to recompile the kernel Apr 02 15:14:22 overlays have always been separate, in https://github.com/RobertCNelson/bb.org-overlays Apr 02 15:16:37 so I can recompile the single dts file and put it to /lib/firmware/BB-ADC-00A0.dtbo replacing the original? Apr 02 15:16:45 yes Apr 02 15:17:06 and what would happen if I update the kernel later? Apr 02 15:17:20 nothing? Apr 02 15:17:42 nothing, the concern of them getting replaced would be when you update the overlays package Apr 02 15:17:47 hold on, there's a way to prevent that Apr 02 15:18:53 sudo dpkg-divert --local --rename --add /lib/firmware/BB-ADC-00A0.dtbo Apr 02 15:19:33 that will rename the package-provided version of that file out of the way, including when installing updates of that package Apr 02 15:19:52 interesting, never heard of this! Apr 02 15:20:33 this lets you safely replace a package-provided file by an administrator-provided file Apr 02 15:21:08 i guess otherwise apt would ask what do I want to do with the file (at least it asks for configs) Apr 02 15:21:21 no, since it's not a config file Apr 02 15:21:50 it would silently replace it Apr 02 15:33:23 thanks again, it works! now I get 390 kb/s reading, which is almost exactly 200 khz (set all delays and avg to zero) Apr 02 15:34:00 min value for avg is 1 Apr 02 15:34:12 you can't take an average of 0 samples :P Apr 02 15:34:28 yeah, but it says: Apr 02 15:34:29 This increases the time taken by ADC to generate a sample. Valid range is 0 average to 16 averages. Maximum value is 16. Apr 02 15:34:37 euh Apr 02 15:34:50 didn't check sanity of samples yet :) Apr 02 15:34:56 I guess that means they implicitly accept 0 as equivalent to 1 ? Apr 02 15:35:02 which is odd but ok Apr 02 15:37:41 and do you happen to know how to sample for best (minimal) jitter? I'd much rather like stable 100 khz than varying 190-195 Apr 02 15:38:38 uhh, that would be an insane amount of jitter Apr 02 15:41:41 don't get, what exaclty? Apr 02 15:41:54 the sampling frequency is simply obtained by dividing down the 24 MHz main oscillator clock Apr 02 15:41:59 "varying 190-195" Apr 02 15:44:50 that was hypothetical Apr 02 15:45:16 so if the CPU load isn't limiting the buffer reads, it is expected that the sampling rate is stable? Apr 02 15:46:18 yes, the adc samples at a regular interval and places the data into a fifo, which is then read by the cpu or by dma (I'm not sure if the linux adc driver currently implements dma or not) Apr 02 15:48:55 so I just set large enough buffer (for small <~1 kb buffers the speed decreases) and that should be it Apr 02 15:49:22 I mean iio buffer, not the one I read /dev/iio with Apr 02 15:49:32 I don't really know anything about iio Apr 02 15:50:37 ok, thanks a lot anyways! at first I though that to reach the expected performance programming pru is required, but it turned out to be much easier Apr 02 15:53:23 actually, if you're getting only 200 kHz while setting all times to zero, that's a very bad sign Apr 02 15:53:33 it means the cpu isn't keeping up Apr 02 15:54:11 or wait, maybe the driver also configures a clock divider, lemme check Apr 02 15:54:21 really? I read in the specs that 200 khz is the maximum adc performance Apr 02 15:54:35 no it can go up to 1.6 MHz Apr 02 15:54:36 and cpu load is just a couple of percent Apr 02 15:54:49 *percents Apr 02 15:55:19 1.6 MHz?! it's way more than I expected Apr 02 15:56:08 time per sample is: open_delay + averaging * (15 + sample_delay) Apr 02 15:56:24 in cycles of the adc clock, which is 24 MHz / clock_div Apr 02 15:56:49 clock_div = 1, open_delay = 0, averaging = 1, sample_delay = 0 yields 24 MHz / 15 = 1.6 MHz Apr 02 15:58:20 oh, they configure the clock_div to 8 Apr 02 15:58:45 which gives a 3 MHz adc clock, and indeed a max sample rate of 3 MHz / 15 = 200 kHz Apr 02 15:58:56 so that explains that Apr 02 16:07:51 where do you find it? I managed to google only then thing that CLKDIV register in ADC is responsible for its clock, but where is it set to 8 as you say? Apr 02 16:08:28 ti_tscadc_probe() in drivers/mfd/ti_am335x_tscadc.c Apr 02 16:09:47 there's actually a constant in include/linux/mfd/ti_am335x_tscadc.h that hardcodes the target adc clock rate: Apr 02 16:09:50 #define ADC_CLK 3000000 Apr 02 16:11:32 this 3 MHz value isn't really explained anywhere, the am335x TRM specifies a max adc clock frequency of 24 MHz Apr 02 16:11:57 (i.e. min clock_div is 1 if the main osc is <= 24 MHz, or 2 if the main osc is 26 MHz) Apr 02 16:13:06 so it should be possible to recompile the driver and increase sampling rate, right? Apr 02 16:13:15 yes Apr 02 16:13:54 can't think of any reasons but for some stability issues why ADC_CLK is not set to maximum Apr 02 16:13:57 but maybe there's a good reason for configuring it to 3 MHz and they just didn't bother to explain it Apr 02 16:14:26 well the quality of the data may very well suffer Apr 02 16:15:54 when using a very short sample time you probably also need to make sure you drive the analog inputs with a sufficiently low-impedance signal to be able to charge/discharge the capacitors of the adc fast enough Apr 02 16:16:20 yeah, of course - but for higher adc_clk and correspondingly higher sample_delay nothing should change as I understand Apr 02 16:17:01 increasing the adc_clk but increasing the sample_delay correspondingly sounds pointless though? Apr 02 16:17:31 dunno, like I said... maybe they had a good reason, but if so I don't know what that reason is Apr 02 16:18:22 I mean that increasing ADC_CLK in the driver and letting users to choose sample_delay they want Apr 02 16:18:36 it would be more general Apr 02 16:19:26 I'm inclined to agree, but at the same time this seems obvious enough that whoever wrote the code must also have realized this Apr 02 16:20:13 yeah, as it's not covered anywhere and 200 khz is enough for me (and of course not to go through recompiling the driver :) ) I'll keep it as is Apr 02 16:21:18 if you want to experiment with it, I'd suggest replacing the ADC_CLK constant in ti_tscadc_probe() by a value obtained from DT using of_property_read_u32() Apr 02 16:21:32 or maybe the clk_div itself Apr 02 16:26:59 something like https://pastebin.com/c711aVML (totally untested) Apr 02 16:28:50 sadly I'm not too experienced with recompiling kernel stuff Apr 02 16:29:22 rebuilding a -bone or -ti kernel is actually really easy if you have a debian or ubuntu host system Apr 02 16:30:25 you grab https://github.com/RobertCNelson/bb-kernel (for -bone kernels) or https://github.com/RobertCNelson/ti-linux-kernel-dev (for -ti kernels), check out the appropriate branch for which kernel series and variant (-rt or not) you want Apr 02 16:31:05 copy system.sh.sample to system.sh and adjust contents to taste (uncomment the AUTO_BUILD=1 if you don't care about doing custom kernel config) Apr 02 16:31:30 and run ./build_deb.sh Apr 02 16:31:52 if it's missing any packages needed to build the kernel, it'll complain and tell you which packages you need to install Apr 02 16:33:17 the first time I'd suggest just letting it rebuild the kernel package without any modifications, just to confirm everything works ok Apr 02 16:33:36 this also yields a git repo of the patched kernel tree in the subdirectory "KERNEL" Apr 02 16:33:54 then apply your patch there, and run tools/rebuild_deb.sh Apr 02 16:34:11 looks really easy, and after build_deb it outputs the dpkg file to install on BBB? Apr 02 16:34:25 *deb file Apr 02 16:34:33 yes, in the subdirectory 'deploy' Apr 02 16:35:07 oh, you may want to add a line to version.sh to append some custom suffix to the $BUILD variable, just to make it easy to distinguish your patched kernel from the normal one Apr 02 16:35:22 BUILD+=-custom Apr 02 16:35:23 or something Apr 02 17:26:26 zmatt: you seen esr hanging around these parts? Apr 02 17:26:43 I've talked to him yes Apr 02 18:05:33 I tried installing node.js which seemed to succeed but then when I do node -v I still see the old version. I tried apt-get remove nodejs but I got an error that it wouldn't work – the old version comes with the distro Apr 02 18:05:40 any ideas? Apr 02 18:06:00 how did you try to install it? what exactly is the complaint from apt-get ? Apr 02 18:06:59 my recommendation for updating nodejs is by adding nodesource as a repository and then just installing it with apt-get install nodejs Apr 02 18:07:51 see https://github.com/nodesource/distributions#deb Apr 02 18:55:41 windsurf_: eh, did you just ask a question and immediately stopped caring or something? Apr 02 18:56:14 oh sorry, I didn't see you there and i'm on a conference call Apr 02 18:57:17 zmatt I did what Node site recomments, running the sh script here https://deb.nodesource.com/setup_8.x piped to bash Apr 02 18:57:22 then apt-get install nodejs Apr 02 18:57:25 and I got no errors Apr 02 18:57:38 just, after I do node -v and I get the old version, 6.13 Apr 02 18:57:44 try: which node Apr 02 18:57:50 to determine where it's getting node from Apr 02 18:57:58 ok Apr 02 18:58:52 on this sd card I haven't tried to install node. which node gives me, /usr/local/bin//node Apr 02 18:59:00 well that explains Apr 02 18:59:19 that's default for the distro Apr 02 18:59:26 not sure what you're gleaning from that? Apr 02 18:59:38 it's a locally installed nodejs, not one coming from a package Apr 02 19:00:13 it's like that on a default image? that sounds like bug report worthy Apr 02 19:00:43 regardless, I'd suggest finding and manually removing everything nodejs-related you manage to find in /usr/local Apr 02 19:01:42 ok super weird, now the version is higher than before Apr 02 19:02:04 lol Apr 02 19:02:10 sorry i was looking at my mac side Apr 02 19:02:33 ok, so this is the location /usr/bin/node Apr 02 19:02:41 for the default 6.13 one Apr 02 19:02:51 eh Apr 02 19:02:59 check apt-cache policy nodejs Apr 02 19:04:36 zmatt that gives me, https://pastebin.com/gyFdFnf5 Apr 02 19:04:48 might have to reload that page if it says its busy Apr 02 19:05:39 uhh that looks like adding the nodejs repository failed entirely. did it not give any error? Apr 02 19:05:45 nodesource repository I mean Apr 02 19:06:25 I reflashed the sd card this morning, I've never installed node on this one so you're looking at the distro default Apr 02 19:06:47 I just tried apt-get remove and here's the output, fyi https://pastebin.com/ydJaZPsp Apr 02 19:06:54 <[kieran]> anyone on that is knowledgeable about the X15 BSP? Apr 02 19:07:01 oh, but that's not remotely useful in debugging why you weren't able to install nodejs 8 now is it? Apr 02 19:07:37 i'll install it again now but it doesn't give me errors Apr 02 19:08:51 the reason I thought it might be useful to know is that I can't uninstall the existing version of node, which I assume is the real culprit Apr 02 19:09:10 no, normally you don't remove the old version before installing the new, you just upgrade Apr 02 19:09:32 ok Apr 02 19:09:52 it's complaining that removing nodejs would also remove bonescript and therefore c9-core-installer, and apparently the latter might be a held package? Apr 02 19:10:34 k Apr 02 19:10:40 if you don't care about these packages, try removing all three explicitly Apr 02 19:11:11 i'll leave it for now and try upgrading... Node installer said, "Run `apt-get install nodejs` (as root) to install". Does 'sudo' suffice or do I need to 'su' ? Apr 02 19:11:28 sudo Apr 02 19:12:10 su requires the root password, which isn't configured by default, hence it is not useful Apr 02 19:12:33 also the syntax is more annoying (it would be su -c 'apt-get install nodejs' ) Apr 02 19:12:44 i see Apr 02 19:12:56 so I did install the new node without errors. here's the output: Apr 02 19:13:01 https://pastebin.com/AT6KTMFQ Apr 02 19:13:25 and apt-get install nodejs reports to have succeeded too Apr 02 19:13:38 which node gives me same as before, so does node -v Apr 02 19:13:57 o.O Apr 02 19:14:00 what? Apr 02 19:14:14 did it actually install nodejs 8 ? Apr 02 19:14:26 hm sec Apr 02 19:14:56 it mentions the version when it's installing I think Apr 02 19:15:05 ok, I see the problem Apr 02 19:15:39 using ansible the apt-get install says it succeeds but I get a different result doing it manually on command line where I do get the new node version installed Apr 02 19:16:30 okay, so problem solved Apr 02 19:19:56 I think yes, I think I just need to figure out the right ansible command. Sorry for the red herring Apr 02 20:13:53 What amount of volts can the BBBlue handle w/out adjustments? Apr 02 20:14:14 e.g. 12v 2A? Apr 02 20:15:29 I saw the LiPo battery connector and the type of LiPo it can handle. Can it handle other sources, i.e. w/ the barrel jack? Apr 02 20:33:10 bbl...whoo Ha! Apr 02 21:28:35 fortnight: the barrel jack accepts 5-18V as far as I can tell Apr 02 21:51:35 Oh. Thank you. Apr 02 21:52:00 It has a 12v sticker on it. I thought this was only for battery chargers for some reason. Apr 02 21:55:42 So...adding two, 9v batteries should be okay (in series). That is good news. Apr 02 21:57:07 I just need to get WiFi working on the BBBlue now. The damn board is not accepting my connmanctl commands from the latest-image on BBB.io/latest-images. Apr 02 21:57:17 ... Apr 02 21:57:33 I could have been out of range. I will check later. Apr 02 23:16:33 zmatt: any chance you can lead me through getting hardware accelerated graphics on my Beaglebone Black? Apr 02 23:30:05 FL4SHK: have you already compiled a patched kernel and the sgx kernel module, for which I gave the necessary pointers earlier? Apr 02 23:30:16 No, let me do that first. Apr 02 23:41:32 Where can I find the sgx kernel module, just in the repo you had? Apr 02 23:42:34 FL4SHK: https://pastebin.com/raw/6nU3egzM Apr 02 23:42:43 oh sorry Apr 02 23:42:46 oops Apr 02 23:42:48 I lost the logs Apr 02 23:42:50 thanks Apr 02 23:56:14 Need help with bbg wireless + groove cape. OS does not detect the cape, see logs https://forum.seeedstudio.com/viewtopic.php?f=38&t=7163&p=25721#p25721 Apr 02 23:56:24 Any experts? Apr 02 23:57:12 is there even anything to detect about the grove cape? Apr 02 23:58:06 are you using a recent image? are you running from eMMC or sd card? Apr 02 23:58:31 since it looks like cape-universal isn't enabled for some reason Apr 02 23:59:34 also, is the grove cape compatible with the bbg-wireless? Apr 03 00:00:50 can you pastebin the output of my show-pins utility: https://github.com/mvduin/bbb-pin-utils/tree/green-wireless#show-pins Apr 03 00:03:02 Pluggin' in the BBBlue, captain. WiFi will be enabled! Apr 03 00:03:33 fortnight: you really don't have to narrate everything you're doing Apr 03 00:03:45 Yes sir...Stopping naration now! Apr 03 00:05:58 WiFi! Apr 03 00:08:25 I got these wires for the BBBlue recently. I am going to make what someone else made. I got as chassis arriving soon. Apr 03 00:08:28 BBBlue! Apr 03 00:08:34 narration... Apr 03 00:08:42 Sorry. I got excited. Apr 03 00:08:44 Stopping now. Apr 03 00:09:08 vantomcat: why do you ask for help if you subsequently just ignore someone trying to help you? Apr 03 00:09:47 hey zmatt: I had/have a v2, grove Cape and a v1, grove Cape. Apr 03 00:09:58 If you need testing, let me know. Apr 03 01:25:21 stuck with bb green Apr 03 01:25:24 omg Apr 03 01:25:35 can't use ports on the grove cape Apr 03 01:27:42 https://pastebin.com/Ru4iVmvp Apr 03 01:27:45 why is that? Apr 03 01:31:56 i have not found a decent case for a beaglebone green. all the cheap cases out there seem to be for bbb Apr 03 02:43:59 I am following some cmds on arduPilot from https://gist.github.com/jadonk/6080ca92d6e225eb89d33ad7744e1775. Apr 03 02:44:26 I am stuck w/ no rc.local directory/file. What should I do from here? Apr 03 02:44:49 Line 13 on that gist. Apr 03 02:47:20 brb Apr 03 02:48:13 Otay...any takers would be great on this one. Apr 03 02:56:41 rc.local is not a file on my system and it bugs me. **** ENDING LOGGING AT Tue Apr 03 03:00:01 2018