board update error

Remork

root@bela ~/Bela# du -sh /root/*
236M	/root/Bela
1.3M	/root/hcs-0.1
0	/root/without
2.5M	/root/zexy-v2.3.0
root@bela ~/Bela#

giuliomoro

Hmmm so the bulk of your disk usage is outside the home folder.. in normal conditions there should be over 1GB available. Could it be you installed a lot of packages with apt-get at some point?

Remork

giuliomoro Could it be you installed a lot of packages with apt-get at some point?

i have no idea what that means, so i doubt it. 🙂

anything i can do to check the contents outside of the home folder?

giuliomoro

Sure, du -sh /*. And also du -sh /var/log/* /var/cache/*

Remork

giuliomoro du -sh /*

duh. could've come up w that maself 🙂

results:

29M	/boot
0	/dev
3.1M	/etc
572K	/home
117M	/lib
16K	/lost+found
4.0K	/media
5.1M	/mnt
78M	/opt
du: 
cannot access '/proc/988/task/988/fd/3': No such file or directory
du: cannot access '/proc/988/task/988/fdinfo/3': No such file or directory
du: 
cannot access '/proc/988/fd/3': No such file or directory
du: cannot access '/proc/988/fdinfo/3': No such file or directory
0	/proc
240M	/root
9.4M	/run
4.9M	/sbin
4.0K	/srv
0	/sys
28K	/tmp
979M	/usr
2.0G	/var

and

root@bela ~/Bela# du -sh /var/log/* /var/cache/*
16K	/var/log/alternatives.log
32K	/var/log/apt
224K	/var/log/auth.log
88K	/var/log/bootstrap.log
0	/var/log/btmp
755M	/var/log/daemon.log
320K	/var/log/debug
0	/var/log/distccd.log
244K	/var/log/dpkg.log
4.0K	/var/log/faillog
7.1M	/var/log/kern.log
8.0K	/var/log/lastlog
6.2M	/var/log/messages
762M	/var/log/syslog
736K	/var/log/wtmp
309M	/var/cache/apt
2.1M	/var/cache/debconf
20K	/var/cache/ldconfig
4.0K	/var/cache/man

giuliomoro

Remork 755M /var/log/daemon.log

Have you got a program running on boot which prints a lot of stuff?

You can safely remove everything in /var/cache and /var/log. Don't touch /usr.

Remork

i would think that /usr at 979M and /var at 2G seem to stand out most..

if i run du -sh /var/*, it's indeed var/log that stands out at 1.5G.
mostly made up of var/log/daemon.log & var/log/syslog, apparently..

is this expected?

Remork

giuliomoro you mean with [print] objects?
i do track three slider values, and some button presses..
does it store all that data? ❓
because it has been on display as an interactive installation for several days.. so yeah, if it stores days worth of slider values.. that would explain a lot 🙂

Remork

probably 🙂
would make for easier updates, for starters.

some questions:

1) the next gen image, as in: the one that came after 0.3.7, or one that's yet to come out?

2) giuliomoro You can safely remove everything in /var/cache and /var/log.

that would be rm -rf /var/cache/* /var/log/*?

3) to run 020 and actually get work started on the real issue 🙂, i would have to be running an image later than 0.3.8f?

thanks for your time again!

giuliomoro

Yeah but I am actually confused as to why it doesn't actually delete older values when close to filling up the disk. There may be some settings to be tweaked ...
In the next gen image, none of this is actually written to disk ever, which is probably a wiser move.

giuliomoro

Remork 1) the next gen image, as in: the one that came after 0.3.7, or one that's yet to come out?

the one that will come out in the future. This week I will make a v0.3.8h to support Bela Cape RevC, but it won't have this feature yet (I think, will let you know if otherwise).

Remork that would be rm -rf /var/cache/ /var/log/?

yes

Remork 3) to run 020 and actually get work started on the real issue 🙂, i would have to be running an image later than 0.3.8f?

no, just have your Bela core relatively up-to-date (because of a change in the OscReceiver API back in March this year).

Remork i have my pd-externalsproject.
there's the hcsand zexy libraries under directories.
in directories/hcsi have folder_list-help.pdand folder_list.pd_linux.

but there's also folder_list.c in sources, which is the one giving me the error.
first line of code there is #include <m_pd.h>.

Wondering how the sources folder got there: it shouldn't be there. But also, it shouldn't hurt: you are not supposed to build the pd-extended project; at most you will be shown some warnings when you open it but you can ignore them.

Remork

giuliomoro no, just have your Bela core relatively up-to-date (because of a change in the OscReceiver API back in March this year).

hmm okay, not sure what that translates to in terms of Bela images, and whether i should upgrade from 0.3.7 to use my Oled easily? advice? after that i'm done bugging you, i promise 🙂
.

Remork

is it possible (really wild stab in the dark) that it either got created when installing the library, or it gets created when using the object?

giuliomoro

You can update your bela code without updating image: https://learn.bela.io/using-bela/bela-techniques/updating-bela/ ; or you can grab v0.3.8g and call it a day if you don't mind reflashing .

Remork

does updating imply reinstalling external libraries?
i'm supposing reflashing does..
would much prefer it if i can avoid it.

giuliomoro

reflashing does; updating the core code via IDE doesn't touch the projects or anything else you may have installed on the image.

Remork

updated via IDE.

am now getting these messages:

Nov 03 17:17:13 bela stdbuf[860]: make: Leaving directory '/root/Bela'
Nov 03 17:17:13 bela systemd[1]: bela_startup.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 03 17:17:13 bela systemd[1]: bela_startup.service: Unit entered failed state.
Nov 03 17:17:13 bela systemd[1]: bela_startup.service: Failed with result 'exit-code'.
Nov 03 17:17:14 bela systemd[1]: bela_startup.service: Service hold-off time over, scheduling restart.
Nov 03 17:17:14 bela systemd[1]: Stopped Run Bela at boot.
Nov 03 17:17:14 bela systemd[1]: bela_startup.service: Start request repeated too quickly.
Nov 03 17:17:14 bela systemd[1]: Failed to start Run Bela at boot.
Nov 03 17:17:14 bela systemd[1]: bela_startup.service: Unit entered failed state.
Nov 03 17:17:14 bela systemd[1]: bela_startup.service: Failed with result 'exit-code'.

then tried starting project manually

Building project ... make: Nothing to be done for 'all'. Build finished Running project ... Warning: -A/--adc-level is deprecated and IGNORED. Use --audio-input-gain instead Warning: --pga-gain-left is deprecated. Use --audio-input-gain instead Warning: --pga-gain-right is deprecated. Use --audio-input-gain instead gpio/direction: No such file or directory Segmentation fault Makefile:613: recipe for target 'runide' failed make: *** [runide] Error 139 Bela stopped

giuliomoro

Oh I see, that seems - coincidentally - to be the same issue observed here. I am confused why that would be the case, but it could be because of the old kernel you are running there on 0.3.7 ? I cannot flash an older image right now so it's a bit complicated to troubleshoot.

what libraries did you install that you want to keep? Is it just everything you have in pd-externals? You could just backup the full projects/ folder, flash a new image and restore that folder on the newer image. Do you need step-by-step instructions to do that? If you get any errors while building projects on the new image, use the "clean" button to force a rebuild of all files.

Remork

kernel? sorry colonel, got distracted there for a second. ba-dum-tss
i mean, i don't even know what that even means. rabbit hole of doom, here i come.

giuliomoro Is it just everything you have in pd-externals?

well, to be honest - i'm not sure.
bear with me here. i'm using two libraries, hcsand zexy. both were installed using the command line.

thing is, i'm using exactly one element from hcs, being hcs/folder_list, and two from zexy, being zexy/z~and zexy/limiter~.
of these three, the only thing i can find in the pd-externals project is the .pd help files, and there appears to be a folder_list.pd_linux.
hence my confusion: i'm not sure the proper code for those objects (i'm guessing C++?) is even in that folder.

have downloaded all my files before the update, so i can just try putting everything back.
and if need be i'd just go through the whole lib installation again, but that's not gonna happen tonight anymore.

Remork

giuliomoro it could be because of the old kernel you are running there on 0.3.7

i'm trying to wrap my head around this.
as an analogy, would the kernel be like which version of an OS you're running (and therefore need reflashing), and the update would be like a new version of an application, Bela in this case?
so that an update can be incompatible with an older OS version? Like the latest version of Logic won't run on anything older than Mac Catalina, say?

Remork

giuliomoro You could just backup the full projects/ folder, flash a new image and restore that folder on the newer image. Do you need step-by-step instructions to do that?

that might be helpful. is that documented on the wiki?
i tried drag&drop but that doesn't work 🙂

giuliomoro

Remork of these three, the only thing i can find in the pd-externals project is the .pd help files, and there appears to be a folder_list.pd_linux.
Remork hence my confusion: i'm not sure the proper code for those objects (i'm guessing C++?) is even in that folder.

zexy is built into a single-file library, so you should only have zexy.pd_linux besides all the help files. I don't think you'll have more files outside of projects/ that you'll need on the new image. Just try that out on an SD card and see how that works out.

Remork

giuliomoro hmm, there's quite a bit of other .pd files in the zexy library..
will run some tests.

would you recommend removing all the [print]objects from _main.pd in the final version?