Bug 1024885

Summary: radeon and amdgpu drivers collide causing screen flashing and inability to log in
Product: [openSUSE] openSUSE Tumbleweed Reporter: fire bird <firebird209>
Component: X.OrgAssignee: E-mail List <xorg-maintainer-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Major    
Priority: P5 - None CC: malcolmlewis, zaitor
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: journalctl output

Description fire bird 2017-02-10 23:19:48 UTC
Greetings,

I ran into an issue today with openSUSE Tumbleweed not correctly booting. I would receive a text version of boot which would inevitable freeze. When trying to switch to a different tty to login and diagnose / fix the issue I was presented with the login prompt (as expected); however, keyboard input was randomly accepted and the text boot (from the other tty) was flashing over top of the login prompt. 

After sorting things out and getting a working system again the issue appears to be radeon and amdgpu fighting over the same real estate causing Xorg to fall into an endless loop of failing to start which then doesn't allow, in my case, gdm to start.

I was able to use boot options of amdgpu.blacklist=yes plymouth.enable=0 verbose 3 to get myself to a console login to fix things. In the end it required blacklisting amdgpu in order to use radeon for the video driver, which did not fix the issue alone, I also needed to zypper rm x86-video-amdgpu because while blacklisted, apparently Xorg still tries using amdgpu.

I hope this report serves to get the right people squashing this bug soon and in the meantime serve as help for those finding themselves facing the same issue and looking for a way back to a working system.

Thank you so much.
Comment 1 fire bird 2017-02-11 00:19:05 UTC
Created attachment 713766 [details]
journalctl output

Attached hereto is the output of journalctl during a failed boot. Hopefully it helps shed some light on what is going on.
Comment 2 Stefan Dirsch 2017-02-11 10:43:19 UTC
dup

*** This bug has been marked as a duplicate of bug 1023385 ***