On 9/4/19 7:55 PM, ToddAndMargo via users wrote:
On 5/1/19 2:48 PM, ToddAndMargo via users wrote:
Hi All,
I have a Fedora 30 flash drive set up for dual booting
from Legacy or UEFI. It boots beautifully from UEFI.
(It also have a bios_grub partition).
It booted perfectly from both under
On 5/1/19 2:48 PM, ToddAndMargo via users wrote:
Hi All,
I have a Fedora 30 flash drive set up for dual booting
from Legacy or UEFI. It boots beautifully from UEFI.
(It also have a bios_grub partition).
It booted perfectly from both under Fedora 29.
Now when booting from legacy, it go into
On Sun, 2019-05-12 at 20:13 -0700, ToddAndMargo via users wrote:
> > > I am confused. :'(
>
> Thank you! I will have to read it over several times
I hesitate to invite more flames, but would people please try to trim
the quoted material when replying? There's really no need to copy an
entire
On 5/12/19 1:51 AM, ja wrote:
On Sat, 2019-05-11 at 17:53 -0700, ToddAndMargo via users wrote:
On 5/11/19 7:25 AM, ja wrote:
On Sun, 2019-05-05 at 00:12 -0700, ToddAndMargo via users wrote:
On 5/4/19 11:42 AM, Chris Murphy wrote:
The grub2-mkconfig script detects EFI and creates a "System
On Sat, 2019-05-11 at 17:53 -0700, ToddAndMargo via users wrote:
> On 5/11/19 7:25 AM, ja wrote:
> > On Sun, 2019-05-05 at 00:12 -0700, ToddAndMargo via users wrote:
> > > On 5/4/19 11:42 AM, Chris Murphy wrote:
> > > > The grub2-mkconfig script detects EFI and creates a "System setup"
> > > >
On 5/11/19 7:25 AM, ja wrote:
On Sun, 2019-05-05 at 00:12 -0700, ToddAndMargo via users wrote:
On 5/4/19 11:42 AM, Chris Murphy wrote:
The grub2-mkconfig script detects EFI and creates a "System setup"
menu entry so the user can get into firmware setup (functionally the
same thing as an F key
On Sun, 2019-05-05 at 00:12 -0700, ToddAndMargo via users wrote:
> On 5/4/19 11:42 AM, Chris Murphy wrote:
> > The grub2-mkconfig script detects EFI and creates a "System setup"
> > menu entry so the user can get into firmware setup (functionally the
> > same thing as an F key at boot time to get
On 5/5/19 6:24 AM, Tom H wrote:
On Sun, May 5, 2019 at 7:57 AM ToddAndMargo via users
wrote:
On 5/4/19 5:23 AM, Tom H wrote:
1) Shouldn't you be able to access the firmware even if you're
booting from csm?
I have two qemu-kvm machines. one for testing usb stick with legacy
bios and one for
On Sun, May 5, 2019 at 7:57 AM ToddAndMargo via users
wrote:
> On 5/4/19 5:23 AM, Tom H wrote:
>>
>> 1) Shouldn't you be able to access the firmware even if you're
>> booting from csm?
>
> I have two qemu-kvm machines. one for testing usb stick with legacy
> bios and one for testing with efi
On Sat, May 4, 2019 at 1:13 PM ToddAndMargo via users
wrote:
> On 5/4/19 3:47 AM, Tom H wrote:
>> On Sat, May 4, 2019 at 1:05 AM Samuel Sieb wrote:
>>> On 5/3/19 2:30 PM, Tom H wrote:
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb wrote:
> On 5/3/19 12:25 PM, Tom H wrote:
>>
>> You
On 5/4/19 11:42 AM, Chris Murphy wrote:
The grub2-mkconfig script detects EFI and creates a "System setup"
menu entry so the user can get into firmware setup (functionally the
same thing as an F key at boot time to get into what some people call
'BIOS setup' but that's confusing to say on a UEFI
On 5/4/19 5:23 AM, Tom H wrote:
1) Shouldn't you be able to access the firmware even if you're booting from csm?
I have two qemu-kvm machines. one for testing usb stick with legacy
bios and one for testing with efi bios. Neither has a is no csm
mode. This is on purpose.
2) Check
On Sat, May 4, 2019 at 3:48 PM Samuel Sieb wrote:
>
> On 5/4/19 11:20 AM, Chris Murphy wrote:
> > I'm not sure when this went away, but on a current Fedora 29 Server on
> > a UEFI Intel NUC, the menu entries are linux and initrd. The linuxefi
> > initrdefi and linux16 initrd16 distinctions aren't
On 5/4/19 11:20 AM, Chris Murphy wrote:
I'm not sure when this went away, but on a current Fedora 29 Server on
a UEFI Intel NUC, the menu entries are linux and initrd. The linuxefi
initrdefi and linux16 initrd16 distinctions aren't present anymore.
And it's the same on both Fedora 30
On 5/4/19 2:49 AM, ToddAndMargo via users wrote:
On 5/3/19 11:17 PM, Samuel Sieb wrote:
On 5/3/19 6:28 PM, ToddAndMargo via users wrote:
What do you mean by?
change linuxefi > linux16,initrdefi > initrd16*
"linuxefi" does not exist in grub.cfg. Neither does
linux16 or initrdefi
The EFI
On Wed, May 1, 2019 at 3:49 PM ToddAndMargo via users
wrote:
>
> Hi All,
>
> I have a Fedora 30 flash drive set up for dual booting
> from Legacy or UEFI. It boots beautifully from UEFI.
> (It also have a bios_grub partition).
>
> It booted perfectly from both under Fedora 29.
>
> Now when
On Fri, May 3, 2019 at 5:05 PM Samuel Sieb wrote:
>
> On 5/3/19 2:30 PM, Tom H wrote:
> > On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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
On Sat, May 4, 2019 at 8:20 AM Samuel Sieb wrote:
>
> On 5/3/19 2:30 PM, Tom H wrote:
>>
>> 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
On Sat, May 4, 2019 at 2:27 AM ToddAndMargo via users
wrote:
> On 5/3/19 2:30 PM, Tom H wrote:
>> On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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"
On 5/4/19 3:47 AM, Tom H wrote:
On Sat, May 4, 2019 at 1:05 AM Samuel Sieb wrote:
On 5/3/19 2:30 PM, Tom H wrote:
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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
On Sat, May 4, 2019 at 1:05 AM Samuel Sieb wrote:
> On 5/3/19 2:30 PM, Tom H wrote:
>> On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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.
>>>
On 5/3/19 11:17 PM, Samuel Sieb wrote:
On 5/3/19 6:28 PM, ToddAndMargo via users wrote:
What do you mean by?
change linuxefi > linux16,initrdefi > initrd16*
"linuxefi" does not exist in grub.cfg. Neither does
linux16 or initrdefi
The EFI grub.cfg should have linuxefi and initrdefi lines.
On 5/3/19 2:30 PM, Tom H wrote:
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
On 5/3/19 6:28 PM, ToddAndMargo via users wrote:
What do you mean by?
change linuxefi > linux16,initrdefi > initrd16*
"linuxefi" does not exist in grub.cfg. Neither does
linux16 or initrdefi
The EFI grub.cfg should have linuxefi and initrdefi lines. Or in the
BLS files if that's enabled.
On 5/3/19 10:50 AM, ja wrote:
On Fri, 2019-05-03 at 09:41 -0700, 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
On 5/3/19 2:30 PM, Tom H wrote:
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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
On 5/3/19 2:30 PM, Tom H wrote:
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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
On 5/3/19 2:30 PM, Tom H wrote:
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
On Fri, May 3, 2019 at 9:52 PM Samuel Sieb 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
On 5/3/19 12:52 PM, Samuel Sieb wrote:
I don't see any flags
for grub2-mkconfig that can indicate which type to create.
If I get time, I am going to RFE that. And it would help if I do it
myself first and can show them the code
___
users mailing
On 5/3/19 12:25 PM, Tom H wrote:
grub2-efi-x64 and grub2-efi-x64-modules
grub2-pc and grub2-pc-modules
Did that
You then have to use "grub2-install" with "--target=i386-pc" for csm
and "--target=x86_64-efi" for efi.
"grub2-mkconfig checks and over rules you now and creates
a grub.cfg
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
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
On Fri, May 3, 2019 at 6:43 PM Samuel Sieb wrote:
>
> 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
On Fri, 2019-05-03 at 09:41 -0700, 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
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
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 ...
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
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
Uh.. I wanted
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
Uh.. I wanted legacy, not EFI.
What am I missing?
Are you
On 5/1/19 2:48 PM, ToddAndMargo via users wrote:
Hi All,
I have a Fedora 30 flash drive set up for dual booting
from Legacy or UEFI. It boots beautifully from UEFI.
(It also have a bios_grub partition).
It booted perfectly from both under Fedora 29.
Now when booting from legacy, it go into
Hi All,
I have a Fedora 30 flash drive set up for dual booting
from Legacy or UEFI. It boots beautifully from UEFI.
(It also have a bios_grub partition).
It booted perfectly from both under Fedora 29.
Now when booting from legacy, it go into "System Setup".
If you press system Setup, I get a
42 matches
Mail list logo
