@juntiedt For me it worked without issues.

I have just re-run the Evok installation script.
Now all inputs etc. work.

Maybe I chose wrong device before.

So Evok now also runs on Debian 11 / Bullseye. :)

@juntiedt There is now new Evok version on github: 2.4.20

It could work now with bullseye, however, when I tried to run the installation script on fresh RPI Bullseye 32 bit image, it seems to work mostly but I'm missing some digital inputs, relays and analog output.

Probably still needs some rework. But I'm optimistic that unipi team will fix it shortly.

Here again the screenshot.

Alternativly as link:
RPI bootup error

Hi all,

I'm currently experimenting to run my unipi 1.1 board with a raspberry compute module 4 and a nvme SSD with the official unipi 1.1 node red image (https://kb.unipi.technology/en:hw:03-unipi11:download-image:02-nodered).

Basically the node red image would work, but only if I boot it from SD card or emmc. May aim, however, is to boot it from the nvme SSD directly.

During bootup from nvme SSD, I'm getting the following error:

Can someone help me to get this fixed?

Regards,
Peter

I'm also curious on this one.

Because when I tried to install evok on fresh bullseye RPI OS according to this how-to (https://github.com/UniPiTechnology/evok#legacy-installation-process-using-a-shell-script-required-for-unipi-11), I could not use the evok GUI.

So to me it seems there might be a compatibility issue.

There is also an open github issue on this: https://github.com/UniPiTechnology/evok/issues/94