MoOde Audio

[neric34]

Hi,
I used PINN to install MoOde and LibreElec on a Pi4. It works very well. But I can't update MoOde... I think the new version isn't "in-place update", a new image is needed, I believe.
Could you update MoOde on PINN, please ?
I would like to try to do it but I don't have that much skills...
I'll maybe try with pinnify, if it's work ?

Thx

[VortexNexus]

Hi,

@procount
Using parts of the procedure defined in the wiki, I tried to create my own partitions TAR files based on MoOde 9 (bookworm). But there was something strange with PINN installation of the OS. MoOde started normally and then after about 2-3 seconds restarted automatically and crashed. Then, I was not able to boot anything, having even PINN's installation broken.

As perhaps you know, during MoOde's boot up, a PHP script is launched that makes checks and configuration stuff. Among others, it checks the /boot/firmware/config.txt file, replacing it when it doesn't match the expected structure. Another important point is that MoOde uses PARTUUID to define its partitions in cmdline.txt and fstab files, so I had to update those files with the standard partitions paths instead of PARTUUIDs before creating the TAR files.

What I noticed while retrying, was that PINN defined MoOde's boot partition in fstab as /dev/mmcblk0p01, that means the very PINN's boot partition ... After that, the PHP script defines the config.txt file it founds (PINN's one) as broken and replaces it, breaking down PINN's boot process. When I manually update MoOde's fstab file before its first boot, then everything goes fine.

Could you tell me if PINN expects any special placeholders values for partition names in cmdline.txt and fstab files in the TAR files ?

@neric34
It's quite an old thread,for sure, but the procedure defined in the wiki can help you. Be aware that it's a little old and some commands won't work without a little refresh through googling. But in the case you don't need more than one OS on the same PI, you can just install MoOde following its normal install process through Raspberry Pi Imager.

[procount]

It looks like you are installing to SD card, so PINN will use the /dev/mmcblk0pX notation. If installing to USB, then it would use PARTUUIDs. I can't remember if you can force PARTUUIDs on an SD card. In any case, it is the responsibility of partition_setup.sh to set up the OS for multiboot by adjusting the cmdline.txt and /etc/fstab files. So the original values in the TAR files are irrelevant apart from pattern matching in the script file. You should be able to parse the parameters passed from PINN to the script and adjust the files as required.

[VortexNexus]

Yes, I am installing on a SD card, you're right, using the /dev/mmcblk0pX notation. The partition_setup.sh script I use is the one present in the original MoOde PINN install directory. A header comment says this is the standard Raspbian Full one. I don't understand why it doesn't work. It seems that the boot partition name given by PINN to the script's parameters is not the good one. This is perhaps due to my installation process: I asked PINN to create the data partition and two project reservations. Then I directly asked PINN to replace the first project by my custom MoOde image taken from my traditional os subdir ;-). What do think?

[VortexNexus]

I tried another installation procedure asking PINN to create the data partition and directly install MoOde and one project reservation, but same result with MoOde automatically restarting and rewriting PINN's config.txt.
Could you tell from where is given the boot partition name to the partition_setup.sh script ? In the case the caller of this script is a system part, it could be modified in the MoOde system and therefor could be somehow "hardcoded" to the first partition of the device ...

[procount]

Sorry, I have no time to look at the moment.
But if MoOde is based on raspios or the latest kernel, then perhaps its partition_setup.sh script should be looking in the /firmware folder for cmdline.txt......? Have a look at the raspios partition_setup.sh for similar changes.

I'm afraid there's no guarantee that things don't have to change when you try to convert an upgraded OS. It's at the whim of the maintainers. Sometimes it is easy, other times more tricky! 😄

[VortexNexus]

So, my bad, you are right 😅, sorry. The MoOde version in PINN's files is 8.0.2 based on RaspiOS Bullseye and kernel 5.15. From the 2023-10-10 release, /boot mount point has been moved to /boot/firmware in RaspiOS. And the partition_setup.sh changed, removing two space chars so that the sed command works ... So using the new version of RaspiOS' partition_setup.sh script solved my problem 😏

As always, thanks a lot for your help and your work 👍