RPI5 with Balena Browser and RPi Touchscreen 2

Hello,
I am using RPI5 4GB Ram with BalenaOS(balenaOS 6.9.4+rev1) Supervisor Version(17.2.1) and connected an official RaspberryPi Touchscreen 2. I have uploaded balena browser project on my device. I am able to see the splash screen on the Display but after that every thing is blank. When I remove the Touch Display and Connect an HDMI monitor it is working fine. The whole touch setup is also working with RPI4. But I am only encountering this problem when connecting the touch display with Rpi5 4GB Ram. Here is my container logs

2025-12-27T14:54:43.578844000Z user.max_user_namespaces = 10000
2025-12-27T14:54:43.709730000Z Running balena base image entrypoint…
2025-12-27T14:54:44.167609000Z setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
2025-12-27T14:54:44.294946000Z balenaLabs browser version: 2.12.0
2025-12-27T14:54:44.295123000Z Setting CPU Scaling Governor to ‘performance’
2025-12-27T14:54:44.295223000Z Disabling cursor
2025-12-27T14:54:44.295287000Z Raspberry Pi 5 detected, injecting X.org config
2025-12-27T14:54:44.333889000Z xauth: file /home/chromium/.Xauthority does not exist
2025-12-27T14:54:44.336895000Z xauth: (stdin):1: bad display name “836e862:0” in “add” command
2025-12-27T14:54:44.337846000Z
2025-12-27T14:54:44.348689000Z
2025-12-27T14:54:44.348887000Z X.Org X Server 1.21.1.16
2025-12-27T14:54:44.348925000Z X Protocol Version 11, Revision 0
2025-12-27T14:54:44.348951000Z Current Operating System: Linux 836e862 6.12.61-v8-16k #1 SMP PREEMPT Tue Dec 9 15:09:13 UTC 2025 aarch64
2025-12-27T14:54:44.348979000Z Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 numa=fake=8 system_heap.max_order=0 iommu_dma_numa_policy=interleave smsc95xx.macaddr=2C:CF:67:84:AA:6E vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 rootfstype=ext4 rootwait dwc_otg.lpm_enable=0 rootwait console=null quiet splash vt.global_cursor_default=0 consoleblank=0 cgroup_enable=memory root=UUID=ba1eadef-d31a-48a3-a544-9d3be1eb2433
2025-12-27T14:54:44.349021000Z xorg-server 2:21.1.16-1.3+rpt1+deb13u1 (Debian -- User Support)
2025-12-27T14:54:44.349046000Z Current version of pixman: 0.44.0
2025-12-27T14:54:44.349069000Z Before reporting problems, check http://wiki.x.org
2025-12-27T14:54:44.349093000Z to make sure that you have the latest version.
2025-12-27T14:54:44.349117000Z Markers: (–) probed, (**) from config file, (==) default setting,
2025-12-27T14:54:44.349141000Z (++) from command line, (!!) notice, (II) informational,
2025-12-27T14:54:44.349175000Z (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
2025-12-27T14:54:44.349202000Z (==) Log file: “/var/log/Xorg.0.log”, Time: Sat Dec 27 14:54:44 2025
2025-12-27T14:54:44.349226000Z (==) Using config directory: “/etc/X11/xorg.conf.d”
2025-12-27T14:54:44.349249000Z (==) Using system config directory “/usr/share/X11/xorg.conf.d”
2025-12-27T14:54:44.565137000Z — List Input Devices —
2025-12-27T14:54:44.567373000Z ⎡ Virtual core pointer id=2 [master pointer (3)]
2025-12-27T14:54:44.568544000Z ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
2025-12-27T14:54:44.568754000Z ⎜ ↳ 11-005d Goodix Capacitive TouchScreen id=6 [slave pointer (2)]
2025-12-27T14:54:44.568789000Z ⎣ Virtual core keyboard id=3 [master keyboard (2)]
2025-12-27T14:54:44.568822000Z ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
2025-12-27T14:54:44.568849000Z ↳ pwr_button id=7 [slave keyboard (3)]
2025-12-27T14:54:44.568877000Z ↳ vc4-hdmi-0 id=8 [slave keyboard (3)]
2025-12-27T14:54:44.568904000Z ↳ vc4-hdmi-1 id=9 [slave keyboard (3)]
2025-12-27T14:54:44.568929000Z ----- End of List --------
2025-12-27T14:54:44.568953000Z Detecting window size from framebuffer
2025-12-27T14:54:44.569411000Z Window size detected as 720,1280
2025-12-27T14:54:44.614019000Z Installed browser version: Chromium 143.0.7499.109 built on Debian GNU/Linux 13 (trixie)
2025-12-27T14:54:44.784982000Z Browser API running on port: 5011
2025-12-27T14:54:44.785555000Z Using LAUNCH_URL: https://www.google.com
2025-12-27T14:54:44.786003000Z Enabling GPU
2025-12-27T14:54:44.786093000Z Enabling KIOSK mode
2025-12-27T14:54:44.786191000Z Starting Chromium with flags: --disable-features=TranslateUI,–disable-component-extensions-with-background-pages,–disable-background-networking,–disable-sync,–metrics-recording-only,–disable-default-apps,–no-default-browser-check,–no-first-run,–disable-backgrounding-occluded-windows,–disable-renderer-backgrounding,–disable-background-timer-throttling,–force-fieldtrials=*BackgroundTracing/default/,–window-size=720,1280,–window-position=0,0,–autoplay-policy=no-user-gesture-required,–noerrdialogs,–disable-session-crashed-bubble,–check-for-update-interval=31536000,–disable-dev-shm-usage,–enable-zero-copy,–num-raster-threads=4,–ignore-gpu-blocklist,–enable-gpu-rasterization,–enable-features=Vulkan
2025-12-27T14:54:44.786294000Z Displaying URL: --app= https://www.google.com
2025-12-27T14:54:45.823143000Z Chromium remote debugging tools running on port: 35173

I have also added this in my DTOVERLAY configuration “vc4-kms-v3d”,“vc4-kms-dsi-ili9881-7inch”,
Define device GPU memory in megabytes is set to 396
BALENA_HOST_CONFIG_display_auto_detect is set to 1

Can anyone help me here I have no Idea what I am doing wrong here.

Thank you

Hi @mani13jha ,

Looks like you are doing the right things e.g. BALENA_HOST_CONFIG_display_auto_detect set to 1. I replicated the core of what you describe i.e. blank screen, when using an older Pi5. Updating the Pi5 EEPROM resolved the issue.

As you probably know, there are several ways to update the Pi5 EEPROM. For a Pi5 running balenaOS the quickest may be to use Raspberry Pi Imager to create an microSD card whose sole purpose is to update EEPROM. The process is described here: Raspberry Pi 5 EEPROM Recovery Guide – Pi Australia. Once the EEPROM is updated, swap back in your regular microSD card.

1 Like

Hi @rosswesleyporter ,
Thank You for the reply, but I was able to solve the problem. I just tweaked the DTOVERLAY configuration and it was working.
Before
DTOVERLAY configuration “vc4-kms-v3d”,“vc4-kms-dsi-ili9881-7inch”
After
DTOVERLAY configuration “vc4-kms-dsi-ili9881-7inch”.