Building zynthian image now works with docker

++++ grep 2018-11-13-raspbian-stretch-lite.img2
++++ awk ‘{print $4-0}’
+++ root_offset=50331648
+++ echo ‘Mounting image 2018-11-13-raspbian-stretch-lite.img on /distro/workspace/mount, offset for boot partition is 4194304, offset for root partition is 50331648’
Mounting image 2018-11-13-raspbian-stretch-lite.img on /distro/workspace/mount, offset for boot partition is 4194304, offset for root partition is 50331648
+++ sudo mount -o loop,offset=50331648 2018-11-13-raspbian-stretch-lite.img /distro/workspace/mount/
+++ [[ 1 != \2 ]]
++++ expr 50331648 - 4194304
+++ sudo mount -o loop,offset=4194304,sizelimit=46137344 2018-11-13-raspbian-stretch-lite.img /distro/workspace/mount/boot
mount: /distro/workspace/2018-11-13-raspbian-stretch-lite.img: failed to setup loop device: No such file or directory

  • exit 1

Sorry that this is little more than an error msg dump . . .

Perhaps I should dispose of my docker installation and start again . . .

sudo modprobe loop ?

No direct reply.

Tried that but I don’t see a loop module in lsmod after doing it . . .

and now I’m back to the instant error about the build.log… :frowning:

I’m sorry this has become just plain bewildering . . .
Time to read a docker book. . . .

Again . . .

No such file or directory error gives missing loopback kernel module too. On device tree loopback nodes created?

rmmod loop && ls /dev/loop*

ls: /dev/loop* ei saa kasutada: No such file or directory

modprobe loop && ls /dev/loop*

/dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/loop7 /dev/loop-control

root@wyleu-HP-G72-Notebook-PC:/home/wyleu# modprobe loop && ls /dev/loop*
/dev/loop0 /dev/loop11 /dev/loop14 /dev/loop17 /dev/loop2 /dev/loop3 /dev/loop6 /dev/loop9
/dev/loop1 /dev/loop12 /dev/loop15 /dev/loop18 /dev/loop20 /dev/loop4 /dev/loop7 /dev/loop-control
/dev/loop10 /dev/loop13 /dev/loop16 /dev/loop19 /dev/loop21 /dev/loop5 /dev/loop8
root@wyleu-HP-G72-Notebook-PC:/home/wyleu# rmmod loop && ls /dev/loop*
rmmod: ERROR: Module loop is builtin.

This is what I loath about docker . It has all the predictability of git …

You can use the vagrant build method if you don’t like docker.
Docker is good for this mostly because it works on cloud services.

I try to use Docker to make an image for my raspberry 4.
I use Linux Mint, to use Docker, I also need to install

When I run the building with step 9, I have an error about git not installed, since I don’t know what to do, I look in the source and finally add in Zynthianos/src/modules/zynthianos/start_chroot_script the line apt install git before gitclone.

With this modification, the build process run normally.
I see that start_chroot_script call the wrong sh file to buster :bash -x I think we need now bash -x

Do I need to make an issue on github?

How can I help, I’m not a developper but I make some compilation in the past and try to solve compilation error when possible

Yes please do, also provide a build.log from your build

Ok, I try another compilation with the modification of
The last build.log is more than 3MB, do I need to provide all the log?

Just for my knowledge, for the installation of git, start_chroot_script is the good place to make the modification?

Preferred you give all the log, you can snap parts but it would give the best picture of what is going on

For moment compilation is not finished, only error is on where we need to add apt install 2to3

Compilation is finished.
I put the bluid.log on ZynthianOs issue

Hi! Congratulations @lguyome45,

Please, send a testing report when you have tested your Buster Image :wink:

BTW, we already have a new Buster image in our Nightly Builds dir:

I can’t test here because i’m in a Masia (rural house) and my bandwidth is quite limited now, so please, let me know if someone test this image.


1 Like

Hello, Zynthian boots up ok on my V2 kit adapted for RPi4, b̶u̶t̶ ̶c̶o̶n̶t̶r̶o̶l̶ ̶k̶n̶o̶b̶s̶ ̶d̶o̶ ̶n̶o̶t̶ ̶w̶o̶r̶k̶. First test results of Pianoteq (using touch screen, which works) are good. No crackling, but both cores fully loaded. I will give it more time later.

Good work!

With my image compiled yesterday, I have this result :

  • ZynthianOs boots ok.
  • The control knobs works
  • Wifi seems to not working, I try to add my networks, wbconf interface did not show any SSID
  • Pianoteq stage 6.5.3 works without xrun a 22.1khz, at 44khz xruns comes. I don’t play many notes but I have the score of 17 in Pianoteq panel

Instruments Zynaddsubfx, Fluidsynth, setBfree, Calf monosynth, Helm, MDA DX10, JX10, E.piano, Nekobi, Noize Mak3r, Obxd, Roffo synth, Triceraptops, Vex, Wolpertinger, padthv1, synthv1, aeolus, all fluid instrument work

Mod-UI and pure data work. I will try later with Mod-UI, lv2 plugins

  • Linuxsampler does not show any preset
    Edit: I miss that there is no soundfont, I add one sfz(Salamander piano) but no sound, I have this message in the CLI:
    ERROR:root:sfz (ERR 0)

  • Dexed does not work

That’s all for moment, will try to run zynthian from CLI to have debug information


I can confirm what you said…on a v2 pi3plus

1 Like

The SFZ soundfont collection is not downloaded when building the image, but copied from a local directory, so your fresh-build image don’t have any SFZ for Linuxsampler.

Also, copying an SFZ to the directory doesn’t work., You have to create some bank directory, like “pianos”, and put your SFZ inside. Please, confirm that this work for you …


I erased my build and put the nightly which works, so until I make a new build I can’t test.
On the nightly build, work as expected, I will try to add some soundfont on nightly.

The big problematic for me is the missing wifi, I try the command ifup wlan0, the raspberry tell me that there is no wlan0

I will work on it ASAP.

I try to understand all modification made when running the installation process.
setup_system for buster make a firmware downgrade, I try to upgrade the firmware and after a reboot Wifi works :wink:

I make an issue

1 Like