Hello, I am new to linux for about the last 6 or so months. A friend helped me set up my Manjaro plasma environment with Wayland to accommodate gaming on my nvidia gpu.
My PC was down for the last 3 months due to a fatal manufacturer defect on my gpu that lead to a shitstorm getting the card RMA’d by EVGA.
I launched once successfully into the desktop upon replacing the card and then I began updating, upon requested restart for a package update, my computer now freezes on boot. I can access BIOS and I have spent about three days hunting for answers here and elsewhere before I am now finally making a post.
Any help is appreciated.
Extracted text from a picture of my monitor:
0.0035501 common interrupt: 1.55 No irq handler for vector
0.0035501_common_interrupt: 2.55 No irq handler for vector
0.0035501_common_interrupt: 3.55 No irq handler for vector
0.0035501_common_interrupt: 4.55 No irq handler for vector
0.0035501 _common_interrupt: 5.55 No irq handler for vector
0.0035501_common_interrupt: 6.55 No irq handler for vector
0.0035501_common_interrupt: 7.55 No irq handler for vector
0.0035501_common_interrupt: 8.55 No irq handler for vector
0.0035501 common_interrupt: 9.55 No irq handler for vector
0.0035501 Connon_interrupt: 10.55 No irq handler for vector
I can access recovery menu and was able to successfully get into a timeshift snapshot backup once, I restarted after attempting to figure out which package update caused the issue, and now after restart each of my three snapshots fail to boot.
This is a problem because that kernel is EOL.
You need to install another, supported, one. Boot into that, then remove 6.2.
Then your updates will be less problematic.
I tried booting into runlevel 3 and I am greeted by the same no irq handler error followed by what looks like a bash terminal with an error reading “/sbin/init does not exist Bailing out, you are on your own. Good luck.”
Its possible one of the fallback images may work if you generated those.
Otherwise … running another system (like a live USB) and chrooting in might be your best bet.
Once there you will probably want to execute:
mhwd-kernel -r linux62
If that doesnt work then
sudo pacman -Rns $(pacman -Qsq linux62)
Then go for update:
sudo pacman -Syu
And rebuild images, etc, for good measure:
sudo mkinitcpio -P
sudo update-grub
Of course share any errors … but assuming all is well…
Make sure to boot the USB as Legacy-BIOS or UEFI, depending on which the system was installed as. Ostensibly whichever one you arent currently booted into.
So I got chroot working, ran through these commands, pacman -Syu says everything is uptodate there is nothing to do, and then update grub returns errors for Kernels not found.
No kernels found is definitely a problem.
Was an upgrade interrupted? Or maybe some removal operation was not careful?
I wonder what the end of /var/log/pacman.log might have.
You can check for kernels a few ways…
Listing installed kernels returns no result in the chroot but when I try to mhwd install linux62 it errors for installing same kernel currently running.
6.2 kernel is dead. You cannot use that one.
It was likely the cause of your original problems (using an EOL kernel) …
Please install a currently supported one.
6.4 is latest Stable.
6.1 is latest Long Term Support.
My apologies running install on linux61 throws “You cant reinstall your current kernel” Then it recommends I system update to which pacman says nothing to do
for your problem in the forum ? (Wisdom lies in asking → listening → reading 
)