Description of problem: After a plain F31 install w/KDE on a new E595 Lenovo laptop with integrated AMD GPU: lspci | grep VGA 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) lspci -n -s 05:00.0 05:00.0 0300: 1002:15d8 (rev c2) suspend and resume does not work, see this thread for more details: https://forums.lenovo.com/t5/Other-Linux-Discussions/LENOVO-E595-Black-screen-on-resume/m-p/4613891/highlight/false#M14202 After spending considerable time digging and looking for solutions/workarounds, I realized that X was using radeon user mode driver against amdgpu kernel mode, and the problem seems to be fixed by installing the amdgpu user mode package that this bug is filed against. I have no idea whether that's supposed to work at all, but anyway as long as it is unstable it would be good if Fedora could make sure people do not end up in the same "hole". Workaround/solution: For the E595 it is likely sufficient just to include xorg-x11-drv-amdgpu in the install, but at least include it if an AMD Picasso or similar newer device is found, in case there are other reasons not to have this module present in other systems. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Boot the system, log in as a normal KDE user 2. Close lid, use systemctl suspend or suspend from the menu (seems to work fine the first time) 3. Open lid or press power button again Actual results: Screen goes blank, fan spins up and system does not appear to work. Occasionally it is possible to get in via ssh, and there are kernel errors related to amdgpu. Expected results: A normal resume of the desktop session Additional info:
(In reply to Knut Omang from comment #0) > I realized that X was using radeon user mode driver against amdgpu kernel > mode, [...] That's not possible; the Xorg radeon driver cannot work with the amdgpu kernel driver. What might actually have happened was that Xorg tried to use the radeon driver, which failed, so Xorg fell back to using the modesetting driver. > I have no idea whether that's supposed to work at all, [...] It is. The suspend/resume problem is most certainly an amdgpu kernel driver issue, and using the Xorg amdgpu driver just works around it somehow. That said, I do support xorg-x11-drv-amdgpu getting installed by default, at least on systems with a GPU supported by the amdgpu kernel driver, or otherwise corresponding to the circumstances under which xorg-x11-drv-ati is installed by default. Reassigning to anaconda accordingly.
Yes, you are probably right, thanks for the clarification. During the back and forth with this problem I seem to have forgotten to store any relevant X log file so I am actually now not sure radeon was involved at all, but definitely a kernel driver issue. Note that on the Lenovo thread I refer to above it is now reported as been fixed w/kernel 5.4.x, I haven't tested it but it should not make any difference for this bug anyway.
jadahl pointed out this is actually the "comps" component, not anaconda.
comps is the right place to add it, but lets move to the xorg-x11-drv-amdgpu component and make sure maintainers are ok with that first.
Adding to comps is not sufficient though, because it only affects new installs, not upgrades. A Recommends or Requires is needed somewhere as well.
I apologize for the off topic, can anybody please remind me what is the difference between using amdgpu drivers from kernel or from xorg-x11-drv-amdgpu? Some days ago I installed a fresh Fedora 31 KDE (now upgraded to 32) on a system with RX480 and xorg-x11-drv-amdgpu is not installed by default, but lsmod returns amdgpu loaded
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.