On 10/04/13 05:50 PM, Brian Fagioli wrote:
When I installed it on the same machine without UEFI, it booted fine. Running it now.
10.04.13, 20:47, "John Reiser" <jreiser@xxxxxxxxxxxx>":
Fails at Grub. Missing file. En.mo.gz
That message probably is just informative, and not the cause of
failing to boot. The same message occurs in many successful
boots of current release Fedora 18.
Right now the suspected culprit of failing to boot Fedora 19
is somewhere in passing control of the active video graphics
from one stage to the next.
It seems that every tester who doesn't hit the 'ENOSPC' issue and gets a
successful install hits this issue where grub fails to display instead.
So far the only bootable UEFI install I've heard of is one tflink did
where he set grub up to use a serial console.
The bug report for this problem is
https://bugzilla.redhat.com/show_bug.cgi?id=949761 , we're poking at it
there. One thing the devs would like people to try is:
<pjones>: adamw: get them to try putting "GRUB_TERMINAL_OUTPUT=console"
in /etc/default/grub and re-running grub2-mkconfig
you could do that from ctrl-alt-f2 after install is complete but before
rebooting, or you could do it from rescue mode or a live image on the
installed system. The theory is that by disabling grub's graphical mode
we'll work around whatever the problem is, and hence prove that the
problem is with the graphical mode.
If anyone actually got an entirely successful UEFI install with Alpha
RC1 or RC2 - it installed without errors, and the installed system
boots, showing you a graphical grub screen - that would be useful info
to add to the bug; right now I'm working on the assumption that this is
a complete showstopper for all UEFI installs.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
