And that kernel has also already been EOL for a while.
The above tells me that you have not been keeping your system up to date, and/or that you’ve created a mess out of it, but given that you’re not giving us any details, there’s nothing more I can say, other than the quick & dirty advice of reinstalling.
Manjaro is a rolling-release distribution, which means that it must be kept up to date, and that it also requires maintenance — such as merging .pacnew files. As such, you should also read the first two posts of every Stable Updates announcement thread, because they contain important information.
What more details would you like? My system is updated regularly , if nor daily, at least weekly. I upgraded to 6.2 within the last week and that was from 6.x, not 5.x. I am as puzzled as you as to why it is referring to 5.19 and I am also puzzled why I was offered 6.2 when I now see that that is not a supported kernel.
What commends can I run that will provide helpful information?
Please forgive my ignorance, but how do I get network access in the chroot environment? I do have network access in the live cd booted environment that I am chrooting from but the pacman command is failing because of no network.
Thank you so much. I was able to edit the grub configuration so that the menu appeared and then was able to select 5.15 and boot just fine. I have manually removed all the 6.2 files and now have 6.5, 6.4, 6.1 and 5.15 installed with 6.4 booting just fine. I am still puzzled as to why I was offered 6.2 to install, and why there were some other old kernel related files still on the system. However, I am eternally grateful to the support offered in this forum and the fact that I am up and running again.
In my humble opinion…
1st the system was looking to boot with linux 5.19 for some reason… and it couldn’t find it so…
2nd It tried to look for WARNING: Preset file ‘/etc/mkinitcpio.d/linux61.preset’, but that’s missing, meaning no initramfs-6.1-x86_64-fallback.img, initramfs-6.1-x86_64.img, so…
3rd It tried to boot with kernel 6.2 but it was missing ===>ERROR: ‘/lib/modules/6.2.16-2-MANJARO’ is not a valid kernel module directory, because the kernel is not in the repos anymore, hence on upadate it couldn’t create the folder in the error above…
You mast have installed the k. 6.2 long before it was EOL, but as to why the system was looking for k. 5.19 I dont know…
Another thing, please stay on one LTS and one current kernel.
Why do you need so much kernels anyway ??
I believe kernel 6.4 will go EOL soon, so you might run into the same trouble again…