Fedora boot entry not present in its own grub bootloader

Ask Fedora
,
21

That is why the EXTBOOT partition type was invented. It should be created as a vfat file system and marked as bls-boot in gparted. Furthermore, it should be mounted as /boot. Then all the kernels and initrd files will be stored in that file system instead of the ESP file system.

On new installation of Fedora, the /boot file system will be marked as EXTBOOT, but usually created as an ext4 system. Thus not suitable for sd-boot.

2 Likes
22

Apologies for delayed response.

These are the things I did in the end:

Reinstalled Windows with clean installation, meaning remove all partitions including ESP. Tried to install Fedora. Same result.

Then clean installation with Fedora, chose custom allocation and removed all partitions including ESP. Same result.

In the next windows installation, I was setting battery thresh-hold in myAsus app and saw that a firmware update is available. Updated. Tried to install fedora. It worked. Seems update was necessary.

I learned a lot about partitions and else doing this.
Thank you every one for the assistance.
Have a great day.

2 Likes
23

It seems that some of the newer kernels require that the firmware for newer laptops be up to date.

Glad to hear that you found the problem. :+1:

1 Like
24

Just as an additional FYI.
There is a command fwupdmgr that is able to update firmware on a lot of devices, including some of the laptops. Use fwupdmgr -h to see most of the command options then use fwupdmgr get-updates to see the available updates and sudo fwupdmgr update to actually install the updates

25

I was wondering how Iā€™d be doing it in fedora. Thank you.

26

Also see /usr/share/doc/fwupd/README.md on your system about halfway down.

Basic usage flow (command line)

If you have a device with firmware supported by fwupd, this is how you can check
for updates and apply them using fwupdā€™s command line tools.

# fwupdmgr get-devices

This will display all devices detected by fwupd.

# fwupdmgr refresh

This will download the latest metadata from LVFS.

# fwupdmgr get-updates

If updates are available for any devices on the system, theyā€™ll be displayed.

# fwupdmgr update

This will download and apply all updates for your system.

  • Updates that can be applied live will be done immediately.
  • Updates that run at bootup will be staged for the next reboot.

You can find more information about the update workflow in the end
users section of the fwupd website.

/usr/share/doc contains mostly useless information, but occasionally there are some useful tidbits.

3 Likes
27

Hi,

I have the exact same issue during the installation of F41.
Iā€™m on an Asus TUF dash F15, intel processor and Nvidia RTX 3060 GPU, 2 SSD (1 with windows and 1 with Linux)

"The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?

Failed to set new efi boot target. This is most likely a kernel or firmware bug."

I tried to update my BIOS as you said here, but the command line you gave told me that there is no update available for it.

I also tried to make a custom install as I saw on other forum discussions to be sure of partitions choices.

I tried to use gparted and the disk manager preinstalled in the live version to erase all partition of my linux SSD before starting the install.

I tried to that all again with my windows SSD dismounted. I already done that one time by the past and it solved my installation issue with an Ubuntu based distro.

I also tried to reinstall my previous linux distro (Cachy OS) and itā€™s worked perfectly. For info, this distro use system d instead grub.

And finally I tried to install another distro based on fedora : bazzite, to see. And practically the same issue :
"The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?

Failed to write the boot loader configuration."

With fedora and bazzite, I can see in my BIOS my SSD named Fedora.
When I decide to boot on it with fedora installed on it, it automatically restart on windows, if my windows SSD is mounted, and it restart on the BIOS if the windows SSD is dismounted.
With bazzite, if I boot on Fedora SSD, it open a bash command line page in the grub.

Maybe I did something wrong, Iā€™m daily use linux just for one year and I never have to go as deep in boot issue. So Iā€™m glad to learn if you have any wiki about this topic that could help me.

Sorry for this long message, I tried to give all information I can.
I hope someone can help me.

28

It looks like there are known issues with secure boot and Grub on that system:

https://wiki.archlinux.org/title/ASUS_TUF_DASH_F15_(2022)#Secure_Boot

Can you disable secure boot?

You should also check your vendorā€™s website. Iā€™m not sure that the CLI tool that comes with Fedora Linux will always see the latest updates. Use dmidecode to find your systemā€™s current BIOS Revision.

29

I forgot to tell it but I did all of my try with secure boot disabled.

I updated my BIOS by USB key with the firmware downloaded on the Asus website. Then I tried again the installation and it worked !!!
Thank you very much for the help.

I have still a question, because Iā€™m not understanding something :

Before the BIOS update I made sudo dmidecode on the F41 flash, I had this result :
BIOS Information
Vendor: American Megatrends International, LLC.
Version: FX516PM.330
Release Date: 05/15/2023
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
ACPI is supported
Smart battery is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.19
Firmware Revision: 3.16

I compared with the Asus website and it seems that it was the same version (330) with different date 2023/06/21 instead 2023/05/15.
So I made the update, then try again to install F41.
The fedora install worked perfectly.
Now on fedora I did again sudo dmidecode and I can see the exact same result than before the bios update. It seems that my BIOS was already up to date.
So my question, why it didnā€™t install well before ?

If you donā€™t have the answer, no problem all functioning well now.

Thank you very much

1 Like
30

Itā€™s a good question. I donā€™t know. I guess it isnā€™t impossible that they could release a firmware update without changing the embedded revision number. I donā€™t know why they would do that though.

1 Like
31

I have a brand new micro PC that I just purchased with win11 installed.
To install fedora I added an additional SSD and installed fedora on that second drive.
The system refused to boot fedora even though the installation seemed to work perfectly.

What I found was that in the AMI bios it would allow only one drive to be in the boot list. Normally I would have the fedora installation first and the windows installation second, but in this case I was forced to select only the SSD containing fedora and it works properly for booting with grub and dual booting.

Sometimes problems with booting on a new installation may be related to settings within bios ā€“ particularly when having an efi partition of both drives.

3 Likes