On 08/28/2015 03:02 AM, Paul Cartwright wrote:
well it changed now, booting from fedora, the original screen ( before
grub?) when it booted ubuntu default, had a line on the screen before
anything else happened.. something about booting insecure.. then the
grub menu came up. Now that the default is fedora, that line was missing
and it was REALLY fast getting the grub menu, I really didn't have much
time to try F12..
At this point I'd have to start guessing. There seem to be a handful of
unrelated things changing on your system, and I tend to think you're
making more changes than you document. In this case, enabling "quiet
boot" in most UEFI or BIOS configurations would do what you're
describing, making the boot process shorter.
Doesn't matter, really. Don't use grub2-install on UEFI systems. :)
right, and that is what I am trying to figure out, how I update
grub/UEFI so it knows when I have new kernels..
When new kernels are installed, grubby adds a new stanza to grub.cfg.
You don't need to reinstall grub, you only need the cfg updated. This
is actually the same as it was under BIOS, it hasn't changed. The part
that has changed is the initial installation of grub. In that case, the
grub2-efi and shim rpms place the files on the FAT32 system partition
which are required to boot, and efibootmgr is used to create an UEFI
boot entry. grub2-install is never used (AFAIK).
oh... I think I get it, but now my entries look like ( 10 entries in
boot order):
BootOrder: 0005,0009,000C,0004,0003,0010,0000,0001,0002,0008
Boot0000* P0: WDC WD10EZEX-75M2NA0 BBS(17,,0x0)
Boot0001* P4: TSSTcorp DVD+/-RW SH-216DB BBS(19,,0x0)
Boot0002* Fedora
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\fedora\shim.efi)
Boot0003* Windows Boot Manager
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...9................
Boot0004* ubuntu
HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
Boot0005* Fedora
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\FEDORA\shim.efi)
Boot0009* UEFI OS
HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\BOOT\BOOTX64.EFI)
so 0005 and 0009 are both fedora, different kernels... one is
shimx64.efi and the other is shim.efi
Have another look. Boot002 and Boot005 are Fedora, and they are
identical. They identify \EFI\FEDORA\shim.efi on partition 8. Notably,
they don't refer to a kernel at all.
UEFI loads and runs shim.efi, which is identified in the UEFI boot
list. shim.efi loads and runs grubx64.efi. grubx64.efi loads its
configuration file, then loads and runs a Linux kernel (or Windows).
The kernel runs /sbin/init on its root filesystem.
, whatever they are.. except there
is no shimx64.efi ...
-rwx------ 1 root root 1293304 Feb 17 2015 shim.efi
-rwx------ 1 root root 1287032 Feb 17 2015 shim-fedora.efi
The full path relative to the system partition is
"\EFI\ubuntu\shimx64.efi". It's in a different directory than the
Fedora-installed shim.efi.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
