On 5/3/19 2:30 PM, Tom H wrote:
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb <samuel@xxxxxxxx> 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!
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
