[Bug 247416] x11-servers/xorg-server: DRI2 fails on AMD Polaris 10
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jun 20 02:18:41 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247416
--- Comment #17 from Adam Jimerson <vendion at gmail.com> ---
This is getting stranger by the minute, I updated everything but the mesa-dri
package and rebooted to test if everything would come back up as expected (same
"No screens found" error).
Strangely without the xf86-video-vesa package installed X11 failed to start,
but installing, X11 works and picom which seems happy but yet doing something
like glxgears with LIBGL_DEBUG flag I still get the following.
> libGL: screen 0 does not appear to be DRI2 capable
> libGL: Can't open configuration file /usr/local/etc/drirc: No such file or directory.
> libGL: Can't open configuration file /home/vendion/.drirc: No such file or directory.
> libGL: Can't open configuration file /usr/local/etc/drirc: No such file or directory.
> libGL: Can't open configuration file /home/vendion/.drirc: No such file or directory.
> 511 frames in 5.0 seconds = 102.029 FPS
> 439 frames in 5.0 seconds = 87.668 FPS
I also still see the following in my Xorg.0.log file
> [ 139.052] (EE) open /dev/dri/card0: Operation not supported by device
> [ 139.052] (WW) Falling back to old probe method for modesetting
> [ 139.052] (EE) open /dev/dri/card0: Operation not supported by device
> [ 139.052] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
> [ 139.052] (EE) Screen 0 deleted because of no matching config section.
So I guess the amdgpu driver may have been failing all this time and vesa has
just been playing a trick on me.
I also don't know if this is related to anything but it seems that X11 is
looking for a module that does not exist for some reason:
> [ 139.051] (II) LoadModule: "ati"
> [ 139.051] (WW) Warning, couldn't open module ati
> [ 139.051] (EE) Failed to load module "ati" (module does not exist, 0)
rather than looking for amdgpu
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-x11
mailing list