Can't set monitor type
Chris Mahoney (1684) 2093 posts |
I updated the Boot application to the latest version today (by downloading the nightly HD4 zip and using the merge feature in Configure) and can no longer set the monitor type. When I go to Configure/Screen, it’s on Auto. If I pick any other type, colour depth and resolution, then click either Try or Set, then it drops to 640×480 and reverts to Auto. This didn’t happen in the past, but unfortunately I don’t know what the last-working version was. Does anyone else have the same issue? I’m on a Pi 1. |
Jon Abbott (1421) 2592 posts |
This is a long running issue. I think you can workaround it by deleting the configuration file from !Boot (which off the top of my head, is in one of the Boot subfolders, PreDesk perhaps) |
Chris Mahoney (1684) 2093 posts |
Thanks for the pointer, but unfortunately I haven’t been able to track down which file to delete. I found a handful of obey files called “Monitor” but they don’t appear to do anything. |
Chris Hall (132) 3494 posts |
!Boot.Choices.Boot.PreDesk.Configure.Monitor – it will say something like: LoadModeFile BootResources:Configure.Monitors.Other.Generic just comment out the second line with a ‘|’. I copy the original ‘Monitor’ file to somewhere else in PreDesk (and make sure it selects the mode I want) so it overrules the original. |
Chris Mahoney (1684) 2093 posts |
Hmm. I do have that file but it’s completely empty (0 bytes). |
John Williams (567) 768 posts |
Mine has a single pipe character (RPi with AnyMode, 5.23 (02-Jul-15)). |
Sprow (202) 1107 posts |
The PreDesk$Configure file can exist in one of precisely 3 states
It looks like when I grouped all the MDFs by manufacturer back in May, I didn’t spot that in the routine that writes the file out it uses the current monitor number to infer if ‘Auto’ was selected (which would be zero when the menu was one big one). Now that the monitors are grouped by manufacturer choosing the 0th model in any submenu is taken as meaning ‘Auto’, oops. Presumably most people don’t use the 0th model, or haven’t noticed.
That would just cause the boot sequence to fail and dump you in the desktop, because there’s nothing recreating the file you just deleted unless the rather drastic !ResetBoot is run. |
Chris Mahoney (1684) 2093 posts |
In the meantime I’ve replaced ScrnSetup (RO500Hook.Res.Configure) with the version from 5.22, which appears to have fixed the issue. Sprow: I do indeed use the 0th model (Other > Generic) because Auto dims the Resolution menu. It’s good to know why the problem exists! :) Thanks to everyone for your assistance. Edit: That was quick! Will test and confirm when I get a chance. Thanks again :) |
Chris Mahoney (1684) 2093 posts |
I updated ScrnSetup to the latest version (from HD4 2016-08-03) and I can confirm that it now allows me to choose Other > Generic without issue. Thanks! But… it’s now not possible to manually change it back to Auto. Fortunately this doesn’t affect me personally, but it looks like there is still an issue here :( |
Chris Mahoney (1684) 2093 posts |
Quick update: Confirmed all working with ScrnSetup 0.39 :) |