Closed gitroli closed 2 days ago
We had a similar problem to you, try changing setting "vc4-fkms-v3d" instead of "vc4-kms-v3d" in your device's dt_overlay configuration.
I didn't help, same situation, screen, stays black.
Alright, what screen are you using? If you're using an external touchscreen then try booting the raspberry pi with a HDMI screen instead, this could help narrow the problems down a bit.
Also, are you able to view the terminal in the Balena dashboard? If you can then it would be helpful to see the logs.
Lastly, does the raspberry pi display the Balena logo and then go blank, or does it not output anything at all?
I tried Touch Monitor Hannspree and also normal TV with HDMI.
I can enable terminal, but I didnt try so far, because its running in kiosk mode.
On boot I see the balena logo on fullscreen.
Alright, I'll wait until you give me the logs, but the fact that you see the Balena logo rules out the possibility of an incorrect OS configuration.
which logs do you need exactly, can I copy the logs also from the balena webinterface, because on terminal with keyboard it is hard to copy
You can copy the logs from the Balena dashboard, they should be identical to the logs on the device.
`
Here is only the kiosk (balenablock browser) filtered:
kiosk 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=1920,1080,--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-blacklist,--enable-gpu-rasterization,--user-data-dir=/data/chromium
kiosk Displaying URL: --app= http://google.at
kiosk (node:385) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:35173
kiosk at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
kiosk (node:385) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
kiosk (node:385) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I'm not a JavaScript expert, but it appears as if the browser is running into an unhandled exception:
UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:35173
Have you tried setting the LAUNCH_URL
variable to nothing, so that it will attempt to display the default html page?
It seems the issue is known: https://github.com/balena-os/meta-balena/issues/2319
but I find no solution
Is there any particular reason you need to use such an outdated OS? The latest version is 2.98.11!
yes I am using 2.98.11, it is not working with this version, chromium is only working when balena OS <= 2.85
We had a similar problem to you, try changing setting "vc4-fkms-v3d" instead of "vc4-kms-v3d" in your device's dt_overlay configuration.
This has helped me. I was having a black screen and changed the dt_overlay and now it works for me on the latest stable balenaOS.
I tried this already, but it didnt help.
I tried this already, but it didnt help.
In the past, I had issues with the browser when another container on my device was trying to use udev for USB access. Do you have other containers with UDEV=on?
No
I think this is the problem: It seems the issue is known: https://github.com/balena-os/meta-balena/issues/2319
I get no screen, just black, when using balenaOS > 2.80.5+rev1 I am using RPi4. Is there any fix or idea for that?