Out of curiosity, does the autotools build work as well?
And yes, a simple embedded-only distort would be *very* useful as I had problems with performance turning Raspbian in the past.
On Feb 3, 2018, at 12:00 PM, pd-list-request@lists.iem.at wrote:
Date: Sat, 3 Feb 2018 14:45:50 +0800 From: Chris McCormick <chris@mccormick.cx mailto:chris@mccormick.cx> To: "pd-list@lists.iem.at mailto:pd-list@lists.iem.at" <pd-list@lists.iem.at mailto:pd-list@lists.iem.at> Subject: [PD] Pd on Tiny Core Linux on Raspberry Pi Message-ID: <59001321-177a-dfc0-a19a-b0cb01e7f985@mccormick.cx mailto:59001321-177a-dfc0-a19a-b0cb01e7f985@mccormick.cx> Content-Type: text/plain; charset=utf-8; format=flowed
Hi all,
This is fan mail for Pd on Tiny Core Linux onn Raspberry Pi.
TCL is a 50 megabyte GNU/Linux distribution which is immutable-by-default and runs very well on the Raspberry Pi.
I managed to compile Pd and got it to output a test tone which is why I am posting here. To do it yourself:
- Install the alsa packages
- Install the compiletc package
- Compile Pd with
make -f makefile.gnuinside the src directory- Run
pd -nogui mypatch.pdfrom the bin directoryIf you want to launch a Pd patch at startup add your command to /opt/bootlocal.sh
So far this seems like fertile ground as an alternative to the Raspbian distribution with its multiple-gigabyte bloat. Seems perfect for embedded Pd devices like guitar pedals, synths, and what-not.
Tiny Core Linux does not use systemd.
Cheers,
Chris.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Hi Dan,
On 03/02/18 21:15, Dan Wilcox wrote:
Out of curiosity, does the autotools build work as well?
I got this when I tried:
tc@box:~/pure-data$ autoconf configure.ac:9: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:149: error: possibly undefined macro: AM_CONDITIONAL configure.ac:162: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.ac:163: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.ac:164: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:230: error: possibly undefined macro: AC_CHECK_LIBM
Then when I tried to run configure:
tc@box:~/pure-data$ ./configure configure: error: cannot find install-sh, install.sh, or shtool in m4/config "."/m4/config
I guess there are some additional build dependencies I'd need to install to get this working.
For now the old makefile.gnu route works great on this platform.
Cheers,
Chris.
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
If you have any more time, you could try building a dist tarball on your main system and then build Pd with it using configure/make on the pi. Building the tarball is:
./autogen.sh ./configure make dist
That gives you a pd-0.48.1.tgz with the pregenerated configure scripts.
enohp ym morf tnes
Dan Wilcox danomatika.com robotcowboy.com
On Feb 7, 2018, at 8:30 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 03/02/18 21:15, Dan Wilcox wrote:
Out of curiosity, does the autotools build work as well?
I got this when I tried:
tc@box:~/pure-data$ autoconf configure.ac:9: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:149: error: possibly undefined macro: AM_CONDITIONAL configure.ac:162: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.ac:163: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.ac:164: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:230: error: possibly undefined macro: AC_CHECK_LIBM
Then when I tried to run configure:
tc@box:~/pure-data$ ./configure configure: error: cannot find install-sh, install.sh, or shtool in m4/config "."/m4/config
I guess there are some additional build dependencies I'd need to install to get this working.
For now the old makefile.gnu route works great on this platform.
Cheers,
Chris.
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Dear all, i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
Copy the package files from your local machine to the tinycore: scp $SOURCEDIR/puredata.tcz{,.dep,.md5.txt} tc@$TINYCOREIP:/etc/sysconfig/tcedir/optional/
then logon to the tinycore: ssh tc@$TINYCOREIP chown tc.staff /etc/sysconfig/tcedir/optional/puredata.tcz* chmod 664 /etc/sysconfig/tcedir/optional/puredata.tcz* echo puredata.tcz >> /etc/sysconfig/tcedir/onboot.lst
and reboot the tinycore
These are just the binary files needed to run pd. The doc/help files are in the puredata-doc.tcz package, the development header m_pd.h is in puredata-dev.tcz . To install those permanently, follow the procedure from above with changed package names.
best, Thomas
-- Thomas Grill http://grrrr.org
Am 15.02.2018 um 04:22 schrieb Dan Wilcox danomatika@gmail.com:
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Hi Thomas, On 17/02/18 06:58, Thomas Grill wrote:
i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
Thanks for taking the time to do this.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
I was able to do a manual install quite easily by copying the puredata.tcz file over to the RPi and then running:
tce-load -i ./puredata.tcz
The reason this did not work before (which I emailed you about) was I
had been doing wget http://l.grrrr.org/puredata_tcz not realising this
was your ownCloud server page rather than the package file itself.
One thing I noticed is your package seems to be mounted from a different location to all of the other packages:
$ mount | tail -n 4 /mnt/mmcblk0p2/tce/optional/libvorbis.tcz on /tmp/tcloop/libvorbis type squashfs (ro,relatime) /mnt/mmcblk0p2/tce/optional/libogg-dev.tcz on /tmp/tcloop/libogg-dev type squashfs (ro,relatime) /mnt/mmcblk0p2/tce/optional/libogg.tcz on /tmp/tcloop/libogg type squashfs (ro,relatime) /dev/loop108 on /tmp/tcloop/puredata type squashfs (ro,relatime)
Note the mount source of /dev/loop108 instead of /mnt/mmcblk0p2....
In any case, running running a test tone patch produces sound with your package installed (despite the Alsa error):
$ pd -nogui test-tone.pd priority 92 scheduling failed; running at normal priority priority 94 scheduling failed. ALSA input error (snd_pcm_open): No such file or directory
If I run with sudo the scheduling messages disappear.
Thanks again. Hope the package gets accepted!
Cheers,
Chris.
Hi Chris,
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
I was able to do a manual install quite easily by copying the puredata.tcz file over to the RPi and then running:
tce-load -i ./puredata.tcz
The reason this did not work before (which I emailed you about) was I had been doing
wget http://l.grrrr.org/puredata_tcznot realising this was your ownCloud server page rather than the package file itself.One thing I noticed is your package seems to be mounted from a different location to all of the other packages:
$ mount | tail -n 4 /mnt/mmcblk0p2/tce/optional/libvorbis.tcz on /tmp/tcloop/libvorbis type squashfs (ro,relatime) /mnt/mmcblk0p2/tce/optional/libogg-dev.tcz on /tmp/tcloop/libogg-dev type squashfs (ro,relatime) /mnt/mmcblk0p2/tce/optional/libogg.tcz on /tmp/tcloop/libogg type squashfs (ro,relatime) /dev/loop108 on /tmp/tcloop/puredata type squashfs (ro,relatime)
Note the mount source of
/dev/loop108instead of/mnt/mmcblk0p2....
The reason is that the "tce-load -i" command doesn't update the onboot.txt file which governs which packages are mounted at startup. Hence the mount is temporary.
best, Thomas
Dear all, puredata-0.48-1 is now in the PiCore repository! That's a binary build for tinycorelinux on Raspberry Pi. http://repo.tinycorelinux.net/9.x/armv6/tcz/ best, Thomas
-- Thomas Grill http://grrrr.org
Am 16.02.2018 um 23:58 schrieb Thomas Grill gr@grrrr.org:
Dear all, i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
Copy the package files from your local machine to the tinycore: scp $SOURCEDIR/puredata.tcz{,.dep,.md5.txt} tc@$TINYCOREIP:/etc/sysconfig/tcedir/optional/
then logon to the tinycore: ssh tc@$TINYCOREIP chown tc.staff /etc/sysconfig/tcedir/optional/puredata.tcz* chmod 664 /etc/sysconfig/tcedir/optional/puredata.tcz* echo puredata.tcz >> /etc/sysconfig/tcedir/onboot.lst
and reboot the tinycore
These are just the binary files needed to run pd. The doc/help files are in the puredata-doc.tcz package, the development header m_pd.h is in puredata-dev.tcz . To install those permanently, follow the procedure from above with changed package names.
best, Thomas
-- Thomas Grill http://grrrr.org
Am 15.02.2018 um 04:22 schrieb Dan Wilcox danomatika@gmail.com:
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Ah, i forgot... it would be cool for the future to have a buildable package with source included and working build scripts. Don't know when/whether i have the time for that, so if someone wants to stand in, please go for it. best, Thomas
Am 07.03.2018 um 09:35 schrieb Thomas Grill gr@grrrr.org:
Dear all, puredata-0.48-1 is now in the PiCore repository! That's a binary build for tinycorelinux on Raspberry Pi. http://repo.tinycorelinux.net/9.x/armv6/tcz/ best, Thomas
-- Thomas Grill http://grrrr.org
Am 16.02.2018 um 23:58 schrieb Thomas Grill gr@grrrr.org:
Dear all, i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
Copy the package files from your local machine to the tinycore: scp $SOURCEDIR/puredata.tcz{,.dep,.md5.txt} tc@$TINYCOREIP:/etc/sysconfig/tcedir/optional/
then logon to the tinycore: ssh tc@$TINYCOREIP chown tc.staff /etc/sysconfig/tcedir/optional/puredata.tcz* chmod 664 /etc/sysconfig/tcedir/optional/puredata.tcz* echo puredata.tcz >> /etc/sysconfig/tcedir/onboot.lst
and reboot the tinycore
These are just the binary files needed to run pd. The doc/help files are in the puredata-doc.tcz package, the development header m_pd.h is in puredata-dev.tcz . To install those permanently, follow the procedure from above with changed package names.
best, Thomas
-- Thomas Grill http://grrrr.org
Am 15.02.2018 um 04:22 schrieb Dan Wilcox danomatika@gmail.com:
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
It should work with makefile.gnu in src. We still need to update the autotools setup to support the "build in place" approach beyond the halfway symlinking it does now, so I wouldn't use the configure script et al. in the package for this yet.
On Mar 7, 2018, at 12:34 PM, Thomas Grill gr@grrrr.org wrote:
Ah, i forgot... it would be cool for the future to have a buildable package with source included and working build scripts. Don't know when/whether i have the time for that, so if someone wants to stand in, please go for it. best, Thomas
Am 07.03.2018 um 09:35 schrieb Thomas Grill gr@grrrr.org:
Dear all, puredata-0.48-1 is now in the PiCore repository! That's a binary build for tinycorelinux on Raspberry Pi. http://repo.tinycorelinux.net/9.x/armv6/tcz/ best, Thomas
-- Thomas Grill http://grrrr.org
Am 16.02.2018 um 23:58 schrieb Thomas Grill gr@grrrr.org:
Dear all, i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
Copy the package files from your local machine to the tinycore: scp $SOURCEDIR/puredata.tcz{,.dep,.md5.txt} tc@$TINYCOREIP:/etc/sysconfig/tcedir/optional/
then logon to the tinycore: ssh tc@$TINYCOREIP chown tc.staff /etc/sysconfig/tcedir/optional/puredata.tcz* chmod 664 /etc/sysconfig/tcedir/optional/puredata.tcz* echo puredata.tcz >> /etc/sysconfig/tcedir/onboot.lst
and reboot the tinycore
These are just the binary files needed to run pd. The doc/help files are in the puredata-doc.tcz package, the development header m_pd.h is in puredata-dev.tcz . To install those permanently, follow the procedure from above with changed package names.
best, Thomas
-- Thomas Grill http://grrrr.org
Am 15.02.2018 um 04:22 schrieb Dan Wilcox danomatika@gmail.com:
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote:
Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make.
I followed your instructions to build the dist tarball:
./autogen.sh ./configure make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
That's how i performed the compilation - the process, including the separation of the results into -bin, -dev and -doc packages should be made reproducible with some scripts. That is the wish of the picore repo keepers. best, Thomas
Am 07.03.2018 um 15:48 schrieb Dan Wilcox danomatika@gmail.com:
It should work with makefile.gnu in src. We still need to update the autotools setup to support the "build in place" approach beyond the halfway symlinking it does now, so I wouldn't use the configure script et al. in the package for this yet.
On Mar 7, 2018, at 12:34 PM, Thomas Grill <gr@grrrr.org mailto:gr@grrrr.org> wrote:
Ah, i forgot... it would be cool for the future to have a buildable package with source included and working build scripts. Don't know when/whether i have the time for that, so if someone wants to stand in, please go for it. best, Thomas
Am 07.03.2018 um 09:35 schrieb Thomas Grill <gr@grrrr.org mailto:gr@grrrr.org>:
Dear all, puredata-0.48-1 is now in the PiCore repository! That's a binary build for tinycorelinux on Raspberry Pi. http://repo.tinycorelinux.net/9.x/armv6/tcz/ http://repo.tinycorelinux.net/9.x/armv6/tcz/ best, Thomas
-- Thomas Grill http://grrrr.org
Am 16.02.2018 um 23:58 schrieb Thomas Grill gr@grrrr.org:
Dear all, i have just submitted picore extension packages for pd-0.48-1 to the respective repertory. I hope i have met all the requirements, so that the package can become canonical very soon.
If you want to install them in the meantime, please grab the files from http://l.grrrr.org/puredata_tcz The manual installation procedure is the following:
Copy the package files from your local machine to the tinycore: scp $SOURCEDIR/puredata.tcz{,.dep,.md5.txt} tc@$TINYCOREIP:/etc/sysconfig/tcedir/optional/
then logon to the tinycore: ssh tc@$TINYCOREIP chown tc.staff /etc/sysconfig/tcedir/optional/puredata.tcz* chmod 664 /etc/sysconfig/tcedir/optional/puredata.tcz* echo puredata.tcz >> /etc/sysconfig/tcedir/onboot.lst
and reboot the tinycore
These are just the binary files needed to run pd. The doc/help files are in the puredata-doc.tcz package, the development header m_pd.h is in puredata-dev.tcz . To install those permanently, follow the procedure from above with changed package names.
best, Thomas
-- Thomas Grill http://grrrr.org
Am 15.02.2018 um 04:22 schrieb Dan Wilcox danomatika@gmail.com:
Sweet, good to know. I think it would be good if the Pd distribution tarball was built this way so you don't need autoconf/autogen installed to build.
On Feb 15, 2018, at 4:20 AM, Chris McCormick chris@mccormick.cx wrote:
Hi Dan,
On 07/02/18 16:50, Dan Wilcox wrote: > Looks like an issue with autoconf of your system. If we used a dist tarball with pregenerated configure scripts, this probably wouldn't be an issue since then autoconf and automaker are not needed, just gcc and make. I followed your instructions to build the dist tarball:
> ./autogen.sh > ./configure > make dist
Then copied the tarball pd-0.48.1.tgz to the Raspberry Pi running Tiny Core Linux and ran:
./configure make
The resulting binary successfully runs a test tone Pd patch and outputs a sine wave to the audio jack.
Hope this helps!
Cheers,
Chris.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 07/03/18 16:35, Thomas Grill wrote:
puredata-0.48-1 is now in the PiCore repository!
\o/ thanks for your time and effort getting this in!
Chris.
- Thomas Grill gr@grrrr.org [2018-03-07 09:35]:
Dear all, puredata-0.48-1 is now in the PiCore repository! That's a binary build for tinycorelinux on Raspberry Pi. http://repo.tinycorelinux.net/9.x/armv6/tcz/
Thank you! This runs really great (compared to Pd on raspbian) on my version 1 RPi! I am currently wondering about realtime priorities:
When I launch pd as user 'tc' I get priority 94 scheduling failed. regardless if I use the -rt flag or not.
When I launch it as root using sudo with or without the -rt flag I get [...] priority 92 scheduling enabled. memory locking enabled. [...] audio buffer set to 25 configuring sound output... Sample width set to 2 bytes running at normal (non-real-time) priority. memory locking enabled. /usr/local/lib/pd/bin/pd-watchdog [...] and htop shows a -93 priority value. I am curious what the message about non-real-time priority means?
Furthermore, does anyone know if the 'tc' user can be added to an audiogroup, whose permissions could be elevated through /etc/security/limits.conf (currently not present in piCore).
This might be off-topic, but has anyone managed to create a persisntent home directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize already)?
I am so happy my patch runs without dropouts on the RPi 1 and that it boots so fast!
Hi,
On 11/07/18 04:13, Peter P. wrote:
Furthermore, does anyone know if the 'tc' user can be added to an audiogroup, whose permissions could be elevated through /etc/security/limits.conf (currently not present in piCore).
I think you could do this by settings the rtprio limit directly in: /opt/bootscript.sh
It seems that sysctl and ulimit can't set this but maybe this will help:
https://serverfault.com/questions/889635/seting-rtprio-limit-in-system-witho...
This might be off-topic, but has anyone managed to create a persisntent home directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize already)?
You can use the command filetool.sh -b to backup a snapshot of the
homedir to the SD card and it will be returned to that state on reboot.
There is also a kernel boot parameter to make the homedir persist automatically:
http://forum.tinycorelinux.net/index.php?topic=15450.0
I am so happy my patch runs without dropouts on the RPi 1 and that it boots so fast!
I'm a huge fan of this platform too! I had the original RPi 1 rendering mod files to Alsa out and only using 4% CPU.
Probably OT but I gave a talk about my experience with piCore last night at the local Linux users group:
https://github.com/chr15m/gnu-linux-in-tiny-places-plug
Cheers,
Chris.
Hi,
- Chris McCormick chris@mccormick.cx [2018-07-11 10:41]:
Hi,
On 11/07/18 04:13, Peter P. wrote:
Furthermore, does anyone know if the 'tc' user can be added to an audiogroup, whose permissions could be elevated through /etc/security/limits.conf (currently not present in piCore).
I think you could do this by settings the rtprio limit directly in: /opt/bootscript.sh
It seems that sysctl and ulimit can't set this but maybe this will help:
https://serverfault.com/questions/889635/seting-rtprio-limit-in-system-witho...
Thanks for that link! In this case I could run the patch as root anyway I think.
Interestingly, starting pd from /opt/bootlocal.sh as root at startup will make Pd use all of the CPU and hence produce stuttering audio. When I change the corresponding line in /opt/bootlocal.sh to start as user tc sudo -u tc /home/tc/myPdStartupScript.sh Pd runs normally.
This might be off-topic, but has anyone managed to create a persisntent home directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize already)?
You can use the command
filetool.sh -bto backup a snapshot of the homedir to the SD card and it will be returned to that state on reboot.
This is what I read from the docs and what I am currently using. Albeit, I am having a 300MB sound file in my home dir and it being part of the filetool.sh backup immensely slows down startup as the OS has to uncompress the audiofile.
There is also a kernel boot parameter to make the homedir persist automatically:
This is the method I am trying to use with a directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize to the full available space on the memory card). Possibly I have to try to shrink that partition to make space for yet another partition as dedicated /home. Any hints appreciated!
I am so happy my patch runs without dropouts on the RPi 1 and that it boots so fast!
I'm a huge fan of this platform too! I had the original RPi 1 rendering mod files to Alsa out and only using 4% CPU.
Probably OT but I gave a talk about my experience with piCore last night at the local Linux users group:
Nice, great talk!
P
Replying to myself below.
- Peter P. peterparker@fastmail.com [2018-07-11 12:31]:
Hi,
- Chris McCormick chris@mccormick.cx [2018-07-11 10:41]:
Hi,
On 11/07/18 04:13, Peter P. wrote:
Furthermore, does anyone know if the 'tc' user can be added to an audiogroup, whose permissions could be elevated through /etc/security/limits.conf (currently not present in piCore).
I think you could do this by settings the rtprio limit directly in: /opt/bootscript.sh
It seems that sysctl and ulimit can't set this but maybe this will help:
https://serverfault.com/questions/889635/seting-rtprio-limit-in-system-witho...
Thanks for that link! In this case I could run the patch as root anyway I think.
Interestingly, starting pd from /opt/bootlocal.sh as root at startup will make Pd use all of the CPU and hence produce stuttering audio. When I change the corresponding line in /opt/bootlocal.sh to start as user tc sudo -u tc /home/tc/myPdStartupScript.sh Pd runs normally.
This might be off-topic, but has anyone managed to create a persisntent home directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize already)?
You can use the command
filetool.sh -bto backup a snapshot of the homedir to the SD card and it will be returned to that state on reboot.This is what I read from the docs and what I am currently using. Albeit, I am having a 300MB sound file in my home dir and it being part of the filetool.sh backup immensely slows down startup as the OS has to uncompress the audiofile.
Managed to shrink the existing filesystem in /dev/mmcblk0p2 using resize2fs as well as the partition using fdisk. Created yet another partition /dev/mmcblk0p3 with an ext4 filesystem which now gets mounted as home with the boot option home=/dev/mmcblk0p3
There might be more elegant ways of doing this, but it works fine for me.
thanks Chris and list again, P
Hi all,
Am 11.07.2018 um 14:07 schrieb Peter P. peterparker@fastmail.com:
This might be off-topic, but has anyone managed to create a persisntent home directory inside /dev/mmcblk0p2 (the ext2/3 partition created by piCore itself, which I did maximize already)?
You can use the command
filetool.sh -bto backup a snapshot of the homedir to the SD card and it will be returned to that state on reboot.This is what I read from the docs and what I am currently using. Albeit, I am having a 300MB sound file in my home dir and it being part of the filetool.sh backup immensely slows down startup as the OS has to uncompress the audiofile.
Managed to shrink the existing filesystem in /dev/mmcblk0p2 using resize2fs as well as the partition using fdisk. Created yet another partition /dev/mmcblk0p3 with an ext4 filesystem which now gets mounted as home with the boot option home=/dev/mmcblk0p3
I do a similar thing, mounting an extra partition as read-only using /etc/fstab. I my home, i have a symbol link to the actual startup script on the extra partition. It is easy to remount the extra partition read/write when i have to update a project (which is usually simply a transfer from my laptop using rsync)
best, Thomas
-- Thomas Grill http://grrrr.org
-
Chris McCormick -
Dan Wilcox -
Peter P. -
Thomas Grill