For those who aren’t familiar with this wank stain, the first time he was in the hospital, he was moved to a special care unit because, in the words of another member of his party, “you wouldn’t want him to be placed in the same room as a gypsy, would you?!” ( source in portuguese).

Then again, the “gypsy” would probably beat the shit out of him as soon as they could, which is fine by me. Chat shit, get banged, and all that.

I use mkinitcpio. You mean regenerating the initramfs? If so, yeah I’ve done that a few times without much success. I suppose reinstalling the bootloader could be an option but I’ve tried using a live ISO from another distro (Ubuntu) and the problem still manifested itself. But it is something to keep in mind, so thanks.

Anyway, so far it seems to be a faulty PCIe slot, so I changed the GPU to another slot and things seem to be working fine. But I’ll wait until tomorrow to do a final edit to my post.

PieFed isn’t letting me edit the OP due to an unexpected error. The errors keep piling up, haha! [EDIT: It’s fixed now!]

Just wanted to thank all of you wonderful people for all the help you’ve given me. I love each and everyone of you (even the ones who skimmed through my post :p). A user on the other thread I created in the Arch Linux community suggested I add the nomedeset parameter, with which I managed to boot into the system. I updated it and installed linux-lts along with linux-lts-headers. Adjusted /boot/loader/entries/arch_linux.conf to switch to the lts kernel by default and rebooted the PC. Unfortunately, didn’t work but I got logs! Here’s the relevant part, I think:

mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0xffffffff  
mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x2000000, error code: 0xffffffff  
mai 03 11:04:23 arch kernel: [drm:resource_construct [amdgpu]] *ERROR* DC: unexpected audio fuse!  
mai 03 11:04:23 arch kernel: [drm] Display Core v3.2.316 initialized on DCE 12.0  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
mai 03 11:04:23 arch kernel: [drm] Timeout wait for RLC serdes 0,0  
mai 03 11:04:23 arch kernel: [drm] kiq ring mec 2 pipe 1 q 0  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110)  
mai 03 11:04:23 arch kernel: [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed  
mai 03 11:04:23 arch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v9_0> failed -110  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu_device_ip_init failed  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init  
mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.  

I did a search and it seems like it’s the GPU’s fault due to the ring errors. I think. I remembered I have an old nvidia GPU laying around so I’m going to try to reseat the current GPU and, if that doesn’t work, try the old one. Not sure if I have to uninstall the amd drivers or if it’s ok to have both the amd and nvidia drivers installed. If that doesn’t work, I’m going to go through all the other suggestions y’all gave me to try and pinpoint the problem.

Again, thank you so much!

Will do it tomorrow, thanks!

I tried adding the kernel parameter mentioned in that thread but it didn’t work. But thank you anyway!

Regarding your edit: no, I haven’t tried that, but I will keep those suggestions in mind, thanks!

Yeah, it might be the dreaded hardware problem, then.

No, I had to use the latest one. Nope, tried the Ubuntu live ISO but it also didn’t work.