**** BEGIN LOGGING AT Thu Dec 11 02:59:58 2014 Dec 11 03:11:29 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC Dec 11 03:19:08 py0: How are you trying to install FreeBSD? Dec 11 03:19:27 well.. I want to do it using that method ^ Dec 11 03:19:55 but on https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack it says a known issue is "no emmc device or unstable operation of emmc" Dec 11 03:20:00 I don't want to brick my beagle Dec 11 03:20:07 What, the steps to flash a prebuilt debian disk image? Dec 11 03:20:24 it came with debian on it Dec 11 03:20:30 That is not going to work, unless you have a source for similarly prebuilt FreeBSD images. Dec 11 03:20:45 Yes, all of them do. Debian is the supported operating system. Dec 11 03:20:46 ..? there is a freebsd beaglebone image Dec 11 03:21:00 And you are doing what with that image? Dec 11 03:21:14 it's on a microsd card.. I want to get rid of debian and have freebsd Dec 11 03:22:20 py0: https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack Dec 11 03:22:30 py0: OK, take a step back, breathe, and clearly state what you are trying to do, how you are trying to do it, and how it is failing to do what you expect. Dec 11 03:22:38 I just pasted that link vvu Dec 11 03:22:45 IVE SAID IT MULTIPLE TIMES Dec 11 03:23:02 py0: Yes, but I am not following it very well. Dec 11 03:23:21 i've got a beaglebone with the latest debian installed. connected to it is a USB device that works great for a few days - then stops working entirely (the light turns off, even). dmesg shows this error: CAUTION: musb: Babble Interrupt Occurred Dec 11 03:23:26 py0: Help me help you. Dec 11 03:23:26 i think (s)he is wanting to install freeBSD but using the m,ethod outlined for flashing the Debian image and is that possible / practical Dec 11 03:23:32 least thats what i got from it Dec 11 03:23:33 i haven't found really any solid solutions online - anyone got any ideas? Dec 11 03:23:35 /lurk Dec 11 03:23:51 loans: USB on the bone sucks. Avoid use. Dec 11 03:24:02 py0: if you want to flash a binary on the eMMC without making any uSD card you can use https://github.com/ungureanuvladvictor/BBBlfs Dec 11 03:24:04 I own a beaglebone black rev c that shipped with debian on it. I own a microsd card that I wrote a freebsd img to using dd. I want to install the freebsd beaglebone image to my beaglebone black, completly replacing debian in its entirety Dec 11 03:24:16 if that is not clear enough I'm gonna smash my brains out with a log Dec 11 03:24:24 py0: And booting off the uSD card is unacceptable? Dec 11 03:24:33 yes, entirely unacceptable Dec 11 03:24:41 You *must* have the FreeBSD installed to the eMMC...why? Dec 11 03:24:46 performance Dec 11 03:24:52 ...performance? Dec 11 03:25:01 it's going to be a webserver Dec 11 03:25:05 So? Dec 11 03:25:20 I don't want to be booting off an external drive Dec 11 03:25:26 such as a microsd card Dec 11 03:25:32 Anyone use ALSA? I'm experiencing what I think are buffer underruns. ALSA's speaker-test tool, for example, has little pops and crackles periodically as it plays. I'm using a USB audio output dongle on BBB. The same dongle works fine on Ubuntu in a VM on my Mac. Dec 11 03:25:40 The builtin uSD slot is hardly an "external drive". Dec 11 03:25:40 py0: have you actually confirmed that the microsd isn't sufficiently performant for your needs? Dec 11 03:26:05 But in any case, I cdoubt you will see any better disk performance from the eMMC than with a good uSD card. Dec 11 03:26:19 it doesn't matter if it is or not.. I paid $55 for this thing and I want everything I can get out o fit Dec 11 03:26:22 After all, they are effectively the same type of memory, on similar interfaces. Dec 11 03:26:46 OK. Dec 11 03:27:12 So, what steps have you taken to install FreeBSD to the eMMC, and how have they failed? Dec 11 03:27:30 I'm not sure if I should because there has been debate about the docs at https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack Dec 11 03:27:40 I'm afraid if I take the step with http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC that it will brick my beagle Dec 11 03:27:57 Fortunately, there is an image that unbricks the bone. Dec 11 03:28:01 So, no harm no foul. Dec 11 03:28:08 that doesn't make sense to me Dec 11 03:28:13 How so? Dec 11 03:28:14 I thought once you bricked a device.. that's it Dec 11 03:28:27 where is this image you speak of Dec 11 03:28:30 Not when you have a device inj your hand that is designed to be unbrickable. Dec 11 03:28:43 what makes it unbrickable Dec 11 03:28:44 Linked somewhere off one of the begineer tutorials. Dec 11 03:29:05 py0: The bootloader can be sourced from a uSD card. Dec 11 03:29:20 So if you manage to screw it up on the device, you jsut fix it with a card image. Dec 11 03:29:31 I have no idea how to do any of that Dec 11 03:29:38 I know almost nothing of the bootloader Dec 11 03:29:45 py0: For a more detailed answer, read up on how uBoot works, and how the bone's boot sequence operates. Dec 11 03:29:57 But that is irrelevant right now. Dec 11 03:30:08 Simply knowing it can be done should be sufficient safety net. Dec 11 03:30:35 I'm just going to pickup with this in the morning Dec 11 03:30:39 OK. Dec 11 03:30:48 I am so pissed at this point that it is not an enjoyable experience right now Dec 11 03:30:56 have a good night and thank you for your help Dec 11 03:31:33 agmlego: is the source of USB shittiness known? some people have intimated that newer kernels would be somewhat less shitty Dec 11 03:31:52 py0: Also, for reference: a) this channel is made solely of volunteers b) there is no warranty or promise of support for a dev board, especially with an unsupported OS c) it is poor form in an IRC channel to specifically call out individuals unless they told you you could; anyone can help. Dec 11 03:32:41 loans: From what I hear, musb is the devil's own spawn and was a bad idea since the Big Bang. But hey, I know nothing of the issue, and I attempt at all costs not to use USB for things I care about. Dec 11 03:32:57 py0: But, good night, and good luck. Dec 11 03:33:04 bummer Dec 11 03:33:13 loans: What do you need USB for? Dec 11 03:33:25 USB makes my current task slightly easier Dec 11 03:33:31 How so? Dec 11 03:33:33 i guess I can contrive to connect to one of the uarts Dec 11 03:33:41 it means less soldering and similar fuckery Dec 11 03:34:00 using one of these https://www.sparkfun.com/products/9963 Dec 11 03:34:35 Yeah, definitely just use UART. Dec 11 03:34:57 that shouldn't change the code much Dec 11 03:35:05 Nope. Dec 11 03:35:12 Wonderful thing about serial. Dec 11 03:36:27 other than that the beaglebone has been doing great Dec 11 03:36:36 Yup. Dec 11 03:36:59 guess i'll get a couple breakouts for these rfid modules Dec 11 03:37:03 Basically keep in mind the board was designed a) to be cheap b) to have a shitload of GPIO c) to fit into an Altoids tin. Dec 11 03:37:19 oh no doubt Dec 11 03:37:19 It is a dev board, an experimental system. Dec 11 03:37:29 There will be warts; one of those happens to be USB. Dec 11 03:37:38 i'm nailing them to the doors on a hackerspace Dec 11 03:37:44 we get experimental stuff Dec 11 03:38:08 ....yeah just use a UART then. Pony up the iron and be done with it. ;-P Dec 11 03:38:20 Or, you know, OpenAccess. ;-P Dec 11 03:38:41 we're rolling our own backend at the moment Dec 11 03:38:51 that replaces the CRM we've been using for member management Dec 11 03:39:08 Sure. Dec 11 03:39:31 i3Detroit is working on some things similar, looking at a new CRM and OpenAccess. Dec 11 03:39:45 is that where you're at? Dec 11 03:40:09 if you haven't committed yet, I'm trying to convince some folks to pick up ours and help with development Dec 11 03:40:39 We already have several OpenAccess boards fully working. Dec 11 03:41:07 Any C hackers about? I'm reading through one of the PRU examples and I'm having trouble following lines 98-104 of one of the header files in the provided package: https://github.com/beagleboard/am335x_pru_package/blob/master/pru_sw/app_loader/include/pruss_intc_mapping.h Dec 11 03:41:07 I know that HackForge over in Windsor also wanted to try getting in on what we were doing; less DIY and more standardisation. Dec 11 03:41:34 It's a #define but I'm not familliar with the curly bracket syntax Dec 11 03:41:36 yeah. i think another space running our auth system would do a lot for making it better, faster Dec 11 03:41:50 loans: Or, you co-opting another space's ;-P Dec 11 03:42:01 we're pretty invested at this point Dec 11 03:42:05 loans: What space? Dec 11 03:42:09 pumping station: one Dec 11 03:42:13 Oh, hey! Dec 11 03:42:24 Yeah, I have heard about your guys' project too. Dec 11 03:43:00 entry is working pretty well Dec 11 03:43:33 i think 30 people have added tags to the system Dec 11 03:45:00 Yeah, OAC is 100% hardware-complete, just waiting the CRM backend to make it more useful than the eBay special currently running our door. Dec 11 03:45:55 oh, i think the old system here was based on that Dec 11 03:46:03 but someone put that together and didn't make it manageable Dec 11 03:46:40 loans: Hence why we are waiting until the backend exists before changing. Dec 11 03:47:09 reasonable Dec 11 03:48:30 abzman over in #i3detroit did most of the code work for our OAC system--we inevitably added things. Dec 11 03:49:16 And last I heard, kd8wcr was looking into a replacement for SeltzerCRM, which we can actully get support for and make extensions to. Dec 11 03:50:00 this is what we're working on Dec 11 03:50:01 https://github.com/hef/ps1auth Dec 11 03:51:30 Yeah. Dec 11 03:53:33 i'm also going to have to implement a buzzer of some sort Dec 11 03:53:44 becuase that's currently built into the usb breakout Dec 11 03:54:05 And not accessible from UART? Dec 11 03:56:39 agmlego: if I ditch the USB board then i lose the buzzer Dec 11 03:56:52 OK. Dec 11 03:56:59 the rfid module has a buzzer output but you've got to put together a driver and stick a buzzer on it Dec 11 03:57:05 Not that big a loss--piezos are easy to drive. Dec 11 03:57:38 it adds work Dec 11 03:58:09 Yeah, but not much, and the system will work better for it. Dec 11 04:53:43 Another C or general memory management question. In the examples of PRU communication, when the goal is to show how the PRU can write to its memory using local or global addressing, the 'test' is to have the PRU write 64 bits to its own memory as two ints, the first using an address in the local memory map and the second using an address in the global memory map. Then the C (BBB cpu, i.e. non-PRU) side of the process reads the data Dec 11 04:53:43 at that location and checks to make sure it's what was expected. So far so good. However, when the BBB is getting set up, before it runs the code on the PRU, it gets a pointer to the PRU's memory and zeros out the 64 bits to be used in the test. What is the point of this? The PRU should just overwrite those locations anyway, no matter what was in them, right? Dec 11 04:54:45 All this is in the example apps at https://github.com/beagleboard/am335x_pru_package/tree/master/pru_sw/example_apps/PRU_memAccessPRUDataRam Dec 11 04:56:04 Maybe they're just showing how to write to that memory from the cpu-side? anyway, it was pretty helpful to have the example. Dec 11 11:03:42 i'm a bit confused. can i actually use uart5 on the bbb or not? i need 4 uarts: aside uart1, uart2 and uart4 i see that uart5 is the only one left with both tx/rx signals, but then i don't undestand if i can modify the pin mode of P8-37 and P8-38 (given that i'll use them AFTER the mcu startup phase, of course) Dec 11 11:04:15 for example, the config-pin script says "Pin is not modifyable: P8_37 lcd_data8" Dec 11 11:42:18 I created a custom cape for my beagle bone, and each time I put it on the beagle bone, within several seconds my beaglebone starts to throw I/O-errors in the memory, resulting in a re-mount read-only of the memory, and after some minutes shutdown. What can be the reason for that? If needed, I can provide the schematics of my cape, too. Dec 11 11:42:23 Thanks! Dec 11 12:05:06 Hi all, been using serialport on beaglebone black for a good few weeks now. love it. but had to rest BBB back to factory settings (debian image) and serialport will no longer install or build with npm can anyone help Dec 11 12:52:46 What is the drawback of omitting the eMMC-Module? Can't I save anything anymore, or are there more drawbacks? Dec 11 13:33:35 anates: ? Dec 11 13:38:34 hi Dec 11 13:38:51 anybody here runnig latest u-boot on beaglebone (white) Dec 11 13:39:05 I have an issue with watchdog -> board is not reset after timeout Dec 11 14:03:32 @av500: I found it out, board does not boot anymore... Dec 11 14:03:42 ? Dec 11 14:03:44 sure it boots Dec 11 14:03:47 from sd card Dec 11 14:03:49 serial Dec 11 14:03:50 usb Dec 11 14:04:24 but not from the preinstalled software anymore -> I have to copy the operating system on the sd card Dec 11 14:05:03 btw., which cape behaviour can result in a memory I/O-problem on the beagle bone? Dec 11 14:07:15 well, if your SW is on the emmc and you remove the emmc, then yes it wont boot Dec 11 14:08:01 if your cape collides with the eMMC pins, yes that might be a problem Dec 11 14:08:13 refer to the SRM for further details Dec 11 14:09:27 that means if my cape uses some pins which are reserved for the emmc, even if I never control them directly (i.e. because I only used two pins for testing on the cape, but all were connected) it can result in data loss? Dec 11 14:09:59 well it can interfere with the emmc Dec 11 14:10:33 even if these pins are only connected to inputs and outputs of an IC without me controlling the IC? Dec 11 14:11:48 ja Dec 11 14:12:47 ok, that could solve a lot of my problems, thanks! Dec 11 14:15:29 Hi everyone. Got a question, any luck with using crypto module on am335x? Tried to use cryptodev, enabling modules of aes and sha in kernel config, no luck. Dec 11 14:15:40 using kernel 3.14 mainline Dec 11 14:50:08 I put my custom device tree into lib/firmware, compiled it, and now I wanted to echo it into slots, But I get the error "No such file or directory". Why? Dec 11 15:06:07 anates: look in dmesg which file it is actually trying to laod. Dec 11 15:06:10 load even. Dec 11 15:06:23 It might append a version number to the filename, for instance. Dec 11 15:09:03 Peanut: Error is "Failed to load firmware" Dec 11 15:11:01 what is it supposed to mean if you just hang at lianli# cu -l /dev/ttyU1 -s 115200 Dec 11 15:11:01 Connected Dec 11 15:13:24 py0: On what system are you typing that? If you are trying to connect to your BBB over serial, how is it connected? Dec 11 15:13:33 Have you tried hitting 'Enter' to get a response? Dec 11 15:13:33 freebsd Dec 11 15:13:36 yes Dec 11 15:14:02 it's connected with the 4-pin adafruit usb to ttl cable Dec 11 15:14:08 red pin is not on Dec 11 15:14:21 1 - black, 4 - green, 5 - white Dec 11 15:15:05 What you can do is first of all verify that the cable works by connecting the Rx and Tx pin together. Then everything you type should be echoed back. Once you verified that, you can look at why the BBB isn't replying. Dec 11 15:15:29 how do I connect them.. Dec 11 15:16:17 Put a small piece of wire into the white and green pins, connecting them together. A jumper cable for a breadboard would be perfect. Dec 11 15:16:45 I don't own any of that :| Dec 11 15:16:58 I got a basic setup so I can turn it into a webserver Dec 11 15:17:11 I have no shiny toys for my beagle :[ Dec 11 15:17:28 Ah ok - not even a resistor or something that you can clip a leg off? Dec 11 15:17:39 py0 it ships running Express (node.js) and Apache. Dec 11 15:17:41 nope Dec 11 15:17:44 nginix is trival. Dec 11 15:17:48 trivial even Dec 11 15:17:53 I like nginx Dec 11 15:18:08 Why do you need the serial over USB then, can't you just connect to it over the USB port? Dec 11 15:18:11 I have the element14 version with debian Dec 11 15:18:21 freebsd says we can't do that Dec 11 15:18:23 no serial over usb Dec 11 15:18:27 py0: did you get that link I gave yesterday with the serial hookup? Dec 11 15:18:39 yeah Dec 11 15:18:39 oh, right, forgot you were doing FreeBSD. Dec 11 15:18:45 py0: and ethernet over USB? Dec 11 15:18:52 Don't want ethernet over usb Dec 11 15:18:56 what's wrong with serial Dec 11 15:19:24 I'm only trying to help you connect to it. If your reply is "Don't want", there's not much I can help with. Dec 11 15:19:44 Well, I don't want it because all too often people circumvent issues and that's not the way to go Dec 11 15:19:46 http://shallowsky.com/blog/hardware/talking-to-beaglebone.html seems to have a pic. Dec 11 15:19:53 I just want help solving the problem not avoiding it Dec 11 15:19:56 black green and white wires. Dec 11 15:20:06 it's already wired properly Dec 11 15:20:19 running at 115200 baud? N81? Dec 11 15:20:30 I just use cu -l /dev/ttyU1 -s 115200 Dec 11 15:20:58 what do you capture at boot? nothing? Dec 11 15:21:22 nothing.. I plug it in, enter that cu command and it hangs repeatedly after Connected Dec 11 15:22:11 If you can't try the loopback (using a piece of wire), you could try to replace cu with something else. Not sure whether cu depends on any hardware handshake. You could try picocom if that's available for FreeBSD. Dec 11 15:22:26 if you don't get anything, then you aren't likely running the ROM bootloader. Dec 11 15:22:29 er... Dec 11 15:22:38 that is, you aren't likely running the Serial bootloader. Dec 11 15:22:47 from the ROM... which should spit out some values... Dec 11 15:23:01 and if there isn't a valid boot image, you should get to the serial boot. Dec 11 15:23:09 I personally use 'screen' most of the time. Dec 11 15:23:19 'screen /dev/ttyUSB0 115200' Dec 11 15:23:22 Good question, does the BBB boot? What image are you running on it? Dec 11 15:23:49 It comes with element14's debian Dec 11 15:23:55 I'd at least test the serial connection by booting the Debian image. Dec 11 15:24:11 the microsd card isn't in and it still hangs after connected Dec 11 15:24:17 k, so you are just trying to monitor the out-of-box boot right now? Dec 11 15:24:23 yeah Dec 11 15:24:25 Linux doesn't boot at all? Dec 11 15:24:31 not right now it doesn't Dec 11 15:24:33 no blinky LEDs? Dec 11 15:24:38 yeah blinkys Dec 11 15:24:50 you do see blinky LEDs? Dec 11 15:24:55 on all USRs Dec 11 15:25:09 if you see blinky LEDs, then your issue is your serial connection (hardware or softare)... Dec 11 15:25:24 guaranteed that the Linux is spitting out all sorts of stuff on serial. Dec 11 15:26:41 I tried this 'screen /dev/ttyUSB0 115200' Dec 11 15:26:46 without the quotes obv Dec 11 15:26:49 no dice Dec 11 15:26:56 said it could not exec, screen terminating Dec 11 15:27:52 I just got this to come up https://gist.github.com/anonymous/fd11a6b1565941318c4e Dec 11 15:27:58 it hangs at DRAM Dec 11 15:28:21 py0: the name of your serial port is not ttyUSB0, that's what it would be on Linux. Dec 11 15:28:51 check link? Dec 11 15:29:22 py0: did you just get this on your serial port then? So u-boot works, but stuff crashes during boot, it seems? Dec 11 15:29:40 I guess so Dec 11 15:31:14 Either your serial communication broke down, or your BBB. If the LEDs are still flashing, you could assume the OS is actually booted succesfully. Dec 11 15:32:28 I think it's serial Dec 11 15:33:01 https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack Dec 11 15:33:06 Problem: Serial console dies upon reboot. Dec 11 15:34:15 Eh wait.. are you running FreeBSD on the BBB, I thought you had it running on your Desktop. Dec 11 15:34:42 noth Dec 11 15:34:44 both* Dec 11 15:34:47 :D Dec 11 15:34:53 Ahh... Dec 11 15:35:47 Well, you must have read their comments on the serial problem if you use an adafruit cable, and their 'resolution'. Dec 11 15:36:06 This kernel panic is under debian: https://gist.github.com/anonymous/0fda045b60f1d09ed322 Dec 11 15:36:22 what resolution Dec 11 15:36:52 "But I can reliably solve it by leaving the serial cable attached, then removing and re-applying power" Dec 11 15:37:10 oh.. I don't think that's a good resolution haha Dec 11 15:37:23 doesn't it damage the bbb to just pull the power cord Dec 11 16:19:36 py0: how does removing the power damage bbb? Dec 11 16:19:50 improper shutdown for hardware..? Dec 11 16:19:59 i have seen the warning sticker but dont understand it Dec 11 16:20:15 I don't understand damn near any of this Dec 11 16:20:21 I wish there was a lot more documentation Dec 11 16:21:01 my guess is that it just warns the risks it causes for the filesystem Dec 11 16:21:27 but that's just a guess Dec 11 16:24:07 There might also be the risk of providing CPU pins with power while the CPU itself is unpowered. Dec 11 16:47:40 insserv: Starting led_aging.sh depends on rmnologin and therefore on system facility `$all' which can not be true! Dec 11 16:47:51 after apt-get remove apache2 on debian with bbb Dec 11 16:48:05 got thousands of lines like that Dec 11 16:49:27 py0 just remove /etc/init.d/led_aging.sh it's a random hack embest stuck in their image.. Dec 11 16:50:07 or use the offical image: http://beagleboard.org/latest-images (if i ever meet the idoit who did that, i'll give him a yelling..) Dec 11 16:50:40 sweet man, deleting the .sh file worked Dec 11 17:52:35 rcn-ee: i don't think you were here when i mentioned that my lab radiation tested BBB to 14krad with no dmage Dec 11 17:55:02 johnwalkr, that's very cool to hear!! Dec 11 17:55:23 yeah, it rebooted twice but nothing broke Dec 11 17:55:45 there's a satellite with 2 raspberry pis on orbit now too.. Dec 11 17:55:45 Good morning everybody! Dec 11 17:56:12 Has anyone tried USB-OTG on kernel 3.15+? Dec 11 17:56:17 i met the designer, he prefers BBB over rpi but chose rpi to avoid using usb (since the camera interface is exposed on rpi) Dec 11 17:56:52 specialy in space, who know's what the MUSB ip would do! ;) Dec 11 17:57:04 well Dec 11 17:57:15 I wouldn't know what MUSB would do when it's sitting on my desk... =( Dec 11 17:57:28 it was fine in thermal vacuum testing and vibration testing ;) Dec 11 17:58:11 That's still so cool, thanks for sharing! Dec 11 17:58:25 when i can i'll let you know more Dec 11 17:58:29 when it's published and such Dec 11 17:58:51 i know everyone behind bb.org would like to see that! Dec 11 19:44:50 hi johnwalkr Dec 11 19:44:57 very cool news about the 14krad! Dec 11 19:45:22 johnwalkr: you can use the PRUs to create a camera interface on BBB. Dec 11 20:03:03 rcn-ee: ping Dec 11 20:07:57 vvu, pong Dec 11 20:09:59 rcn-ee: any clue how to pass the environment variables in the early_chroot_script. i need to have ${rfs_username} and the rest Dec 11 20:13:37 vvu, yeap, source ". /etc/rcn-ee.conf" which has: https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L365 Dec 11 20:14:17 but in early_chroot_script i am not in the chroot. is that available ? Dec 11 20:14:21 or ". /etc/oib.project" which should be the full *.conf used for building: https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org.sh#L34 Dec 11 20:14:33 oh true... Dec 11 20:14:46 i need kinda to source the .config file Dec 11 20:15:20 if you pass tempdir, it'll be right there... Dec 11 20:15:30 perfect if so Dec 11 20:16:46 Hi everyone. Using mainline 3.14.16 kernel., beaglebone black am3358. In kernel there are two drivers: omap_sham for sha and md5 crypto hw and omap_aes for aes crypto hw. In /proc/interrupts i can only see omap_sham and while using it I see that it is used. However I cannot bring omap_aes up, anyone had this problem? Dec 11 20:19:24 so . /${tmp_dir}/oib.project you say ? Dec 11 20:21:27 ${tempdir} is the full path so : ${tempdir}/etc/oib.project (probally have to exprot tempdir in scripts/chroot.sh) Dec 11 20:25:18 rcn-ee: nop, does not work. oib.project is copied just for the chroot_script not the early one Dec 11 20:26:47 vvu, we can move it earlier, as it's just a copy of the .project file and it should be useful to any early chroot scripts.. Dec 11 20:28:42 ok so another pull request on the way :) Dec 11 21:09:02 I have my beaglebone black successfully connected to the internet.. and it's also running nginx. When I go to the ip though it shows the beaglebone page and not my index.html file Dec 11 21:09:08 what am I supposed to do about this Dec 11 21:09:48 py0: is this the debian image or the FreeBSD you were setting up? Dec 11 21:09:58 debian Dec 11 21:10:08 I had to drop the fbsd image because it has too many errors Dec 11 21:10:34 well, are you browsing to the nginx port or port 80 (default)? Dec 11 21:10:54 the nginx port should be port 80.. because that's http Dec 11 21:13:17 you need to 'systemctl disable bonescript.service; systemctl disable bonescript.socket' to get port 80 back. Dec 11 21:15:07 jkridner, are those preserved through reboot Dec 11 21:15:19 and/or shutdown Dec 11 21:16:50 yes Dec 11 21:17:06 rm '/etc/systemd/system/sockets.target.wants/bonescript.socket' Dec 11 21:17:07 Use 'stop' to stop them and 'disable' to prevent them from running on future boots. Dec 11 21:17:20 'disable' will do that rm for you. Dec 11 21:18:14 jkridner, it still takes me to the beaglebone site Dec 11 21:19:15 did you stop them as well and do 'systemctl start nginx.service'? Dec 11 21:19:27 I just tested it out myself. Dec 11 21:21:18 I did 'apt-get install nginx', edited /etc/nginx/sites-enabled/default to point to port 8081 and 'systemctl start nginx.service'... then browsed to beaglebone.local:8081 Dec 11 21:21:37 Fireye, this is really strange. I can use service start nginx and all that fun stuff and it says [ ok ] Starting nginx (via systemctl): nginx.service. but when I go to use ps aux | grep nginx the only thing that shows is root 1539 0.0 0.1 3100 692 ttyO0 S+ 21:20 0:00 grep nginx Dec 11 21:22:19 yeah jkridner I stopped them too and did that Dec 11 21:22:23 still no dice Dec 11 21:22:33 keeps going to beaglebone site Dec 11 21:22:57 do you still have apache at 80? Dec 11 21:23:07 apache isn't at 80 by default. Dec 11 21:23:12 not on the shipped Debian images... Dec 11 21:23:20 apache is set to port 8080. Dec 11 21:23:25 bonescript/node.js is on port 80 Dec 11 21:23:34 ah, ok Dec 11 21:23:53 I bought the begale bone black pre installed with debian and I have no clue what to do after installing the drivers Dec 11 21:24:10 I tried to remove apache but it kept giving me shit Dec 11 21:24:19 Blo_: what do you want to do with it? Dec 11 21:24:22 like.. it doesn't exist yet it's clearly running stuff with top Dec 11 21:24:35 py0, once you got rid of that led script, apt-get should work fine.. Dec 11 21:24:54 I get a web page from IP:8080 through apache Dec 11 21:25:01 how on earth do I destroy apache Dec 11 21:25:08 thurgood_: as of right now be able to use it Dec 11 21:25:22 Apache/2.2.22 (Debian) Dec 11 21:25:36 py0: sudo apt-get remove apache2 --purge Dec 11 21:25:55 how do you define using it? log in to a desktop, ssh in on a network, etc... Dec 11 21:26:08 Package 'apache2' is not installed, so not removed Dec 11 21:26:08 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Dec 11 21:26:12 ... Dec 11 21:26:25 see :[ Dec 11 21:26:31 py0: did you restart? Dec 11 21:26:37 py0: then sudo apt-get remove apache2* Dec 11 21:26:37 yes I've rebooted Dec 11 21:27:01 The following packages will be REMOVED: Dec 11 21:27:01 apache2-mpm-worker apache2-utils apache2.2-bin apache2.2-common Dec 11 21:27:19 thurgood_: I trired pluging in to a laptop but I am starting to like the idea of sshing into it but I dont know how Dec 11 21:28:45 thurgood_: I cant even login to it through my laptop Dec 11 21:28:48 rcn-ee: https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L625 can we hide this via a env variable somehow ? like show_user_pass="enable" ? Dec 11 21:28:53 I've removed all that stuff rcn-ee, and now it still continues to take me to the beaglebone page, but port 8080 is down now Dec 11 21:29:31 py0, port 80 is node.js.. Dec 11 21:29:47 why Dec 11 21:29:51 nginx is listening on 80 Dec 11 21:29:57 vvu, i'm fine with that.. Dec 11 21:30:04 Blo_: there are a couple of ways to ssh in, you can use a mini USB and ssh to 192.168.2.7 Dec 11 21:30:28 py0, it's setup that way by default.... so you need to also remove...... Dec 11 21:31:03 this is annoying Dec 11 21:31:10 thurgood_: Okay Dec 11 21:31:10 /lib/systemd/system/bonescript.socket & /lib/systemd/system/bonescript.service Dec 11 21:31:56 py0, what's annoying? if you want a bare bones install (with no extra stuff) flash this: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-11-19 (console image).. Dec 11 21:32:22 otherwise the "out of box" experience has to appease mass market... Dec 11 21:32:27 depending on your configuration you may or may not be able to login with the root account Dec 11 21:32:58 Blo_: do you have the stock debian on there? Dec 11 21:33:11 hooray Dec 11 21:33:17 thurgood_, (192.168.7.2) Dec 11 21:33:23 rcn-ee, deleting those two files with rm and rebooting has done it Dec 11 21:33:24 :D Dec 11 21:33:27 I think so I just start using it 5 minutes ago Dec 11 21:33:43 d'oh sorry about that :/ Dec 11 21:33:51 thanks rcn-ee Dec 11 21:34:06 ^ +1 Dec 11 21:34:36 thurgood_: It says it isnt availible Dec 11 21:35:17 did you try 192.168.7.2, I transposed the last numbers, as rcn-ee pointed out Dec 11 21:36:00 otherwise, 192.168.7.2:3000 then click on the terminal windows on the bottom and you'll have console access.. Dec 11 21:36:36 It works Thank you both Dec 11 21:37:43 But It wont allow me to actually log in Dec 11 21:38:06 vvu, do a grep for rfs_password, i'm pretty sure i broadcast that info in lots of places. (it stopped all the what is the user/pass email spam. ;)) Dec 11 21:38:40 Blo_, either: ssh debian@192.168.7.2 (pass: temppwd) or: ssh root@192.168.7.2 (no pass, just hit enter) Dec 11 21:39:31 Nope neither work Dec 11 21:40:10 I think I might have to just put debian on a micro sd card Dec 11 21:40:36 Well, if neither don't work.. it's not my image. ;) Dec 11 21:41:33 My thing about putting debian on a micro sd is that I dont know if it is able to Dec 11 21:42:39 rcn-ee: mainly i would like to put there a hook to enable a custom welcome message Dec 11 21:43:37 ah, that too.. Just remember if the end user upgrades from wheezy -> jessie there's a bit possiblty that file will be blown out. ;) Dec 11 21:44:37 I got it to work Dec 11 21:44:53 My laptop wasnt chosig ssh Dec 11 21:44:57 * vvu thinks his machine does not like him...those random seg faults Dec 11 21:45:05 choosing ssh Dec 11 21:45:24 vvu, in qemu? Dec 11 21:45:30 nop Dec 11 21:45:45 i think one of my RAM boards fails slowly Dec 11 21:46:02 i get some random segfaults in libc, chrome libs and so on Dec 11 21:46:04 ah.. bump the voltage till it really fails. ;) Dec 11 21:46:48 I like my bbb way better than my rpi Dec 11 21:46:59 Thank you guys for the help Dec 11 21:47:39 rcn-ee: i will see what to do with that welcome message. if something i'll ping you on github Dec 11 21:47:45 rpi tastes pretty good after you microwave it a bit, add some cool whip/ice cream.. ;) Dec 11 21:48:39 I may have to try that ;) Dec 11 21:49:40 r:pi is nice if you need small cheap full hd playback Dec 11 21:50:02 or a chromecast.. Dec 11 21:50:52 chromecast is nice if you have the desktop/laptop to power it Dec 11 21:51:37 of course that will consume a lot more energy than the pi Dec 11 21:52:18 or just phone.. depending if your serving the rpi media off an external server.. Dec 11 21:54:00 I imagine most use cases are smaller loops, not so much a media server Dec 11 21:54:16 but there's no accounting for other people's situtations Dec 11 22:15:56 is anyone running kernel 3.15 or newer? **** ENDING LOGGING AT Fri Dec 12 02:59:59 2014