Make and model of computer: http://www.dell.com/vn/business/p/vostro-15-3578-laptop/pd Summary: radeon driver + graphical mode causes Fedora to black screen without chance of recovery How to reproduce: 1. Boot the aforesaid device with Fedora without nomodeset 2. Wait until "Starting Switch Root..." appears and Fedora tries to load the graphical user interface 3. Observe that the screen turns to black and that the device stops making noises (possible kernel panic?) 4. Try to switch to a text console using Ctrl+Alt+F3 and observe that the system doesn't respond 5. Reboot the system with kernel parameters "nomodeset" and/or "modprobe.blacklist=radeon" (only one is necessary), observe that the system successfully boots into graphical mode without any problem. 6. However, when the following commands are executed: "systemctl isolate multi-user.target;modprobe radeon;systemctl isolate graphical.target" the kernel decisively panics. 7. Conclude that the problem is related to the AMD/ATI graphics card. What should happen: It should be possible to use the device normally with Fedora and the discrete graphics card. Opening the "About" dialog box should list the name of the discrete graphics card. What actually happens: It is impossible to use the device on Fedora with the graphics card enabled. As a workaround, I can disable the GPU but it isn't an ideal solution and there is still a bug in the Linux kernel and/or radeon driver. What I'm doing: Collecting debug data for the device. Stay tuned!
Created attachment 1475115 [details] The result of "journalctl -o export"
Hi, I am trying to install Fedora Workstation 29 on my new Dell Vostro 3578. I am observing the same symptom as above. Centos 7, Ubuntu 16 / 18 LTS, Elementary OS 5 are working fine without issues. Is there anything I can do? Thanks!
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days