On Sat, May 4, 2019 at 2:27 AM ToddAndMargo via users
<users(a)lists.fedoraproject.org> wrote:
On 5/3/19 2:30 PM, Tom H wrote:
> On Fri, May 3, 2019 at 9:52 PM Samuel Sieb <samuel(a)sieb.net> wrote:
>> On 5/3/19 12:25 PM, Tom H wrote:
>>>
>>> You then have to use "grub2-install" with
"--target=i386-pc" for
>>> csm and "--target=x86_64-efi" for efi.
>>
>> He mentioned that originally, but that's not where the problem is.
>> He's trying to create a grub.cfg file for legacy, but I don't see
>> any flags for grub2-mkconfig that can indicate which type to create.
>
> grub.cfg doesn't vary that way. On Fedora, it's location varies.
>
> But on F30, if you set "GRUB_ENABLE_BLSCFG=true" in
> "/etc/default/grub" and run "grub2-mkconfig -o
/boot/grub2/grub.cfg",
> the latter'll be generic and blscfg'll build a menu from
> "/boot/loader/entries/*.conf" at boot, whether booting from csm or
> efi. This is theoretical because I'm not running Fedora on EFI to
> check.
# cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=UUID=5da7eab6-6440-4e44-9ad9-3fd1a17dbb1d
rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
It is already set. No joy!
#grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done
Back to EFI again!
1) Shouldn't you be able to access the firmware even if you're booting from csm?
2) Check "/boot/grub2/grub.cfg" and "/boot/locader/entries/*". Does
"grub.cfg" have menu entries or is it generic and does it run
"blscfg"
and create a menu from "/boot/locader/entries/*"?