I ran an update this morning and this is what it updated: btrfs-progs-5.10.1-2 enchant-2.2.15-1 libdatrie-0.2.13-1 nano-5.6-1 python-pyqt5-5.15.3-2 python-sip4-4.19.25-1 snapd-2.49-2
yay-10.1.2-3
When it finished it rebuilt the kernels I have installed and then gave me this.
Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: ‘default’
→ -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> ERROR: ‘/lib/modules/5.7.19-2-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: ‘fallback’
→ -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> ERROR: ‘/lib/modules/5.7.19-2-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: ‘default’
→ -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
==> ERROR: ‘/lib/modules/5.9.16-1-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: ‘fallback’
→ -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
==> ERROR: ‘/lib/modules/5.9.16-1-MANJARO’ is not a valid kernel module directory
I had the problem once before where kernel headers went missing somehow and I couldn’t boot. I fixed it with: sudo mkinitcpio -P but this time it spat out the same error. I don’t want to reboot until I know what’s going on and if it’s safe to do so.
It might be, it’s not going to harm you, and you can always enter the chroot environment from a live USB, if all else fails. So I guess you can give it a go…Just make sure there is a working kernel as well…
I safely rebooted. When I went into grub to select the new kernel it is still showing 5.9 in the grub menu even though my list of installed kernels doesn’t show it as installed. Could this be the problem?
Strange, the grub update shows there is an image for 5.9
sudo update-grub
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.11-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.11-x86_64.img
Found initrd fallback image: /boot/initramfs-5.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
And running sudo mkinitcpio -P still gives me the previous errors.