Installing bootloader failed on installing Fedora KDE Plasma 42

Ask Fedora
,
1

Hi everyone.

My name is Sajed.

I’ve a problem with installing the bootloader when I am trying to install Fedora KDE Plasma on my laptop as primary OS.
Previously I had Windows 10 installed on my one disk drive (ssd SATA), partitioned into two drive (C as sys files l, and D for data).
I downloaded the .iso from the official site and used Fedora media writer to put the system into the USB flash disk. Then I booted normally, with checking that my BIOS is on UEFI mode and the secure boot is enabled.
Then I go to install the system beyond the live experience normally, first I choose automatic as partitioning type and all the previous partitions got deleted as I want. Enable the root user, and create an account and hit begin installation, the first operations goes well, until the installing bootloader comes, waiting like 3~5 min and a pop-up shows to tell that an unknown error occurred and the program needs to quit (With another button to report the bug to redhat bugzilla site and I did that).
And so, the system keeps do that even If I restarted the process.
Notice that: I did pass the testing media drive on the starting booting point.

I’ve checked that my drive is GPT. Also I followed a video to use custom partitioning and the same results happened.

I will update the topic with the log output soon (I am in the middle of trying another USB).
All I remembered is the Anaconda which throw this error and it is related on UTF-8.

My BIOS support bith Legacy and UEFI modes and the TPM is always activated during all the experiment. Secure booting is always activated also and I did try to switch to Legacy mode and then the machine couldn’t boot or even recognize the USB disk.

2

Sounds like it could be the same issue this person had: Fedora 41 Bootloader Fails to Install with Anaconda Error 41.35

The problem then was that the UEFI NVRAM contained old entries with special characters.

Can you boot into the live USB environment, execute efibootmgr in a terminal, and paste the result?

1 Like
3

Nice! The same exact problem that I’m faced in the link that you specified.

Here’s the output of the efibootmgr command:

BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0008,0007,0006,0001,0002,0005,0004
Boot0001* HDD/SSD       PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)
Boot0002* ODD   PciRoot(0x0)/Pci(0x1f,0x2)/Sata(1,0,0)
Boot0003* LAN1  BBS(128,X�,0x0)030000000000190000000000000002009b0000d080000000450b00d0db0000d0000000000000000000000000000000000000000000000000000000000000000000000000000900
Boot0004* LAN2  PciRoot(0x0)/Pci(0x19,0x0)/MAC(ec21e51cfa24,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)
Boot0005* LAN1  PciRoot(0x0)/Pci(0x19,0x0)/MAC(ec21e51cfa24,0)/IPv6([::],0,Static,[::],[::],64)
Boot0006* Windows Boot Manager  HD(1,GPT,4d91abce-ed77-4f61-ab9c-f437e97714b9,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0007* USB Memory    PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)
Boot0008* Fedora        HD(2,GPT,c3bbe1bc-8618-4e18-bd9a-b10e2cc88779,0x53d5dc,0xf000)/\EFI\fedora\shimx64.efi
4

That does indeed look like the same problem!

You should be able to fix it by doing:

efibootmgr --delete-bootnum -b 0003

and then retrying the installation.

(I’m assuming that you aren’t actively using this 0003 boot entry - it seems to be some compatibility-mode LAN boot).

If you don’t mind sharing, what brand is your laptop? I’m wondering if it’s some specific manufacturer’s UEFI that creates these NVRAM entries with the special characters.

5

Thank you sir so much for help.

Yeah I did what you tell there by deleting the specific boot line which contains the ? mark on it.

And yes nvm, I could share my laptop brand!

I think it’s a Toshiba related issue. My laptop is the same as the guy in the related topic link that you specified (old PC made in 2017). Exactly Toshiba dynabook Satellite.

Again thank you for your time :smiley:

1 Like
6

Interesting, I’m guessing it is a Toshiba-specific issue. Thanks for sharing!