**** BEGIN LOGGING AT Fri Oct 03 03:00:00 2014
Oct 03 03:38:15 <black_> Hi, I'm plugging my Beaglebone Black into my Debian Linux laptop but I can't get it to show up when I browse to http://192.168.7.2
Oct 03 03:38:34 <black_> Any ideas?
Oct 03 03:43:24 <strukturalna> do you have the element 14 board?
Oct 03 03:44:52 <black_> i don't believe so, i'll double check the description from the seller
Oct 03 03:45:07 <strukturalna> just look on the board
Oct 03 03:45:53 <strukturalna> it will have the beaglebone logo if it is the original producer
Oct 03 03:46:24 <black_> it has the beaglebone logo on the board
Oct 03 03:46:43 <ahills> anyone running openbsd on the internal memory?
Oct 03 03:46:50 <hewball> it has big lettering of element14 behing the ethernet connector
Oct 03 03:47:20 <strukturalna> the element 14 board has yea
Oct 03 03:47:51 <strukturalna> errr no, sorry
Oct 03 03:47:52 <black_> no, don't see any element14 text anywhere
Oct 03 03:47:56 <strukturalna> it's embest's logo
Oct 03 03:48:05 <strukturalna> which is the manufacturer for element 14
Oct 03 03:48:35 <black_> i don't think it is, i only see the beaglebone logo on the board
Oct 03 03:48:46 <strukturalna> ok cool you have the original board
Oct 03 03:49:06 <strukturalna> where did you buy it?
Oct 03 03:49:24 <black_> amazon, thought it was the official seller
Oct 03 03:50:24 <funkster> looking to create a kiosk - boot linux, load minimal window manager and browser - the page is pretty heavy jquery animation which RPi and BBB just cant handle, so am i looking at more processing speed that i need or?
Oct 03 03:50:27 <strukturalna> oh hmm, I have to check amazon
Oct 03 03:50:29 <black_> Here's the link to the one that I purchased http://www.amazon.com/gp/product/B00K7EEX2U/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1
Oct 03 03:50:52 <black_> I got Revision C
Oct 03 03:51:15 <strukturalna> ah ok, that looks like the element 14 board
Oct 03 03:51:24 <ahills> funkster: to run javascript, I recommend a core i7
Oct 03 03:51:48 <black_> really? how can you tell?
Oct 03 03:52:10 <funkster> ahills: i7? the hell?
Oct 03 03:52:21 <funkster> that would be overkill.
Oct 03 03:52:41 <strukturalna> well the picture shows an element14 board but that's just an image I guess
Oct 03 03:52:52 <strukturalna> if you have the beaglebone logo then they must be using the wrong image
Oct 03 03:53:20 <black_> oh ok
Oct 03 03:54:20 <black_> So, my power light is on, and USR0 is flashing normally, also USR2 appears to be lit
Oct 03 03:55:04 <black_> but when I go to the URL nothing is coming up
Oct 03 03:58:31 <black_> I'm connecting through USB
Oct 03 03:59:20 <strukturalna> I am not sure
Oct 03 03:59:47 <strukturalna> I'm still waiting for mine :(
Oct 03 04:00:12 <black_> oh ok
Oct 03 04:01:06 <strukturalna> I think the mailman stole it because he wants one too maybe
Oct 03 04:02:08 <black_> haha probably
Oct 03 04:02:12 <black_> where'd you order it
Oct 03 04:02:31 <strukturalna> ada
Oct 03 04:03:02 <black_> oh ok
Oct 03 04:55:06 <yates> i found a site that says you can use "resize2fs -M my.img" but it doesn't work for me. this is under fedora 20
Oct 03 04:56:05 <yates> resize2fs: Bad magic number in super-block while trying to open my.img
Oct 03 04:56:28 <yates> (use resize2fs to shrink the fs, that is)
Oct 03 05:00:40 <yates> the resize2fs man page says it works with ext2, ext3, and ext4. this is ext4
Oct 03 05:04:51 <yates> i can mount it as a ext4, but neither resize2fs nor "file" seem to recognize it as such.
Oct 03 05:07:25 <alainh> Hello everyone! I'm currently doing some wifi magic on my BBB but I'm running into some issues. Specifically I set my wlan0 interface to be an AP. However, now I cannot ssh via usb anymore. Is there any solution to this? I can provide more details.
Oct 03 05:16:43 <nyt-> it shouldn't be related
Oct 03 05:21:36 <alainh> Yeah, I'm not quite sure how this problem propped up. Could it be related to dnsmasq?
Oct 03 05:22:54 <yates> ssh in via usb?
Oct 03 05:23:09 <yates> how are you using your usb as a network interface?
Oct 03 05:25:02 <alainh> I think its configed by default in the debian image. It assigns a static ip to the usb0 interface
Oct 03 05:34:40 <yates> can someone confirm that the lastest deb images only have one partition - boot?
Oct 03 05:41:19 <yates> alainh: Section 1, item 9 here may help give you a clue on where to start. thanks to rcn. http://www.digitalsignallabs.com/kb-debian-bbb.htm
Oct 03 08:05:59 <yates> can someone confirm that the lastest deb images only have one partition - boot?
Oct 03 08:42:57 <Luke-Jr> Any ideas why a lot of RNDIS traffic causes my BBB to reset the USB after a few seconds? :/
Oct 03 08:58:53 <plaw> Luke-Jr: I dunno but I've heard tales that if one's using USB Wireless it's ideal to put the dongle at the end of a USB lead least it interferes with the board's EMF (or something like that)
Oct 03 09:01:11 <Luke-Jr> nope, just a direct USB cable
Oct 03 09:01:47 <KotH> Luke-Jr: could be many things, from problems with power to bugs in the musb code
Oct 03 09:02:07 <KotH> Luke-Jr: if you want to debug that kind of stuff you will need something like a beagle480
Oct 03 09:02:21 <KotH> Luke-Jr: and a good osciloscope
Oct 03 09:02:56 <KotH> everything is trial and error.. and mostly symptom fixing
Oct 03 09:04:33 <Luke-Jr> hm, it occurs to me that /dev/mmcblk1 may have swapped with /dev/mmcblk0 after rebooting it :|
Oct 03 09:04:58 <Luke-Jr> think I just bricked it if that is the case
Oct 03 09:07:56 <KotH> all hail detectable busses and the randomnes of detection order!
Oct 03 09:11:12 * Luke-Jr ponders how to debrick without a way to flash the microsd card :x
Oct 03 09:12:12 <KotH> you have a pc? no? so you can just write a new image on the sd card
Oct 03 09:13:19 <Luke-Jr> I have a PC without a SD card reader
Oct 03 09:13:31 <KotH> not even one of those usb thingies?
Oct 03 09:13:32 <Luke-Jr> the BBB was my uSD card 'drive'
Oct 03 09:13:36 <KotH> oh..
Oct 03 09:15:58 <Luke-Jr> that being said, I happen to have a spare BBB *yay*
Oct 03 09:16:06 <Luke-Jr> (and I found it)
Oct 03 10:16:54 <bort> Any expert on the PRU here?
Oct 03 10:25:36 <CareBear\> bort : just ask your question
Oct 03 10:54:41 <bort> Hey guys, I'm trying to create a decent bitbanged communication protocol using the PRU, and I'm having some issues. I posted this question here https://groups.google.com/forum/#!topic/beaglebone/IcMoTjEyUBo .
Oct 03 10:55:01 <bort> Could anyone help me? It would be most appreciated
Oct 03 10:55:10 <yates> can someone confirm that the lastest deb images only have one ext4 partition - boot?
Oct 03 10:55:28 <yates> e.g., bone-debian-7.6-console-armhf-2014-09-04-2gb.img
Oct 03 10:55:57 <yates> that's what it looks like when viewing it with gparted
Oct 03 10:58:16 <yates> bort: i am not clear on your current procedure - are you loading the pru for EACH BURST?
Oct 03 10:58:30 <yates> loading the program to the pru, that is?
Oct 03 11:00:19 <bort> yes, loading the program to the PRU, that's why I think its highly inefficient
Oct 03 11:00:37 <yates> yes, why are you doing that? the pru should only need to be loaded once.
Oct 03 11:01:04 <yates> you'd have to establish a flag in shared memory to synchronize the pru and user space code
Oct 03 11:01:48 <bort> That is exactly what I want to do, but having troubles
Oct 03 11:02:46 <bort> one question about that, If the ARM is reading a register in the shared memory, to see if the flag has been set, can the PRU still write to it?
Oct 03 11:02:55 <yates> a "newInputDataReady" flag - the bbb resets it before loading the pru code, then loads the pru code, then loads the memory, then sets the flag and waits for the pru interrupt. the pru when started waits for the flag, then processes the data when the flag is set, then resets the flag and generates the interrupt back to the bbb
Oct 03 11:02:56 <KotH> sure
Oct 03 11:03:06 <KotH> but concurency problems apply
Oct 03 11:03:28 <KotH> bort: i'm pretty sure there are example codes around for that kind of stuff
Oct 03 11:03:40 <bort> sorry, but what do you mean by concurrency problems?
Oct 03 11:04:00 <KotH> you have two processors accesing the same memory location
Oct 03 11:04:26 <yates> you sort that out with the flag and the interrupt
Oct 03 11:04:36 <yates> s/sort that out/prevent that/
Oct 03 11:04:39 <KotH> so A updates, B still reads old value until B's "copy" gets updated
Oct 03 11:05:02 <KotH> for a flag it's intended, but you have to keep in mind that the behaviour is not 100% deterministic, time wise
Oct 03 11:05:42 <yates> what behavior?
Oct 03 11:07:01 <bort> Ok, this makes sense. And do you believe the best is to use the Shared memory? Or should I try to use interrupts?
Oct 03 11:07:04 <KotH> http://en.wikipedia.org/wiki/Memory_coherence
Oct 03 11:07:28 <KotH> bort: i dont know the details of the PRU. as i said there msut be example codes around
Oct 03 11:07:37 <KotH> bort: you are definitly not the first one with this problem
Oct 03 11:08:16 <yates> is the shared memory between bbb and pru cached?
Oct 03 11:08:44 <yates> this is only a problem for cached memory.
Oct 03 11:11:41 <KotH> bort: do not private message people without being asked
Oct 03 11:11:42 <bort> I don't know if it is cached, I can look that up
Oct 03 11:11:46 <KotH> bort: it's considered rude
Oct 03 11:11:57 <yates> fine, bort, i'm outta here.
Oct 03 11:12:47 <bort> KotH : sorry, I don't know the etiquette rules for open IRC channels. My bad
Oct 03 11:12:59 <KotH> bort: #1: dont annoy people
Oct 03 11:13:11 <KotH> bort: #2: public discussions shall always stay public
Oct 03 11:13:59 <KotH> i also might just stand up and walk away from my desk, never to be seen again. then your question is lost and will never be answered
Oct 03 11:14:13 <KotH> not to mention people who know stuff better than i will never have the chance to see it
Oct 03 11:14:53 <KotH> interestingly, it's only #beagle where i get pmsgs with such regularity
Oct 03 11:15:02 * KotH wonders why
Oct 03 11:15:31 <bort> Maybe is because its full of IRC newbies, like myself
Oct 03 11:15:39 <KotH> also: who names their child bort?
Oct 03 11:15:41 <KotH> ;)
Oct 03 11:16:23 <KotH> other channels have n00bs as well
Oct 03 11:17:05 <bort> Anyways, thanks a lot for the help both in the PRU issue and in the IRC etiquette rules. Most enlightening
Oct 03 11:17:12 <KotH> np
Oct 03 11:17:18 <bort> And I know about the name, bad parenting choice from my folks
Oct 03 11:17:24 <KotH> lol
Oct 03 11:17:45 <KotH> i guess, you know that simpsons episode? :)
Oct 03 11:20:36 <bort> Yeah , I got your reference. And my facebook wall is full of , so called friends, posting me photos of a can of coke with the name "bort" on it
Oct 03 11:21:05 <KotH> uh.. poor you!
Oct 03 13:05:52 <mike7b4_on_x230> Hi, I am trying kernel 3.12.13 with SGX driver 5.01.01.01 but geting     egl error 'EGL_BAD_ALLOC' (0x3003) when running eglinfo or similar apps? Can someone tell me what can be wrong?
Oct 03 13:09:19 <woglinde> mike7b4_on_x230 maybe 5.01.01.01 does not work with 3.12.13?
Oct 03 13:11:03 <mike7b4_on_x230> woglinde: Could be, but drivers loads without errors
Oct 03 13:16:00 <thisisbrians> unrelated to the channel...but does anyone in here use tmux on os x?
Oct 03 13:16:05 <honestly> mrrgh. I had debian eabi booting on a BBxM in like 10 seconds, then I made some updates and now it takes a minute or so for the serial terminal to come up
Oct 03 13:16:11 <honestly> how do I debug that...
Oct 03 13:16:35 <thisisbrians> i'm trying to bind to the cmd key in my .tmux.conf, but no dice so far
Oct 03 13:26:32 <honestly> god damn. it takes 6 minutes for the terminal and ssh to come up.
Oct 03 13:28:18 <honestly> systemd claims startup took 1 minute 52s
Oct 03 13:28:25 <honestly> grr.
Oct 03 13:29:58 <shiniest> sounds like a something you autostart after the OS booted up
Oct 03 13:30:47 <honestly> explain wtf you mean by that
Oct 03 13:34:42 <shiniest> well, if systemd claims that it was done after ..roughly 33% of the time your system needed to get to somewhere where you where responsive, I'd say that whatever took the rest of the time was taking 6 minutes to start up wasn't logged by systemd,...so it might be something that was started after systemd did its deed....I'd look for network agents
Oct 03 13:38:47 <honestly> how exactly would that stop getty or even sshd from starting up
Oct 03 13:46:43 <shiniest> I'm not sure. But if something that negotiates the pecularities of your network isn't ready, it means that sshd does not even receive any data it could handle. Not sure how it is handled, maybe sshd isn't started until the network is pretty much there. I'm not too certain of the whole thing, just remembered that once I had a system that took 2+ minutes to boot up because of my network agent programs taking a long while to finsih
Oct 03 13:46:43 <shiniest> configuration
Oct 03 13:54:03 <honestly> something starts ntpdate. grah.
Oct 03 13:55:42 <Humpelstilzchen> debian always executes ntpdate on ifup
Oct 03 13:55:56 <honestly> that's absolutely terrible
Oct 03 13:56:03 <Humpelstilzchen> I like that
Oct 03 13:56:27 <Humpelstilzchen> but at least on non-system thats done in the background
Oct 03 13:58:02 <honestly> if I chmod -x the files in /etc/network/if-up.d will it ignore them?
Oct 03 13:59:58 * Humpelstilzchen would just remove systemd and install sysvinit...
Oct 03 14:00:14 <honestly> ...because why?
Oct 03 14:00:45 <honestly> there's no universe where sysvinit gets faster to a login prompt or reachable ssh than systemd.
Oct 03 14:02:11 <Humpelstilzchen> I thought I just read otherwise
Oct 03 14:03:01 <honestly> performance is one of the main priorities of systemd and I haven't seen anyone suggest that it isn't doing well at that
Oct 03 14:03:24 <KotH> Humpelstilzchen: nope, debian does _not_ execute ntpdate on ifup
Oct 03 14:03:39 <Humpelstilzchen> KotH: yes it does
Oct 03 14:03:46 <honestly> KotH: then why is there an ntpdate script in /etc/network/if-up.d?
Oct 03 14:03:49 <KotH> Humpelstilzchen: it will be executed during boot, after network is brought up, if configured that way (you can switch it off)
Oct 03 14:03:49 <Humpelstilzchen> at least if ntpdate is installed
Oct 03 14:03:58 <KotH> honestly: i dont have that
Oct 03 14:04:28 <honestly> KotH: I didn't put it there.
Oct 03 14:04:32 <KotH> hmm...
Oct 03 14:04:42 <Humpelstilzchen> KotH: do you even have ntpdate installed?
Oct 03 14:04:48 * KotH wonders whether that is a relict of having ntpdate installed for decades
Oct 03 14:05:24 <Humpelstilzchen> KotH: https://packages.debian.org/wheezy/armhf/ntpdate/filelist
Oct 03 14:05:42 <KotH> Humpelstilzchen: hm...
Oct 03 14:05:45 <KotH> weird
Oct 03 14:06:03 * KotH goes back into his hole and tries to figure out why he doesnt have that file
Oct 03 14:06:48 <honestly> you know what, this might totally be a result of having a dodgy sdcard...
Oct 03 14:06:56 * honestly tries different sdcard
Oct 03 14:13:52 <honestly> different class 4 sdcard, no apparent difference
Oct 03 14:14:08 * honestly sets up class 10 sdcard
Oct 03 14:23:33 <honestly> that appears to be a good bit snappier.
Oct 03 15:38:19 <buzzsaw> good morning
Oct 03 16:28:22 <ecdhe> Page 51 of the BBB System Reference Manual says that P9-18 is 'spi0_d1' and P9-21 is 'spi0_d0'.
Oct 03 16:28:53 <ecdhe> I assumed that the 1 meant 'in' and the 0 meant 'out'.
Oct 03 16:29:48 <ecdhe> But my scope seems to show that the BBB is writing data out on P9-18.
Oct 03 16:29:56 <ecdhe> Is that expected?
Oct 03 17:10:03 <BusMaster> I installed the wheezy demo image from http://elinux.org/BeagleBoardDebian and booted with it on a beaglebone white. There are no *.dtbo files in /lib/firmware or anywhere else under /. How can I get them? I would like to use generate a PWM signal and use the eQEP devices
Oct 03 17:11:19 <BusMaster> I probably need to echo the correct .dtbo file to /sys/devices/bone_capemgr.8/slots to get the thing rolling, right?
Oct 03 17:27:44 <smurray> ecdhe: you do have it backwards, spi0_d0 is input (MISO), spi0_d1 is output (MOSI)
Oct 03 18:39:04 <GJN> Hello Guys
Oct 03 18:43:52 <ecdhe> smurray, thanks!
Oct 03 18:44:08 <smurray> no problem
Oct 03 18:44:43 <ecdhe> When in doubt, trust the oscilloscope.
Oct 03 18:45:11 <ecdhe> I was looking at this page, which lists the IO direction wrong:
Oct 03 18:45:12 <ecdhe> https://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/spi
Oct 03 18:52:08 <Kellen> I am trying to flash a BBB and am getting the strangest behavior. When flashing with the EMMC flash file, it appears to start working, then all of a sudden all 4 leds will blink in unison and the board will then shut down, after removing the sd card and rebooting nothing happens.
Oct 03 18:52:11 <Kellen> Help please
Oct 03 19:05:49 <woglinde> Kellen connect a serial ftdi alike cable and look the problems up yourself
Oct 03 19:10:32 <Kellen> I have done that, it is not descriptive enough to tell me what is wrong.
Oct 03 19:12:38 <honestly> am I going to run into problems debugging armhf binaries with an armel gdb?
Oct 03 19:12:41 <woglinde> yes but you did not share it with us
Oct 03 19:12:53 <woglinde> honestly yes I think so
Oct 03 19:13:03 <honestly> blargh.
Oct 03 19:13:23 <woglinde> hm hm
Oct 03 19:13:29 <woglinde> depends
Oct 03 19:13:46 <woglinde> where do you run the gdb as client?
Oct 03 19:13:59 <honestly> on a beagleboard xM...?
Oct 03 19:14:01 <woglinde> than it maybee works
Oct 03 19:14:14 <honestly> well yes, it's an armhf machine
Oct 03 19:14:15 <woglinde> Kellen pastebin the serial console output
Oct 03 20:07:30 <HoloPed> Does the BB have a 5mp camera, like the PI ?
Oct 03 20:13:07 <honestly> lol
Oct 03 20:17:10 <HoloPed> lol?
Oct 03 20:18:15 <honestly> yes. I find that question amusing.
Oct 03 20:19:46 <HoloPed> Why ?
Oct 03 20:37:21 <thurgood> the PI has a camera?
Oct 03 20:38:54 <thurgood> I think they both have addon boards for cameras
Oct 03 20:47:56 <HoloPed> thurgood, yes. An addon board. The PI has a 5mp addon camera.
Oct 03 20:49:00 <thurgood> only cape I know of for the bbb is 3.1MP
Oct 03 23:33:05 <beagleangstrom> hhii
Oct 03 23:33:25 <beagleangstrom> cananyone help me regarding beaglebone on angstrom?
Oct 04 02:02:46 <yates> is there some known problem with debian on the beagle and systemd? i've installed a .service file like this: http://paste.fedoraproject.org/139085/12386938
Oct 04 02:03:16 <yates> but "systemctl enable easld" doesn't work
Oct 04 02:32:27 <zsnafu> evening
Oct 04 02:33:21 <zsnafu> i was looking in the trm for the bbb's processor
Oct 04 02:33:28 <zsnafu> was trying to find the uart fifo buffer size
Oct 04 02:36:25 <zsnafu> found it n/m
**** ENDING LOGGING AT Sat Oct 04 03:00:00 2014