Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: The latest system update has mesa-dri-drivers-21.1.1-1.fc34.x86_64. But desktop cannot launch after update, with black screen. Check logs in $HOME/.local/share/xorg/Xorg.0.log and found that X11 failed to launch with below error: (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_video_caps_info (EE) AIGLX error: unable to load driver swrast (EE) GLX: could not load software renderer (II) GLX: No usable GL providers found for screen 0 Now everything works fine after downgrade to mesa-dri-drivers-21.0.2-1.fc34.x86_64. Version-Release number of selected component (if applicable): mesa-dri-drivers-21.1.1-1.fc34.x86_64 How reproducible: Use AMD GPU then do system update to latest. Steps to Reproduce: 1. Do system update then reboot. Actual results: Booted but black screen after login. Expected results: Show up the desktop after login. Additional info: My GPU is AMD Radeon VII. And I can login to desktop if I install amdgpu-pro from AMD official website, but I can't use it since AMD didn't support EGL on this driver already.
Created attachment 1786508 [details] Xorg log when error
Can confirm I'm seeing this same bug, same error in my Xorg log. Fedora Workstation 34 with a Vega 56 card running the amdgpu kernel drivers.
*** Bug 1964480 has been marked as a duplicate of this bug. ***
What does ldd /usr/lib64/dri/swrast_dri.so | grep amdgpu say? Which version of the libdrm package is installed?
(In reply to Michel Dänzer from comment #4) > What does > > ldd /usr/lib64/dri/swrast_dri.so | grep amdgpu > > say? > > Which version of the libdrm package is installed? Hi. This notice me the lib dependency of swrast_dri.so Found that it caused by AMD official OpenCL driver, which will install its own libdrm-amdgpu package. And another package will make swrast_dri.so to link its own libdrm-amdgpu package. Issue solved after remove AMD OpenCl driver then update mesa-dri-drivers again. In conclusion, this is caused by AMD OpenCL driver. I'll close this issue and report to AMD. Sorry about inconvenience.