"EFI Stub: error: unable to allocate memory for event log" On HP

Hello,

I am very new to using Linux, but I want to become more knowledgeable because I don’t like Windows’ politics. I came here from Lunduke’s podcasts.

I have an old HP Pavillion Notebook Laptop that I am trying to get OM to install and work on. The specs of the laptop are as follows:

  • 4 x AMD A8-7410 APU with AMD Raedon R5 Graphics
  • 6.7 GiB of RAM
  • AMD Raedon R5 Graphics

I am trying to install and run the following version of OM (this is what it tells me when I load the live image):

  • “You are using Open Mandriva Lx 24.12 (ROME) Rolling with Kernel 6.12.1 desktop”

I flashed a thumb drive with that ISO of OM about two weeks ago using Balena Etcher. I have flashed it onto a different laptop, but I am not playing with that one because the battery won’t charge. I have been playing with the laptop (specs above) because it was an old one my mom had but didn’t use anymore. I think she bought it around 2014 or so.

I was able to start the live image and install what I thought was just fine. I did notice that there was an error, “EFI Stub: error: unable to allocate memory for event log”. I didn’t know what this meant, and I was able to keep installing and using, so I just moved forward. I tinkered around on the laptop every other day or so for a few minutes and it ran just fine. I could surf the web and use a few applications. Today, however, I installed some updates which required me to restart. Once I restarted, It would not boot up properly.

What that looks like now is as follows:

  • I turn the laptop off
  • I turn the laptop on. About 3-5 seconds after hitting power on, it shows the OM screen asking for how I want to boot. I either let it time out for regular boot, or press enter to regular boot. I don’t really know what I’m doing to pick any of the other options.
  • It then says what linux kernel version I’m running (6.12) then, a few seconds later, displays that error again, “EFI Stub: error: unable to allocate memory for event log”.
  • It then either goes to a blank screen, or sometimes to a blank screen with a vertical blinking pipe.
  • This is the same process even if I repeat turning the laptop off and on.

I just put the flash drive in again to load the live image. When I did that, I get that same error again even with the live image.

Is there something wrong with the flash? Is there something bad about the laptop? I don’t recall this being an issue with the first laptop I tried, but I really don’t remember.

I appreciate your help! I am happy to provide more details if needed.
-Garrett

if you can boot with the iso usb openmandriva ,
can you open kconsole and provide

inxi -Fza
sudo parted -l 

Here you go:

System:
  Kernel: 6.12.1-desktop-1omv2490 arch: x86_64 bits: 64 compiler: clang
    v: 19.1.4 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz0
    root=live:UUID=2024-12-06-08-34-26-00 rootfstype=auto ro rd.luks=0
    rd.lvm=0 rd.md=0 rd.dm=0 rd.live.image audit=0 logo.nologo
    scsi_mod.use_blk_mq=1 dm_mod.use_blk_mq=1 rd.loglevel=0
    rd.systemd.show_status=false rd.udev.log-priority=0
    systemd.show_status=auto loglevel=2 udev.log-priority=0 i915.fastboot=1
    locale.LANG=en_US.UTF-8 vconsole.keymap=us
    vconsole.font=latarcyrheb-sun16 vt.global_cursor_default=0 quiet rhgb
    splash=silent
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_x11 vt: 1 dm: SDDM Distro: OpenMandriva Lx 24.12 ROME
Machine:
  Type: Laptop System: HP product: HP Pavilion Notebook v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 80B2 v: 82.28 serial: <superuser required>
    part-nu: K8Y43AV uuid: <superuser required> UEFI: American Megatrends
    v: F.13 date: 08/06/2015
Battery:
  ID-1: BAT0 charge: 17.5 Wh (53.5%) condition: 32.7/32.7 Wh (100.0%)
    power: 20.3 W volts: 16.5 min: 14.8 model: Hewlett-Packard Primary
    type: Li-ion serial: N/A status: charging cycles: 294
CPU:
  Info: model: AMD A8-7410 APU with AMD Radeon R5 Graphics bits: 64 type: MCP
    arch: Puma level: v2 built: 2014-15 process: GF 28nm family: 0x16 (22)
    model-id: 0x30 (48) stepping: 1 microcode: 0x7030105
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1000 min/max: 1000/2200 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1000 2: 1000 3: 1000
    4: 1000 bogomips: 17567
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
    vendor: Hewlett-Packard driver: amdgpu v: kernel alternate: radeon
    arch: GCN-2 code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9851
    class-ID: 0300
  Device-2: Chicony HP Truevision HD driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 2-1.2:3 chip-ID: 04f2:b50d
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.org v: 1.21.1.14 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x45ec built: 2013
    res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6")
    diag: 394mm (15.5") ratio: 16:9 modes: max: 1366x768 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.0 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon R5 Graphics (radeonsi kabini LLVM
    19.1.4 DRM 3.59 6.12.1-desktop-1omv2490) device-ID: 1002:9851
    memory: 1000 MiB unified: no
  API: Vulkan v: 1.3.302 layers: 2 device: 0 type: integrated-gpu name: AMD
    Radeon R5 Graphics (RADV KABINI) driver: N/A device-ID: 1002:9851
    surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.4 256
    bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:01.1
    chip-ID: 1002:9840 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1022:780d
    class-ID: 0403
  API: ALSA v: k6.12.1-desktop-1omv2490 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: off 3: wireplumber
    status: active tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8188EE Wireless Network Adapter vendor: Hewlett-Packard
    driver: rtl8188ee v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8179 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Drives:
  Local Storage: total: 727.56 GiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: ST750LM022 HN-M750MBB
    size: 698.64 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5400 serial: <filter> fw-rev: 0001 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 model: General USB Flash Disk size: 28.92 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
    lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 3.36 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.1 C mobo: N/A gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 6.72 GiB used: 2.37 GiB (35.3%)
  Processes: 215 Power: uptime: 28m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.63 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 target: graphical (5)
    default: graphical tool: systemctl
  Packages: pm: rpm pkgs: N/A note: see --rpm tools: dnf pm: flatpak pkgs: 0
    Compilers: N/A Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.36
Model: ATA ST750LM022 HN-M7 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      2097kB  317MB  315MB  fat32        EFI   boot, esp
 2      317MB   750GB  750GB  ext4         root


Model: General USB Flash Disk (scsi)
Disk /dev/sdb: 31.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      512B    3211MB  3211MB  primary               boot
 2      3211MB  3218MB  6740kB  primary  fat16        esp


Model: Unknown (unknown)
Disk /dev/zram0: 3608MB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system     Flags
 1      0.00B  3608MB  3608MB  linux-swap(v1)

@GarrettJ37 first try this, see if you can boot in to Console Mode in the installed system.

You want the option that has (console mode) at the end of the line. See if that boots. If it does you will see prompt to login. Type your user name and password and press enter to login.

  1. If that all works we will first try installing a newer kernel, to do that type sudo dnf up kernel-desktop, you will be asked for root or administrator password. Enter that and press enter to upgrade your kernel. When the kernel upgrade is complete type reboot and press enter to reboot. Let’s hope this works.

Explanation: sudo gives user administrator or root privileges for tasks that require admin privileges, dnf is the package manager OMLx uses, up is an abbreviation for upgrade and kernel-desktop tells dnf to upgrade to the most recent kernel-desktop for ROME. The kernel install will take a little bit of time.

I have another possibility that may work if that does not. Also we can ask OM developers for a solution if we need to.

If the new kernel does not work we can try one of the solutions listed here.

Edit: We can also try doing a full system upgrade from Console Mode.

Alrighty, here goes:

  • I restarted the computer while in live mode so that it would boot into the regular install
  • Once at the main page, I selected the advanced options line item
  • I selected to boot into Console
  • It did then present my Linux Kernel version, the popped up the error on top of that 1-3 seconds later
  • After about 10 seconds, it prompted me to log in. I entered my username and PW.
  • I entered the command you suggested, then entered my PW.
  • It only took about 10 seconds before it told me “Nothing to do. Complete!” then is now waiting for more of my input.
  • I entered “reboot” then pressed enter.
  • I tried to run the regular OM startup, with the same results that I described before. This time it is just a blank screen, no blinky pipe.

I left something our of the command, should have been sudo dnf --refresh up kernel-desktop.

Edit: You will see what --refresh does when you run that command. It refreshes the repository metadata so you get the latest packages.

I retried it with this command. It did about the same thing as it did last time. It only took a few seconds to roll through checking for updates. It ended with the same result. When I tried to load the normal OM launcher, it is now on a blank screen with a blinky horizontal line. I apologize, I think I should have said it was a blinky horizontal line before.

Is the real time clock battery on the motherboard still working? When you power up and go to the bios, is the time correct?

The time in the BIOS is incorrect. It has the date correct, but the time is five hours ahead of what it should be. Should I change it?

1 Like

Yes, that was a great suggestion by @WilsonPhillips.

Edit: @GarrettJ37 if you get your system to boot properly first thing to do is open Konsole (terminal) and upgrade it with the following:

sudo dnf --refresh --allowerasing dsync

OR open OM-Welcome and use this:

And we can go from there, I need to go out while it is daylight. Back in a bit.

Many things require the time to be correct. Repositories are one.

Also, EFI Stub makes me think that if the battery is run down, each time it comes back up default, the TPM is on. I don’t know if it has one, but check to see and turn it off if it exists.

I changed the time in the BIOS, by saving and exiting. I then asked it to boot OM as normal, and it did present that same error message. It is now on a blank screen with a horizontal blinky line. I should note that it is consistently displaying the OM background screen in between showing the error message in the corner and going to the blank screens.

I confirmed several times that the BIOS time is my local time now by restarting the computer.

TPM is trusted platform module, correct? How do I check if it has one/turn it off? Is that just done my searching of this model of laptop on the internet?

One last thing from me. I don’t want to be annoying. If it has secure boot, make sure that is off.

Yes, Trusted Platform Module. I have no idea where to look in your bios

Certainly not annoying me! I just want the thing to work.

I can confirm secure boot is off. I just checked, but I think I also had to do that to switch to Linux from Windows.

I also found the TPM and turned it from “Enable” to “Disable”.

It is still presenting that error message. It then went to a blank screen.

I restarted then checked the BIOS again. TPM was still disabled, but the time had reverted back to 5hrs ahead. I changed it to my local time and booted again. Same result as before.

After a couple more reboots, the time is proper and TPM is disabled. Same results.

1 Like

I don’t have that much stuff in this install of OM, so I am fine with trying to reinstall a fresh version.

The OS is getting the time and setting it after you login. That is fine.

You may have to install fresh to get rid of the EFI Stub error.

I will try that, but I notice that when I press F9, tell it to boot from USB, then select the option to boot the live image, it then gives the same error there as well.

1 Like