Updating kernel: vmlinuz in /boot not being created by DNF

Unix & Linux Asked by Big Millz on December 26, 2020

Brand new F23 install, trying to update the kernel. I did lose power during the first round of dnf update and have to go clear out a bunch of conflicts that dnf kept reporting. It’s possible I removed something that’s needed, to be totally honest here.

Anyways, I’ve tried both dnf update and dnf install kernel (after dnf remove kernel). They install the latest kernel to /lib/modules/4.4.9-300.fc23.x86_64/, but no new vmlinuz files end up in /boot, so grub2-mkconfig won’t find it and use it.

Any suggestions as to where I could start troubleshooting this?

4 Answers

ensure /etc/machine-id exist and is valid/not empty

test -s /etc/machine-id

instead "kernel-install" command will not provide kernel below /boot

  • from systemd package
  • called in kernel-core rpm post-install script (rpm -qp --scripts kernel-core-*.rpm)

reinstall kernel-core package then

dnf reinstall kernel-core

Answered by 47VTAQZS on December 26, 2020

dnf reinstall kernel-core

vmlinuz file is provided by kernel-core package so you will need to reinstall it


Answered by Tomot on December 26, 2020

Ended up updating to the F24 beta, as it's being frozen anyways. This fixed the problem, and I'm now running on the 4.7 kernel.

Answered by Big Millz on December 26, 2020

I'd try

dnf reinstall kernel

or (better)

dnf reinstall kernel-4.4.9-300

since it's possible that dnf has status saying that the given set of files is complete.

Answered by Thomas Dickey on December 26, 2020

Add your own answers!

Ask a Question

Get help from others!

© 2024 All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP