Hello,
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Now
-rw-r--r--. 1 root root 155 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-memtest86+.conf -rw-r--r--. 1 root root 466 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-rescue.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64.conf
Thanks.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com ===========================================================================
Am 21.04.2025 um 12:32:52 Uhr schrieb Patrick Dupre via users:
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Check the dnf log (/var/log/dnf). Run sudo dnf update
If a kernel update is being installed, grub-mkconfig will be invoked which creates the grub files to boot the new kernel.
You can do that manually by running update-grub or sudo grub-mkconfig -o /boot/grub/grub.cfg
Am 21.04.2025 um 12:32:52 Uhr schrieb Patrick Dupre via users:
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Check the dnf log (/var/log/dnf). Run sudo dnf update
grub2-common noarch 1:2.12-16.fc40 updates 1.0 M grub2-efi-ia32 x86_64 1:2.12-16.fc40 updates 2.1 M grub2-efi-ia32-cdboot x86_64 1:2.12-16.fc40 updates 2.1 M grub2-efi-x64 x86_64 1:2.12-16.fc40 updates 2.1 M grub2-efi-x64-cdboot x86_64 1:2.12-16.fc40 updates 2.1 M grub2-pc x86_64 1:2.12-16.fc40 updates 14 k grub2-pc-modules noarch 1:2.12-16.fc40 updates 1.1 M grub2-tools x86_64 1:2.12-16.fc40 updates 1.8 M grub2-tools-efi x86_64 1:2.12-16.fc40 updates 545 k grub2-tools-extra x86_64 1:2.12-16.fc40 updates 836 k grub2-tools-minimal x86_64 1:2.12-16.fc40 updates 613 k shim-ia32 x86_64 15.8-3 fedora 413 k shim-x64 x86_64 15.8-3 fedora 467 k
Transaction Summary ================================================================================
2025-04-21T12:17:50+0200 INFO Total download size: 15 M 2025-04-21T12:17:50+0200 INFO Installed size: 56 M 2025-04-21T12:17:54+0200 INFO Downloading Packages: 2025-04-21T12:17:59+0200 INFO -------------------------------------------------------------------------------- 2025-04-21T12:17:59+0200 INFO Total 2.8 MB/s | 15 MB 00:05 2025-04-21T12:17:59+0200 DEBUG Using rpmkeys executable at /usr/bin/rpmkeys to verify signatures 2025-04-21T12:17:59+0200 INFO Running transaction check 2025-04-21T12:18:00+0200 INFO Transaction check succeeded. 2025-04-21T12:18:00+0200 INFO Running transaction test 2025-04-21T12:18:03+0200 INFO Transaction test succeeded. 2025-04-21T12:18:03+0200 DDEBUG timer: transaction test: 2174 ms 2025-04-21T12:18:03+0200 INFO Running transaction 2025-04-21T12:18:03+0200 DDEBUG RPM transaction start. 2025-04-21T12:18:10+0200 DDEBUG RPM transaction over. 2025-04-21T12:18:11+0200 DDEBUG timer: verify transaction: 1188 ms 2025-04-21T12:18:11+0200 DDEBUG timer: transaction: 8541 ms 2025-04-21T12:18:11+0200 DEBUG Completion plugin: Generating completion cache... 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-common-1:2.12-16.fc40.noarch 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-efi-ia32-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-efi-ia32-cdboot-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-efi-x64-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-efi-x64-cdboot-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-pc-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-pc-modules-1:2.12-16.fc40.noarch 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-tools-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-tools-efi-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-tools-extra-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: grub2-tools-minimal-1:2.12-16.fc40.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: shim-ia32-15.8-3.x86_64 2025-04-21T12:18:12+0200 DEBUG Reinstalled: shim-x64-15.8-3.x86_64 2025-04-21T12:18:12+0200 INFO Complete! 2025-04-21T12:18:12+0200 DDEBUG Cleaning up. 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-pc-modules-2.12-16.fc40.noarch.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-efi-ia32-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-tools-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/fedora-6c3a9e5977a00788/packages/shim-x64-15.8-3.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-efi-ia32-cdboot-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-efi-x64-cdboot-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-tools-efi-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-common-2.12-16.fc40.noarch.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-tools-extra-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/fedora-6c3a9e5977a00788/packages/shim-ia32-15.8-3.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-efi-x64-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-pc-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG /var/cache/dnf/updates-02a32a5ce99e20ab/packages/grub2-tools-minimal-2.12-16.fc40.x86_64.rpm removed 2025-04-21T12:18:12+0200 DDEBUG Plugins were unloaded.
If a kernel update is being installed, grub-mkconfig will be invoked which creates the grub files to boot the new kernel.
You can do that manually by running update-grub or sudo grub-mkconfig -o /boot/grub/grub.cfg
This command did not solve the issue.
update-grub no such a command
-- Gruß Marco
Send unsolicited bulk mail to 1745231572muell@cartoonies.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 21 Apr 2025, at 11:33, Patrick Dupre via users users@lists.fedoraproject.org wrote:
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Check you do not have a disk space issue on /boot or /boot/efi.
You might try to remove one recent kernel snd then reinstall from the command line. Do you see any errors?
Do you use any akmods or dkms to build kernel modules? Do they complete without errors?
Barry
On 21 Apr 2025, at 11:33, Patrick Dupre via users users@lists.fedoraproject.org wrote:
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Check you do not have a disk space issue on /boot or /boot/efi.
/dev/mapper/VolSys1-root 72807472 44815152 24248168 65% /
/boot/efi is in under /
You might try to remove one recent kernel snd then reinstall from the command line. Do you see any errors?
Last update did not show error
dnf update Repository vivaldi is listed more than once in the configuration Last metadata expiration check: 2:12:30 ago on Mon 21 Apr 2025 01:09:39 PM CEST. Dependencies resolved. Nothing to do. Complete!
rpm -qa |grep kernel-core kernel-core-6.13.8-100.fc40.x86_64 kernel-core-6.13.9-100.fc40.x86_64 kernel-core-6.13.11-100.fc40.x86_64
grubby --info=ALL index=0 kernel="/boot/vmlinuz-6.13.9-100.fc40.x86_64" args="ro resume=UUID=cc01ef93-ef1c-4a18-9bbb-6339aa8a5e97 rd.lvm.lv=VolSys1/root nouveau.modeset=0 pci=noaer" root="/dev/mapper/VolSys1-root" initrd="/boot/initramfs-6.13.9-100.fc40.x86_64.img" title="Fedora Linux (6.13.9-100.fc40.x86_64) 40 (Workstation Edition)" id="c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64" index=1 kernel="/boot/vmlinuz-6.13.8-100.fc40.x86_64" args="ro resume=UUID=cc01ef93-ef1c-4a18-9bbb-6339aa8a5e97 rd.lvm.lv=VolSys1/root nouveau.modeset=0 pci=noaer" root="/dev/mapper/VolSys1-root" initrd="/boot/initramfs-6.13.8-100.fc40.x86_64.img" title="Fedora Linux (6.13.8-100.fc40.x86_64) 40 (Workstation Edition)" id="c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64" index=2 kernel="/boot/vmlinuz-0-rescue-c60d54440c4d444a9eb5a084a65edf40" args="ro resume=UUID=cc01ef93-ef1c-4a18-9bbb-6339aa8a5e97 rd.lvm.lv=VolSys1/root nouveau.modeset=0 pci=noaer" root="/dev/mapper/VolSys1-root" initrd="/boot/initramfs-0-rescue-c60d54440c4d444a9eb5a084a65edf40.img" title="Fedora Linux (0-rescue-c60d54440c4d444a9eb5a084a65edf40) 36 (Workstation Edition)" id="c60d54440c4d444a9eb5a084a65edf40-0-rescue" index=3 kernel="/boot/memtest86+x64.bin" args="" initrd="/boot" title="Memory test (memtest86+x64.bin)" id="c60d54440c4d444a9eb5a084a65edf40-0-memtest86+"
Do you use any akmods or dkms to build kernel modules?
No that I know
Do they complete without errors?
Barry
On Mon, Apr 21, 2025 at 6:33 AM Patrick Dupre via users users@lists.fedoraproject.org wrote:
Hello,
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Now
-rw-r--r--. 1 root root 155 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-memtest86+.conf -rw-r--r--. 1 root root 466 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-rescue.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64.conf
Forgive my ignorance... Why are you putzing around with Fedora 40 kernels when the latest releases are F41 and F42?
Jeff
On Mon, Apr 21, 2025 at 6:33 AM Patrick Dupre via users users@lists.fedoraproject.org wrote:
Hello,
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Now
-rw-r--r--. 1 root root 155 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-memtest86+.conf -rw-r--r--. 1 root root 466 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-rescue.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64.conf
Forgive my ignorance... Why are you putzing around with Fedora 40 kernels when the latest releases are F41 and F42?
I will move to F42 as soon as F40 will not be updated:wq
On 21 Apr 2025, at 14:53, Patrick Dupre via users users@lists.fedoraproject.org wrote:
I will move to F42 as soon as F40 will not be updated:wq
Note the 6.14 kernel seems to be causing more the the usually new kernel issues at the moment. We are seeing a lot of users with issue over on https://discussion.fedoraproject.org/
You can always check your hardware is working from a live usb image before doing the upgrade to f42, which is what I do to avoid disappointment.
Having said that my desktop (amdgpu) and server systems all upgraded without issue.
Barry
On Mon, 2025-04-21 at 09:34 -0400, Jeffrey Walton wrote:
Forgive my ignorance... Why are you putzing around with Fedora 40 kernels when the latest releases are F41 and F42?
Is it one of those "update your current OS to the lastest bits" before upgrading to the next release issues?
I gave-up upgrades, years ago. It takes ages to calculate the updates, there's always a lot of post-update fix-ups, and it can take weeks to resolve them all (if there are new-release bug-caused problems in that, rather than just your own set-up). I find it far easier to do fresh installs, then import old configurations and data from a second drive. Or simply always have the data on a second drive.
I know some recommend that you should do over-the-top updates, but any new release ought to be able stand on its own, and not rely on you having pre-installed something.
I'm fortunate to not have things like databases which are harder to migrate with simple file copies. The nearest I get to that is the mail server.
On 22 Apr 2025, at 01:46, Tim via users users@lists.fedoraproject.org wrote:
On Mon, 2025-04-21 at 09:34 -0400, Jeffrey Walton wrote:
Forgive my ignorance... Why are you putzing around with Fedora 40 kernels when the latest releases are F41 and F42?
Is it one of those "update your current OS to the lastest bits" before upgrading to the next release issues?
I gave-up upgrades, years ago. It takes ages to calculate the updates, there's always a lot of post-update fix-ups, and it can take weeks to resolve them all (if there are new-release bug-caused problems in that, rather than just your own set-up). I find it far easier to do fresh installs, then import old configurations and data from a second drive. Or simply always have the data on a second drive.
I run a number of Fedora systems a router, file server, IMAP server, subversion server and game on a desktop.
My experience is that there is very little I have needed to do on an upgrade. From f41 to f42 no changes at all for me.
I know some recommend that you should do over-the-top updates, but any new release ought to be able stand on its own, and not rely on you having pre-installed something.
Why put yourself to the work of applying the config changes on a new install? I *can* fresh install if needed and have all my config changes in source control.
I'm fortunate to not have things like databases which are harder to migrate with simple file copies. The nearest I get to that is the mail server.
Barry
--
uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Tim:
I know some recommend that you should do over-the-top updates, but any new release ought to be able stand on its own, and not rely on you having pre-installed something.
Barry Scott:
Why put yourself to the work of applying the config changes on a new install? I *can* fresh install if needed and have all my config changes in source control.
Because of the massive amount of timewasting involved in the pre- install, install, then all the clean-up and debugging afterwards.
On Mon, Apr 21, 2025 at 6:33 AM Patrick Dupre via users users@lists.fedoraproject.org wrote:
Hello,
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Now
-rw-r--r--. 1 root root 155 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-memtest86+.conf -rw-r--r--. 1 root root 466 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-rescue.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64.conf
Well, perhaps you can reinstall the kernel you want to boot.
On Fedora 42, here is what I have:
$ dnf list installed kernel* Updating and loading repositories: Repositories loaded. Installed packages kernel.x86_64 6.13.11-200.fc41 updates kernel.x86_64 6.14.2-300.fc42 updates kernel-core.x86_64 6.13.11-200.fc41 updates kernel-core.x86_64 6.14.2-300.fc42 updates kernel-devel.x86_64 6.13.11-200.fc41 updates kernel-devel.x86_64 6.14.2-300.fc42 updates kernel-devel-matched.x86_64 6.14.2-300.fc42 updates kernel-headers.x86_64 6.14.0-63.fc42 fedora kernel-modules.x86_64 6.13.11-200.fc41 updates kernel-modules.x86_64 6.14.2-300.fc42 updates kernel-modules-core.x86_64 6.13.11-200.fc41 updates kernel-modules-core.x86_64 6.14.2-300.fc42 updates kernel-modules-extra.x86_64 6.13.11-200.fc41 updates kernel-modules-extra.x86_64 6.14.2-300.fc42 updates kernel-srpm-macros.noarch 1.0-25.fc42 fedora kernel-tools.x86_64 6.14.2-300.fc42 updates kernel-tools-libs.x86_64 6.14.2-300.fc42 updates
So a `dnf reinstall` of kernel, kernel-core, kernel-modules, kernel-modules-core, and kernel-modules-extra should reinstall the latest kernel.
Be sure to include kernel-modules-extra. That's where drivers like for your nic adapter are probably located.
Jeff
OK, it solved the issue
Subject: Re: grub2
On Mon, Apr 21, 2025 at 6:33 AM Patrick Dupre via users users@lists.fedoraproject.org wrote:
Hello,
I do not understand, on my laptop, the 2 last releases of the kernel have not been done properly, and I cannot boot on them. How can I populate /boot/loader/entries properly?
Now
-rw-r--r--. 1 root root 155 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-memtest86+.conf -rw-r--r--. 1 root root 466 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-0-rescue.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.8-100.fc40.x86_64.conf -rw-r--r--. 1 root root 391 Apr 21 12:21 c60d54440c4d444a9eb5a084a65edf40-6.13.9-100.fc40.x86_64.conf
Well, perhaps you can reinstall the kernel you want to boot.
On Fedora 42, here is what I have:
$ dnf list installed kernel\* Updating and loading repositories: Repositories loaded. Installed packages kernel.x86_64 6.13.11-200.fc41 updates kernel.x86_64 6.14.2-300.fc42 updates kernel-core.x86_64 6.13.11-200.fc41 updates kernel-core.x86_64 6.14.2-300.fc42 updates kernel-devel.x86_64 6.13.11-200.fc41 updates kernel-devel.x86_64 6.14.2-300.fc42 updates kernel-devel-matched.x86_64 6.14.2-300.fc42 updates kernel-headers.x86_64 6.14.0-63.fc42 fedora kernel-modules.x86_64 6.13.11-200.fc41 updates kernel-modules.x86_64 6.14.2-300.fc42 updates kernel-modules-core.x86_64 6.13.11-200.fc41 updates kernel-modules-core.x86_64 6.14.2-300.fc42 updates kernel-modules-extra.x86_64 6.13.11-200.fc41 updates kernel-modules-extra.x86_64 6.14.2-300.fc42 updates kernel-srpm-macros.noarch 1.0-25.fc42 fedora kernel-tools.x86_64 6.14.2-300.fc42 updates kernel-tools-libs.x86_64 6.14.2-300.fc42 updatesSo a `dnf reinstall` of kernel, kernel-core, kernel-modules, kernel-modules-core, and kernel-modules-extra should reinstall the latest kernel.
Be sure to include kernel-modules-extra. That's where drivers like for your nic adapter are probably located.
Jeff
-
Barry -
Barry Scott
-
Jeffrey Walton -
Marco Moock -
Patrick Dupre -
Tim