Bizarre error during and after installation

Ask Fedora
, ,
1

Hi everyone,

I’m still relatively inexperienced with the Linux ecosystem and wanted to install Fedora on an old desktop I had lying around, mostly for learning purposes, and immediately started having issues.

I managed to install it from the Live USB after completely wiping the disk with gparted (removing all partitions, creating a new empty gpt table, running the installer), but at the very end, I believe it said setting up initramfs, Anaconda threw an error saying something along the lines of “an old EFI entry could not be deleted”.

When rebooting the PC, I now see another error message saying failed to open \EFI\fedora - not found, however, afterwards it still boots into Fedora just fine? If I press ESC to get to the GRUB menu it does show me a Fedora configuration, Ctrl+X will boot it up properly as well.

efibootmgr -v returns the following:

BootCurrent: 0000
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery

lsblk -f -o +PARTUUID returns the following:

NAME FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda                                                                                      
├─sda1
│    vfat   FAT32        7EB7-6AE2                             579,5M     3% /boot/efi   5af766ca-d1a8-454f-8e8c-3323a63780d6
├─sda2
│    ext4   1.0          cf140c7b-64a7-41a8-b7ed-575ed70c65cb    1,4G    18% /boot       0d0138dc-5955-433f-8970-67e21872b116
└─sda3
     btrfs        fedora 07b78042-25fe-4fc2-bfce-3d728c5d3d4f  102,2G     5% /home       58d56314-7f1c-4230-8aba-dbab7ccd29dd
                                                                             /           
sr0                                                                                      
zram0
     swap   1     zram0  2759bbf8-421e-4db6-aca9-52649ad5e0d2                [SWAP]

sudo bootctl status returns the following (without sudo the 6 lines at the top said “no access” instead):

systemd-boot not installed in ESP.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:8: Unknown line 'grub_class', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:8: Unknown line 'grub_class', ignoring.
System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (unsupported)
  TPM2 Support: no
  Measured UKI: no
  Boot into FW: not supported

Current Boot Loader:
       Product: GRUB 2.12
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Enroll SecureBoot keys
               ✗ Retain SHIM protocols
               ✗ Menu can be disabled
               ✗ Multi-Profile UKIs are supported
               ✗ Loader reports network boot URL
               ✗ Support Type #1 uki field
               ✗ Support Type #1 uki-url field
               ✗ Loader reports TPM2 active PCR banks
     Partition: /dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6)
         File: ├─/boot/efi//EFI/BOOT/BOOTIA32.EFI
               ├─/boot/efi//EFI/BOOT/BOOTX64.EFI
               ├─/boot/efi//EFI/BOOT/fbia32.efi
               └─/boot/efi//EFI/BOOT/fbx64.efi

No boot loaders listed in EFI Variables.

Boot Loader Entry Locations:
          ESP: /boot/efi (/dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6)
       config: /boot/efi//loader/loader.conf: Datei oder Verzeichnis nicht gefunden
systemd-boot not installed in ESP.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf:8: Unknown line 'grub_class', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:6: Unknown line 'grub_users', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:7: Unknown line 'grub_arg', ignoring.
/boot/loader/entries/64a2b452a71248fa909e5efe1a58499a-0-rescue.conf:8: Unknown line 'grub_class', ignoring.
System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (unsupported)
  TPM2 Support: no
  Measured UKI: no
  Boot into FW: not supported

Current Boot Loader:
       Product: GRUB 2.12
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Enroll SecureBoot keys
               ✗ Retain SHIM protocols
               ✗ Menu can be disabled
               ✗ Multi-Profile UKIs are supported
               ✗ Loader reports network boot URL
               ✗ Support Type #1 uki field
               ✗ Support Type #1 uki-url field
               ✗ Loader reports TPM2 active PCR banks
     Partition: /dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6)
         File: ├─/boot/efi//EFI/BOOT/BOOTIA32.EFI
               ├─/boot/efi//EFI/BOOT/BOOTX64.EFI
               ├─/boot/efi//EFI/BOOT/fbia32.efi
               └─/boot/efi//EFI/BOOT/fbx64.efi

No boot loaders listed in EFI Variables.

Boot Loader Entry Locations:
          ESP: /boot/efi (/dev/disk/by-partuuid/5af766ca-d1a8-454f-8e8c-3323a63780d6)
       config: /boot/efi//loader/loader.conf: Datei oder Verzeichnis nicht gefunden
     XBOOTLDR: /boot (/dev/disk/by-partuuid/0d0138dc-5955-433f-8970-67e21872b116, $BOOT)
        token: fedora

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Fedora Linux (6.17.1-300.fc43.x86_64) 43 (Workstation Edition)
           id: 64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf
       source: /boot//loader/entries/64a2b452a71248fa909e5efe1a58499a-6.17.1-300.fc43.x86_64.conf (on the Extended Boot Loader Partition)
      version: 6.17.1-300.fc43.x86_64
        linux: /boot//vmlinuz-6.17.1-300.fc43.x86_64
       initrd: /boot//initramfs-6.17.1-300.fc43.x86_64.img $tuned_initrd (Datei oder Verzeichnis nicht gefunden)
      options: root=UUID=07b78042-25fe-4fc2-bfce-3d728c5d3d4f ro rootflags=subvol=root rhgb quiet

WARNING: default boot entry is broken
~ [...]

I have attempted to fix this by manually creating the entry with efibootmgr like some other threads here suggested, which usually ends up booting me in a blackscreen that beeps after I press a couple of keys with zero feedback.

Honestly I am inclined to believe it’s probably related to the hardware/motherboard since this is an old HP Compaq model from 2012:

System:
  Kernel: 6.17.1-300.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: GNOME v: 49.1 tk: GTK v: 3.24.51 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 43 (Workstation Edition)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq 8200 Elite SFF PC
    v: N/A serial: <superuser required> Chassis: type: 6
    serial: <superuser required>
  Mobo: Hewlett-Packard model: 1495 serial: <superuser required>
    part-nu: XL510AV Firmware: UEFI vendor: Hewlett-Packard v: J01 v02.06
    date: 06/09/2011
CPU:
  Info: quad core model: Intel Core i5-2400 bits: 64 type: MCP
    arch: Sandy Bridge rev: 7 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 1715 min/max: 1600/3400 cores: 1: 1715 2: 1715 3: 1715
    4: 1715 bogomips: 24744
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-6 ports:
    active: VGA-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0102
  Display: wayland server: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: gpu: i915 display-ID: 0
  Monitor-1: VGA-1 model: HP Z24i res: 1920x1200 dpi: 94 diag: 611mm (24.1")
  API: OpenGL v: 3.3 vendor: intel mesa v: 25.2.4 glx-v: 1.4 es-v: 3.0
    direct-render: yes renderer: Mesa Intel HD Graphics 2000 (SNB GT1)
    device-ID: 8086:0102 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:1c20
  API: ALSA v: k6.17.1-300.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard
    driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 111.79 GiB used: 5.85 GiB (5.2%)
  ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 109.2 GiB used: 5.49 GiB (5.0%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 1.9 GiB used: 350.3 MiB (18.0%) fs: ext4 dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 109.2 GiB used: 5.49 GiB (5.0%) fs: btrfs dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 7.63 GiB used: 3.1 MiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 31.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.63 GiB used: 3.12 GiB (40.9%)
  Processes: 975 Power: uptime: 52m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
    v: 5.3.0 running-in: ptyxis-agent inxi: 3.3.40

The BIOS/EFI does indeed not have a secure boot option (only QuickBoot, FullBoot, Clear Memory and FullBoot after X days) and the settings in general feel a lot more arcane than they do on my more modern machine in terms of labelling (No information on what “hardware security” is present, though it IS present) so I have NO idea what I should even touch in there.

As I said, ultimately it still boots after the error, but I have no idea why and there is clearly something wrong with this and I would like to iron it out. I am kind of stumped with my limited experience at the moment so if anyone could point me in the right direction I’d be grateful. Excuse me for the occasional German line in the codeblocks.

2

Use https://linux-hardware.org to see if others are using linux on your hardware and if they have a more recent BIOS/UEFI firmware. Check for firmware updates and alternatives such as https://libreboot.org/docs/install/hp8200sff.html.

1 Like
3

Your bios is version

  Mobo: Hewlett-Packard model: 1495 serial: <superuser required>
    part-nu: XL510AV Firmware: UEFI vendor: Hewlett-Packard v: J01 v02.06
    date: 06/09/2011

and the HP site shows version 5.03 dated June 2014 available for that motherboard.
https://support.hp.com/ee-en/drivers/hp-compaq-8200-elite-small-form-factor-pc/5037931

1 Like
4

Thank you very much for the suggestions George and Jeff!

I tried performing the hardware probe but when it uploads the data all I see is this:
Could not run query: Index for table 'probe_info' is corrupt; try to repair it
Searching for the issue online mostly gives me SQL-related issues…

As for the BIOS update, it seems that on Linux I have to build it from files extracted from the .exe

I managed to get to the hpuefi-mod compilation step but now face this issue:

binarybagel@fedora:~/hpuefi/hpuefi-mod-1.0.3$ sudo make
make -C /lib/modules/6.18.16-200.fc43.x86_64/build SUBDIRS= modules
make[1]: Verzeichnis „/usr/src/kernels/6.18.16-200.fc43.x86_64“ wird betreten
  SYNC    include/config/auto.conf
  HOSTLD  scripts/kconfig/conf
*
* Restart config...
*
*
* Scheduler features
*
Enable utilization clamping for RT/FAIR tasks (UCLAMP_TASK) [Y/n/?] y
  Number of supported utilization clamp buckets (UCLAMP_BUCKETS_COUNT) [5] 5
Proxy Execution (SCHED_PROXY_EXEC) [N/y/?] (NEW) y
make[2]: *** Keine Regel vorhanden, um das Ziel „arch/x86/tools/cpufeaturemasks.awk“, benötigt von „arch/x86/include/generated/asm/cpufeaturemasks.h“, zu erstellen.  Schluss.
make[1]: *** [Makefile:248: __sub-make] Fehler 2
make[1]: Verzeichnis „/usr/src/kernels/6.18.16-200.fc43.x86_64“ wird verlassen
make: *** [Makefile:13: default] Fehler 2

I made sure to update all software since yesterday and downloaded everything to make make run, but it seems like I’m still missing something. Did I make a mistake? This is kind of already way beyond anything I have ever done before :sweat_smile:

Or should I just try to read up on Libreboot instead of installing the proprietary one? I just figured it’d be a better idea to stick to what the official hp support provided

5

Not necessarily.
You can create a winpe bootable usb and update the driver from there.

1 Like
6

Hi Jeff, sorry for the late response and thank you very much for the suggestion. As it turned out, I was kind of on a wild goose chase:

Apparently, this was not an actual BIOS, only some Business BIOS Utilities:

This package contains the Replicated Setup and POST Image Flash BIOS support utilities for supported desktop models running a supported operating system. The Replicated Setup utility enables system settings to be ''replicated'' throughout an enterprise. See Repsetup.txt after installing.

The DOS Flash utility can be used to replace the standard HP logo that appears during Power-On Self Test (POST) with a custom image. See DOSFlash.txt after installing.

The HP Utilities for Linux folder contains versions of the Replicated Setup and DOS Flash utilities that are compatible with the Linux Operating System. See README.txt after installing.

So even when I extracted the files, I was unable to find anything that actually upgraded the BIOS. I don’t know why it took so long for me to notice.

I ended up finding the actual BIOS file (ROM Firmware for 8200 Elite and 6200 Pro Business PCs (J01)) when I selected Windows 7 or Windows XP in the OS option menu. With Linux or Windows 8 it would just not be listed for SOME reason.

Anyways, that BIOS version was dated 2019 and had an instruction on how to flash it with a .bin from a regular portable USB stick, directly from the BIOS screen, no special environments or anything needed.

My BIOS is now upgraded to 00.02.33 (May 2019)

Now, this did not magically fix the issue I described before, so I guess my new question now is whether I should reinstall Fedora and see if that fixes it, and if so what the best way to go about it would be? (i.e. wipe partitions first or just run the installer as-is, etc.)

PS: on another note, the PE environment sort of worked at least. Though it ended up being unnecessary in the end.

7

I get that error every time I boot my older computer. Since it doesn’t matter at all to function, I just ignore it. I am on the latest BIOS for my motherboard. My computer hardware is probably 15 years old now and the CPU is a Phenom II X6. It works pretty well frankly.

8

Yeah, fair enough. I just hoped there was an easy fix for it that I was simply unable to figure out with my limited know-how. After spending God knows how much time figuring out the BIOS update though I feel like I should just tank the jank for now.

1 Like