lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<DC-IRC>
[Discord] <microlinux> I am trying all the workarounds, but so far no luck on resolving the issue
<DC-IRC>
[Discord] <microlinux> I can see anything weird when login into the other display, systemctl says its running fine
<DC-IRC>
[Discord] <microlinux> I can't see anything weird when login into the other display, systemctl says its running fine
<DC-IRC>
[Discord] <microlinux> @amazingfate solved, partially.. it was starting gdm on the other hdmi port. Can I force the other one???
<DC-IRC>
[Discord] <microlinux> Consider to help me on that. It's putting pressure on my type c connector
<DC-IRC>
[Discord] <microlinux> But glad that it's working as expected, sorta
<DC-IRC>
[Discord] <microlinux> On real, it shouldn't turn on an hdmi port that isn't connected, and it should only start gdm3 for the hdmi port that IS connected.
<DC-IRC>
[Discord] <microlinux> It also may increase a tiny bit the power consumption otherwise
<DC-IRC>
[Discord] <viraniac> You can override it by creating monitors.xml file and copying it to /var/lib/gdm3 directory. To automatically create the file, you can login to gnome and modify your display settings as needed using gnome-control-center. The monitors.xml will then be created in ~/.config/ directory. For copying it to the /var/lib/gdm3 directory, you can follow the "Setup default monitors settings <clipped message>