s the partition
table to find the correct partition, mounts that partition and reads the
configured executables from it.
OK I see, thanks exactly what I was asking. So if for some reason
you wanted to save boot code, I guess, you would save partitions and
files?
Yes. And maybe I guess dump out th
e partition
> >table to find the correct partition, mounts that partition and reads the
> >configured executables from it.
>
> OK I see, thanks exactly what I was asking. So if for some reason
> you wanted to save boot code, I guess, you would save partitions and
> files?
On 9/25/2023 4:44 PM, Chris Adams wrote:
Once upon a time, Bill Cunningham said:
...
There's no magic reserved space outside partitions that is used for
booting anymore. The firmware finds the device, reads the partition
table to find the correct partition, mounts that partition and reads the
inary of the drive? Or, is that all
> gone now and we are just looking at files in text in partitions like
> boot/efi ?
UEFI uses GPT partitioning, and uses a partition to store the files
needed for booting (which Fedora usually mounts at /boot/efi). The
partition has a special assigne
just looking at files in text in partitions like boot/efi ?
Bill
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
On 17 Jul 2023 at 17:29, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 17:29:17 -0400
Subject:works fine - Re: F38 install fails on a Lenovo x120e - Failed
to set
new efi boot traget
From: Robert Moskowitz
To: Community support for Fedora users ,
Roger
I got the error again when the install got to that point. I told it to
ignore and continue installing.
I have a usable system.
I did notice on boot an option to edit the EFI firmware. I selected
that and got an error that cannot boot into the EFI editor.
But that is ok. the system is
On 7/17/23 16:07, Michael D. Setzer II wrote:
First computer was a 1963 IBM 1130 with punch cards back in
1975. So started with old machines that still were working.. High
School..
I started with a teletype 55 baudot to a GE MarkV in '66. Best I can
figure out was our school (Euclid OH) w
On 17 Jul 2023 at 11:25, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 11:25:31 -0400
To: Community support for Fedora users
From: Robert Moskowitz
Subject:F38 install fails on a Lenovo x120e - Failed to set
new efi boot
do the install again, keep the drive partitions I set
up and ignore the EFI warning and see how it goes...
On 7/17/23 15:05, Roger Heflin wrote:
Yes, some did have efi back then. i have some fm2 mbs that did. There
will be an option in the bios to enable efi if it does. efi dates to
early
Yes, some did have efi back then. i have some fm2 mbs that did. There will
be an option in the bios to enable efi if it does. efi dates to early
itanium systems in 2002. it was so bad it took years to make it to x86
systems. very little was in the classic bios menu and most config was in a
Bios ver is "current", ver 1.17 dated 11/7/2012!
Did we have EFI back then?
Oh, F37 live CD booted fine.
On 7/17/23 13:17, Jeffrey Walton wrote:
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz wrote:
this system had F22 on it.
I just went through all the steps to blow aw
hour with the spindizzy on "Installing boot loader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to s
On Mon, Jul 17, 2023 at 1:56 PM Robert Moskowitz wrote:
>
> I just recalled. There was a /boot/efi partition on the old F22 setup.
>
> But booting up F37 live now.
If you haven't done so, now would be a good time to update the
laptop's firmware. Get on the latest version
I just recalled. There was a /boot/efi partition on the old F22 setup.
But booting up F37 live now.
On 7/17/23 13:17, Jeffrey Walton wrote:
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz wrote:
this system had F22 on it.
I just went through all the steps to blow away the old partitions
came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No
t; If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and continue
> with the installation?
>
> Failed to set new efi boot target. This is most
It has the AMD E-350 duo core CPU which I am pretty sure is x64.
On 7/17/23 12:58, Barry wrote:
On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
What should I do at this point. It IS an old system that has had a number of
ver of Fedora on it. It was booting F22 just fine, it seemed but n
oot
loader".
If finally came back with a dialog box with an error of:
The following error occurred while installing the boot loader. The
system will not be bootable. Would you like to ignore this and
continue
with the installation?
Failed to set new efi boot target. This is most likely a ker
> On 17 Jul 2023, at 16:26, Robert Moskowitz wrote:
>
> What should I do at this point. It IS an old system that has had a number of
> ver of Fedora on it. It was booting F22 just fine, it seemed but now it is
> all gone...
Is it a 64bit system or 32bit? Fedora needs 64bit now.
Barry
gt;
> If finally came back with a dialog box with an error of:
>
> The following error occurred while installing the boot loader. The
> system will not be bootable. Would you like to ignore this and
> continue
> with the installation?
>
> Failed to set new efi boot target.
alling the boot loader. The
system will not be bootable. Would you like to ignore this and continue
with the installation?
Failed to set new efi boot target. This is most likely a kernel or
firmware bug.
No|Yes
What should I do at this point. It IS an old system that has had a
number
it
automatically
create. After complete, the Acer would not show the flash as a boot option??
For some reason the default setup had created the EFI System as 600M with
Fat32. On one of my other Fedora machines used gparted to resize it to 63M
and that converted it to Fat16? Then the 128G usb
On 10/12/22 16:28, Michael D. Setzer II via users wrote:
Wondering if possible to add non-Fedora options to EFI boot menu with some
method similar to the 40_Custom. Thanks.
I've maintained a project on Sourceforge going back to 2004, and it was
originally a cd only boot option, but over
Michael D. Setzer II composed on 2022-12-10 15:28 (UTC+1000):
> Wondering if possible to add non-Fedora options to EFI boot menu with some
> method similar to the 40_Custom. Thanks.
...
> Also have this to run memtest since regular Fedora one doesn't seem to work??
> title mem
Wondering if possible to add non-Fedora options to EFI boot menu with some
method similar to the 40_Custom. Thanks.
I've maintained a project on Sourceforge going back to 2004, and it was
originally a cd only boot option, but over years create usb and ability to boot
directly from grub2
veral
> >> disks, should I have a single /boot/efi ?
> >
> > It will work as long as none of the installed distributions are
> > duplicated, because that will duplicate the label. e.g. default
> > fedora label is fedora, so if more than one is installed there will
> How is generated /boot/grub2/grub.cfg ?
grub2-mkconfig creates /boot/grub2/grub.cfg
There's a script in grub2-common that creates /boot/efi/fedora/grub.cfg, hence
the reinstallation instructions to delete it so it's properly recreated if
accidentally stepped on:
https:
On Wed, Jul 27, 2022, at 11:20 AM, stan via users wrote:
> On Wed, 27 Jul 2022 10:54:51 +0200
> Patrick Dupre wrote:
>
>> If I have several distributions on a single machine with several
>> disks, should I have a single /boot/efi ?
>
> It will work as lo
, Patrick Dupre wrote:
> > In addition to my previous question.
> > Should I have a grub.cfg in /boot/efi/EFI/fedora ?
>
> There should be two:
>
> /boot/efi/EFI/fedora/grub.cfg
> /boot/grub2/grub.cfg
>
> The first one has a few lines to find and load the 2nd one.
&g
On Wed, Jul 27, 2022, at 5:22 AM, Patrick Dupre wrote:
> In addition to my previous question.
> Should I have a grub.cfg in /boot/efi/EFI/fedora ?
There should be two:
/boot/efi/EFI/fedora/grub.cfg
/boot/grub2/grub.cfg
The first one has a few lines to find and load the 2nd one.
On Wed, 27 Jul 2022 10:54:51 +0200
Patrick Dupre wrote:
> If I have several distributions on a single machine with several
> disks, should I have a single /boot/efi ?
It will work as long as none of the installed distributions are
duplicated, because that will duplicate the label
On Wed, 2022-07-27 at 10:54 +0200, Patrick Dupre wrote:
> If I have several distributions on a single machine with several
> disks, should I have a single /boot/efi ?
That is the general idea. It's part of the system bootloader, and
different OSs put their bits in there.
You'll
In addition to my previous question.
Should I have a grub.cfg in /boot/efi/EFI/fedora ?
>
> Hello,
>
> Is there not something wrong with this
>
> When /boot/efi is ot mounted:
> ls /boot/efi/
> EFI
>
>
> while in the fstab
> UUID=A686-D625 /boo
Hello,
If I have several distributions on a single machine with several
disks, should I have a single /boot/efi ?
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire
> On 26 Jul 2022, at 19:02, Patrick Dupre wrote:
>
> Hello,
>
> Is there not something wrong with this
>
> When /boot/efi is ot mounted:
> ls /boot/efi/
> EFI
That is normal - at least for my systems.
$ mount | grep efi
efivarfs on /sys/firmware/efi/efivars type
>
> df /boot/efi
>
> And see if it is really mounted.
Sorry, it is really mounted at boot.
I can umount and remount even with a file in /boot/efi/EFI is here
I am going to guess it is not. And
> it has nofail so will cleanly fail and not block the os.
>
> After the
df /boot/efi
And see if it is really mounted. I am going to guess it is not. And
it has nofail so will cleanly fail and not block the os.
After the df then try a
mount /boot/efi
On Tue, Jul 26, 2022 at 1:02 PM Patrick Dupre wrote:
>
> Hello,
>
> Is there not something wro
Hello,
Is there not something wrong with this
When /boot/efi is ot mounted:
ls /boot/efi/
EFI
while in the fstab
UUID=A686-D625 /boot/efi vfat
umask=0077,shortname=winnt,nofail 0 2
Indeed, I really have the mount the of /boot/efi during the boot
and of course
ls
On Fri, 24 Dec 2021 at 19:00, Tom Horsley wrote:
> I recently got a new mini PC that is UEFI only. Out of curiosity
> I started reading about the EFI shell. I now have only one
> question: Would any "ordinary" user ever have any reason to
> use the EFI shell? (Secondary
Well, when EFI started it was so screwed up that pretty much
everything had to be done in that EFI shell (the classic bios screen
did very little in the early systems). That was 2002-2003 (or
before), and it has taken so long for EFI to take over is because of
how badly the first implementations
> I recently got a new mini PC that is UEFI only. Out of curiosity
> I started reading about the EFI shell. I now have only one
> question: Would any "ordinary" user ever have any reason to
> use the EFI shell? (Secondary question: Would he be able to
> anyway?)
>
>
I recently got a new mini PC that is UEFI only. Out of curiosity
I started reading about the EFI shell. I now have only one
question: Would any "ordinary" user ever have any reason to
use the EFI shell? (Secondary question: Would he be able to
anyway?)
Trying to decrypt the things I
On Sun, 05 Sep 2021 17:34:49 -
"Gunnar Gervin" wrote:
Welcome to Fedora.
> Where do I find a Fedora distro with EFI ?
If you go here, you should be able to download an install image. There
are also images that allow most of the install to be done from the net
(netinstall)
On 6 Sep 2021 at 1:02, Samuel Sieb wrote:
Subject:Re: OT: How to load kernels in EFI setup.
To: Community support for Fedora users
From: Samuel Sieb
Date sent: Mon, 6 Sep 2021 01:02:18 -0700
Send reply to: Community
On 9/4/21 4:21 AM, Michael D. Setzer II wrote:
Thanks for the quick response.
Yes, the kernel EFI options are built into the kernels build
from the kernel.org source code, but don't have
signatures, since that seems to be a very expensive and
long process, as I've seen on the memtest
> El sep. 5, 2021, a la(s) 9:12 p.m., Ryan Cunningham
> escribió:
>
> El sep. 5, 2021, a la(s) 10:35 a.m., Gunnar Gervin
> escribió:
>>
>> Hi all.
>> Where do I find a Fedora distro with EFI ?
>> In here cos heard & read that Fedora supports EFI
El sep. 5, 2021, a la(s) 10:35 a.m., Gunnar Gervin
escribió:
>
> Hi all.
> Where do I find a Fedora distro with EFI ?
> In here cos heard & read that Fedora supports EFI boot.
> I set wrongfully up my Macbook 2,1 OSX 10.6.8 (2007) x86-64 with Debian
> 32bit.
> Becaus
On Sun, Sep 05, 2021 at 10:49:21PM +0300, Gunnar Gervin wrote:
> Hi all.
> Where do I find a live Fedora x86-64 iso image with EFI 'cd image' in it ?
> (My 2007 ex-Mac computer now only runs Puppy x86-64 live dvd in RAM.)
> My Macbook 64b computer won't open any iso w
Hi all.
Where do I find a live Fedora x86-64 iso image with EFI 'cd image' in it ?
(My 2007 ex-Mac computer now only runs Puppy x86-64 live dvd in RAM.)
My Macbook 64b computer won't open any iso without a cd image named EFI.
Alt key on startup will show a 'Window cd', on
Hi all.
Where do I find a Fedora distro with EFI ?
In here cos heard & read that Fedora supports EFI boot.
I set wrongfully up my Macbook 2,1 OSX 10.6.8 (2007) x86-64 with Debian 32bit.
Because 32bit gets outdated and bnasically is wrong for the computer, I wanted
64bit.
But of some reason
On 3 Sep 2021 at 22:51, Samuel Sieb wrote:
Subject:Re: OT: How to load kernels in EFI setup.
To: users@lists.fedoraproject.org
From: Samuel Sieb
Date sent: Fri, 3 Sep 2021 22:51:57 -0700
Send reply to: Community support
nitrd /ramdisk.lzma
}
Just copy the kernel and ramdisk.lzma to /boot and it
becomes an option in the grub menu.
Just had a use that got 140 new Dell machines, and they
seem to no longer support any bios boot?? So, EFI is the
only option.
Have the EFI kernel options set, but haven't found info on
how
t and it
becomes an option in the grub menu.
Just had a use that got 140 new Dell machines, and they
seem to no longer support any bios boot?? So, EFI is the
only option.
Have the EFI kernel options set, but haven't found info on
how to make an efi boot. I've looked, but I've not
d to mount /boot/efi
>
> On Jul 17, 2021, at 04:29, Patrick Dupre wrote:
> >
> > Then,
> > mount /boot/efi
> > mount: /boot/efi: unknown filesystem type 'vfat'.
> >
> > I also noted during the load:
> > FAILED: failed to start load kernel
xt4
> defaults1 1
> UUID=B2EF-0CE4 /boot/efi vfat
> umask=0077,shortname=winnt,nofail 0 2
>
> /boot/efi is mounted properly with fc32.
>
> Is it an issue with the modules ?
You never answered my question.
Can you share with us the output o
Thanks for the feedback,
However, I do not understand.
Do you mean in the grub configuration
/boot/efi/EFI/fedora/grub.cfg
I have
menuentry 'Fedora 34 (Workstation Edition) (on /dev/sda6)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-/boot/vmli
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults 1 1
> UUID=B2EF-0CE4 /boot/efi vfat
> umask=0077,shortname=winnt,nofail 0 2
>
> /boot/efi is mounted properly with fc32.
>
> Is it an issue with the modules ?
>
Hello,
It is now 2 days that I am stuck with this issue.
I search on internet, but I did not find clear solutions which I could trust.
Here is the fstab
UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
defaults1 1
UUID=B2EF-0CE4 /boot/efi
t; Then,
> > mount /boot/efi
> > mount: /boot/efi: unknown filesystem type 'vfat'.
> >
> > I also noted during the load:
> > FAILED: failed to start load kernel modules
>
> You appear to be booting into a kernel that doesn’t have any kernel modules
>
On Jul 17, 2021, at 04:29, Patrick Dupre wrote:
>
> Then,
> mount /boot/efi
> mount: /boot/efi: unknown filesystem type 'vfat'.
>
> I also noted during the load:
> FAILED: failed to start load kernel modules
You appear to be booting into a kernel that doesn’t hav
Thanks,
nofail let me run the initialization.
Then,
mount /boot/efi
mount: /boot/efi: unknown filesystem type 'vfat'.
I also noted during the load:
FAILED: failed to start load kernel modules
Now
journalctl -b -o short-monotonic --no-hostname
It is long, I noted (in red):
[
On Fri, Jul 16, 2021 at 1:20 PM Patrick Dupre wrote:
>
> I collected the maximum information that I could
>
> Failed Mounting /boot/efi
> See "systemctl boot-efi" for details
> Dependency failed for local file system
> Dependency failed for mark the ... to relabel a
I collected the maximum information that I could
Failed Mounting /boot/efi
See "systemctl boot-efi" for details
Dependency failed for local file system
Dependency failed for mark the ... to relabel after reboot
Stopped
You are in emergency mode. After logging in type "journalc
t;cannot boot" means because it
> doesn't tell me how it's failing.
>
>
> > I get
> > failed to mount /boot/efi
> > /boot/efi is shared by both machines
> >
> > Here is the fstab of the fc34 machine
> >
> > #
> > UUID=a5b809ae-
On Thu, Jul 15, 2021 at 12:31 PM Patrick Dupre wrote:
>
> I have been able to boot on a rescue kernel!
> Linux localhost.localdomain 5.6.13-100.fc30.x86_64 #1 SMP Fri May 15 00:36:06
> UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>
> bootctl
> systemd-boot not installed in ESP.
> System:
> Firmwa
tell me how it's failing.
> I get
> failed to mount /boot/efi
> /boot/efi is shared by both machines
>
> Here is the fstab of the fc34 machine
>
> #
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults1 1
> UUID=B2EF
fc34, I cannot boot on the new fc34.
> I get
> failed to mount /boot/efi
> /boot/efi is shared by both machines
>
> Here is the fstab of the fc34 machine
>
> #
> UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39 / ext4
> defaults
Hello,
On a dual boot machine (one fc32, and one fc34).
after I upgraded the fc32 to fc34, I cannot boot on the new fc34.
I get
failed to mount /boot/efi
/boot/efi is shared by both machines
Here is the fstab of the fc34 machine
#
UUID=a5b809ae-61c2-4d67-b0f3-109e99faad39
debug code (in my working case it doesn't
> mean anything to me) and then it goes black then i get kernel boot
> scroll.
Thanks! Yes, cryptic indeed. This is transcribed from a photograph
so hopefully I didn't make a mistake:
script/lexer.c:336: token 259 text [
]
On Mon, Mar 29, 2021 at 1:55 AM Richard W.M. Jones wrote:
>
>
> I have a weird problem on an old Asus Zenbook UX305C where new kernels
> cannot be installed by grub. Specifically what happens is they appear
> in the boot menu fine, but if you try to boot them then the machine
> hangs hard with a
I have a weird problem on an old Asus Zenbook UX305C where new kernels
cannot be installed by grub. Specifically what happens is they appear
in the boot menu fine, but if you try to boot them then the machine
hangs hard with a completely black screen.
Oddly the kernel installed by Anaconda can b
Thanks for the suggestions. I did boot off liveusb and ran fsck on
/boot/efi. It did report problems, and I answered questions with wild
guesses.
Seems to be OK now, and the dnf update completed OK.
On Sat, Jul 25, 2020 at 3:55 PM Joe Zeff wrote:
> On 07/25/2020 12:42 PM, Sam Varshavc
On 07/25/2020 12:42 PM, Sam Varshavchik wrote:
Perhaps the /boot/efi FAT partition got corrupted. Try fscking it.
Before you go that far, you might consider trying this:
df -h /boot/efi
This will tell you how much space is used and how much is free, in a
human readable format
Neal Becker writes:
« HTML content follows »
Trying to install updates today failed because not enough space on
/boot/efi. Any idea how I can fix this?
installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB on
the /boot/efi filesystem
Error Summary
On Sat, 25 Jul 2020 13:30:24 -0400
Neal Becker wrote:
> Trying to install updates today failed because not enough space on
> /boot/efi. Any idea how I can fix this?
>
> installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs
> 6MB on the /boot/efi filesystem
>
On Sat, 25 Jul 2020 at 14:31, Neal Becker wrote:
> Trying to install updates today failed because not enough space on
> /boot/efi. Any idea how I can fix this?
>
> installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB
> on the /boot/efi filesystem
&g
Trying to install updates today failed because not enough space on
/boot/efi. Any idea how I can fix this?
installing package grub2-efi-x64-cdboot-1:2.04-21.fc32.x86_64 needs 6MB
on the /boot/efi filesystem
Error Summary
-
Disk Requirements:
At least 6MB more space needed on
On Fri, Jul 3, 2020 at 2:11 PM Patrick Dupre wrote:
>
> When I run grub2-install /dev/sda
> I get
> grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't
< exist. Please specify --target or --directory
>
> In /usr/lib/grub/
> total 24
> drwxr-xr-x
Hello,
When I run grub2-install /dev/sda
I get
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please
specify --target or --directory
In /usr/lib/grub/
total 24
drwxr-xr-x. 2 root root 12288 Jul 3 13:56 arm64-efi
drwxr-xr-x. 2 root root 12288 Jul 3 13:01 i3
On 5/1/20 1:32 PM, sean darcy wrote:
I got here with:
dnf system-upgrade download
dnf system-upgrade reboot
Then what was that comment about the installer failing? Did you mean
the boot?
grub shows the FC32 kernel. When I boot from that fc32 kernel, I get
this LoaderDevicePartUUID error.
On 5/1/20 3:03 PM, Samuel Sieb wrote:
On 4/30/20 6:44 AM, sean darcy wrote:
The F32 installer fails. systemd-gpt-auto-generator can't find the EFI
partition because the bootloader did not set it. Therefore sysroot is
not setup.
This is an Acer laptop, upgrading from F31.
You say "
On 4/30/20 6:44 AM, sean darcy wrote:
The F32 installer fails. systemd-gpt-auto-generator can't find the EFI
partition because the bootloader did not set it. Therefore sysroot is
not setup.
This is an Acer laptop, upgrading from F31.
You say "installer", but then you say &quo
On 4/30/20 9:44 AM, sean darcy wrote:
The F32 installer fails. systemd-gpt-auto-generator can't find the EFI
partition because the bootloader did not set it. Therefore sysroot is
not setup.
This is an Acer laptop, upgrading from F31.
Before that error, and maybe related to it, ther
The F32 installer fails. systemd-gpt-auto-generator can't find the EFI
partition because the bootloader did not set it. Therefore sysroot is
not setup.
This is an Acer laptop, upgrading from F31.
Before that error, and maybe related to it, there are errors loading 2
X.509 certificates.
On 11/28/19 3:08 PM, Tom Horsley wrote:
I'm wondering if it is remotely possible to do the
same sort of install with EFI booting. I assume I'd
need the qemu EFI bios so the virtual machine is
set up for EFI booting. Would efibootmgr be able to
fix things after the copy? Anyone ever
puter I'm building
supports old fashioned MSDOS booting, or if I'll
finally be forced to go with EFI.
I'm wondering if it is remotely possible to do the
same sort of install with EFI booting. I assume I'd
need the qemu EFI bios so the virtual machine is
set up for EFI booting. Wo
On Sat, 9 Nov 2019 00:36:04 +0200
Kad Zayar via users wrote:
> Does that mean that the install media should appear in my uefi boot
> menu as (at least) two entries? Or are we talking about the grub menu
> that appears *after* booting from the flash drive?
Yes to the first question, an
stall media to boot. That will boot it in EFI
mode, and it will install in EFI mode.
Does that mean that the install media should appear in my uefi boot menu
as (at least) two entries? Or are we talking about the grub menu that
appears *after* booting from the flash drive?
If you have legacy
On 07/11/2019 23:59, stan via users wrote:
press the key that opens the machine
firmware (used to be called BIOS, but it isn't really any more),
usually F2 or Del. Then look at the boot menu provided, and select the
UEFI version of the install media to boot. That will boot it in EFI
mode
it
> > his own).
>
> You will have to re-install Fedora to get a UEFI install. I don't
> think there is a way to boot the windows EFI partition from an MBR grub.
There isn't. See
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/
>
on't
think there is a way to boot the windows EFI partition from an MBR grub.
When the install media is booting, press the key that opens the machine
firmware (used to be called BIOS, but it isn't really any more),
usually F2 or Del. Then look at the boot menu provided, and select th
Hello, this is the first time I participate in a mailing list.
Today I attempted installing Fedora Workstation on a friend's computer
and there were some peculiar quirks to the process.
- Anaconda-installer asked me for a 2MB boot partition
- the resulting install had no /sys/firmwar
Tim via users writes:
On Tue, 2019-10-29 at 18:17 -0400, Sam Varshavchik wrote:
> Doesn't really matter, just curious that Anaconda sets /dev/sdb4 to
> be first in the boot order.
Did you install from some kind of boot disc? That can shuffle the
order of things, so (temporarily) it's sda, maki
On Tue, 2019-10-29 at 18:17 -0400, Sam Varshavchik wrote:
> Doesn't really matter, just curious that Anaconda sets /dev/sdb4 to
> be first in the boot order.
Did you install from some kind of boot disc? That can shuffle the
order of things, so (temporarily) it's sda, making your drives sdb,
sdc,
Gordon Messmer writes:
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
With BIOS I knew I needed to run grub-install to manually install grub on
/dev/sdb in addition to /dev/sda; do I need to do anything analogous to
that, with EFI?
Typically, no. Anaconda should have created boot records
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
With BIOS I knew I needed to run grub-install to manually install grub
on /dev/sdb in addition to /dev/sda; do I need to do anything
analogous to that, with EFI?
Typically, no. Anaconda should have created boot records for both. Use
"efibo
On 10/28/19 4:32 PM, Sam Varshavchik wrote:
I want to make sure that in the event one of the disks fail I'll be able
to boot off the other one. Are any additional steps needed for this,
beyond the ones that were done by F30's installer?
You could make another EFI boot entry that poi
I installed F30 on a replacement server with two HDDs. My existing hardware
earned its well-deserved retirement. My replacement hardware is the first
server hardware I'm using that uses EFI and the GPT.
I configured all my partitions with mdraid, including /boot/efi:
/dev/md124 on /boo
On 6/21/19 1:35 AM, Patrick Dupre wrote:
What is the advantage in having the /boot/efi on a single partition,
and not /boot for example (which was the case before EFI)?
UEFI doesn't boot from code stuffed into a tiny section of the MBR.
Under UEFI, the non-volatile RAM holds a descri
1 - 100 of 218 matches
Mail list logo
