# Description of problem: As per the following discussions on the Mageia forums, the "amdgpu" and "modesetting" drivers don't work on AMD Navi-series graphics cards: * https://forums.mageia.org/en/viewtopic.php?f=23&t=13511 * https://forums.mageia.org/en/viewtopic.php?f=23&t=13335 This problem affects Mageia 7.1 (after installing the relevant kernel/firmware updates), but does **not** affect Linux Lite 5.0 (based on Ubuntu 20.04). Out of the box, Linux Mint 19.3 (based on Ubuntu 18.04.3) falls back to the fbdev driver, but after installing updates, it starts working with amdgpu. It seems to me that this is due to Mageia 7.1 running an outdated version of LLVM (8). By comparison, Linux Mint 19.3 works after installing updates, because its parent distro (Ubuntu 18.04) backported LLVM 9. To review the troubleshooting process that led to this conclusion, see the following forum thread: https://forums.mageia.org/en/viewtopic.php?f=23&t=13511 # Version-Release number of selected component (if applicable): # How reproducible: Always # Steps to Reproduce (on Wayland): 1. Ensure that you have a computer with an AMD Navi-series graphics card (e.g. an AMD Radeon RX 5700 XT) 2. Using the Mageia 7.1 64-bit Classic Installer, install a fresh copy of Mageia 7.1, with GNOME as the only desktop environment (to ensure that the Wayland-based GNOME Display Manager gets selected as the display manager) 3. Allow the Classic Installer to apply updates to the new installation (otherwise, you'll be stuck with an old kernel, and an old "radeon-firmware" package, which don't support AMD Navi) 4. Reboot, and verify that the display/keyboard lock up for a while, before the GUI crashes 5. Switch to a TTY (you'll have to wait for the GUI to crash first, in order to unlock the keyboard) 6. Log in as "root" 7. Inspect the output of the command "journalctl -b -0" 8. Verify that GNOME printed the following message: "radeonsi: Navi family support requires LLVM 9 or higher" # Steps to Reproduce (on X11): 1. Ensure that you have a computer with an AMD Navi-series graphics card (e.g. an AMD Radeon RX 5700 XT) 2. Using the Mageia 7.1 64-bit Classic Installer, install a fresh copy of Mageia 7.1, with any desktop environment other than GNOME (I've only tested this with KDE), to ensure that an X11-based display manager gets selected 3. Allow the Classic Installer to apply updates to the new installation (otherwise, you'll be stuck with an old kernel, and an old "radeon-firmware" package, which don't support AMD Navi) 4. Reboot, and verify that the display and keyboard lock up 5. Turn off the computer. You should be able to just press the power button (i.e. a forced shutdown shouldn't be necessary), though if SDDM is your display manager, it will take 1:30 minutes to shut down. 6. You can try inspecting the output of journalctl, as per steps 6-8 for Wayland - however, you might not get any useful error messages (with SDDM, all I got was a timeout error)
Sorry, I got the "Steps to reproduce (on X11)" above incorrect (the steps for Wayland are correct, though). Here is a corrected version of the X11 steps: # Steps to Reproduce (on X11): 1. Ensure that you have a computer with an AMD Navi-series graphics card (e.g. an AMD Radeon RX 5700 XT) 2. Using the Mageia 7.1 64-bit Classic Installer, install a fresh copy of Mageia 7.1, with any desktop environment other than GNOME (I've only tested this with KDE), to ensure that an X11-based display manager gets selected 3. Leave the graphics driver set to "Framebuffer" or "vesa" (at this stage, the system has an old kernel and an old "radeon-firmware" package, which don't support AMD Navi) 4. Allow the Classic Installer to apply updates to the new installation (to update the kernel and the "radeon-firmware" package, to support AMD Navi) 5. Reboot, and launch the Mageia Control Center 6. Use the "Set up the display server" module, to set the graphics card correctly (i.e. "ATI Volcanic Islands or later") 7. Check the file /etc/X11/xorg.conf, to verify that "amdgpu" has been correctly selected as the graphics driver 8. Reboot, and verify that the display and keyboard lock up 9. Turn off the computer. You should be able to just press the power button (i.e. a forced shutdown shouldn't be necessary), though if SDDM is your display manager, it should take 1:30 minutes to shut down. 10. You can try inspecting the output of journalctl, as per steps 6-8 for Wayland - however, you might not get any useful error messages (with SDDM, all I got was a timeout error)
Thank you for reporting this, and the detailed 'how to reproduce' instructions. If this gets corrected by an update, we may well ask you to test that since the hardware requirement is specific. Assigning to the Kernel/Drivers team.
Assignee: bugsquad => kernel
> If this gets corrected by an update, we may well ask you to test that since the hardware requirement is specific. That's fine with me. I'd prefer to test the update via a "Backports" or "Testing" repository for Mageia 7 (rather than Cauldron). Nonetheless, if necessary, I'm willing to install Cauldron - just let me know if you want me to do that.
I was bored, so I installed a second copy of Mageia 7.1 KDE (using fbdev as the X11 driver), and upgraded it to Cauldron. Note that Cauldron is currently using LLVM 10.0.0 (Navi-series AMD GPUs apparently require LLVM 9 or newer, whereas Mageia 7.1 currently uses LLVM 8.0.0). After upgrading to Cauldron, I used the Mageia Control Center's "Set up the display server" module, set my graphics card to "ATI Volcanic Islands or later", and rebooted, as per the above procedure. It works. KDE's visual effects (transparency et. al.) are working now (they were automatically disabled under fbdev), and working fluidly. inxi and hardinfo both report that I'm using amdgpu as my X11 driver. And I can run 0 A.D. (an OpenGL game) at its maximum graphics settings, with a good framerate (55+ during the early game). Is it possible to backport Cauldron's LLVM 10.0.0, to Mageia 7.1? (Obviously, I don't want to use Cauldron as my daily driver) If it turns out there are programs in Mageia 7.1 that depend on LLVM, and which break with the newer LLVM version, then it might be worth considering Ubuntu 18.04's approach: Ubuntu 18.04 has a package called "llvm" (the original package that shipped with the distro, back when it was released in 2018 April, containing LLVM 6), and another package called "llvm-9" (backported to Ubuntu 18.04, for hardware enablement purposes). Perhaps Mageia could try a similar approach?
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Sorry for the very late response - I've had various health issues. I can confirm that this bug does **not** affect Mageia 8. Mageia 8 ships with LLVM 11.0.1, and works well for me on 2 different devices with AMD Navi graphics cards. I don't have that much experience with Mageia's bug reporting processes. Should I close this bug as "FIXED", or "OLD" (given that it was never fixed in Mageia 7 / 7.1)?
old is the most fitting one
Resolution: (none) => OLDStatus: NEW => RESOLVED