Fedora 27 x86_64. When DNF installs a new kernel, it isn't going into
the right place (/boot) and is not detected by GRUB. Why not?
For example, after installing the most recent new kernel, I see this.
[root@machine ~]# ls /boot
7725dfc225d14958a625ddaaaea5962b
config-4.14.11-300.fc27.x86_64
efi
extlinux
grub2
initramfs-0-rescue-7725dfc225d14958a625ddaaaea5962b.img
initramfs-4.14.11-300.fc27.x86_64.img
initrd-plymouth.img
loader
lost+found
System.map-4.14.11-300.fc27.x86_64
vmlinuz-0-rescue-7725dfc225d14958a625ddaaaea5962b
vmlinuz-4.14.11-300.fc27.x86_64
[root@machine ~]# ls /boot/7725dfc225d14958a625ddaaaea5962b
0-rescue 4.13.10-200.fc26.x86_64 4.13.9-200.fc26.x86_64
4.11.11-300.fc26.x86_64 4.13.11-200.fc26.x86_64 4.14.11-300.fc27.x86_64
4.12.11-300.fc26.x86_64 4.13.12-200.fc26.x86_64 4.14.4-200.fc26.x86_64
4.12.12-300.fc26.x86_64 4.13.13-200.fc26.x86_64 4.14.5-200.fc26.x86_64
4.12.13-300.fc26.x86_64 4.13.15-100.fc25.x86_64 4.14.6-200.fc26.x86_64
4.12.14-300.fc26.x86_64 4.13.15-200.fc26.x86_64 4.15.8-300.fc27.x86_64
4.12.5-300.fc26.x86_64 4.13.16-200.fc26.x86_64 4.15.9-300.fc27.x86_64
4.12.8-300.fc26.x86_64 4.13.16-202.fc26.x86_64
4.12.9-300.fc26.x86_64 4.13.4-200.fc26.x86_64
But RPM thinks the new kernel was installed correctly!
[root@machine ~]# rpm -V kernel-core-4.15.9-300.fc27
(no output)
--
Dave Close
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
