Jivelite not working after enabling SD Card Write Protection

Max2Play Home › Forums › Max2Play Add-ons › Jivelite not working after enabling SD Card Write Protection

Tagged: 

Viewing 4 posts - 1 through 4 (of 4 total)
  • Back to forum
    Posted in: Max2Play Add-ons
  • peterbite premium
    16. April 2021 at 10:30 #51135

    Hi,
    i just did a fresh install on/of:
    – Raspi 2
    – Hifiberry DAC+
    – 7″ Touchdisplay
    – mp2_buster_rpi-v253 Image
    – Installed/configured Hifiberry and Display with Max2play addons.
    – squeezelite, jivelite (no LMS)
    Everything worked fine.

    Then I installed the SD Card Write Protection and rebooted.
    Jivelite did not start. (Squeezelite played music fine.)
    After uninstalling the SD Card Write Protection addon, everything worked fine, again.

    What did I do wrong?
    Should I have used the mp2_stretch_rpi-v251_7zoll Image?

    Thanks for the help!

    MarioM Moderator
    20. April 2021 at 14:12 #51141

    Hi Peter,

    The write protection plugin has often caused problems in the past. Some services, such as the Squeezebox Server or Jivelite, have to write to the SD card regularly in order to function correctly. The write protection plugin prevents this. We therefore recommend the use of write protection only for very specific applications. If you system doesn’t depend on it, I would recommend you not to use the plugin for now.

    By the way, we primarily develop for the Raspberry Pi 3 and 4. So it can happen that the new buster image causes problems with older Pis. In this case, I would also recommend switching to stretch.

    peterbite premium
    20. April 2021 at 15:02 #51144

    So, will the write protection plugin work with the special „7zoll“ image?

    Is there anything done differently with jivelite in that image?

    Is it worth trying and possibly wasting some time?

    MarioM Moderator
    20. April 2021 at 15:51 #51146

    Hi Peter,

    No, I don’t think the 7 inch stretch image will make any difference. We are currently evaluating internally how we can optimize the write protection plugin and better communicate its use cases and restrictions.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here