Fwupdmgr looking for EFI/kalpa-desktop when only EFI/kalpa exists

English Install/Boot/Login
1

First time using Kalpa.

I tried to update the firmware and got this problem.

gg@p14s:~> sudo fwupdmgr update --verbose

[removed previous information]

Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷▏Fwupd-INFO: 09:04:58.416: download progress: 99.8%
Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷▏Fwupd-INFO: 09:04:58.417: download progress: 99.9%
Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷▏Fwupd-INFO: 09:04:58.419: download progress: 99.9%
Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷▏Fwupd-INFO: 09:04:58.421: download progress: 100.0%
Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷▏Fwupd-INFO: 09:04:58.422: download progress: 100.0%
Fwupd-INFO: 09:04:58.422: status-code was 200
Downloading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:58.535: emitting ::status-changed() [decompressing]
Decompressing… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.134: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.134: emitting ::status-changed() [waiting-for-auth]
Authenticating… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [device-busy]
Waiting… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [device-write]
Writing… ▕⣤ ▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [decompressing]
Decompressing… ▕⣤ ▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [device-restart]
Restarting device… ▕⣤ ▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [device-write]
Writing… ▕⣤ ▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.181: emitting ::status-changed() [scheduling]
Scheduling… ▕⣤ ▏(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.225: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.225: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.225: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.231: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.231: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.236: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.242: emitting ::device-changed(08a40a69b9e3927c0772b9b995ac8da6c14edd62)
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.242: emitting ::status-changed() [idle]
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.249: no per-user credentials in /root/.config/fwupd/remotes.d/lvfs-embargo.conf
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.249: no per-user credentials in /root/.config/fwupd/remotes.d/lvfs-testing.conf
(fwupdmgr:9682): Fwupd-DEBUG: 09:04:59.249: no per-user credentials in /root/.config/fwupd/remotes.d/lvfs.conf

failed to write-firmware: cannot find either EFI/systemd or EFI/kalpa-desktop in ESP

gg@p14s:~> sudo fwupdtool esp-list
Loading… ▕⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣦▏
Selected volume: /org/freedesktop/UDisks2/block_devices/nvme0n1p1
/boot/efi/EFI/boot/bootx64.efi
/boot/efi/EFI/boot/fallback.efi
/boot/efi/EFI/boot/MokManager.efi
/boot/efi/EFI/kalpa/MokManager.efi
/boot/efi/EFI/kalpa/grub.efi
/boot/efi/EFI/kalpa/shim.efi
/boot/efi/EFI/kalpa/boot.csv
/boot/efi/EFI/kalpa/grubx64.efi
/boot/efi/EFI/kalpa/grub.cfg
gg@p14s:~>

2

Hi, welcome

Could you try Discover, from the desktop? It is preconfigured. I think this is due to Kalpa’s nature of being iimmutable, or selinux

3

Hi,
Discover only shows the Lenovo update when the laptop is plugged in, i don’t know if that’s a bug or feature… When plugged in, Discover has the same problem, and it says there was an issue with the update.

“failed to write-firmware: cannot find either EFI/systemd or EFI/kalpa-desktop in ESP”

I used the cli to update, so I could get more information, and it seems fwupdmgr is looking for “EFI/kalpa-desktop” but only “EFI/kalpa” exists. I have never used Aeon, so I don’t know if it has the same issue.

The only other issue I am having with Kalpa is the touchpad goes weird after a long time of use. The cursor starts jumping about. I didn’t have this touchpad problem when using Debian, but i have recently replaced the touchpad, so not sure if its a hardware fault, or a Kalpa or Wayland issue.

Thanks

4

There were different bugreports for fwupdmgr. It always looks for a different distributor/distribution string in the efi directory. It was fixed several times. But the naming of the string differs between distributions and flavors…and changes. So maybe have a look if it was already reported upstream.

5

I did this:

sudo mkdir -p /boot/efi/EFI/kalpa-desktop
sudo cp -a /boot/efi/EFI/kalpa/. /boot/efi/EFI/kalpa-desktop/

And the firmware was installed.

But this is obviously as bug.

1 Like
6

Good move.

I did something similar here. I noticed that fwupd was looking for “EFI/opensuse/shim.efi” and could not find it, even though it existed. It happened that I had installed a second hard drive, which also had an EFI partition, and fwupd was looking there instead of at the EFI partition I was booting from. So I copied the “EFI/opensuse” directory to that second EFI partition. And then it all worked. I just have to remember that when “shim” updates, I have to copy over that updated “shim”.