Yes, the methods you linked to are not applicable to KMS. You need to find alternative techniques that do a similar thing. I was just hintimg at things you need to look at.
First find a way to detect the displays attached and secondly find a way to configure only the display you want.
You will need to remove 'display_auto_detect=1' as that will load up the correct dtoverlays but without the priority of display that you want. To reverse the priority you need to detect the displays yourself and only load the dtoverlays you need.
In PINN I sometimes had to detect the displays on first boot, alter config.txt, and then reboot to use the display configuration requested. But you may be able to do it using conditions in config.txt.
This is on my roadmap to implement but I'm afraid I have higher priority things to fix first. KMS has caused many things to change and I'm only just getting to grips with it myself.
First find a way to detect the displays attached and secondly find a way to configure only the display you want.
You will need to remove 'display_auto_detect=1' as that will load up the correct dtoverlays but without the priority of display that you want. To reverse the priority you need to detect the displays yourself and only load the dtoverlays you need.
In PINN I sometimes had to detect the displays on first boot, alter config.txt, and then reboot to use the display configuration requested. But you may be able to do it using conditions in config.txt.
This is on my roadmap to implement but I'm afraid I have higher priority things to fix first. KMS has caused many things to change and I'm only just getting to grips with it myself.
Statistics: Posted by procount — Sat Jul 06, 2024 8:06 am