Desktop, UEFI, Z87 chipset, Intel Xeon E3-1230 v3, AMD R9 280X GPU -
Fails, does not show the specified error instead journalctl shows:
gnome-shell[1820]: Failed to create backend: No GPUs found with udev
Which is likely caused by (from dmesg):
[ 11.994228] [drm] VGACON disable radeon kernel modesetting.
[ 11.994258] [drm:radeon_init [radeon]] *ERROR* No UMS support in
radeon module!
On 4/8/19 8:02 PM, Adam Williamson wrote:
Hi folks!
A few weeks back we asked for testing of 'basic graphics mode' /
nomodeset booting - the feedback from that was very helpful in
establishing that we had a generic issue which dated back to Fedora 29,
thanks a lot. We have now established more or less what that initial
issue is, and work is ongoing to get it fixed entirely. However, it's
already been fixed *partially*, and that revealed a subsequent bug.
The initial bug is fixed for the case of UEFI native boots (it is not
fixed for BIOS native boots yet). However, in testing, I and others
found that several UEFI test systems still do not boot successfully to
GDM, because they run into a *different* bug later:
https://bugzilla.redhat.com/show_bug.cgi?id=1693409
This bug can be identified by the presence of the following string in
the journal:
"(EE) Cannot run in framebuffer mode. Please specify busIDs for
all framebuffer devices"
(yes, with a bunch of spaces - but just the first part of the line is
sufficient to identify the problem, I think).
It would be great if folks with UEFI-capable systems could try booting
a recent Fedora 30 Workstation live image on them, e.g. this one:
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-30-20190408.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-30-20190408.n.0.iso
ensure you boot in UEFI mode. Please report back whether it works. If
it doesn't work, please check the logs - you should be able to log into
a console on tty3 (ctrl-alt-f3 to get there) as root with no password,
then run 'journalctl -b' to see the logs - and report if that line is
present or not. If it isn't, it'd be useful to know if some other error
message is present.
Thanks a lot, folks!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
