Deploy to RPI-4 not working

[Mark Greenway]

Clicked and created a new fleet.

Tried to deploy to RPi-4 64bit and page will not load

Changes to Variables :

• LAUNCH_URL : https://google.com

Changes to Device Variables:

• ENABLE_GPU: 1 (0 didn't work either)

Versions info

Logs after reboot.

Supervisor starting
<browsercontrol> running

<browsercontrol> warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]

<browsercontrol>       Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.

<browsercontrol> info: Microsoft.Hosting.Lifetime[0]

<browsercontrol>       Now listening on: http://[::]:80

<browsercontrol> info: Microsoft.Hosting.Lifetime[0]

<browsercontrol>       Application started. Press Ctrl+C to shut down.

<browsercontrol> info: Microsoft.Hosting.Lifetime[0]

<browsercontrol>       Hosting environment: Production

<browsercontrol> info: Microsoft.Hosting.Lifetime[0]

<browsercontrol>       Content root path: /app

<fbcp> WARNING: FBCP_DISPLAY variable not set.

<fbcp>  Set the value if you are using an attached display.

<wifi-connect> Checking internet connectivity ...

<wifi-connect> Your device is already connected to the internet.

<wifi-connect> Skipping setting up Wifi-Connect Access Point. Will check again in 120 seconds

<scheduler> crond[15]: crond (busybox 1.35.0) started, log level 8

<kiosk> user.max_user_namespaces = 10000

<kiosk> umount: /dev: target is busy.

<kiosk> mount: /sys/kernel/debug: nodev already mounted on /sys/kernel/debug.

<kiosk> Running balena base image entrypoint...

<kiosk> setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file

<kiosk> balenaBlocks browser version: 2.4.5

<kiosk> Setting CPU Scaling Governor to 'performance'

<kiosk> Disabling cursor

<kiosk> 

<kiosk> 

<kiosk> X.Org X Server 1.20.4

<kiosk> X Protocol Version 11, Revision 0

<kiosk> Build Operating System: Linux 5.10.0-10-arm64 aarch64 Debian

<kiosk> Current Operating System: Linux fbabc15b8629 5.15.92-v8 #1 SMP PREEMPT Wed Feb 8 16:47:50 UTC 2023 aarch64

<kiosk> Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=DC:A6:32:03:B8:54 vc_mem.mem_base=0x3ec00000 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-5ec9-44ab-9ff6-0251a5d22bcf rootwait

<kiosk> Build Date: 18 December 2021  09:05:36AM

<kiosk> xorg-server 2:1.20.4-1+deb10u4 (https://www.debian.org/support) 

<kiosk> Current version of pixman: 0.36.0

<kiosk> 	Before reporting problems, check http://wiki.x.org

<kiosk> 	to make sure that you have the latest version.

<kiosk> Markers: (--) probed, (**) from config file, (==) default setting,

<kiosk> 	(++) from command line, (!!) notice, (II) informational,

<kiosk> 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

<kiosk> (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul  1 02:39:34 2023

<kiosk> (==) Using system config directory "/usr/share/X11/xorg.conf.d"

<kiosk> (EE) 

<kiosk> Fatal server error:

<kiosk> (EE) AddScreen/ScreenInit failed for driver 0

<kiosk> (EE) 

<kiosk> (EE) 

<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.

<browsercontrol> warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]

<browsercontrol>       Failed to determine the https port for redirect.

<kiosk> xinit: giving up

<kiosk> xinit: unable to connect to X server: Cannot assign requested address

<kiosk> xinit: server error

<kiosk> Idling...

[Mike]

Same issue, I found the tagged release of 2.0.7 and tried that as well.

[Mark Greenway]

For those of you that cannot wait for this to work Anthias has an alternate solution that produces similar results. Including Fleet management with Balena.

You can see their instructions here : https://github.com/Screenly/Anthias/blob/master/docs/balena-fleet-deployment.md

[Mike]

@hurricanepkt I found a fix for it. The versions for the kiosk container and the fbcp container were significantly behind. All I had to do was update the version numbers and re-deploy the app.

Bump fbcp to 1.1.0

Bump kiosk (browser container) to 2.5.1

[Mike]

Tested the version bumps on an RPI 3 with 64-bit OS and Offical Raspberry Pi 7in Touchscreen, no issues there either.