EDID on the Titanium

An EDID aware ScreenModes, 0.61, is now in the Titanium daily beta ROM, 09May17. The EDID aware Screen configuration tool, 0.40, is installed.

To avoid any softload issues the new ROM has been flashed.

With the machine configured :-

*st. MonitorType
MonitorType EDID
*st. Mode
Mode       Auto
*

And with Auto set in the Screen Configuration the Titanium starts in Mode 0 and enters a Mode 0 Desktop. The Raspberry Pi 3, using the same monitor, did successfully find the monitor’s native resolution.

Attempts to get to a sensible mode just result in “This screen mode is unsuitable for displaying the desktop”.

Guessing a bit, is this a missing LTRGB issue?

*SaveModeFile generates a sensible MDF. The raw data is not appended, if it was I would have included it.

Sounds like you might be better waiting for some official guidance from ROOL; the guesswork isn’t hitting many home runs here on the bleeding edge.

But in brief:

• You should select the named monitor in the Screen Setup plugin below Auto. The meaning of Auto is unchanged (run !Help for more details) and is trying to read the DB15 id pins. Then, select Native from the resolution menu (or a different resolution if a specific one is desired).
• There’s no need to configure the MonitorType CMOS particularly, that only affects discless boot (and the bit before getting to the desktop). The Screen Setup plugin respects that by not changing it (as for other non-Auto monitor types).

This post by David Pitt knows where raw data is, but if the exported MDF looks sensible it’s much more likely to be not selecting the named monitor right.

This post by David Pitt knows where raw data

In my capacity as David Pitt I can say that there is no raw data at that location on my Titanium. It is there on the RPi3.

There is no named monitor under Auto either on the Titanium, as there is on the RPi3.

In my capacity as David Pitt I can say that there is no raw data at that location on my Titanium.

Right, that looks like the components file update got missed. Sorry!
If you change castle.RiscOS.BuildSys.Components.ROOL.Titanium
and move “ScreenModes” up to the slot before “GC320Video” in the list, that should sort it out. Or wait for tomorrow’s freshly baked ROM.

move “ScreenModes” up to the slot before “GC320Video”

That works, many thanks.