Using various online suggestions found in forums and blogs on boot and setup adjustments I had managed to reduce a Raspian setup to boot headless and loading several instances of PD to run on a couple of reserved cores (using jack2) in about 23 seconds. Some of the obvious ones were purging any apps that would not be used as well as reducing the services. I think to remember that disabling networking made quite a difference as it avoids several ‘waiting’ loops, but obviously that restricts possible applications significantly and is therefore only useful if you are after a ’standalone’ audio setup.

I wish I would have kept a conclusive list what I had done and what worked, but as I had several quite severe fails in the process and I had tried that while being new to pi and linux, I ended up not quite having a complete overview of the final version and steps. I’m very interested in the piCore os, thanks Thomas for making compiles available for it!

Best, Sebastian On 5 Oct 2020, 22:29 +0100, Thomas Grill gr@grrrr.org, wrote:

Hi all, i am a big fan of the piCore os. [1] That is a stripped down read-only linux distro with loadable modules for alsa, pure data etc.. Boot times are considerable shorter than with raspbian. Of course it also needs some dedication to get used with it.

I have compiled pd, jack and libfftw3 for piCore 11, to be found here: https://grrrr.org/data/dev/picore/piCore-11/

best, Thomas

[1] http://tinycorelinux.net/11.x/armv6/releases/RPi/

...

Am 05.10.2020 um 17:05 schrieb Martin Peach chakekatzil@gmail.com:

It takes about a minute for the pi to boot. There is not much you can do about that.

Martiin

On Mon, Oct 5, 2020 at 11:03 AM Yann Seznec yann@yannseznec.com wrote:

...

Hi everyone, long time reader first time writer.

I’m wondering what people’s experiences are with regards to the startup time for running a patch on a raspberry pi.

For various reasons I’ve started to use Patchbox OS to auto-run my patches on startup, which is very reliable and consistent however it usually takes about 60 seconds from switching on to making sound. This is on various models of Raspberry Pi 3.

Has anyone managed to speed this up? I haven’t tried the Raspi 4, perhaps that is significantly faster?

Thanks, Yann

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

-- Thomas Grill http://grrrr.org

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

Late follow up for topic a my experiences and rfc.

roughly documented, in
https://git.iem.at/cm/diyasb see firmware/debian ...

With an Olimex A64, (quite like RaspPi3, but industrial specs), I run Debian (Armbian) now on many of them over 6 month outdoors, so quite stable and they boot in 20sec-30sec from internal emmc-flash with usb-sound devices. It quite fast (14s sec), except for Pd patch waiting for jackd 5-10 seconds with my systemd scripts, so there is room for improvement, systemd-analyze says::

algo@DIYasb5:~$ systemd-analyze Startup finished in 6.013s (kernel) + 27.266s (userspace) = 33.280s graphical.target reached after 14.179s in userspace

in details it blames:

algo@DIYasb5:~$ systemd-analyze blame 10.009s jackd.service 5.108s olsrd.service 3.271s armbian-ramlog.service 3.018s pd_stream.service 2.547s armbian-zram-config.service 1.829s dev-mmcblk1p1.device 948ms keyboard-setup.service 872ms ifupdown-pre.service 669ms systemd-udev-trigger.service 527ms man-db.service 521ms networking.service 510ms systemd-journald.service 423ms resolvconf.service 356ms darkice.service

note: olsrd for network-mesg is not needed so graphical.target is after pd is started with no-gui.

to start pd faster we could theoretically rearrange it, after sound.target and jackd.service, but I didn't succeed.

Any hints on optimize the systemd scripts are welcomed.

mfg winfried

Am Dienstag, 6. Oktober 2020, 17:29:24 CEST schrieb Yann Seznec:

Thanks for all the thoughts and feedback. I should have said that my 60 second boot time is when I use the Pi headless, console-only, running the patch with -nogui.

I’ll have a look at disabling some things as suggested, and I’ll report back if I make any significant progress! I imagine I’m not alone in this quest so I’ll try and document it somehow, or at least post it here for future generations.

I really like the look of piCore OS too. It seems like the right approach for me in the long run, though I am wary of jumping into a new system. Maybe eventually we can make our own pdCore OS :)

...

On Oct 5, 2020, at 5:27 PM, Thomas Grill gr@grrrr.org wrote:

Hi all, i am a big fan of the piCore os. [1] That is a stripped down read-only linux distro with loadable modules for alsa, pure data etc.. Boot times are considerable shorter than with raspbian. Of course it also needs some dedication to get used with it.

I have compiled pd, jack and libfftw3 for piCore 11, to be found here: https://grrrr.org/data/dev/picore/piCore-11/

best, Thomas

[1] http://tinycorelinux.net/11.x/armv6/releases/RPi/

...

Am 05.10.2020 um 17:05 schrieb Martin Peach chakekatzil@gmail.com:

It takes about a minute for the pi to boot. There is not much you can do about that.

Martiin

On Mon, Oct 5, 2020 at 11:03 AM Yann Seznec yann@yannseznec.com wrote:

...

Hi everyone, long time reader first time writer.

I’m wondering what people’s experiences are with regards to the startup time for running a patch on a raspberry pi.

For various reasons I’ve started to use Patchbox OS to auto-run my patches on startup, which is very reliable and consistent however it usually takes about 60 seconds from switching on to making sound. This is on various models of Raspberry Pi 3.

Has anyone managed to speed this up? I haven’t tried the Raspi 4, perhaps that is significantly faster?

Thanks, Yann

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list%3E%3E

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list%3E

-- Thomas Grill http://grrrr.org

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

Am Montag, 19. Oktober 2020, 11:44:20 CEST schrieb Roman Haefeli:

On Mon, 2020-10-19 at 11:08 +0200, Winfried Ritsch wrote:

...

algo@DIYasb5:~$ systemd-analyze blame

     10.009s jackd.service

That seems long. How does the systemd unit file looks like? It appears jackd fires up quicker (<1s) on my old RPi 3, but then I might be fooled by the fact that it has been loaded before and it would require more time after boot.

thanks for the info, the problem was not really correct addressed:

In experiments I saw it will take 10 seconds to savely start pd after jackd So I put an 10s in jackd.service: ExecStartPost=/bin/sleep ${WAIT_AFTER_START}

The problem is jackd either provides dbus or socket-connection socket to late or the connection is not established because some parameters didnt stabilize, such as sound card binding with samplerate... but I didnt try to hard to find the reason, since for this purpose it was sufficient.

But for new applications (streaming box) I want a faster boot up

mfg winfried

Roman