You are not logged in.

#1 2023-10-09 12:43:10

realGulagboi
Member
Registered: 2023-10-09
Posts: 5

Arch stuck on boot after changing Mainboard and GPU

when I boot the system the normal list of things come where it starts its services, however on the line:"[  OK  ] Started Accounts Service" the system stops and the only input it seems to accept is ctrl+alt+delete to reset the system.
is there any way to save this or is this system bricked?
here is an image link incase it helps.
sorry for my bad english in advance.

https://cdn.discordapp.com/attachments/ … 8d4deeb3e&

regards
Martin

Offline

#2 2023-10-09 12:49:50

loqs
Member
Registered: 2014-03-06
Posts: 18,859

Re: Arch stuck on boot after changing Mainboard and GPU

Have you tried switching to another TTY with Ctrl+Alt+F2?  If that fails try booting into multi-user.target if that fails try rescue.target.  If that still fails chroot in from the live media.  Then please post the full system journal for a boot with the issue probably to a pastebin.

Offline

#3 2023-10-09 12:54:09

realGulagboi
Member
Registered: 2023-10-09
Posts: 5

Re: Arch stuck on boot after changing Mainboard and GPU

i managed to log into the root account on another tty currently working on getting a file with the log of the newest boot using journalctl -b

Last edited by realGulagboi (2023-10-09 12:57:56)

Offline

#4 2023-10-09 13:16:28

realGulagboi
Member
Registered: 2023-10-09
Posts: 5

Re: Arch stuck on boot after changing Mainboard and GPU

UPDATE:
Here is the pastebin of the last boot journal using "journalctl -b": https://pastebin.com/z66kpbGL

Last edited by realGulagboi (2023-10-09 13:18:22)

Offline

#5 2023-10-09 13:22:07

loqs
Member
Registered: 2014-03-06
Posts: 18,859

Re: Arch stuck on boot after changing Mainboard and GPU

Is linux-firmware installed?

Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: amdgpu: Fetched VBIOS from VFCT
Oct 09 14:52:47 arch kernel: amdgpu: ATOM BIOS: 113-D7120200-O02
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: Direct firmware load for amdgpu/psp_13_0_10_sos.bin failed with error -2
Oct 09 14:52:47 arch kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <psp> failed -19
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: Direct firmware load for amdgpu/smu_13_0_10.bin failed with error -2
Oct 09 14:52:47 arch kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <smu> failed -19
....
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: Direct firmware load for amdgpu/gc_11_0_3_pfp.bin failed with error -2
Oct 09 14:52:47 arch kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <gfx_v11_0> failed -19
Oct 09 14:52:47 arch kernel: [drm] VCN(0) encode/decode are enabled in VM mode
Oct 09 14:52:47 arch kernel: [drm] VCN(1) encode/decode are enabled in VM mode
....
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: Direct firmware load for amdgpu/gc_11_0_3_mes_2.bin failed with error -2
Oct 09 14:52:47 arch kernel: [drm] try to fall back to amdgpu/gc_11_0_3_mes.bin
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: Direct firmware load for amdgpu/gc_11_0_3_mes.bin failed with error -2
Oct 09 14:52:47 arch kernel: [drm:amdgpu_device_init [amdgpu]] *ERROR* early_init of IP block <mes_v11_0> failed -19
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: amdgpu: Fatal error during GPU init
Oct 09 14:52:47 arch kernel: amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.

Offline

#6 2023-10-09 13:26:09

realGulagboi
Member
Registered: 2023-10-09
Posts: 5

Re: Arch stuck on boot after changing Mainboard and GPU

I havent done anything on arch since changing the hardware.

the package linux-firmware is installed (checked with "sudo pacman -Qi linux-firmware")

Last edited by realGulagboi (2023-10-09 13:26:32)

Offline

#7 2023-10-09 14:46:56

realGulagboi
Member
Registered: 2023-10-09
Posts: 5

Re: Arch stuck on boot after changing Mainboard and GPU

UPDATE: a repo update(sudo pacman -y) and a linux firmware(sudo pacman -S) update seems to have fixed the issue

Last edited by realGulagboi (2023-10-09 14:49:59)

Offline

Board footer

Powered by FluxBB