We’ve been very grateful to have early access to this board, not only so we could add balenaOS support, but also to think about all the new possibilities…
Very nice x3. Looking forward to getting my hands on the hardware end of october - hopefully. Or so x.x
… Raspberry 5s ordered, initial shipment planned for end October, I will IMMEDIATLY put them to the task of testing my Balena project on it!
Thank you so much Balena Team for the hard work and the Raspberry foundation for the early access,
BTW: I remember when I got delivery of my first Raspberry 4 and had to wait some month to get it supported, so count on me to provide you any feedback here! 
Henry
Thanks for sharing your feedback in the near future here @theonlyzby
Looking forward to test the Pi5 with balena as well!
I’ve gotten a new Raspberry Pi 5 and I’ve tried installing balenaOS on it using balena etcher. I’m running in to some problems related to /dev/vchiq - “No such file or directory”. Not sure what that is, but I see it in the docker-compose.yml file under devices in anthias-celery and anthias-server.
Hello @kwf first of all welcome to the balena community.
Could you please tell us more details of the balena version that you are using? Thanks!
Hi @mpous. Thanks for getting back to me!
I’m using 4.0.16, which is the only one I see available when adding a new device to my fleet.
Here’s a device that I just set up, but is having the issue:
Here are some lines from the device diagnostics:
Dec 01 12:43:24 c1260bcd8c94[2011]: [e[31merrore[39m] at fn (/usr/src/app/dist/app.js:10:9708)
Dec 01 12:43:24 c1260bcd8c94[2011]: [e[31merrore[39m] at processTicksAndRejections (node:internal/process/task_queues:96:5)
Dec 01 12:43:24 c1260bcd8c94[2011]: [e[31merrore[39m] Device state apply error Error: Failed to apply state transition steps. (HTTP code 500) server error - error gathering device information while adding custom device “/dev/vchiq”: no such file or directory Steps:[“start”]
Dec 01 12:43:24 c1260bcd8c94[2011]: [e[31merrore[39m] at fn (/usr/src/app/dist/app.js:10:9708)
Dec 01 12:43:24 c1260bcd8c94[2011]: [e[31merrore[39m] at processTicksAndRejections (node:internal/process/task_queues:96:5)
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[34minfoe[39m] Applying target state
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[33mwarne[39m] Could not parse config.txt entry: [cm4]. Ignoring.
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[33mwarne[39m] Could not parse config.txt entry: [all]. Ignoring.
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[33mwarne[39m] Could not parse config.txt entry: [pi4]. Ignoring.
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[33mwarne[39m] Could not parse config.txt entry: [all]. Ignoring.
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[36mevente[39m] Event: Service start {“service”:{“appId”:2082835,“serviceId”:2320090,“serviceName”:“anthias-server”,“commit”:“ef3aa05cc8fd34ddd42896d88981665f”,“releaseId”:2712039}}
Dec 01 12:43:56 balenad[2011]: time=“2023-12-01T12:43:56.607984258Z” level=error msg=“3de96c07323cda249be55cc0f63156f5e4fc4492be959903c17a002e50c12023 cleanup: failed to delete container from containerd: no such container”
Dec 01 12:43:56 balenad[2011]: time=“2023-12-01T12:43:56.608037684Z” level=error msg=“Handler for POST /containers/3de96c07323cda249be55cc0f63156f5e4fc4492be959903c17a002e50c12023/start returned error: error gathering device information while adding custom device "/dev/vchiq": no such file or directory”
Dec 01 12:43:56 c1260bcd8c94[2011]: [e[31merrore[39m] Scheduling another update attempt in 64000ms due to failure: Error: Failed to apply state transition steps. (HTTP code 500) server error - error gathering device information while adding custom device “/dev/vchiq”: no such file or directory Steps:[“start”]
Dear kwf,
the /dev/vchiq error is in regards to anthias trying to access the GPU interface of the Raspberry Pi, which was at this location in the past. With Raspberry Pi 5, this has significantly changed and is not compatible anymore. Looking at the source ( GitHub - Screenly/Anthias: The world's most popular open source digital signage project. ) you can see that Anthias does not support Raspberry Pi 5 yet, so this will not work without fix by the vendor. ( Anthias works on all Raspberry Pi versions, including Raspberry Pi Zero, Raspberry Pi 3 Model B, and Raspberry Pi 4 Model B. )
