Headless Pi 3B+ running 5.28

Some time ago, there has been discussion on running RISC OS Pi headless.

I have just tried to setup a Pi 3B+ to run headless with a new download of 5.28.

It worked first time and gave a VNC screen size of 640×480, But ….

The file Resources:$.Resources.ScreenMode.Monitors.EDID0 is missing from the build, so I get an error from Screen Configuration when I try to set the boot screen size.

Is this a bug or have I done something silly?

I get an error from Screen Configuration when I try to set the boot screen size.

Try selecting a “real” monitor (e.g. Acorn AKF85) which will give you a range of screen sizes to choose from.

If you actually want 1920×1080 (or similar) you’ll have to construct your own MDF because – as you’ve discovered – there’s no EDID. Alternatively, set hdmi_group and hdmi_mode in config.txt and add “disable_mode_changes” to cmdline.txt

The Other.Generic MDF has a particularly fine selection of sizes, including 1920×1080.

Sorry. I did not make myself clear.

5.27 RC16 and 5.29 all have the EDID0 file and do not give the error.

The file appears to be missing on 5.28. Why?

Now running OS5.28 on a headless RPi3B+ with MonitorType EDID configured. As it is headless there is no EDID0 file but there is no error on selecting something else from the Screen Configuration.

Take 2. Start up with EDID configured and a monitot connected, the Resources:$.Resources.ScreenMode.Monitors.EDID0 file is now there. Set Native in Screen configuration an this file is referenced in !Boot.Choices.Boot.PreDesk.Configure.Monitor with this :-

LoadModeFile Resources:$.Resources.ScreenMode.Monitors.EDID0

Disconnect the Monitor and restart the Pi. The EDID0 file is not there but the reference to it remains in Choices. The missing EDID0 error as reported above does initially occur when opening the Screen Configuration but it was possible to clear the error and configure something.

HTH.

The missing EDID0 error as reported above does initially occur when opening the Screen Configuration but it was possible to clear the error and configure something.

Thank You. I know how to clear work around the the error. I had to do it previously.

I am just disapointed that I had to do it again.