**** BEGIN LOGGING AT Tue Sep 13 02:59:58 2016 Sep 13 05:25:20 Is there something very WRONG with the debian image for the bbb? I am going crazy trying to get the static IP to stick, my /etc/network/interfaces is 100% correct and set for a static ip on eth0 yet something else is forcing dhcp...ugh Sep 13 05:25:45 I can't figure it out, there must be some hacky script that comes with the image running on boot or something weird. Sep 13 05:28:03 looks like connman is installed and enabled, just wtf. Sep 13 05:28:12 this is on the console image to... Sep 13 05:32:54 Anyone know what the diff between the console images and iot images are? Sep 13 05:35:10 update, removed connman now the static ip sticks. connman really really really should not be installed on a "console" minimal image. Sep 13 07:09:55 connman on the console image? huh what? that I've never seen before Sep 13 08:08:14 Has anyone gotten video acceleration to work on the X15 yet? Sep 13 08:08:26 (outside of the TI SDK) Sep 13 08:48:29 hm, strangenesses with device tree. Sep 13 09:59:56 hello Sep 13 10:02:33 how to decrease the CPU load in BeagleBone Black? Sep 13 10:07:01 that is a strange question. Sep 13 10:07:54 pull the power plug ? Sep 13 10:13:46 ogra_++; Sep 13 10:14:10 plug in ethernet or disable the buggy "powersave" feature of the PHY Sep 13 10:16:32 interesting "powersave" feature if it causes CPU load ... Sep 13 10:18:15 seriously, get an idle beaglebone, disable the distracting heartbeat led so you can see the cpu activity led more clearly, then compare with vs without ethernet plugged in Sep 13 10:19:54 the buggy powersave feature itself doesn't cause load, but the cpu workaround to it does Sep 13 11:06:08 I guess not?? Sep 13 11:06:50 ? Sep 13 11:26:53 really good, a metric assload of processing power but no way to use it outside of the sdk, thank you x15 Sep 13 12:51:16 hi. i'm having a hard time identifying a problem that is present in my custom distro but not in the official beaglebone distro (Jessie). Sep 13 12:53:00 i would like to build the exact same kernel and test with my custom distro. where do i find the original source, configuration and device tree used in the official distro? Sep 13 12:57:17 there are several kernels available for the debian images Sep 13 12:57:42 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Kernel_Options Sep 13 13:03:19 tbr: thanks! Sep 13 13:03:42 by the way: is there any reason to use the TI kernel instead of mainline these days? Sep 13 13:07:18 i find it a bit confusing selecting the correct kernel with all vendors having their own set of patches. there's the mainline. there's the ti-kernel. there's the beaglebone kernel. there's also seeed studios kernel which seems relevant because i use beaglebone green wireless currently... Sep 13 13:17:31 ionte_: AFAIU mainline is really good by now. I don't know how much of the BBG specifics are mainline yet. Could be anywhere from 100% to 0 Sep 13 13:19:10 ok, good to know Sep 13 13:50:03 ionte_: RCN has a repo with cross compiler & tools that sets up the -bone kernels, https://github.com/RobertCNelson/linux-dev Sep 13 13:50:25 ionte_: Afaik that's what he's using to build the .deb kernels for the debian image. Sep 13 13:50:54 ionte_: then theres a stable-kernel repo for the stable ones. (doh) Sep 13 13:52:53 Hi all. I'm trying to get the display working in the 3.14.20 kernel on the Beagleboard C5. Sep 13 13:53:55 there is a base device tree in the kernel, but it does not appear to have the pin defines for the HDMI port. I've tried looking around Google, but everything I find is on the Beaglebone Black. Sep 13 13:54:39 I extracted the kernel from Angstrom 2014.12 Sep 13 13:55:03 fun. I'm currently looking into disabling HDMI on the black. ;) Sep 13 13:55:12 ha, the irony. Sep 13 13:55:24 need some of the shared pins. Sep 13 14:50:34 Disable has info on the 'net. On some it's a simple uEnv.txt uncomment. Sep 13 18:25:58 l Sep 13 21:52:05 ssh: connect to host 169.254.219.203 port 22: Connection refused Sep 13 21:52:18 anyone knows how to resolve this problem ? Sep 13 22:08:30 If you are certain that 169.254.219.203 is the right ip of your beaglebone, it should work Sep 13 22:09:22 If you have a firewall you could check that. Sep 13 22:09:57 If you have local access, try "ip a" to see that the ip is correct. Sep 13 23:14:42 169.254. looks like a fallback address .. I highly doubt that's actually 'active' on your network Sep 14 00:45:34 Hello... Sep 14 01:23:21 Hello Sep 14 01:23:48 I'm trying to connect a Grove temperature sensor to Beaglebone Black using I2C Sep 14 01:24:05 byt when I try to detect the sensor, it doesn't show up Sep 14 01:24:07 any help Sep 14 01:24:08 ?? Sep 14 01:24:17 use kernel 4.1.x Sep 14 01:24:44 i.e. for Debian. Sep 14 01:25:28 Thank you for the quick reply Sep 14 01:25:57 Oh and you can use MRAA and UPM on gitHub.com. **** ENDING LOGGING AT Wed Sep 14 02:59:58 2016