Remove these packages, from chroot, then remove kernel 5.10 with mhwd-kernel, then reinstall it or install kernel 5.15 with mhwd-kernel, exit the chroot and reboot, see if that works.
No, obviously what command did you type in the terminal to end up with this error? You removed it from the terminal output you pasted and I don’t know what you typed.
I don’t believe you typed that, as the error is saying you didn’t use proper target.
Please type the command once more in the terminal, make sure it is correct. From the error message you have you don’t type the right command. Provide full terminal output. Don’t remove tiny bits that would otherwise show your error, it wastes time for everybody, do full copy paste of code, like that, don’t remove the command you type, or anything.
Also I don’t know what’s going on with your other error about the breeze-xcursor package, the path it is referencing is not a file from the package. (//EDIT: probably reinstalling the package would generate this file)
I can reproduce the error only without specifying the kernel version. I tried all “combination” I could think of, and it seems this error message is generated when you type mhwd-kernel -i command like that.
[omano@omano-nvme ~]$ sudo mhwd-kernel
Error: No arguments given (use -h for help).
[omano@omano-nvme ~]$ sudo mhwd-kernel -i linux5
Error: Please make sure if the given kernel(s) exist(s).
available kernels:
* linux419
* linux510
* linux515
* linux517
* linux518
* linux519
* linux54
* linux515-rt
* linux518-rt
Yes but what I’m saying is even without having an existing kernel name/version in the command, if you provide a kernel name/version in the command, this is not the error you should get (see my previous message with my command examples).
Your error I can generate only with the command mhwd-kernel -i, nothing more nothing less (or else I get other error message).
weirdly enough I was finally able to install 5.10 by mhwd-kernel -i linux510 after a grub update and mkinitcpio -P, but disappointingly I still have the same kernel panic error relating to init here: