Sorry for not getting back sooner. I’ve typed this response twice and removed it because I keep figuring out a little bit more.
So, I have a 4k@120 hz monitor (my tv) along with the Neo G9. I couldn’t get the board at first to do anything but boot loop after the second half of start startup with just the 4k. With the 4k and the Neo, the display manager would load and let me login. The whole time the Neo caught in a turn on/off loop with a bunch of noise in dmesg that I will post shortly. I unplugged the Neo and ran updates and rebooted. Now the board will allow the 4k to start the dm by itself. I was able to get it to also run at 120hz. Xrandr is only showing a max of [email protected] and seems to be the resolution KDE keeps attempting to start with and fail. I went into rsetup to see if there was any overlay stuff I could enable. I found the enable 8k for hdmi0 and another for hdmi1, I was told I could only use one at a time. There was also a driver for the Mail GPU. If the Mali GPU driver is enabled, KDE/Plasma seems to get confused and won’t allow the task bar to show or really complete loading. I tried to enable 8k on hdmi1 and plug the neo g9 in, the monitor just loops trying to turn on I tried to enable it for hdmi0 and swap the ports, same story. I tried to reboot with hdmi1 enabled and everything plugged in, same story. I tried to boot just the Neo G9, same story. I tried to switch to a text virtual console, same story. I just happen to also have a running Raspberry Pi 5 on the bench, and out of curiosity sake, tried to plug the Neo G9 into it, the monitor sprang to life to show me the virtual terminal. The Rpi 5 doesn’t have a GUI installed so I couldn’t test it further.
I will post the dmesg logs later today when I return home. I’m assuming that either there is an overlay I need, a kernel that needs updating, or a kernel flag I need to pass.
I am also going to try forcing hdmi to stay on using the solution mentioned here:
Does anyone else have any other suggestion that I might try tonight?