**** BEGIN LOGGING AT Wed Feb 21 03:00:03 2018 Feb 21 03:00:30 That last link shows a Photoresistor and the BBB. Feb 21 03:02:05 If you are trying to run software for a photoresistor and Motion Detection sensor, try: https://pastebin.com/P9PDvPLX Feb 21 03:02:43 that pastebin.com paste will show you how to set up one photoresistor. Feb 21 03:02:47 That is the start. Feb 21 03:06:07 Thank you..Adafruit_BBIO..this libray..can it solve this problem that two or more sensors are detected in same time? Feb 21 03:06:18 Second...https://software.intel.com/en-us/iot/hardware/sensors/passive-infrared-pir-motion-sensor will show you how to set up your software for one Grove Enabled PIR. Feb 21 03:06:20 Yes. Feb 21 03:07:35 Hey W_Olympic: Do you know of their Library for the PIR? Feb 21 03:08:32 sorry, i don't know. Feb 21 03:08:52 Me Neither! I always wondered if they made time to setup a PIR library in Python. Feb 21 03:08:53 Oh well. Feb 21 03:09:12 but i have it, i think i should read this libray. Feb 21 03:11:35 I was wrong about the Grove PIR. It is not for the BBB. Feb 21 03:13:45 Erm, I think a program is a set of commands executed in sequence. Need i calculate sampling rate? Feb 21 03:16:41 Okay. Sampling rate. I have no clue what sampling rates are... Feb 21 03:16:46 <<<<< looking it up Feb 21 03:17:55 You seem to know more than me on sampling. Maybe you can just plug those suckers in and start. Feb 21 03:18:20 ... Feb 21 03:18:24 That is my idea. Feb 21 03:19:51 W_Olympic: If you want to know everything first, I understand. I will leave you alone now. Sorry to bug you. Feb 21 03:22:09 worm_duel:Thank you very much! Feb 21 03:22:32 I am not the person w/ knowledge. I just know research and performance. Feb 21 03:23:17 Does my BBB work w/ this sensor? I do not know. Let me test it. = ideas to research Feb 21 03:25:24 Does anyone know how to use MRAA and UPM modules w/ their sensors on the BBB? Feb 21 04:50:54 How can I downgrade my version of u-boot to [U-Boot 2017.09-00002-g0f3f1c7907]? Feb 21 05:12:23 a Feb 21 08:04:01 Hello, I just got my brand new "beaglebone black rev c", and I follow the instructions to the step three, browse to web server on board. But it just never works to link http://192.168.7.2/. Feb 21 08:04:26 The error message is ERR_CONNECTION_TIMED_OUT in the page. Feb 21 08:04:59 Anyone please help! Feb 21 09:11:02 (windows firewall?) Feb 21 09:12:13 hi Feb 21 09:12:26 anyone is there in online Feb 21 09:12:42 no, the internet is down Feb 21 09:12:48 and i'm so totally offline. Feb 21 09:13:25 can anyone tell me how to install multimedia packages for beaglebone black Feb 21 09:13:53 multimedia, like....? Feb 21 09:14:06 sound drivers video drivers Feb 21 09:14:22 for what? Feb 21 09:14:48 the beagle has no sound output that i'm aware of, and the hdmi driver should be included in the default image. so whats the actual question`? Feb 21 09:15:01 it has audio out via hdmi Feb 21 09:15:18 ah :) Feb 21 09:15:32 it also has terminal bell :-) Feb 21 09:16:01 like LetoThe2nd said, the necessary drivers are included and enabled by default Feb 21 09:18:37 just i want to know the procedure about how to install multimedia package for beaglebone black Feb 21 09:19:17 unless you can define what actually want, there will probably not be a helpful answer. Feb 21 09:20:32 hi Feb 21 09:21:22 how can i configure multimedia package for beaglebone in yocto project Feb 21 09:23:30 repeating the question is not going to magically make it clearer, although the fact that you're using yocto is relevant and something you should have mentioned from the start Feb 21 09:23:36 try #yocto Feb 21 09:24:14 ... where you will get the same answer: "what is it exactly that you want to install" :-P Feb 21 09:24:24 for hdmi Feb 21 09:26:20 maybe yocto doesn't include drivers for that by default unless you set some config flag somewhere? I have no idea, I've never used yocto Feb 21 09:26:25 hence, try #yocto Feb 21 09:28:34 the drivers are in mainline linux, and the am335x-boneblack.dts includes the necessary definitions for hdmi Feb 21 09:28:44 so as long as the kernel is configured properly, hdmi will work Feb 21 11:55:43 Excuse me, I want to make a monitoring system of product line. I think 20 photoelectric sensors and 10 PIR sensors will connect BBB board. I have some question,1.which kind of ports is connected? GPIO port or PRU port? 2. If two or more sensors are detected in same time, how to solve this problem ? Feb 21 12:18:21 Hi, I just bought a new beagleboard x15, since beaglebone black cannot match my requirement. But I want to boot the system from a micro SDcard and use the rest spaces just like what I did on BBB. Does anyone can give advices how can I do this to Beagleboard x15? Many thanks. Feb 21 12:20:09 there's a microSD slot on the x15, what else do you need? be more specific in your question.. Feb 21 12:20:17 Micky: I personally boot from microSD and put my rootfs on a USB3 stick. Feb 21 12:20:44 (is there an x15 SRM somewhere?) Feb 21 12:20:44 So, it works fine. Not much to say. Feb 21 12:21:04 there is. PDF only right now. Feb 21 12:21:22 linked on bbb.io/x15 Feb 21 12:21:50 ahh, I was looking at https://elinux.org/Beagleboard:BeagleBoard-X15 and not finding it Feb 21 12:22:24 wait, that’s the QSG I was thinking about. :-( Feb 21 12:22:37 thought Gerald did an SRM. maybe not. Feb 21 12:22:38 yeah, I found the QSG.... hmm Feb 21 12:22:58 I was about to beat the "have you read the SRM?" drum, but checked myself. Feb 21 12:23:49 https://github.com/beagleboard/beagleboard-x15/blob/master/BeagleBoard-X15_SRM.pdf Feb 21 12:24:01 so, it needs a link. Feb 21 12:24:19 but at least I was right Gerald did one. Feb 21 12:24:33 Is it intended for random noobs to have edit access to that wiki, or should we wait for y'all to link that? Feb 21 12:36:41 random people being able to edit is the whole concept of a wiki Feb 21 12:39:27 https://xkcd.com/1957/ - "A remote attacker can inject arbitrary text into public-facing pages via the comments box" Feb 21 12:39:37 uhuh :) Feb 21 13:28:29 yes and no, wiki-as-CMS has been done, one of my favorite power-products vendors keeps most of their website in Doku, but the edit controls are for employees only. Feb 21 14:19:41 I have the Micro SDcard inserted on the BeagleBoard X15, but I don't know how to make the system boot from the SDcard. Many thanks for any advices Feb 21 14:22:37 Micky: it will default to booting from sd card Feb 21 14:22:46 and reverts to eMMC if the sd card is not bootable Feb 21 14:26:40 Thank you zmatt for your advice. Feb 21 16:53:27 Does anyone know how to downgrade the bootloader to a previous version on the BBB? Feb 21 16:54:13 I found update intructions but nothing in the way of downgrade/reverting info. Feb 21 17:04:58 why would you want to do that? Feb 21 17:05:09 I mean, it's not particularly hard Feb 21 17:05:25 My Motor Bridge Cape only works w/ this specific bootloader, i.e. from what I can tell. Feb 21 17:05:30 just follow the upgrade instructions Feb 21 17:05:39 ... using an older binary Feb 21 17:05:42 It does not work w/ the newer 01.2018 bootloader. Feb 21 17:05:44 that sounds very strange to me. elaborate? Feb 21 17:06:01 if you have trouble with u-boot overlays, you can disable those in /boot/uEnv.txt Feb 21 17:06:16 which makes it behave like earlier u-boot versions Feb 21 17:06:26 Well...I tried to use this Cape and I had an older board w/ the older bootloader. Feb 21 17:06:27 ... Feb 21 17:06:54 The Cape worked w/ this bootloader and board but not w/ the updated version of bootloader. Feb 21 17:07:10 ogra: Okay. Feb 21 17:07:14 Thank you. Feb 21 17:07:16 that's with no changes other than the bootloader? Feb 21 17:07:46 Right. This is all I can figure out. I looked around my uEnv.txt file and saw no difference. Feb 21 17:07:56 actually, I can imagine that updating the bootloader might require also updating some other stuff Feb 21 17:08:09 Aw, I figured this too. Feb 21 17:08:44 My kernel is 4.9.x like my other boards. Feb 21 17:08:50 yeah ok, since you updated the bootloader separately that also means your uEnv.txt doesn't include the new config vars Feb 21 17:09:00 Oh. Feb 21 17:09:05 but wait, then u-boot overlays should be disabled, i.e. u-boot should behave like older versions Feb 21 17:09:15 can you pastebin the contents of your /boot/uEnv.txt ? Feb 21 17:09:30 I updated an image and started from scratch. Feb 21 17:09:32 Sure. Feb 21 17:09:35 Please hold. Feb 21 17:09:48 you flashed a new image? okay, so you didn't change just the bootloader Feb 21 17:12:44 No...I tried to update the bootloader and did but then I forgot to press the S2 button when booting from the SD Card. Feb 21 17:12:59 Then, I refreshed a new image and pressed the S2 button. Feb 21 17:13:16 My bootloader reads in at 01.2018. Feb 21 17:13:27 for eMMC and Push Button. Feb 21 17:13:41 https://pastebin.com/JRU0dJUF Feb 21 17:13:42 what do you mean "for eMMC and push button" ? Feb 21 17:13:57 push button = sd card Feb 21 17:14:55 Sorry... Feb 21 17:15:08 it's really reaaaaly unclear what you've been trying to do and what issues you observed Feb 21 17:15:44 Okay. The Cape has a library typed up in Python. I typed up some software based on the library. Feb 21 17:15:57 It only seems to work w/ older versions of bootloader. Feb 21 17:16:13 ... Feb 21 17:17:11 That is it. Feb 21 17:17:14 first, is this the cape you're referring to? -> http://wiki.seeed.cc/Motor_Bridge_Cape_v1.0/ Feb 21 17:17:19 Yes. Feb 21 17:17:50 okay, so it just uses.... I2C and one gpio Feb 21 17:18:04 so that should work on basically anything Feb 21 17:18:17 I thought so but it does not. Feb 21 17:19:44 yeah so either you or the software is just doing something stupid probably... but hold on, I'm taking a quick peek at the schematic first Feb 21 17:20:03 Smart! Feb 21 17:20:52 ogra_: Are you still here? Feb 21 17:20:56 nicely done seeed... part of the schematic is cut off in the pdf Feb 21 17:21:04 I know. I noticed that. Feb 21 17:23:08 https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-DealingwitholdBootloaderineMMC is what I found. Feb 21 17:23:23 ... Feb 21 17:24:07 I tried to "update" my bootloader to this version: [U-Boot 2017.09-00002-g0f3f1c7907] Feb 21 17:24:15 worm_duel: uhh, don't tell me you have a beaglebone that's *that* old, and moreover a motivation to keep it? Feb 21 17:24:31 No...I have a BBG. Feb 21 17:24:34 I really think you're off in the wrong direction by messing with the bootloader in the first place Feb 21 17:24:44 My older BBB works. Feb 21 17:25:02 the cape mainly uses i2c 2, which is always available Feb 21 17:25:07 I have that A5 model of the BBB. Feb 21 17:25:31 so all that's needed is muxing the reset pin and it should work Feb 21 17:25:39 what problem are you seeing? you're getting some sort of error? Feb 21 17:25:39 Oh. Feb 21 17:26:22 So, yea. I get this error: Adafruit_I2C has been deprecated. Use Adafruit_GPIO.I2C instead. Feb 21 17:26:29 I already see problems in your uEnv.txt btw Feb 21 17:26:40 lines 14-15 ... don't do that Feb 21 17:26:43 Oh? Feb 21 17:26:46 Okay. Feb 21 17:27:50 I commented them out... Feb 21 17:27:56 it looks like you don't need the uart anyway? the python library didn't seem to use it anyway. presumably it's just used for reflashing the microcontroller on the cape Feb 21 17:28:11 Okay. Feb 21 17:28:40 anyway, yeah that deprecation warning is just a deprecation warning that you're supposed to use some other adafruit call Feb 21 17:28:46 or just use python-smbus2 instead Feb 21 17:28:51 The cape has had issues w/ the people using it but I used to have it up and running all the time. Feb 21 17:28:52 ... Feb 21 17:29:31 I just rebooted b/c of commenting out 14 & 15. Feb 21 17:31:03 good, now what problem were you seeing? I mean, the Adafruit error is just a result of trying to use Adafruit_I2C, which has been replaced by Adafruit_GPIO.I2C. so just replace that Feb 21 17:32:02 Same. Feb 21 17:32:07 Module is Deprecated. Feb 21 17:32:34 Well anyway, I will test it some more. Feb 21 17:32:50 ... Feb 21 17:33:11 Oh and sir...I tried to use Adafruit_GPIO.I2C instead. Feb 21 17:33:40 I changed my library to suit the needs of the error. Feb 21 17:34:36 well you have to Feb 21 17:34:49 Adafruit_I2C really doesn't work anymore: https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/Adafruit_I2C.py Feb 21 17:35:19 I found out first hand w/out the info. you just produced. Feb 21 17:35:22 I read about it. Feb 21 17:35:35 this obviously has absolutely nothing to do with the bootloader though Feb 21 17:36:37 Well...okay. So, the Adafruit library for I2C worked years ago when this cape came out. I am trying to revert specifics back to when this library worked. Feb 21 17:37:00 So, I should downgrade the Adafruit library? Feb 21 17:37:09 Ya! Feb 21 17:37:12 I will. Feb 21 17:37:33 why not just fix the code? Feb 21 17:37:45 really just replace 'from Adafruit_I2C import Adafruit_I2C Feb 21 17:37:57 I tried. Feb 21 17:38:01 by import Adafruit_BBIO.I2C as I2C Feb 21 17:38:08 okay, what went wrong? Feb 21 17:38:10 More errors...yea. Feb 21 17:38:22 namely? Feb 21 17:38:37 Please hold. I will post a pastebin thing. Feb 21 17:39:54 well: It states SyntaxError: Invalid syntax Feb 21 17:40:00 MotorBridge = I2C(0x4b, 2) Feb 21 17:40:05 Yea? Feb 21 17:40:13 That is it? Feb 21 17:40:20 syntaxerror? then just literally just typed something that isn't valid python code Feb 21 17:40:26 *means you typed Feb 21 17:40:35 yes, combined with replacing the import line Feb 21 17:40:56 actually Feb 21 17:41:27 no wait the constructor is different I think, lemme quickly read up Feb 21 17:41:42 Okay. Take your time. Feb 21 17:43:01 I am going on a smoke break. BRb. Feb 21 17:44:31 lol, well done Adafruit... https://github.com/adafruit/Adafruit_Python_GPIO/blob/master/Adafruit_GPIO/I2C.py#L53-L54 Feb 21 17:44:46 P9.19/20 is I2C bus 2 you morons, not bus 1 Feb 21 17:46:49 import Adafruit_BBIO.I2C as I2C Feb 21 17:47:02 MotorBridge = I2C.Device(0x4b, 2) Feb 21 17:50:24 Okay.a Feb 21 17:50:28 I will try it. Feb 21 17:52:05 import error: NO module named I2C Feb 21 17:52:24 hmm? did I fuck it up, hold on Feb 21 17:52:28 No. Feb 21 17:52:39 Just an error. Feb 21 17:52:50 Okay...holding. Feb 21 17:53:35 oh sorry, Adafruit_GPIO.I2C Feb 21 17:53:41 not Adafruit_BBIO.I2C Feb 21 17:54:15 Okay. Feb 21 17:54:48 I have tried that too but not w/ the MotorBridge = I2C.DEVICE(0x4b, 2) line. Feb 21 17:54:54 Please hold. Feb 21 17:54:55 I2C.Device Feb 21 17:54:57 not DEVICE Feb 21 17:55:01 Oh. Feb 21 17:55:02 Okay. Feb 21 17:57:18 I am back to Import Error: No Module Named Adafruit_GPIO.I2C Feb 21 17:58:01 that makes no sense Feb 21 17:58:13 zmatt: What lines are you reading on the Library for I2C? Feb 21 17:58:43 I will pastbin some software and the library that is listed on my computer. Feb 21 17:58:50 BBB! Feb 21 17:58:53 Adafruit_GPIO.I2C is specifically the library that you were told to use by the warning you got earlier Feb 21 17:59:01 i.e. this thing -> https://github.com/adafruit/Adafruit_Python_GPIO/blob/master/Adafruit_GPIO/I2C.py Feb 21 18:00:12 Okay but what lines? Feb 21 18:00:22 of what? Feb 21 18:00:29 for what? Feb 21 18:01:30 I figured you could read some lines of that library that made you understand what to do. Feb 21 18:01:32 That is all. Feb 21 18:01:47 Here is my crappy software: https://pastebin.com/rmHXP6gG Feb 21 18:01:59 I import MotorBridge and import time Feb 21 18:03:16 https://pastebin.com/wYwWuSg0 is the link to my setup on the MotorBridge.py library. Feb 21 18:03:36 maybe you need to do something to install the Adafruit_GPIO library? I dunno, I assumed that since Adafruit_I2C was installed and telling you to use Adafruit_GPIO instead, that it would also be installed already :P Feb 21 18:03:56 wait, did I say that? Feb 21 18:04:00 I think. Feb 21 18:04:04 18:46 < zmatt> import Adafruit_BBIO.I2C as I2C Feb 21 18:04:13 that's not the same as from Adafruit_GPIO.I2C import I2C Feb 21 18:04:18 Okay. Feb 21 18:04:33 So use BBIO instead of GPIO? Feb 21 18:04:40 no Feb 21 18:04:44 I corrected myself on that Feb 21 18:04:50 but use 'import ... as' Feb 21 18:04:56 Oh...use GPIO instead of BBIO! Feb 21 18:04:56 not 'from ... import' Feb 21 18:05:14 import Adafruit_GPIO.I2C as I2C Feb 21 18:05:20 Okay. Feb 21 18:05:31 hopefully that works Feb 21 18:07:00 this MotorBridge.py file is really ugly code too... Feb 21 18:07:22 plus the annoying practice of capitalizing variable names Feb 21 18:09:45 No-go. Feb 21 18:09:55 import error. Feb 21 18:09:57 no I figured, it still can't find it Feb 21 18:10:08 so, either it's not installed or it's not in a place where it can find it Feb 21 18:10:15 Oh. Feb 21 18:10:32 So, the damn Adafruit_BBIO is listed in an odd directory. Feb 21 18:10:38 Adafruit_GPIO Feb 21 18:10:42 Sorry. That. Feb 21 18:10:53 Adafruit_GPIO. Feb 21 18:11:08 Off too look it up. Feb 21 18:11:33 ok it *is* a separate library Feb 21 18:12:30 it has a readme with install instructions: https://github.com/adafruit/Adafruit_Python_GPIO/ Feb 21 18:13:03 you can also just skip that entirely and use a python i2c library such as python-smbus2 directly Feb 21 18:13:10 (Adafruit_GPIO.I2C is just a wrapper) Feb 21 18:13:34 or python-smbus Feb 21 18:13:40 Adafruit_BBIO in /usr/local/lib/python2.7/dist-packages/Adafruit_BBIO-1.0.10-py2.7-linux-armv7l.egg is where it is located. Feb 21 18:14:10 that however isn't Adafruit_GPIO Feb 21 18:14:39 It is Adafruit_Python_GPIO? Feb 21 18:14:54 that's the name of the git repository for some reason Feb 21 18:14:57 So...I do not have Adafruit_GPIO maybe? Feb 21 18:14:58 not the name of the module itself though Feb 21 18:15:05 Oh. Feb 21 18:15:14 it seems that's the case Feb 21 18:15:19 Odd. Feb 21 18:15:32 I thought when I got Adafruit_BBIO, all that stuff was included. Feb 21 18:28:49 worm_duel: as alternative to Adafruit_GPIO.I2C, you can also just install the 'smbus' module (apt-get install python-smbus or python3-smbus depending on whether you use python 2 or 3) Feb 21 18:29:28 it isn't API-compatible, but the MotorBridge code is simple enough to make the change quick and easy Feb 21 18:29:44 Okay. Feb 21 18:29:53 I have python-smbus Feb 21 18:29:56 installed! Feb 21 18:30:03 https://pastebin.com/ytK22Qwc Feb 21 18:30:26 so, instead of creating an object for an i2c device, it creates one for the whole bus Feb 21 18:30:55 I can start out w/ this...I will look up more info. on the python-smbus today. Feb 21 18:31:09 and calling .writeList(reg, data) on the i2c device instead becomes bus.write_i2c_block_data(address, reg, data) Feb 21 18:31:26 Oh. Feb 21 18:31:43 and it looks like that's the only call used by the MotorBridge python code Feb 21 18:32:09 anyway, I'm off Feb 21 18:33:13 http://wiki.erazor-zone.de/wiki:linux:python:smbus:doc Feb 21 18:33:18 Okay. Thank you. Feb 21 20:47:00 dealing w/ an old bootloader in eMMC! Feb 21 20:48:23 Where is rootfs listed on our BBGs? uname -r 4.9.78-ti-r94 Feb 21 21:02:35 I found fs at proc/mount/sys on the BBG w/ uname -r 4.9.78-ti-r94. Feb 21 22:59:31 Hi. Can I change the shared ram between between PRU and host while the pru is running from the host side? It seems to me that this is not working. But when the PRU changes anything in the shared ram I can read it from the host. Feb 21 23:03:37 I am using the Beagle Bone Green. Feb 21 23:04:18 what is inside this 176KB ROM of the AM335x? Feb 21 23:04:47 can this what is there inside be rewritten? Feb 21 23:06:08 is there recently any free GPU driver existing for the PowerVR GPU chip? Feb 21 23:40:16 iwcw: it cannot be altered, it's part of the chip's mask Feb 21 23:40:53 zmatt: there is no sourcecode for this? Feb 21 23:41:00 the kernel driver for the gpu is open, the userspace libraries are not. it doesn't seem like there's much hope of this changing Feb 21 23:41:03 no Feb 21 23:41:20 the first 128 KB ("secure rom") can't even be dumped on the am335x Feb 21 23:42:09 https://electronics.stackexchange.com/questions/268002/flash-obtain-rom-code-for-sitara-on-beaglebone-black Feb 21 23:42:10 https://e2e.ti.com/support/arm/sitara_arm/f/791/p/341752/1447857 Feb 21 23:42:24 however TI messed up the protection of secure rom on a related SoC and I analyzed it. on GP ("general purpose") parts, such as found on the beaglebone, not much of importance happens in secure rom Feb 21 23:42:49 great! thanks for that :) Feb 21 23:42:53 basically when it determines it's a GP SoC it just quickly transitions to the start of public rom Feb 21 23:43:50 and secure rom offers a "secure monitor call" to allow a privileged caller to alter some special cpu registers that can normally only be modified in secure privileged mode Feb 21 23:43:52 is the kernel driver in the mainline kernel? Feb 21 23:44:04 *for the GPU Feb 21 23:44:08 no Feb 21 23:45:03 I think most kernel maintainers would have a heart attack if they'd see the code style of the gpu kernel driver :) Feb 21 23:53:00 are there really that low amount of people who use the bbb that it dies out and no free GPU driver ever gets into the kernel? Feb 21 23:53:23 i dont want to use broadcom and i dont like broadcom :( Feb 21 23:53:56 I don't see any reason to assume "it dies out" Feb 21 23:54:24 making the kernel driver mainlineable is just a large amount of tedious work Feb 21 23:57:21 all the "interesting" stuff is in the userspace libs anyway... making an open source replacement of those would require a very serious reverse-engineering effort, and the result would likely remain inferior to the closed-source libs for a long long time Feb 21 23:58:19 most people who use the gpu simply tolerate the current situation as "not ideal, but it'll do" Feb 22 00:35:18 zmatt: did you think that when we make a kickstarter project of 10000$ for a working free driver, that then someone would do the work? Feb 22 00:35:45 lol, no Feb 22 00:35:55 at least I doubt it Feb 22 00:37:02 its more work then the work that have been done for 10000$ for the broadcom driver? Feb 22 00:37:21 I don't know the details of that Feb 22 00:38:03 I guess 10K could fund *some* development, assuming you can even find the right people for it... and the money Feb 22 01:13:40 Hi, i use to copy my beaglebone emmc to my microsd using beaglebone-black-copy-eMMC-to-microSD.sh but having error. can anyone help? Feb 22 01:14:08 my error is something like these Feb 22 01:14:12 cp: writing ‘/tmp/mkinitramfs_ZMVxty/lib/modules/3.8.13-bone30/modules.builtin’: No space left on device cp: failed to extend ‘/tmp/mkinitramfs_ZMVxty/lib/modules/3.8.13-bone30/modules.builtin’: No space left on device cp: writing ‘/tmp/mkinitramfs_ZMVxty/lib/modules/3.8.13-bone30/modules.order’: No space left on device Feb 22 01:15:28 Ray_: you have a 2gb or 4gb beaglebone black emmc? Feb 22 01:15:34 the error seems pretty self-explanatory Feb 22 01:15:40 how big is the sd card you're using? Feb 22 01:16:12 oh wait, /tmp/ ... Feb 22 01:16:23 so maybe it's actually out of space on eMMC rather than on SD card Feb 22 01:16:33 oh, yes, its copy-eMMC-to-microSD. Thanks for reading it right zmatt ;) Feb 22 01:18:02 I made /tmp an actual tmpfs on our beaglebones, so stuff there is not written to eMMC. that would help with this situation too Feb 22 01:18:28 Ray_: you can boot some more recent linux from the microsd, connect a usb-drive to the usb-connector and then just make a dump copy of the emmc with dd. Feb 22 01:19:51 my sd card is 16gb Feb 22 01:19:54 indeed Feb 22 01:20:00 how can i do that? Feb 22 01:20:06 Ray_: but if you make a backup of the emmc "for security", then thats not needed. The preinstalled things there when you receive the device are outdated and not needed. You can and should overwrite those with recent versions of the bbb linux Feb 22 01:20:53 doesn't hurt to make a backup though, especially if you have a 16gb SD card anyway Feb 22 01:21:02 i want to duplicate a copy on the sd card so that i can run it on other bbb using this sd card Feb 22 01:21:36 Ray_: maybe try to see if you can clean up some space? how much free space is there on eMMC right now? (check df -h / ) Feb 22 01:22:16 1.6g left Feb 22 01:22:37 okay what? Feb 22 01:22:41 Ray_: you could for fun run such a duplication over the network and boot two bbb with each a micro-sd or a live-usb. Feb 22 01:22:42 what about df -h /tmp Feb 22 01:22:47 maybe it *is* a tmpfs Feb 22 01:22:58 iwcw: no need to make this more complicated Feb 22 01:23:20 avail is 0 Feb 22 01:23:26 for /tmp ? Feb 22 01:23:53 yup Feb 22 01:23:57 size is 1M Feb 22 01:24:04 used 1M Feb 22 01:24:05 that's odd, I'm pretty sure it's not the default Feb 22 01:24:42 hmm I wonder if you can change the limit on a mounted tmpfs Feb 22 01:24:45 hold on lemme try Feb 22 01:25:31 you can Feb 22 01:25:38 Ray_: but the most simple and out of the way solution is: get a image from https://beagleboard.org/latest-images , dd it to a usb-drive or micro-sd, insert this into your bbb and hold down the boot selection button. Then you have a live-linux running and you can access the emmc. Then just dd the emmc content to an other free memory device (usb-pendrive when using micro-sd for live image or micro-sd card with free space when using live- Feb 22 01:25:42 mount -o remount,size=32768k /tmp Feb 22 01:26:08 that will change the limit on your /tmp to 32 MB Feb 22 01:26:27 which should allow the script to complete normally Feb 22 01:27:08 it would still be interesting to find out where/why /tmp is being mounted as a tmpfs with such a small size... 1 MB isn't much Feb 22 01:27:25 iwcw: pretty sure that doesn't sound like the simplest solution Feb 22 01:27:58 iwcw: you also need to expand the filesystem on sd card to actually span the card Feb 22 01:28:26 fixing the size limit on /tmp that's preventing the script from working is hopefully a simpler fix :) Feb 22 01:30:39 zmatt: hm? why should i expand the filesystem on anything? Example when using a micro-sd card where a dd from latest image is been installed: You boot, connect a usb-flash-drive with more then 4gb of free space, mount it, and run dd from the emmc to the usb-drive. then unmount usb-drive and you are done. Feb 22 01:32:50 oh I didn't fully read what you said (it also actually got truncated)... booting from microsd but then making a backup to an usb drive instead of using all the free space on the microsd is... an option I guess Feb 22 01:32:57 tmpfs usually defaults to half the ram... Feb 22 01:33:13 yeah 1 MB is a limit that was clearly set on purpose Feb 22 01:33:42 but also one that sounds pretty prone to breaking stuff Feb 22 01:34:56 1MB in /tmp is asking for problems. Feb 22 01:35:55 indeed it is Feb 22 01:36:15 I think I set it to 64 MB or something on our beaglebones Feb 22 01:37:46 * vagrantc waves to dgilmore Feb 22 01:39:00 cool. it's works. thanks for the help zmatt Feb 22 01:39:56 Ray_: so keep in mind this raised limit will only be in effect until reboot... you may want to dig around to see where the tmpfs is being mounted and raise that limit more permanently to avoid trouble in the future Feb 22 01:40:20 maybe grep -rsI 'tmpfs.*size' /etc Feb 22 01:40:37 or maybe just tmpfs Feb 22 01:40:57 (I guess it's possible the size limit isn't on the same line as 'tmpfs', or might use nr_blocks instead of size) Feb 22 01:41:36 zmatt: does the debian arm image work now for installation? Feb 22 01:41:47 what do you mean? Feb 22 01:42:45 when i tested it last time, i understood that you put the instsllation image to the sd-card and this overwirtes itself with the later installed partitions and so on. but when i tested it last time, it crashed somewhere Feb 22 01:43:14 uhh what? Feb 22 01:44:17 iwcw: debian-installer arm image, or the image from beagleboard.org ? Feb 22 01:44:24 the standard images at https://bbb.io/latest-images are (as mentioned below the download link) not eMMC-flashers anymore by default, but you can turn them into one by uncommenting one line in /boot/uEnv.txt Feb 22 01:44:32 vagrantc: debian installer arm image Feb 22 01:44:38 oh Feb 22 01:44:47 no idea about that, never heard of anyone using it Feb 22 01:44:57 iwcw: i haven't tested it in a while, but it worked last i used it Feb 22 01:45:06 well now I've heard of someone using it Feb 22 01:45:16 heh Feb 22 01:45:36 vagrantc: what image have you put on the micro-sd? Feb 22 01:46:28 iwcw: https://cdn-aws.deb.debian.org/debian/dists/stretch/main/installer-armhf/current/images/netboot/SD-card-images/ be sure to read the README, as you need to assemble the image from two parts Feb 22 01:46:49 iwcw: only supports the beaglebone black and beagleboard-x15 so far Feb 22 01:47:07 maybe some of the other beaglebone variants would work fine with it, no idea Feb 22 01:47:43 ok, just zcat firmware..img.gz partition.img.gz > complete_image.img . thanks :) Feb 22 01:48:19 basically, yeah Feb 22 01:49:03 if you want an image all preconfigured, it's certainly not that Feb 22 01:49:12 it'll walk you through all the typical debian-installer stuff Feb 22 01:50:34 plain debian images might also not be the most convenient for everyone if you actually want to use your embedded system as an embedded system rather than merely a small linux pc Feb 22 01:50:55 i want the "netinstaller" on arm to play around with different desktop environments on beaglebone black and so on Feb 22 01:51:27 u-boot also supports network-boot, although i'm not sure how well it works on the beagleboneblack Feb 22 01:51:40 netboot works Feb 22 01:52:18 iwcw: there are numerous other options to install a directory or two up from the link i showed you Feb 22 01:52:53 it requires a properly built u-boot, and you need to pull the sysboot pins into a configuration that includes ethernet as boot device Feb 22 01:53:34 unless you netboot over usb (rndis), that is an option with the default boot device order (eMMC, μSD, uart, usb) Feb 22 01:53:54 mainline u-boot has PXE enabled out of the box Feb 22 01:54:05 I haven't tried that Feb 22 01:54:13 vagrantc: there dont seem to be daily netinstaller images: https://cdn-aws.deb.debian.org/debian/dists/sid/main/installer-armhf/current/images/netboot/SD-card-images/ Feb 22 01:54:14 if mmc/emmc/etc falls through, it'll try PXE Feb 22 01:54:41 sid image is also 2 months old Feb 22 01:54:43 iwcw: https://d-i.debian.org/daily-images/armhf/ Feb 22 01:54:44 okay, but you still need to ensure that SPL is able to load u-boot.img via tftp, I don't think that's default Feb 22 01:55:05 zmatt: oh, i was presuming loading u-boot off of microSD or eMMC, yeah Feb 22 01:55:12 vagrantc: nice, thanks https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/ Feb 22 01:55:14 that's cheating :) Feb 22 01:55:36 i'm happy to cheat if it means using off-the-shelf builds :) Feb 22 01:55:53 iwcw: yeah, the sid stuff for debian-installer is almost never updated Feb 22 01:56:10 * vagrantc wishes the workflow for debian-installer were more like other things Feb 22 01:56:23 well I have a working netboot build -> https://github.com/dutchanddutch/u-boot/tree/am335x-v2017.11-netboot Feb 22 01:56:48 zmatt: whoah, all the way from last year! Feb 22 01:56:59 3 months ago you mean Feb 22 01:57:18 * vagrantc taunts ineffectually Feb 22 01:57:24 or actually, one month ago Feb 22 01:58:38 if you want to ensure it netboots rather than booting whatever happens to be on eMMC you'd still need to tweak the boot script Feb 22 01:59:00 vagrantc: i talked with zmatt about the gpu driver. would be great if at some time someone could make a upstream mainline kernel driver. Then just connect bbb to a monitor, connect usb-mouse+keyboard, put clean debian image and just run the installation :) Feb 22 01:59:22 I just verified it was able to load u-boot via the network, and if I interrupted boot and manually ran dhcp boot it was able to load and boot a FIT from the tftp server Feb 22 01:59:32 iwcw: it would be great, but i wouldn't hold my breath :) Feb 22 02:00:34 Then we could have wayland on the bbb ;) Feb 22 02:00:41 * vagrantc runs mostly headless systems Feb 22 02:00:56 my impression is that it shouldn't even be that hard to clean up the kernel driver... its main tasks are managing the gpu's mmu and dealing with synchronization Feb 22 02:01:27 (to allow userspace to safely interact with the gpu) Feb 22 02:02:03 thanks a lot so far. great people here in this channel Feb 22 02:02:07 iwcw: btw I don't understand what you're describing has to do with each other Feb 22 02:02:14 why would the debian installer need 3d acceleration? Feb 22 02:02:46 * vagrantc suspects post-install use Feb 22 02:03:02 preinstall use for "typical" people Feb 22 02:03:20 like an install from a live image or something? Feb 22 02:03:30 yes Feb 22 02:03:53 "dd to usb-drive and install" like on other "computer" Feb 22 02:03:56 I don't really understand people who use the bbb as a desktop linux system very much... surely there must be better suited boards for that? Feb 22 02:04:07 much better Feb 22 02:04:23 it sure is low power and quiet, though :) Feb 22 02:04:34 what makes the beaglebone awesomesauce is its peripherals and i/o Feb 22 02:04:44 * vagrantc originally got into arm-based systems searching for a decent thin client ... Feb 22 02:04:56 now thin clients aren't very useable regardless of which architecture Feb 22 02:05:25 yes but even within fanless arm-based linux systems I would expect there are better options Feb 22 02:05:33 * vagrantc agrees Feb 22 02:05:49 where the SoC's display controller actually supports a hardware cursor, things like that :P Feb 22 02:05:50 some people also say "thin client" to their ITX bord with a 4-8 core x86_64 cpu Feb 22 02:07:01 well, the "thin" in thin client doesn't really refer to the cpu Feb 22 02:09:20 or the TDP values Feb 22 02:10:47 my understanding of the term is a zero-configuration system with no persistent storage (other than as cache maybe?), just purely getting everything from a server Feb 22 02:14:08 thanks again. bye Feb 22 02:18:38 What chapter on the BeagleBone Cookbook has the .ini file for the MSP and the node.js file for the BBB on it (updated version)? Feb 22 02:22:03 I am having issues! https://pastebin.com/aPyu3NgT Feb 22 02:35:40 something about parser:b.serialParsers.readline('\n') that keeps me from starting the software. Feb 22 02:35:44 Aw! Feb 22 02:39:46 The error is pointing to (^) "readline" and...and...and I am without ideas. Send rations! Feb 22 02:42:56 ... Feb 22 02:43:43 I am looking at npmjs.com under bonescript. There is nothing about "readline." Is bonescript a thing of the past? Should I move on? Feb 22 02:53:34 I read the software in the example. Add exports.serialParsers = m.module.parsers; to serial.js. I looked in the /usr/ local/ lib/ node_modules/ bonescript/ dir. I was supposed to find that file (serial.js). No such file! Feb 22 02:53:37 ... Feb 22 02:53:40 Send rations. Feb 22 02:57:29 I will bang around some and try other avenues but I may have to try damn Python again. **** ENDING LOGGING AT Thu Feb 22 03:00:04 2018