Complete System Regression Chain: From Fresh Install Kernel Reboot Loops to Brave Video Frame Drops and GNOME Session/Power Crashes (AMD Setup)

Installing Zorin OS
, , , ,
1

System Specifications:

OS: Zorin OS 18 (Core)
Desktop Environment: GNOME
Motherboard: MSI B550M-A PRO Setup
Processor: AMD Ryzen 5 5500GT with Integrated graphics
no dedicated graphics card installed yet now as its new pc build and also price and money constraints .
Graphics: AMD Radeon Integrated Graphics

Complete Chronological Timeline of Issues Faced

Issue 1: Fresh Installation Kernel Restart Loop (The Root Video Driver Conflict)

Behaviour: The problems began immediately upon a fresh install of Zorin OS. When attempting to boot into the newly installed system using the preinstalled kernels 6.17.35 and 20, the machine fell into a continuous, hard restart loop / black screen panic.

Observation: The kernel was completely failing to initialise the display output with the default AMD video graphics drivers. The system could not reach the desktop display server safely without hard-rebooting the motherboard, proving a foundational incompatibility or timing mismatch between the preinstalled kernel's video mode setting (amdgpu) and my hardware out of the box.

Current Fix: Installed Linux kernel 6.8.0-41 version to work ,

Issue 2: Browser Frame Drop / Video Playback Bottleneck (Kernel/Driver Interface)

Behaviour: Once the system was finally forced to boot and stabilise, a massive rendering bottleneck appeared during media playback. Brave Browser suffered from an unplayable 30 to 40 frame loss (dropping 1,290 out of 4,389 frames), causing severe, constant stuttering. Meanwhile, Firefox ran flawlessly (dropping only 17 out of 1,904 frames).

Observation: i don't know!!

Issue 3: Bluetooth Dongle Connectivity Drops (Hardware/Firmware Power Management)

  • Behaviour: Once the system baseline was established, severe peripheral instability occurred. A standard USB Bluetooth Dongle realtek 8821Cu chipset experienced persistent connection drops, timing out, and failing to recognise devices cleanly.
  • Fix: i switched to wired headphones.

Issue 4: Total GNOME Desktop Environment Crash (Application Layer)

Trigger: To monitor system resources, I installed the Mission Center app and for maths i installed Graphs (gnome-graphs) application via the Software Center using the Snap packaging back end.

Behaviour: The moment I attempted to add data or render a plot, the app completely froze. Instantly, the entire screen went black, terminated all active user sessions (Firefox, Telegram, etc.), and forcefully threw me back out to the GDM Login Screen. A similar sudden session crash occurred previously with the Mission Center hardware monitor just after opening it.
Core logs gathered from the display manager crash:
PlaintextMay 29 17:48:12 systemd[1687]: Failed to start app-gnome-gnome-graphs... May 29 17:48:12 systemd[1687]: Failed to start app-gnome-xdg\x... May 29 22:31:22 systemd[86535]: Failed to start app-gnome-gnome-graphs...

*Software Center Corruption: Following the crash, the Software Center corrupted the app's package metadata and refused to uninstall it graphically, requiring a manual command-line purge (sudo snap remove --purge graphs).

Issue 5: Post-Crash Shutdown-to-Reboot Loop Interface

  • Behaviour: Immediately following the GNOME desktop session crash, clicking the standard graphical upper-right GNOME menu to "Power Off" failed. Instead of shutting down, the system executed a machine reboot.*

  • Diagnostics: Running sudo systemctl poweroff from the terminal successfully cut hardware power to the motherboard instantly. This proves that the underlying ACPI state works; the graphical interface (gnome-session) simply cached a corrupt state during the violent Snap crash and began misfiring reset flags instead of a hard power-down signal.

Current Status and Interventions Taken

  1. Purged the problematic Snap app: sudo snap remove --purge graphs
  2. Restored graphical power actions: systemctl --user daemon-reload,gsettings set org.gnome.settings-daemon.plugins.power power-button-action 'interactive'
  3. Mitigation: Relying purely on Firefox for video processing and avoiding sandboxed hardware-accelerated utility apps to keep the display server from panicking.
2

Welcome to the Forum!

With that much Issues, maybe You should think about a fresh Install. For Brave, You could try it with disabled Hardware Acceleration in the Browser Settings.

3

everything is working fine as i am currently using older kernel version and i have tried disabling hardware acceleration it made it worse , i can work fine with Firefox too , and the important part here is some apps by gnome i can't use them, first the screen hangs then with a black screen then i am on the login screen ,

I just installed zorin yesterday , and i do not think these issues will get fixed if did fresh installation.

4

If you don't have dual boot I would suggest you to try Liquorix kernel, it could have better support for your hardware

5

I HAVE DUAL BOOT WINDOWS IS ALSO INSTALLED IN THE SAME SSD AS LINUX,
As My family members also use pc, they use windows, that entire reason for me to install zorin so that they can have familiarity with other os other than windows which is easy to use
I have ArchCraft installed in personal Old laptop (it has Celeron processor)

6

So maybe you can try OEM kernal, larger driver support
Install the signed OEM kernel stack

Open your terminal and run this command:

sudo apt install linux-oem-6.17 -y

Once the installation finishes, update the boot configuration and restart your laptop:

sudo update-grub
sudo reboot
7

tried installing Liquorix kernel and oem kernels they didn't work either facing the same problem as before

8

turns out the RAM i just newly bought was faulty even though it giving perfect memtest86 , given back to company for replacement as it had 10yrs of warranty,

most likely its cell degraded over time that the reason why amdgpu was not able to load properly !!

1 Like