MANJARO' is not a valid kernel module directory

Oh, OK. Then I think I’m out of my league…

Do you think it’s safe to reboot?

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 just installed 5:11 and everything went smoothly. No errors where I was previously getting them. Going to reboot.

Good luck!

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?

I think it might, yes. Try updating GRUB:

sudo update-grub

from the terminal.

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.

Output from:
ls -al /etc/mkinitcpio.d/
ls -al /boot/
ls -al /lib/modules/

you can use ``` befor and after your text/output

see this
you should have same kernels installed as file.preset

sudo mhwd-kernel -li
sudo ls /etc/mkinicpio.d/*.preset

suppress any file.preset tha is no more installed
( 5.7 and 5.9 should be removed )

ls -al /etc/mkinitcpio.d/

drwxr-xr-x 1 root root  218 Feb 28 05:11 .
drwxr-xr-x 1 root root 4328 Feb 28 05:15 ..
-rw-r--r-- 1 root root  396 Jan 10  2020 linux419.preset
-rw-r--r-- 1 root root  396 Jan  1 06:32 linux510.preset
-rw-r--r-- 1 root root  396 Feb 15 03:19 linux511.preset
-rw-r--r-- 1 root root  392 Dec 10  2019 linux54.preset
-rw-r--r-- 1 root root  392 Nov  2 16:12 linux57.preset
-rw-r--r-- 1 root root  392 Aug  3  2020 linux58.preset.pacsave
-rw-r--r-- 1 root root  392 Nov  1 10:51 linux59.preset
total 262736
drwxr-xr-x 4 root root     4096 Dec 31  1969 .
drwxr-xr-x 1 root root      272 Feb 28 04:43 ..
-rwxr-xr-x 1 root root    40960 Feb 11 10:27 amd-ucode.img
drwxr-xr-x 5 root root     4096 Feb 28 05:22 grub
-rwxr-xr-x 1 root root 27850182 Feb 28 05:20 initramfs-4.19-x86_64-fallback.img
-rwxr-xr-x 1 root root  8333444 Feb 28 05:20 initramfs-4.19-x86_64.img
-rwxr-xr-x 1 root root 28343688 Feb 28 05:21 initramfs-5.10-x86_64-fallback.img
-rwxr-xr-x 1 root root  7737159 Feb 28 05:20 initramfs-5.10-x86_64.img
-rwxr-xr-x 1 root root 28722943 Feb 28 05:21 initramfs-5.11-x86_64-fallback.img
-rwxr-xr-x 1 root root  7739266 Feb 28 05:21 initramfs-5.11-x86_64.img
-rwxr-xr-x 1 root root 29006562 Feb 28 05:22 initramfs-5.4-x86_64-fallback.img
-rwxr-xr-x 1 root root  8406527 Feb 28 05:21 initramfs-5.4-x86_64.img
-rwxr-xr-x 1 root root 31140842 Nov  9 12:36 initramfs-5.7-x86_64-fallback.img
-rwxr-xr-x 1 root root 10242755 Nov  9 12:36 initramfs-5.7-x86_64.img
-rwxr-xr-x 1 root root 29078382 Dec 22 16:48 initramfs-5.9-x86_64-fallback.img
-rwxr-xr-x 1 root root  7980240 Dec 22 16:48 initramfs-5.9-x86_64.img
-rwxr-xr-x 1 root root       23 Feb 23 09:15 linux419-x86_64.kver
-rwxr-xr-x 1 root root       22 Feb 26 05:37 linux510-x86_64.kver
-rwxr-xr-x 1 root root       21 Feb 26 06:17 linux511-x86_64.kver
-rwxr-xr-x 1 root root       22 Feb 26 05:18 linux54-x86_64.kver
drwxr-xr-x 2 root root     4096 May 20  2020 memtest86+
-rwxr-xr-x 1 root root  5998400 Feb 24 16:04 vmlinuz-4.19-x86_64
-rwxr-xr-x 1 root root  8330944 Feb 26 15:00 vmlinuz-5.10-x86_64
-rwxr-xr-x 1 root root  8699648 Feb 28 05:11 vmlinuz-5.11-x86_64
-rwxr-xr-x 1 root root  6506816 Feb 26 15:00 vmlinuz-5.4-x86_64
-rwxr-xr-x 1 root root  6681472 Nov  2 16:12 vmlinuz-5.7-x86_64
-rwxr-xr-x 1 root root  8141120 Dec 22 16:47 vmlinuz-5.9-x86_64
total 4
drwxr-xr-x 1 root root    342 Feb 28 05:11 .
drwxr-xr-x 1 root root 172258 Feb 28 04:43 ..
drwxr-xr-x 1 root root    478 Feb 24 16:04 4.19.177-1-MANJARO
drwxr-xr-x 1 root root    524 Feb 26 15:00 5.10.19-1-MANJARO
drwxr-xr-x 1 root root    524 Feb 28 05:11 5.11.2-1-MANJARO
drwxr-xr-x 1 root root    524 Feb 26 15:00 5.4.101-1-MANJARO
drwxr-xr-x 1 root root    142 Feb 24 16:03 extramodules-4.19-MANJARO
drwxr-xr-x 1 root root    142 Feb 26 15:00 extramodules-5.10-MANJARO
drwxr-xr-x 1 root root    110 Feb 28 05:11 extramodules-5.11-MANJARO
drwxr-xr-x 1 root root    142 Feb 26 15:00 extramodules-5.4-MANJARO
-rw-r--r-- 1 root root      1 Feb 17 05:50 .old

I hope that’s formatted correctly.

almost right  ;)

use first line ``` 
text 2nd line... 
text
and then lastline ```

Perfect :+1:

now…you see your difference?! ?! 6x, 6x, 4x ?!

Ok, now do you see the problem?

ok, mkinitcpio -P look in directory /etc/mkinitcpio.d/ for preset’s = finds 6x
and look in directory /lib/modules/ for extramodules = finds 4x

= error at generating , see your first post :wink:

(Generated successfully means that the files are placed in /boot/* )

now, update-grub look only directory /boot/* and finds 6x generated successfully files …
4 current issues, 2 outdated issues

hope you understand me so far :coffee: :bulb:

see terminal output after = diff with /etc/mkinitcpio.d/ !?

it seems as if you have dead kernel files lying around ?!
:coffee:

Currently running: 5.11.2-1-MANJARO (linux511)
The following kernels are installed in your system:
   * linux419
   * linux510
   * linux511
   * linux54

rename or remove in Directory /etc/mkinitcpio.d/

-rw-r--r-- 1 root root  392 Nov  2 16:12 linux57.preset
-rw-r--r-- 1 root root  392 Nov  1 10:51 linux59.preset

I removed the extra from /etc/mkinitcpio.d/ and then ran mkinitcpio -P and update-grub and both commands completed correctly.

and you are sure you are right on unstable branch ?!
:partying_face:

Yes, I am on unstable branch.