An OpenBSD developer on reddit has informed me that the cause of issue 1 
is already known & being worked on (No libLLVM in base).

I have found that issue 2 is also triggered when X screen blanking is 
activated, whether by the DPMS extension or the xset "screen saver" feature.

Dec 2, 2018, 9:08 AM by [email protected]:

> I have recently upgraded from an Intel iGPU to the Sapphire overclocked 
> variant of the Radeon R7 370. I have all the X tarballs installed & start X 
> with xenodm. While it mostly works well in OpenBSD (drm & radeon kernel 
> drivers attach & I get video), I am having 2 distinct major issues with the 
> card:
>
> 1. DRI{1,2,3}, & thus, OpenGL are not working, because glamor will not 
> attach. As seen in the attached Xorg.0.log, glamor gives the cryptic error 
> "EGL_MESA_drm_image required." While I could not figure out exactly
> what this error means, it is somewhat common enough among Linux users to have 
> a few threads pop up; When Linux users have this issue, it is usually fixed 
> by installing or upgrading a lib in the Xorg stack from their package manager 
> (most notably, libEGL,libGLES2, & LLVM), which we obviously cannot do. I have 
> tried every combination of xorg.conf settings to fix this & nothing works; 
> oddly enough, I get the same behavior even when I set the Xorg driver to 
> modesetting, despite modesetting working fine with DRI on my iGPU. I have 
> also tried simply using EXA, however my GPU isn't supported, so glamor is my 
> only option here.
>
> 2. After Xorg starts, any attempt to kill/restart it or use the "xrandr" 
> command to change my monitors (xorg.conf xrandr works fine) will permanently 
> freeze up all 3 of my screens, forcing me to use CTRL+ALT+DEL to halt the 
> machine. While I haven't been able to get a dmesg after this happens (due to 
> the screen freezing), the attached Xorg.0.log.old should be from the last 
> time this has happened. Oddly enough, I can switch to tty, & if I switch to 
> tty first then kill X it works most of the time' I am only having issues from 
> within the running X server itself.
>
> I am running the latest build of current as of 2:00 AM (America/New_York 
> timezone).
>
>

Reply via email to