On 12/1/23 9:30 PM, Samuel Sieb wrote:
On 12/1/23 20:23, home user wrote:
On 12/1/23 8:38 PM, Samuel Sieb wrote:
Remove the files for the entry that doesn't have a kernel package.
Here's what I did:
-----
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.3[entries]: rm 70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
rm: remove regular file '70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf'? y
-bash.4[entries]: rm 70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
rm: remove regular file '70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf'? y
-bash.5[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.6[entries]:
-----
That's what you meant, right?
Partly. You also need to remove the corresponding files from /boot if they're there.
In /boot/, the symvers-*.fc38.x86_64.xz were links to /lib/modules/*.fc38.x86_64/symvers.xz
I deleted the links, but not what they "point" to.
The other 8 files were deleted.
I notice that /lib/modules/ looks huge. I'm wondering if that needs a serious cleaning. But I'll come back to that in a new thread after some other f38 issues are dealt with.
Here we go...
-----
-bash.25[~]: rpm -qa kernel-core
kernel-core-6.5.5-200.fc38.x86_64
kernel-core-6.5.12-200.fc38.x86_64
kernel-core-6.6.2-101.fc38.x86_64
-bash.26[~]: ls /boot/loader/entries/
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.27[~]: ls /boot/
config-6.5.12-200.fc38.x86_64
config-6.6.2-101.fc38.x86_64
efi
grub2
initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img
initramfs-6.5.12-200.fc38.x86_64.img
initramfs-6.6.2-101.fc38.x86_64.img
loader
lost+found
memtest86+x64.bin
symvers-6.5.12-200.fc38.x86_64.xz
symvers-6.6.2-101.fc38.x86_64.xz
System.map-6.5.12-200.fc38.x86_64
System.map-6.6.2-101.fc38.x86_64
vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
vmlinuz-6.5.12-200.fc38.x86_64
vmlinuz-6.6.2-101.fc38.x86_64
-bash.28[~]:
-----
The grub menu now includes kernel entries for 6.5.12 and 6.6.2 only (plus rescue, memory test, and windows).
Progress!
Yes, but I would recommend installing it again.
So how do I install the "meta package" "kernel" only for 6.6.2-101.fc38.x86_64?
It's not in the repo anymore, so you would have to get it from koji. But see if your next upgrade brings in all the packages. It should, since you still have other kernel packages installed.
ok, I'll punt this. I gather that the fix happens only when the kernel itself gets patched, and weekly patches that don't patch the kernel won't restore "kernel".
I'll turn my focus to the extra memory test in the grub menu tomorrow.
--
--
_______________________________________________
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
