Created attachment 117709 [details] Log of the failed boot System Information Fedora 22 MSI GX79 AMD A10-5750M CPU AMD Radeon HD 8650G & 8970M Short Summary of the past problems: Fedora 21 clean install with Kernel 3.17, the system wont boot. Only after a reboot into the recovery mode. With Kernel 3.18, System will boot, but the HD 8970M wont be recognized. All Kernels after 3.18.8, the System will finish the boot sequence, the mouse will show up and the look screen and then the systems freezes and reboots. Now the actual Bug: A few days ago I tried Kernel 4.2 RC4, Xorg 1.17, Mesa (fedora rawhide) out. Result: The System tries to load the Hainan Code for the HD 8970M, but given the PCI nummber, its a Pitcairn card. Today I updated to Kernel 4.2 RC6, Xorg 1.18 and Mesa 11 (fedora rawhide). Now the Pitcairn Code gets loaded, but the System will still crash and reboot. How to reproduce: 1. Install Fedora 21/22 or use an Live CD 2. Boot Additional Information $lspci | grep -i vga 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Neptune XT [Radeon HD 8970M] $lspci -n | grep 01:00.0 01:00.0 0300: 1002:6801 About the Xorg.log Well I had it, but it got overriden by the catalyst driver (yeah D:). The log had the same information in it as the boot log (ring test failed, resume failed). But if you really need the log file, I will get it. I hope I provided enough information. If not, just tell me what oter logs etc I need to post and I will get them. I really want to solve this problem
Created attachment 117712 [details] All informations from the abrt bug reporting tool
Does booting with radeon.runpm=0 on the kernel command line in grub help?
(In reply to Alex Deucher from comment #2) > Does booting with radeon.runpm=0 on the kernel command line in grub help? Yes that worked, thanks a lot. Final question, what is radeon.runpm=0 actually doing?
(In reply to Fox from comment #3) > Yes that worked, thanks a lot. > Final question, what is radeon.runpm=0 actually doing? It stops the driver from dynamically turning off the dGPU when it's not in use.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.