[SOLVED] Trying to use graphical applications causes system to reboot

Loonix Lover · 2024-07-13 05:02:37

Update:
So I found out that there is a kernel bug that causes instability with the AMD 390 GPU. I was able to get it to work by adding

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1

as kernel parameters in grub. However, there was a plethora of other issues, screen tearing (the fix listed on the Arch Wiki did not work), weird visual artifacts, everything being slow and unresponsive, Elden Ring not launching when it launches fine on Windows (disabling the anti-cheat didn't work), and the system eating up over a hundred gigabytes of disk space on a clean Arch install (which may have just been something I did wrong). I might come back to this later but I'm done for now.

Original Post:
Hi all. I have been having a difficult time trying to get Linux installed on my eight-year-old gaming machine. First I tried installing Mint XFCE. I got through the graphical installer with the live session no issue but when I tried to reboot I had an infinite boot loop (I had configured it so I wouldn’t need to login on startup). Then I tried to install Debian. I could get to LightDM but when I tried to login the system rebooted. Sometimes typing an incorrect password would trigger a reboot but not always. I posted about this issue on Reddit where a user suggested that the issue was possibly caused by a broken Grub configuration. Post here:
https://www.reddit.com/r/linuxquestions … therboard/
I tried to boot manually but that was unsuccessful. What’s strange is that I was able to install Windows and then run Mint inside a VM within that Windows install. This makes me think the issue may be related to my motherboard.

When rebooting I see:
[ 1.877088] [Hardware Error]: System Fatal Error.
[ 1.877096] [Hardware Error]: CPU:0 (15:2:0) MC4_STATUS[OverIUEI-IAddrVIPCCI-]: 0xf600000000070f0f
[ 1.877104] [Hardware Error]: Error Addr: 0x0000000000fe98d210
[ 1.877107] [Hardware Error]: MC4 Error (node ): Watchdog timeout due to lac
[ 1.877111] [Hardware Error]: cache level: L3/GEN, mem-tx: GEN, part-proc: GEN (timed out)

If I do journalctl -b I see in red:
Sp5100-tco sp5100-tco: Failed to reserve MMIO or alternative MMIO region
sp5100 -tco sp5100-tco: probe with driver sp5100-tco failed with error -16

I installed Xorg with “sudo pacman -S xorg-server xorg-apps xorg-xinit xorg-twm xorg-xclock xterm”and the default startx works fine.
I can launch LightDM but it has the same behavior I had on Debian.
I can launch I3 but trying to open the terminal with mod+enter causes a reboot (I also see “Error: status_command not found or is missing a library dependency (exit 127)” printed in red in the corner of the screen)
Trying to launch Firefox or XFCE directly with startx just causes a black screen then a reboot.

Quick Boot and 2.2tb Infinity are disabled

Hardware:
Mobo: 760 GMA-P34 (FX)
CPU: AMD FX-6300
SSD: Samsung 870 QVO 2TB (Was previously running windows on a smaller SSD with a mechanical drive for additional storage)
GPU: AMD Radeon R9 380
RAM Kingston HyperX fury 8GB
PSU: EVGA 600B

Last edited by Loonix Lover (2024-07-27 00:09:51)

seth · 2024-07-13 07:31:20

the issue was possibly caused by a broken Grub configuration

No, spontanous reboots are because
- underpowered
- overheated
- broken CPU or RAM
Not anything in the bootloader, a broken bootloader will prevent the system from booting. Once it has handed over to the OS the bootloader doesn't do anything anymore.

I was able to install Windows and then run Mint inside a VM within that Windows install. …
Was previously running windows on a smaller SSD with a mechanical drive for additional storage

Is "windows is working" historic data or status quo?
The system will end up being underpowered or overheating so when the GPU gets used, the CPU runs undervolted and the system reboots.
Did you forget to attach dedicated power supply to the GPU?
Do you undervolt or overclock the system in the BIOS/UEFI?

Loonix Lover · 2024-07-15 20:41:14

Sorry for the late response.

Is "windows is working" historic data or status quo?

Status quo. After posting this I switched around the drives and tried playing some video games at max setting in Windows. I only played Doom 2016 and Doom Eternal a couple minutes each but they both ran fine. I've stress-tested the ram with Aida 64 three times. I got an error at the end of the benchmark the first time but no errors the two subsequent times. I also ran Prime 95 for an hour to stress-test the CPU, no errors. No overclocking or undervolting

seth · 2024-07-15 20:46:07

Status quo.

=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Then see https://wiki.archlinux.org/title/Ryzen#Troubleshooting

Arch Linux

#1 2024-07-13 05:02:37

[SOLVED] Trying to use graphical applications causes system to reboot

#2 2024-07-13 07:31:20

Re: [SOLVED] Trying to use graphical applications causes system to reboot

#3 2024-07-15 20:41:14

Re: [SOLVED] Trying to use graphical applications causes system to reboot

#4 2024-07-15 20:46:07

Re: [SOLVED] Trying to use graphical applications causes system to reboot

Board footer