Quick update:
-
Built the balena browser block on top of balenalib/jetson-orin-nx-seeed-j4012-node:20-bookworm-run, pulling our custom Chromium (~3 GB) at runtime into /mnt/data and wiring Xorg (startx) with a fallback fbdev config. With /dev/dri mapped and the usual X packages installed, the kiosk comes up reliably.
-
That gets us to the same place as before though: chrome://gpu is still “Software only”. On our Orin NX dev kit running stock Ubuntu + JetPack 5.1.3 the exact same Chromium build reports full HW acceleration, so the binary itself is fine.
-
Digging through the balena hostapp we can’t find the Tegra EGL/GLES stack at all (libEGL.so, libGLESv2.so, libnvidia-egl-wayland.so, etc.), so the container only sees Mesa stubs. Until we can source those NVIDIA userspace libraries (and the matching /dev/nvhost-* nodes) inside the container, Chromium will stay in software mode.
If anyone has guidance on the “official” way to surface the Jetson EGL/GLES libs on balena, whether via bind mounts from the hostapp or a recommended BSP layer, that would unblock the next step. Happy to test any suggestions.
Thx!