Re: DNF upgrade not upgrading my kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave Close wrote:
> Comparing your list to mine, I was struck by the size of /boot/efi.
> The size of mine is inflated by one directory of 288M,
> /boot/efi/7cf63543075b47d48d09f1649641c3a1. I don't know what that
> is or why it's there. But the contents look suggestive:
> # ls -lR  /boot/efi/7cf63543075b47d48d09f1649641c3a1
> /boot/efi/7cf63543075b47d48d09f1649641c3a1:
> total 16
> drwxr-xr-x 2 root root 4096 2024-07-20 19:03 0-rescue
> drwxr-xr-x 2 root root 4096 2024-08-13 09:42 6.10.3-200.fc40.x86_64
> drwxr-xr-x 2 root root 4096 2024-08-01 04:04 6.9.12-200.fc40.x86_64
> drwxr-xr-x 2 root root 4096 2024-07-20 19:03 7.00
> /boot/efi/7cf63543075b47d48d09f1649641c3a1/0-rescue:
> total 188184
> -rw------- 1 root root 176793402 2024-07-20 19:03 initrd
> -rwxr-xr-x 1 root root  15898984 2024-07-20 19:02 linux
> /boot/efi/7cf63543075b47d48d09f1649641c3a1/6.10.3-200.fc40.x86_64:
> total 53844
> -rw-r--r-- 1 root root 39122311 2024-08-13 09:42 initrd
> -rw-r--r-- 1 root root 16009576 2024-08-13 09:42 linux
> /boot/efi/7cf63543075b47d48d09f1649641c3a1/6.9.12-200.fc40.x86_64:
> total 52776
> -rw-r--r-- 1 root root 38149613 2024-08-01 04:04 initrd
> -rw-r--r-- 1 root root 15890792 2024-08-01 04:04 linux
> /boot/efi/7cf63543075b47d48d09f1649641c3a1/7.00:
> total 0
> It certainly seems as though the installation of the last two kernels
> got put into the efi directory. How could that happen?

I suspect I know why this happened.

Do you have the "sdubby" or "systemd-boot-unsigned" package installed (which brings in sdubby)?

The sdubby package installs an /etc/kernel/install.conf that tells the kernel-install script that runs in the kernel-core %post to install kernels and initrds in /boot/efi/$MACHINE_ID/.  (Where $MACHINE_ID is from the contents of /etc/machine-id).

This is something that systemd-boot uses, and I'm not sure why it happens, but some dependency seems to pull that package in for some people.

Backing it out simply means you need to uninstall the sdubby package and re-run the kernel-install command, or more simply, reinstall the kernel-core package. Once that's done, it will do the normal GRUB2 boot method of putting files into /boot/ and blscfg entries in /boot/loader/entries/.  

-- 
Jonathan Billings
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux