**** BEGIN LOGGING AT Thu Sep 24 02:59:58 2015 Sep 24 03:43:17 zmatt: thanks for the link. I was thrown off by the fact that the files in https://rcn-ee.com/rootfs/*/flasher/ look an awful lot like the files in https://rcn-ee.com/rootfs/bb.org/testing/*/console/ Sep 24 03:43:42 The later don't contain apache, so thats all I've been after Sep 24 05:58:33 * suzello slaps Alynna around a bit with a large fishbot Sep 24 07:20:36 zleslie: or make your own rootfs of course... might not be very difficult with something like multistrap but haven't tried it myself yet Sep 24 08:18:07 lol, Analog Devices has a funny 404 Sep 24 11:53:10 http://linuxgizmos.com/autodesk-open-sources-linux-based-3d-printer/ bbb WTF Sep 24 13:28:21 I cannot install the driver Sep 24 13:28:31 can anyone help me Sep 24 13:44:31 keesj_, it has am335x in it, hence it must be just like bbb, journalism :) Sep 24 13:45:07 s/journalism/marketing/? Sep 24 13:48:41 I have a question about eMMCs Sep 24 13:49:32 I changed one on a Beaglebone Black to a Kingston chip that supports 4.4.1, 4.5 and 5.0 Sep 24 13:50:31 kernel 3.8.15-bone50 can#t handle that eMMC, 3.14 does Sep 24 13:50:59 I stimm want 3.8, because of the capemanager support Sep 24 13:51:23 how can I get it to work on the modified Beaglebones? Sep 24 14:00:03 The Kingston chip supports 4.4.1, what is the version of the Micron-Chip that is originally on the Beaglebone, but 3.8.13 answers wit an error message Sep 24 14:05:52 nerienna: I think capemanager like functionality is coming back or is already back since vanilla 4.1 supports dt overlays etc Sep 24 14:08:24 nerienna, capemanager is enable in v4.1.x+ right now.. Sep 24 14:40:00 ok, so I'd have to test our capes and software with a 4.1 kernel, thx Sep 24 14:40:08 I'll try that Sep 24 14:40:32 4 more Beaglebones to play with ^^ Sep 24 15:07:55 hmm ... I'm a systemd noob, but according to the systemd FAQ you choose which "target" systemd starts on bootup via the default.target symlink, however I do not see that in /etc/systemd/system on the lxde debian image (March 2015 image). Sep 24 15:08:06 how do I stop graphical.target from loading on bootup? Sep 24 15:08:31 or for that matter, how does systemd find out which targets to load on bootup on the beaglebone debian image... Sep 24 15:13:26 HI Sep 24 15:13:53 hi Sep 24 15:14:07 can anyone help to achieve the ip on beaglebone Sep 24 15:14:17 i am not getting ip with eth5 as interface Sep 24 15:17:07 what is that network interface? where is it connected to? Sep 24 15:18:38 I have connected beagle board via usb Sep 24 15:19:22 [ 205.505088] usb 2-1: new high-speed USB device number 7 using xhci_hcd [ 205.521763] usb 2-1: New USB device found, idVendor=1d6b, idProduct=0104 [ 205.521773] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [ 205.521778] usb 2-1: Product: BeagleBoneBlack [ 205.521782] usb 2-1: Manufacturer: Circuitco [ 205.521786] usb 2-1: SerialNumber: 0C-0515BBBK0741 [ 205.574340] usb-storage 2-1:1.4: USB Mass Storag Sep 24 15:20:00 after this i am getting a network interface a s Sep 24 15:20:03 eth5 Link encap:Ethernet HWaddr d0:39:72:39:ad:28 inet6 addr: fe80::d239:72ff:fe39:ad28/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:39 errors:0 dropped:0 overruns:0 frame:0 TX packets:159 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7358 (7.3 KB) TX bytes:36433 (36.4 KB) Sep 24 15:20:15 Guest23363, i'm confused, do you want use to answer here in irc or the beagleboard group.. Sep 24 15:20:51 here Sep 24 15:21:12 then why carpet bomb both? ;) Sep 24 15:21:42 I was not known to thi Sep 24 15:21:50 this* Sep 24 15:22:15 so how I can proceed to get the ip Sep 24 15:22:48 "sudo dhclient eth5" Sep 24 15:27:27 "sudo dhclient eth5" it is not coming up with anything Sep 24 15:27:59 Guest23363, what version of the rootfs "cat /etc/dogtag" Sep 24 15:29:34 root@harsh:/home/harsh# dhclient eth5 -v Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth5/d0:39:72:39:ad:28 Sending on LPF/eth5/d0:39:72:39:ad:28 Sending on Socket/fallback DHCPDISCOVER on eth5 to 255.255.255.255 port 67 interval 3 (xid=0xeb6f4434) DHCPDISCOVER on eth5 to 255.255 Sep 24 15:29:57 I am trying this on my ubuntu machine Sep 24 15:32:57 Guest23363, don't care about your ubuntu machine, just the version of the rootfs on the beagle.. "cat /etc/dogtag".. Sep 24 15:33:39 i am not able to login to my beagleboard Sep 24 15:33:48 as i am not getting the ip address Sep 24 15:34:20 Guest23363, just reflash with 2015-07-28, you probally ahve the ancient factory default http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-07-28 Sep 24 15:35:18 also i am not able to connect it through 192.168.7.2 Sep 24 17:12:35 <__butch__> offending bit being b.pinMode(inputPin, b.INPUT); Sep 24 17:12:47 <__butch__> Any thoughts? This is like the easiest thing ever. Sep 24 17:14:55 <__butch__> Here's a gist of the whole thing: https://gist.github.com/ButchAnton/793638ae3c18522e8f8c Sep 24 17:15:13 <__butch__> The jist has the three-line program, followed by the output of trying to run it. Sep 24 17:15:40 <__butch__> Either I'm having a very senior moment, or there's something fishy in Silly-con Valley. Sep 24 17:54:36 <[Butch]> Does anybody have any thoughts on my problem above (or in this gist: https://gist.github.com/ButchAnton/793638ae3c18522e8f8c ? Sep 24 17:54:53 <[Butch]> Namely, I can't get the simplest bonescript to work. Sep 24 17:56:22 Is anyone doing wireless sensor type things with beagle? xbee or 433mhz or something? Sep 24 18:53:02 ok so that's whacked, but, apparently lightdm starts from init scripts.... and there's a "graphical.target" in systemd Sep 24 18:53:19 kinda weird having to turn off X in two places (although I suspect the initscript was the only real place) Sep 24 18:54:17 starting the display manager from init.d is standard practice, no matter your desktop environment .. Sep 24 18:54:33 yeah, but, I thought systemd was supposed to get rid of all that... Sep 24 18:54:38 err no Sep 24 18:54:51 systemd just mucks around with launching and dependencies Sep 24 18:55:15 there's still a 'list' of what to start Sep 24 18:55:34 per run-level .. I don't think that's gonna change any time soon Sep 24 18:55:57 you have always been able to start multi-user without X via the runlevel choice Sep 24 18:56:07 not on debian or ubuntu Sep 24 18:56:12 oh yeah, I'm pretty familiar with how linux systems worked pre-systemd... Sep 24 18:56:33 well I am a systemd noob, but my "first impression" was that it would deprecate the runlevel concept Sep 24 18:56:49 ogra_ .. well they do have some .. interesting .. implementations .. Sep 24 18:56:55 debian based systems have never had any differences between runlevels Sep 24 18:57:03 in any case, this works well enough now :) Sep 24 18:57:25 ogra_ .. reluctantly I tend to agree .. there seems no way to change them .. or what's loaded in them .. Sep 24 18:57:39 sure, there are plenty of ways ... Sep 24 18:57:49 it is just that by default they are all the same Sep 24 18:57:57 dd if=/dev/zero .. lol ?! Sep 24 18:58:10 there is no such think like "multi-user" or "headless" runlevels Sep 24 18:58:12 that's a bit stupid .. imho.. lol. Sep 24 18:58:15 *thing Sep 24 18:58:20 not really Sep 24 18:58:30 it depends on your use-case though Sep 24 18:58:39 most users won't care Sep 24 18:58:49 (other than the single-user runlevel) Sep 24 18:59:13 I've not got debian into single-user ever .. yet .. Sep 24 18:59:31 even with a grub option .. Sep 24 18:59:44 it flies back into whatever Sep 24 19:00:39 when it works its all fine .. but if I wanna debug .. and it breaks 100% of the time .. lol .. really ain't helpful Sep 24 19:01:15 since most of my systems don't have a root password any more .. you gotta be able to get in somehow .. besides a usb boot stick and chroot :) Sep 24 19:08:05 veremit: recent versions seem to not ask for a password if there is no root password set Sep 24 19:08:57 vagrantc .. that would be good :) I've yet to do some upgrades to jessie .. Sep 24 20:45:50 pru pros: I’m implementing a network protocol using the PRU, and trying to use a circular buffer in shared DDR memory to pass messages Sep 24 20:46:03 a similar method to this: http://hipstercircuits.com/beaglebone-pru-ddr-memory-access-the-right-way/ Sep 24 20:46:26 is there a possible problem with concurrent accesses to DDR memory from the CPU and PRU? Sep 24 20:48:19 <_av500_> I would guess there is proper arbitration Sep 24 20:48:41 <_av500_> of course you should not read memory from one cpu that the other is writing Sep 24 20:48:52 <_av500_> also it should be uncached on the ARM side Sep 24 20:49:57 _av500_ yeah, obvs I either need a lock or some kind of lockless data structure Sep 24 20:50:34 <_av500_> which is easy for a circular buffer Sep 24 20:50:44 <_av500_> one cpu advances the wrote pointer Sep 24 20:50:48 <_av500_> another the read pointer Sep 24 20:50:53 <_av500_> write* Sep 24 20:51:21 yeah I did that. I’m still getting weird behavior, was hoping there was some dumb thing that I missed **** ENDING LOGGING AT Fri Sep 25 02:59:58 2015