Okay. Do the following. Run command (from your USB installer):-
sudo mount /dev/nvme0n1p2 /mnt
then,
ls /mnt/boot
Can you produce output of the ls command? Also check the output for
ls /mnt/usr/lib/modules
Do you see your kernel version listed in there? It should be of the form 6.1.xx-yy-MANJARO. Can you give us the full version, ie, including whatever xx and yy are showing?
Concerning your partitions, I’m not sure what type of disk sdb is. It appears to be a multimedia card, but it’s formatted as an MBR drive, as opposed to your Nvme disk being foematted as GPT. Strictly speaking with UEFI mode it’s best practice to have multi-disks all configured as GPT, altthough your particular boot issue is unaffected as the error message indicates you successfully got as far as grub stage. I’m also confused by disk sda. I thought it might be your USB installer, but partition shows that doesn’t appear to be the case.
Strange, because ls commands show your latest kernel is definitely present, as are its modules. However I see the initramfs image for the previous kernel515 is missing (unless I’m missing something), although that won’t affect your booting to current kernel. So need to investigate further.
Boot to USB installer. Then as previoualy, run:-
sudo mount /dev/nvme0n1p2 /mnt
Then run:-
grep -i -A13 "menuentry 'Manjaro " /mnt/boot/grub/grub.cfg | head -14
Post up that output. Rather than do it by a photo, just paste output here, then highlight the whole output and hit the " blockquote button, above.
What forum members expect is that you report back with the results of having tried a suggestion, to know whether or not a suggestion was successful. And, please, try to make it more detail than simply saying something like it doesn’t work.
We’re happy to help where we can, but without sufficient feedback from you, it’s next to impossible. This is why some members might become quite irate about your lack of useful responses (and rightfully so).
Afterall, we’re only trying to help.
Well, most of us, anyway. Some are just grumpy by nature.
I usually press the “tracking” button and change it to “normal” or sometimes even “muted” so I don’t have to be bothered with it any more.
I’m all for helping people, but if the receiver does not return with enough respect to even keep me updated, I walk away.
It’s good that you take these things up in threads that are not going “very well”.
Depending on the response after such a message is when I might leave or get further involved if I haven’t already done so.
Almost correct.
Do you understand what those commands do?
Let me give you a short lesson, let me just put on my professor glasses.
sudo su - means you switch to the root user. ALWAYS be careful when doing operations after this, YOU ARE ROOT!!!
Since you are now root, DO NOT USE SUDO! sudo = super user do, NOT = root (just keep this in mind, usually no problems but CAN be a problem) but all interactions will kinda be like done by root. So if you are root, do not use sudo.
manjaro-chroot -a = the -a tag instructs the script manjaro-chroot to mount the partitions that is needed for you to enter chroot, ie you change to the system you have installed even though you booted with a usb stick.
Should be without sudo
Instead of rebooting from inside the chroot (and again, do not use sudo if you are root) but rather type exit first to exit chroot env THEN reboot. In this case you would still be root so you can just type reboot now or type exit one more time to go back to the “normal” user and THEN sudo reboot now.
A little example of how root and sudo is not the same.
Do this as your user:
cd
pwd
sudo su
cd
pwd
exit
cd
sudo cd
pwd shows what directory you are currently in the shell. cd brings you to your home directory, as your user it would be /home/username.
For root home is /root.
So if you type sudo cd it should bring you to /root just like it did while in sudo su right?