Update on troubleshooting the dual displayport - it looks to me like it may be that Xorg is automatically setting the Screen to 6400x2160, but the physical monitor is 5120x2880, and the opened terminal window in Fvwm is off to the left of the visible area.
Steps (abbreviated) I wanted to see if it was an Fvwm, Xorg, or OpenBSD issue, so I added a new window manager: I installed xfce from packages, and edited my user .xsession file to start xfce. xfce with default configuration was usable, showing the default terminal, so in its terminal I ran xrandr (output below) It appears that the Xorg automatic configuration is incorrectly setting the screen and display parameters. Since the DP connections are DP-1 and DP-2, I'll try shifting them to DP-0 and DP-1 in case there is any special consideration for using DP-0. The next troubleshooting option will be to manually set the resolution either with xrandr or /etc/X11/xorg.conf. The manual configuration will be to create one 5120x2880 Screen out of two Displays set at 2560x2880. $xrandr Screen 0: minimum 320 x 200, current 6400 x 2160, maximum 16384 x 16384 DisplayPort-0 disconnected primary (normal left inverted right x axis y axis) DisplayPort-1 connected 848x480+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 848x480 59.74*+ 2560x2880 59.98 29.99 640x480 59.74 DisplayPort-2 connected 3840x2160+2560+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 60.00*+ 60.00 2560x1440 59.95 + 2560x2880 59.98 29.99 1920x1200 59.88 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 1280x1024 60.02 1440x900 60.00 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 60.00 59.94 HDMI-A-0 disconnected (normal left inverted right x axis y axis) On Wed, Dec 15, 2021 at 12:14 AM Jonathan Gray <j...@jsg.id.au> wrote: > On Tue, Dec 14, 2021 at 10:38:44PM -0600, Phil Vuchetich wrote: > > 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. > > 7.0 drm is based on linux 5.10.65, -current 5.10.85 nothing > stands out but there are some displayport mst related bits. > > There is also a 5.15 port not yet committed you could try. > > > > > 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 > > allowaperture is for userland drivers and is not required with kernel > modesetting drivers like amdgpu. > > > 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. > > yes, dmesg and Xorg.0.log would be interesting > > > > > 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 > > >
