Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1629860 - Fedora 29 Live ISO does not work in safe mode due to "Failed to create backend: Could not find a primary drm kms device"
Summary: Fedora 29 Live ISO does not work in safe mode due to "Failed to create backen...
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-09-17 14:15 UTC by Lukas Ruzicka
Modified: 2019-11-27 22:51 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 22:51:14 UTC
Type: Bug

Attachments (Terms of Use)
Journalctl from the failed attempt to run the Live ISO. (deleted)
2018-09-17 14:15 UTC, Lukas Ruzicka
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1628495 0 unspecified CLOSED In UEFI mode, Fedora 29 cannot be installed in Safe Graphics Mode 2021-02-22 00:41:40 UTC

Internal Links: 1628495

Description Lukas Ruzicka 2018-09-17 14:15:55 UTC
Created attachment 1484046 [details]
Journalctl from the failed attempt to run the Live ISO.

Description of problem:

Fedora 29 Live ISO does not work in safe mode due to "Failed to create backend: Could not find a primary drm kms device" error.

Version-Release number of selected component (if applicable):

Fedora 29 Beta RC 1.3 ISO

How reproducible:


Steps to Reproduce:
1. Start the Live ISO in safe graphical mode.

Actual results:

The Live ISO hangs on a black screen and no graphics can be seen. 

Expected results:

The ISO should boot with no problems.

Additional info:

See the journalctl logs.

Comment 1 Lukas Ruzicka 2018-09-17 14:16:58 UTC
This bug can be another manifestation of bug 1628495. It happens on the same computer.

Comment 2 Lukas Ruzicka 2018-09-17 14:19:19 UTC
Addition: This problem appears both in BIOS and UEFI modes.

Comment 3 Ben Cotton 2019-10-31 19:08:31 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 4 Ben Cotton 2019-11-27 22:51:14 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.