I am trying OpenBSD 7.0 again (now that I have an AMD video card). I'll
follow up with sendbug(1) and would be happy to work with someone to
troubleshoot if this is of interest to anyone. I didn't see an amdgpu(4)
update in -current at https://www.openbsd.org/plus.html but I can switch to
-current if needed.

MB: ASUS Prime X570-P
Video Card: GIGABYTE Radeon RX 5700 XT GAMING OC 8G

The issue is with a fresh install of 7.0 as the only OS, then running
syspatch(8) to get/apply amdgpu(4). No additional packages have been
installed yet. The 5K (5120x2880) Dell UP2715Kt display, connected via dual
displayport connectors brought up the GUI login screen, and after login,
the default gray background screen with the virtual desktop switcher
visible in the lower right corner. The expected XTerm window does not
appear. Left clicking on the screen brings up the Fvwm root menu, but
selecting one of the applications (e.g. XTerm, Top, etc.) causes the GUI to
be "stuck" (no mouse pointer, no interaction seems to work, and no new
windows open, and the Fvwm doesn't open again). The OS appears to be
running fine - I can SSH in from another system, and ultimately reboot via
the SSH connection.

Prior to running syspatch to get amdgpu(4), the Dell monitor worked when
connected via dual displayport at a lower resolution (I didn't check what
the  resolution was at the time, but it was possibly 1920x1080), so the
issue isn't simply having two DP cables connected.

After syspatch, the Dell monitor connected via single display port has a 4K
resolution (as expected, since 5K is only expected to be supported over a
dual DP connection), and works at 4K (Xterm displays on login, additional
windows open from Fvwm menu). Swapping with a different monitor also works
via single displayport (Asus PA279Q, 2560x1440), so this issue is specific
to the use of dual displayport to connect a single monitor trying to run 5K
resolution. It is likely limited to something in amdgpu(4), X.org(1), or
the window manager. Xorg.0.log suggested that the sysctl(1)
'machdep.allowaperture=1' was needed, but that did not resolve the 5K
issue, and was not actually needed for 4K to work, either (I tried =1, =2,
and the default =0). Further troubleshooting may require comparative review
of /var/log/Xorg.0.log and dmesg(8) with single vs. dual displayport
connections, and figuring out what is actually "stuck" in the window
manager, as I was not checking the status of processes at this point.

Overall, since >4K monitors via dual displayport aren't mainstream, and
probably won't be anytime soon, this is at most a minor issue. My future
troubleshooting plan at this point is to try up to several of the window
managers conveniently available as OpenBSD packages since the issue may be
window manager-specific. If those don't resolve the issue, then I would
just use a single DP connection and continue learning more about OpenBSD on
the desktop in 4K or lower resolution.

Thanks,
Phillip Vuchetich
email: p...@vuchetich.com
mastodon: @philvuchetich@bsd.network

Reply via email to