Fedora 44 KDE No Boot on Acer Laptop (Swift 3 SF314-51)

Ask Fedora
,
1

ISO all good, Fedora “Live” smooth and fast, loved it and decided to install in my internal drive. Nice clean install but upon restart, No Boot. Used Boot Repair and the result is below. Appreciate some big help from a newbie.

boot-repair-4ppa2088 [20260520_1554]

============================== Boot Info Summary ===============================

=> No boot loader is installed in the MBR of /dev/sda.

sda1: __________________________________________________________________________

File system:       vfat
Boot sector type:  FAT32
Boot sector info:  No errors found in the Boot Parameter Block.
Operating System:  
Boot files:        /efi/BOOT/fbia32.efi /efi/BOOT/fbx64.efi 
                   /efi/fedora/gcdia32.efi /efi/fedora/gcdx64.efi 
                   /efi/fedora/grubia32.efi /efi/fedora/grubx64.efi 
                   /efi/fedora/mmia32.efi /efi/fedora/mmx64.efi 
                   /efi/fedora/shim.efi /efi/fedora/shimia32.efi 
                   /efi/fedora/shimx64.efi /efi/fedora/grub.cfg

sda2: __________________________________________________________________________

File system:       ext4
Boot sector type:  -
Boot sector info: 
Operating System:  
Boot files:        /grub2/grub.cfg

sda3: __________________________________________________________________________

File system:       btrfs
Boot sector type:  -
Boot sector info: 
Operating System:  
Boot files:

sdb: ___________________________________________________________________________

File system:       iso9660
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.
   dmesg(1) may have more information after failed mount system call.

================================ 0 OS detected =================================

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: HD Graphics 620 from Intel Corporation
Live-session OS is Linuxmint 64-bit (Linux Mint 22.3, zena, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: V1.01(1.1) from Insyde Corp.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* Unknown Device: HD(1,GPT,e8895298-18b7-4082-bf62-c77f0cbc7083,0x800,0x12c000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0001* Linux HD(1,MBR,0x24a1e612,0x2104,0x2800)/File(\EFI\Boot\grubx64.efi)RC
Boot0003* Qubes OS HD(1,GPT,15eadd68-af75-4fd3-b4dd-697c7b3fdb50,0x800,0x12c000)/File(\EFI\qubes\grubx64.efi)
Boot0004* Unknown Device: HD(1,GPT,ccaa105f-439a-43d4-9de0-594d645ce3e9,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) File(.䍒)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC

956d68ff5979023ec50acd882284366f sda1/BOOT/fbia32.efi
16a2c1f4e60eb4196a20a619234d25a2 sda1/BOOT/fbx64.efi
c848be0f2474125f2e3001287675f2e1 sda1/fedora/gcdia32.efi
02438cdd9a993b4db47838ef95f110e9 sda1/fedora/gcdx64.efi
eed9836f76d413effa69149b8bc2d839 sda1/fedora/grubia32.efi
41602409516bb86276375aac6b39704e sda1/fedora/grubx64.efi
e0d7b39239db3afa752bb1d42911a8ca sda1/fedora/mmia32.efi
f5d5be5a1d9e96b66f5d9096e456960d sda1/fedora/mmx64.efi
09765bb702a95887073621c51a0a2a3b sda1/fedora/shim.efi
b033f395f4391a464007f3329dcbaa94 sda1/fedora/shimia32.efi
09765bb702a95887073621c51a0a2a3b sda1/fedora/shimx64.efi
b033f395f4391a464007f3329dcbaa94 sda1/BOOT/BOOTIA32.efi
09765bb702a95887073621c51a0a2a3b sda1/BOOT/BOOTX64.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

sda : is-GPT, no-BIOSboot, has—ESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

sda1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sda3 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB

Partitions info (2/3): _________________________________________________________

sda1 : is—ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, vfat
sda2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, ext4
sda3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, btrfs

Partitions info (3/3): _________________________________________________________

sda1 : not–sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
sda2 : is—sepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda
sda3 : maybesepboot, no—boot, part-has-no-fstab, not-sep-usr, no—usr, part-has-no-fstab, no–grub.d, sda

fdisk -l (filtered): ___________________________________________________________

Disk sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk identifier: 4017BCE2-FCB6-4CA2-A3A0-F26D40B95E9B
Start End Sectors Size Type
sda1 2048 1230847 1228800 600M EFI System
sda2 1230848 5425151 4194304 2G Linux filesystem
sda3 5425152 250068991 244643840 116.7G Linux filesystem
Disk sdb: 29.82 GiB, 32015679488 bytes, 62530624 sectors
Disk identifier: 0x24a1e612
Boot Start End Sectors Size Id Type
sdb1 * 64 6038399 6038336 2.9G 0 Empty
sdb2 8452 18691 10240 5M ef EFI (FAT-12/16/32)
sdb3 6041600 62530623 56489024 26.9G 83 Linux

parted -lm (filtered): _________________________________________________________

sda:128GB:scsi:512:512:gpt:ATA LITEON CV3-8D128:;
1:1049kB:630MB:629MB:fat32:EFI System Partition:boot, esp;
2:630MB:2778MB:2147MB:ext4::;
3:2778MB:128GB:125GB:btrfs::;
sdb:32.0GB:scsi:512:512:unknown:SanDisk Cruzer Edge:;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 vfat 9F96-0931 e8895298-18b7-4082-bf62-c77f0cbc7083 EFI System Partition
├─sda2 ext4 78dde5cb-d240-4796-bf58-ca25f8dddc83 56990924-1721-4b66-b131-a5fb98ef78e6
└─sda3 btrfs 2aba4631-61c6-4ac2-be36-9b9e5adb4b4e 5235f8bf-f9d7-41ad-a1a0-57855ead223d fedora
sdb iso9660 2026-01-08-18-32-58-00 Linux Mint 22.3 Cinnamon 64-bit
├─sdb1 iso9660 2026-01-08-18-32-58-00 24a1e612-01 Linux Mint 22.3 Cinnamon 64-bit
├─sdb2 vfat 695F-F85A 24a1e612-02
└─sdb3 ext4 4ec4d63b-4c1f-4973-be04-7dd0807b868f 24a1e612-03 writable

Mount points (filtered): _______________________________________________________

                                                         Avail Use% Mounted on

/dev/sda1 578.8M 3% /mnt/boot-sav/sda1
/dev/sda2 1.4G 19% /mnt/boot-sav/sda2
/dev/sda3 110.8G 4% /mnt/boot-sav/sda3
/dev/sdb1 0 100% /cdrom
efivarfs 24.4K 71% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/sda2 ext4 rw,relatime
/dev/sda3 btrfs rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/
/dev/sdb1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

===================== sda1/efi/fedora/grub.cfg (filtered) ======================

search --no-floppy --root-dev-only --fs-uuid --set=dev 78dde5cb-d240-4796-bf58-ca25f8dddc83
set prefix=($dev)/grub2
export $prefix
configfile $prefix/grub.cfg

======================== sda2/grub2/grub.cfg (filtered) ========================

END /etc/grub.d/30_os-prober

UEFI Firmware Settings uefi-firmware

END /etc/grub.d/30_uefi-firmware

==================== sda2: Location of files loaded by Grub ====================

       GiB - GB             File                                 Fragment(s)

0.963874817 = 1.034952704 grub2/grub.cfg 1
0.797847748 = 0.856682496 vmlinuz-0-rescue-a6f4b49564294be98644f5c93fe90f28 3
0.821285248 = 0.881848320 vmlinuz-6.19.10-300.fc44.x86_64 2
1.093765259 = 1.174421504 initramfs-0-rescue-a6f4b49564294be98644f5c93fe90f28.img 4
1.144954681 = 1.229385728 initramfs-6.19.10-300.fc44.x86_64.img 1

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sdb

BTRFS detected on sda3
ls /dev/sda3:

mount /dev/sda3 /mnt/boot-sav/sda3/
MOUNTCODE=0

os-prober before @ subvol mount:

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

2

Can you explain what “No Boot” means? What happens when you start your machine?

A potential problem is here:

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* Unknown Device: HD(1,GPT,e8895298-18b7-4082-bf62-c77f0cbc7083,0x800,0x12c000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0001* Linux HD(1,MBR,0x24a1e612,0x2104,0x2800)/File(\EFI\Boot\grubx64.efi)RC
Boot0003* Qubes OS HD(1,GPT,15eadd68-af75-4fd3-b4dd-697c7b3fdb50,0x800,0x12c000)/File(\EFI\qubes\grubx64.efi)
Boot0004* Unknown Device: HD(1,GPT,ccaa105f-439a-43d4-9de0-594d645ce3e9,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi) File(.䍒)

The BootCurrent entry points to Boot0001, which is invalid (it refers to an MBR disk, but your disk is now GPT). 0003 and 0004 are also invalid - they refer to PARTUUIDs that no longer exist on the disk.

Your Fedora boot (Boot0000) doesn’t appear in the BootOrder at all.

I would suggest this from the terminal of a live session (shouldn’t matter whether it is the Fedora Live USB or your Mint Live USB)

sudo efibootmgr --delete-bootnum 0001
sudo efibootmgr --delete-bootnum 0003
sudo efibootmgr --delete-bootnum 0004
sudo efibootmgr --bootorder 0000,2001,2002,2003

This should remove the invalid entries and make Fedora the default.

3

At startup, go into BIOS to Boot Order or Priority whatever it is called on your machine.

Do you see the entry for Fedora?

If yes, highlight it and make it first then save and exit.

Does the computer boot normally and get you to the desktop?

4

This looks wrong.
On every fedora installation I have ever done that should show (within the esp partitions) EFI/… and not efi/…

On a working fedora system it would normally be the full path of /boot/efi/EFI/…

I am not sure it is appropriate to try and do a boot repair of fedora from booting a Mint OS. Those systems are very different in the way they operate. The linix live install media also allows repairs.

That also is wrong, as the path should be sda1/EFI/fedora/…

5

Start up the laptop, pressed F2, make sure the boot sequence is at least on the internal drive

IMG2464
IMG24641920×1440 651 KB

saved upon excit,Restart then this.
IMG2465
IMG24652048×1536 694 KB

Thank you for your advice.

6

Never saw Ferdora, hoping it would like the way Mint and Zorin did. Only had the model of my internal drive. I’ve tried Mint and Zorin. Had problems with booting up from the drive. Boot Repair solved it and prioritized Windows Boot Manager. That’s when I get to choose how to boot up Mint or Zorin, depending in my drive.

IMG2209
IMG22092048×1536 484 KB

7

I used Mint to use the Boot Repair app. I tried looking for a same or similar app with Fedora but couldn’t find one. That boot report shown initially was generated from this app. I rely on talented people since I don’t know squat about programming. :zany_face:

bootrepair
bootrepair1920×1080 842 KB

Here are the specs of my Acer laptop. I thought it was indicated in the report.
Acer System
Acer System507×531 47.4 KB

8

The important thing is to use fedora tools on a fedora system. Using tools from Ubuntu, Mint, Debian, or similar on a fedora system is sure to break things unless the user is an expert and knows the differences (and is prepared to repair what gets broken).

Asking questions here with the details of the problem is almost 100% certain to reach someone who is familiar with the system and can assist.

9

Took your suggestion.

sudo efibootmgr --delete-bootnum 0001
sudo efibootmgr --delete-bootnum 0003
sudo efibootmgr --delete-bootnum 0004
sudo efibootmgr --bootorder 0000,2001,2002,2003
You must specify an entry to delete (see the -b option or -L option).
You must specify an entry to delete (see the -b option or -L option).
You must specify an entry to delete (see the -b option or -L option).
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,2001,2002,2003
Boot0000* Unknown Device: HD(1,GPT,e8895298-18b7-4082-bf62-c77f0cbc7083,0x800,0x12c000)/\EFI\fedora\shim.efiRC
Boot0001* Linux HD(2,GPT,646f982a-2f62-480e-8cb6-f84c79015b25,0x6374c4,0xf000)/\EFI\Boot\grubx64.efiRC
Boot0003* Qubes OS HD(1,GPT,15eadd68-af75-4fd3-b4dd-697c7b3fdb50,0x800,0x12c000)/\EFI\qubes\grubx64.efi
Boot0004* Unknown Device: HD(1,GPT,ccaa105f-439a-43d4-9de0-594d645ce3e9,0x800,0x100000)/\EFI\ubuntu\shimx64.efiRC
Boot0005* Unknown Device: HD(1,GPT,5c786980-7cb8-4ba0-a726-e2ecb48eb7e4,0x800,0x100000)/\EFI\ubuntu\shimx64.efiRC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Went to BIOS, no Fedora or Linux in Boot priority list.
No Bootable Device.

IMG2465
IMG24652048×1536 694 KB

10

Ah, no, the report didn’t show this was an Acer - and that is the smoking gun here.

Acer is notorious for making it difficult to boot into Linux. Particularly, you have to mark the relevant EFI files as “trusted for execution”, which requires enabling Secure Boot at least temporarily.

I would suggest following these steps recommended in the Arch wiki. (For example, that’s how this Fedora user fixed it.)

  1. Start Arch from a bootable USB.
  2. Use the efibootmgr command to remove the non-verified entries.
  3. Reboot and try to access the BIOS (by pressing F2). It should now work.
  4. If available, enable the F12 Boot Menu option (to use as a fallback next time).
  5. Enable Secure Boot and set a Supervisor Password.
  6. Select and mark the .efi files as trusted for execution.
  7. Disable Secure Boot and remove the Supervisor Password.
  8. Reboot and re-enter the BIOS to set up again the appropriate boot priority order.

Notes:

  • At step 1, you should be able to use any Linux Live USB, doesn’t need to be Arch
  • At step 2, the commands should be the following. Sorry for my earlier errors in the syntax.
sudo efibootmgr --delete-bootnum --bootnum 0000
sudo efibootmgr --delete-bootnum --bootnum 0001
sudo efibootmgr --delete-bootnum --bootnum 0003
sudo efibootmgr --delete-bootnum --bootnum 0004
12

Yes, comparing my son’s Dell Latitude 7440 it takes in Linux like anything. Keep you posted. Thank you.

13

Got to step 5, how do I select and mark the .efi files as trusted for execution?

14

I can’t verify this because I don’t have an Acer, but maybe these instructions help. Obviously you’re looking for “Fedora” where the instructions say “Ubuntu”.

15

I thought needed to type in commands. Followed the procedures from the link. Finally got this crazy Acer setup and updated. Thank you, greatly appreciate your patience and help PG. :saluting_face: