Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Jun 2020 02:18:32 +0000
From:      bugzilla-noreply@freebsd.org
To:        x11@FreeBSD.org
Subject:   [Bug 247416] x11-servers/xorg-server: DRI2 fails on AMD Polaris 10
Message-ID:  <bug-247416-7141-JvSTVUuwbr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-247416-7141@https.bugs.freebsd.org/bugzilla/>
References:  <bug-247416-7141@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247416

--- Comment #17 from Adam Jimerson <vendion@gmail.com> ---
This is getting stranger by the minute, I updated everything but the mesa-d=
ri
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 somethi=
ng
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 o=
r directory.
> libGL: Can't open configuration file /home/vendion/.drirc: No such file o=
r directory.
> libGL: Can't open configuration file /usr/local/etc/drirc: No such file o=
r directory.
> libGL: Can't open configuration file /home/vendion/.drirc: No such file o=
r directory.
> 511 frames in 5.0 seconds =3D 102.029 FPS
> 439 frames in 5.0 seconds =3D 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 h=
as
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

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-247416-7141-JvSTVUuwbr>