Date: Sat, 02 Mar 2024 16:21:12 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 275899] graphics/mesa-dri: DRI stopped working with the Intel graphics card Message-ID: <bug-275899-7141-v3BhucIApX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275899-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-275899-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=3D275899 Chris Wells <freebsd@chriswells.io> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd@chriswells.io --- Comment #17 from Chris Wells <freebsd@chriswells.io> --- I believe I'm having this problem as well, but I have an AMD Radeon RX 550. After recent updates (a few weeks ago) on the quarterly branch, I was no longer able to launch Firefox from an XRDP session and saw the failure to l= oad zink when launching it from a terminal. However, it launched fine locally. I also have a "guest" profile in Firefox that I use for testing that did load= in the XRDP session, so I looked for preferences I'd changed in my main profile and found gfx.webrender.all: https://wiki.mozilla.org/Platform/GFX/Quantum_Render With that enabled, my main Firefox profile fails to load in an XRDP session. With it disabled, it loads fine. I can toggle the setting to provide output/logs, if needed. Maybe it would be helpful to see data from 1) worki= ng locally, 2) broken in XRDP, and 3) fixed in XRDP? I just need to know what information might be useful. To start, this is my video card: vgapci0@pci0:16:0:0: class=3D0x030000 rev=3D0xff hdr=3D0x00 vendor=3D0x1= 002 device=3D0x67ff subvendor=3D0x1682 subdevice=3D0x9550 vendor =3D 'Advanced Micro Devices, Inc. [AMD/ATI]' device =3D 'Baffin [Radeon RX 550 640SP / RX 560/560X]' class =3D display subclass =3D VGA cap 09[48] =3D vendor (length 8) cap 01[50] =3D powerspec 3 supports D0 D1 D2 D3 current D0 cap 10[58] =3D PCI-Express 2 legacy endpoint max data 256(256) RO NS max read 512 link x8(x8) speed 2.5(8.0) ASPM disabled(L1) cap 05[a0] =3D MSI supports 1 message, 64 bit enabled with 1 message ecap 000b[100] =3D Vendor [1] ID 0001 Rev 1 Length 16 ecap 0001[150] =3D AER 2 0 fatal 0 non-fatal 1 corrected ecap 0015[200] =3D Resizable BAR 1 ecap 0019[270] =3D PCIe Sec 1 lane errors 0 ecap 000f[2b0] =3D ATS 1 ecap 0013[2c0] =3D Page Page Request 1 ecap 001b[2d0] =3D Process Address Space ID 1 ecap 0018[320] =3D LTR 1 ecap 000e[328] =3D ARI 1 ecap 001e[370] =3D L1 PM Substates 1 DRM: pkg info | grep drm drm-510-kmod-5.10.163_8 DRM drivers modules drm-kmod-20220907_1 Metaport of DRM modules for the linuxkpi-bas= ed KMS components gpu-firmware-kmod-20230210_1,1 Firmware modules for the drm-kmod drivers Mesa: pkg info | grep mesa mesa-demos-8.4.0_3 OpenGL demos distributed with Mesa mesa-dri-23.3.4 OpenGL hardware acceleration drivers for DRI= 2+ mesa-libs-23.3.4 OpenGL libraries that support GLX and EGL clients If you believe my issue is unrelated to this one, just tell me to buzz off. --=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-275899-7141-v3BhucIApX>