fail to upgrade dom0 kernel

[coeusite]

Qubes OS version:

R4.0-rc5

Affected component(s):

• dom0 kernel upgrade

Steps to reproduce the behavior:

• sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest
• reboot, and run uname -a

Expected behavior:

• dom0 should run with a kernel 4.15.6-1 (current kernel-latest)

Actual behavior:

• dom0 still uses kernel 4.14.13-2

General notes:

The build is Ryzen 5 2400G + Gigabytes AB350N, which requires kernel 4.15 or above. So I wanna try kernel-latest. This problem also applies to the "kernel" package.

EFI/qubes/ is not recognized by the build, so I followed the EFI troubleshooting, copied EFI/qubes/ to EFI/BOOT/ and modified filenames. However, both "qubes" and "BOOT" have kernel 4.14.13-2 after upgrade.

By the way, the EFI partition (200M) is almost full.

Here is the output of qubes-hcl-report:
Qubes-HCL-Gigabyte_Technology_Co___Ltd_-AB350N_Gaming_WIFI-20180311-223715.yml.log

Here is a log of sudo dnf reinstall kernel-latest with some errors:
kernel-latest.log

Related issues:

[coeusite]

Well, I forgot to say that it was rc4 and upgraded to rc5 by updating softwares from current-testing repo.

Now I’m making a flesh rc5 installation on an Intel-based platform to check whether it will disappear.

[coeusite]

Well, I forgot to say that it was rc4 and upgraded to rc5 by updating softwares from current-testing repo.

Now I’m making a flesh rc5 installation on an Intel-based platform to check whether it will disappear.

[coeusite]

This issue persists if I simply move the disk to an Intel PC.

However, it disappears with a flesh rc5 installation on an Intel PC.

[coeusite]

This issue persists if I simply move the disk to an Intel PC.

However, it disappears with a flesh rc5 installation on an Intel PC.

[coeusite]

I checked my old build (Qubes R3.2 on a Kabylake platform), and found out that this issue also applied to R3.2, i.e. after kernel upgrade, dom0 on the old build still uses kernel 4.9.35 instead of 4.9.56 or any newer kernel.

Maybe copying EFI/qubes to EFI/BOOT raises this problem.

[coeusite]

I checked my old build (Qubes R3.2 on a Kabylake platform), and found out that this issue also applied to R3.2, i.e. after kernel upgrade, dom0 on the old build still uses kernel 4.9.35 instead of 4.9.56 or any newer kernel.

Maybe copying EFI/qubes to EFI/BOOT raises this problem.

[euidzero]

I confirm here with fresh R4.0 on a lenovo laptop. I did also copy EFI/qubes to EFI/BOOT.
What command is responsible for managing EFI/qubes ? I'd like to investigate.

[euidzero]

I confirm here with fresh R4.0 on a lenovo laptop. I did also copy EFI/qubes to EFI/BOOT.
What command is responsible for managing EFI/qubes ? I'd like to investigate.