On 5/3/19 9:41 AM, Samuel Sieb wrote:
On 5/3/19 1:30 AM, Todd Chester via users wrote:
> On 5/2/19 10:24 PM, Samuel Sieb wrote:
>> On 5/2/19 8:23 PM, Todd Chester via users wrote:
>>> On 5/2/19 5:40 PM, Samuel Sieb wrote:
>>>> On 5/1/19 2:48 PM, ToddAndMargo via users wrote:
>>>>> Remaking grub.cfg, I get
>>>>>
>>>>> # grub2-mkconfig -o /boot/grub2/grub.cfg
>>>>> Generating grub configuration file ...
>>>>> Adding boot menu entry for EFI firmware configuration
>>>>> done
>>>>>
>>>>> Uhhhhh.. I wanted legacy, not EFI.
>>>>>
>>>>> What am I missing?
>>>>
>>>> Are you doing this while booted in EFI or legacy mode?
>>>
>>> Legacy. It only boots in EFI mode. I need both.
>>
>> How are you booting in legacy mode if it doesn't work?
>
> I am not. That is what I am trying to get working.
That's why I asked the previous question which you answered wrong. You
are trying to create a legacy grub config while booted in EFI mode. That
is not likely going to work. You could try booting a netinst image in
legacy mode using the rescue option and try to fix it from there. Or
even a regular live image booted in legacy mode. You could boot the
ISOs using a VM as well.
A friend over on the Linux newsgroup told me that the new the
grub2-mkconfig grubs around your system and determines if you
are booting Legacy or EFI.
And "grub2-mkconfig" is a bash script. So "vi" is my
solution. I will create my own grub2-mkconfig that will do
both. I have to do this anyway as new kernels are installed.