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
@nmaas87 let us know when you will get your own Pi 5 
… 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. )
Thansk for sharing @kwf and @nmaas87 I think @vpetersson can help more on this
This should probably be moved to the Anthias forum if it’s an Anthias specific issue.
Great! i have two RPI5’s and am using them with the browser block.
but i cant seem to get video output unless i delete the “vc4-kms-v3d” from the "Define DT overlays
" parameter. but without that parameter i cant get the display resolution to 4K
With the “vc4-kms-v3d” parameter set im getting the error: Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices any idea?
2023-12-09T12:24:35+01:00 Supervisor starting
2023-12-09T12:24:30+01:00 browser user.max_user_namespaces = 10000
2023-12-09T12:24:30+01:00 browser umount: /dev: target is busy.
2023-12-09T12:24:31+01:00 browser Running balena base image entrypoint…
2023-12-09T12:24:32+01:00 browser setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
2023-12-09T12:24:32+01:00 browser balenaLabs browser version: 2.6.0
2023-12-09T12:24:32+01:00 browser Setting CPU Scaling Governor to ‘performance’
2023-12-09T12:24:32+01:00 browser Disabling cursor
2023-12-09T12:24:32+01:00 browser hostname: No address associated with hostname
2023-12-09T12:24:32+01:00 browser xauth: (stdin):1: bad display name “7f72edd:0” in “add” command
2023-12-09T12:24:32+01:00 browser
2023-12-09T12:24:33+01:00 browser
2023-12-09T12:24:33+01:00 browser X.Org X Server 1.20.11
2023-12-09T12:24:33+01:00 browser X Protocol Version 11, Revision 0
2023-12-09T12:24:33+01:00 browser Build Operating System: linux Debian
2023-12-09T12:24:33+01:00 browser Current Operating System: Linux 7f72edd 6.1.54-v8 #1 SMP PREEMPT Wed Sep 27 16:45:31 UTC 2023 aarch64
2023-12-09T12:24:33+01:00 browser Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:BD:6B:89 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 rootfstype=ext4 rootwait dwc_otg.lpm_enable=0 rootwait vt.global_cursor_default=0 console=null cgroup_enable=memory root=UUID=ba1eadef-63f9-435a-90cf-44d085bed149
2023-12-09T12:24:33+01:00 browser Build Date: 25 October 2023 07:47:13AM
2023-12-09T12:24:33+01:00 browser xorg-server 2:1.20.11-1+deb11u8 (Debian -- User Support)
2023-12-09T12:24:33+01:00 browser Current version of pixman: 0.40.0
2023-12-09T12:24:33+01:00 browser Before reporting problems, check wiki.x.org
2023-12-09T12:24:33+01:00 browser to make sure that you have the latest version.
2023-12-09T12:24:33+01:00 browser Markers: (–) probed, (**) from config file, (==) default setting,
2023-12-09T12:24:33+01:00 browser (++) from command line, (!!) notice, (II) informational,
2023-12-09T12:24:33+01:00 browser (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
2023-12-09T12:24:33+01:00 browser (==) Log file: “/var/log/Xorg.0.log”, Time: Sat Dec 9 11:24:33 2023
2023-12-09T12:24:33+01:00 browser (==) Using system config directory “/usr/share/X11/xorg.conf.d”
2023-12-09T12:24:33+01:00 browser (EE)
2023-12-09T12:24:33+01:00 browser Fatal server error:
2023-12-09T12:24:33+01:00 browser (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
2023-12-09T12:24:33+01:00 browser (EE)
2023-12-09T12:24:33+01:00 browser (EE)
2023-12-09T12:24:33+01:00 browser Please consult the The X.Org Foundation support
2023-12-09T12:24:33+01:00 browser at http://wiki.x.org
2023-12-09T12:24:33+01:00 browser for help.
2023-12-09T12:24:33+01:00 browser (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
2023-12-09T12:24:33+01:00 browser (EE)
2023-12-09T12:24:33+01:00 browser (EE) Server terminated with error (1). Closing log file.
2023-12-09T12:24:47+01:00 browser xinit: giving up
2023-12-09T12:24:47+01:00 browser xinit: unable to connect to X server: Connection refused
2023-12-09T12:24:47+01:00 browser xinit: server error
2023-12-09T12:24:47+01:00 browser xauth: (argv):1: bad display name “7f72edd:0” in “remove” command
2023-12-09T12:24:47+01:00 browser Idling…
Versions:
HOST OS VERSION balenaOS 4.0.16
OS VARIANT production
SUPERVISOR VERSION 15.1.0
CURRENT RELEASE (browser block) 2.6.0
I removed Helium Lora Hat from Nebra M1 helium miner (RPI4) and connected to RPI5 (4GB). Installed Balena OS (with RPI5 support). I can see ecc chip in /dev/i2c-1 but I always get error accessing/testing it:
root@0741433:/dev# ./gateway_mfr --device ecc://i2c-1 info
Error: timeout/retry error.
I installed Nebra Helium miner (GitHub - NebraLtd/helium-miner-software: Software for Nebra (and third party) Helium Miners), but of course Im getting error regarding ecc crypto chip (i2c-1). I tried to add/change setting in DT params / DT overlay regarding i2c but it did not help. Any hints ? In raspberry Pi OS (Bookworm) i2c-1 works fine.
Hello @daimonion first of all welcome to the balena community!
Did you try asking to the Nebra support?
My hypothesis is that the device tree might be different to connect the Nebra hat, but i’m not sure about what is needed. Do you know if there is any change to the Device Tree for the Nebra hotspot?
Today I tested it with RAK/MNTD lora module (taken from MNTD Helium miner) with same result. Also found this older discussion I2C I/O error, or timeout
Not sure if it is related. This guy had simmilar issue on RPI4 with 64 bit Balena OS - but only inside docker container.
He also mentioned i2c worked fine (in container) in Raspbian OS.
Here is mine output from BalenaOS on RPI5
lsmod | grep i2c
i2c_dev 20480 0
i2c_brcmstb 16384 0
i2c_designware_platform 16384 0
i2c_designware_core 24576 1 i2c_designware_platform
And here same command from Raspbian OS - RPI5 (i2c working):
lsmod | grep i2c
i2c_dev 65536 0
i2c_brcmstb 65536 0
i2c_designware_platform 65536 0
i2c_designware_core 65536 1 i2c_designware_platform
I have the same problem. I tried with my new balena Account to set up a kiosk on a Raspberry 5 to
create the solution from Put friends and loved ones on the big screen with this instant video call project - balena Blog
But I can’t bring my raspi 5 to show anything beyond the Balena logo.
I’m running supervisor [15.3.1], Release 2.0.6 and [balenaOS 5.1.37+rev5],
balena-dash was downloaded yesterday from GitHub - balena-labs-projects/balena-dash: Build a Raspberry Pi based desktop dashboard for stats, photos, videos and more!
and installed using CLI.
kiosk Fatal server error:
kiosk (EE)
kiosk (EE)
kiosk (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
kiosk Please consult the The X.Org Foundation support
kiosk at http://wiki.x.org
kiosk for help.
kiosk (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
kiosk (EE)
kiosk (EE) Server terminated with error (1). Closing log file.
Thanks for sharing the logs @Playaowl some applications are broken to move from Pi 4 to Pi 5. We are organising a webinar to explain the differences here. Feel free to join and ask questions.
In the meantime, we are going to check with my colleagues what we can do here. I have seen that you created the github issue here! Good idea!
BTW welcome to the balena community!