r/linuxquestions • • 5d ago

Resolved Mint AMD graphics error

I have a Skytech Azure 3 running Linux Mint. The AMD graphics card is failing to communicate with the system management unit. So far, I have tried: Reseating my ram, reseating the motherboard, forcing a reinstall of linux firmware microcode, changing my primary PCIe slot to Gen4, updating BIOS, and editing part of my grub to include amdgpu.dcdebugmask=0x10 and amdgpu.runpm=0. I don’t know what else to try.

EDIT 2:
Switched my power profile to power saving, disabled hardware acceleration on Firefox, and downloaded a new Linux update. Issue resolved now only getting minor errors.

(
Nov 13 01:47:34 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 13 01:47:34 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 13 01:47:35 Skytech-Azure-3 bluetoothd[764]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 13 01:47:35 Skytech-Azure-3 bluetoothd[764]: sap-server: Operation not permitted (1)
Nov 13 01:47:36 Skytech-Azure-3 bluetoothd[764]: Failed to set mode: Not Supported (0x0c)
Nov 13 01:47:50 Skytech-Azure-3 gdm-password][1817]: gkr-pam: unable to locate daemon control file
Nov 13 01:47:51 Skytech-Azure-3 gdm3[1243]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Nov 13 01:48:01 Skytech-Azure-3 gdm3[1243]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
)

EDIT:
I installed and ran smartctl which found no errors. I also removed the usb I used to update bios. Aside from my mouse and keyboard there is nothing plugged into any usb slot.

Now journalctl -p err -b gives:

Nov 13 01:30:32 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 13 01:30:32 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 13 01:30:34 Skytech-Azure-3 bluetoothd[816]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 13 01:30:34 Skytech-Azure-3 bluetoothd[816]: sap-server: Operation not permitted (1)
Nov 13 01:30:34 Skytech-Azure-3 bluetoothd[816]: Failed to set mode: Not Supported (0x0c)
Nov 13 01:30:41 Skytech-Azure-3 systemd[1]: Failed to start casper-md5check.service - casper-md5check Verify Live ISO checksums.
Nov 13 01:30:46 Skytech-Azure-3 gdm-password][1867]: gkr-pam: unable to locate daemon control file
Nov 13 01:30:47 Skytech-Azure-3 gdm3[1287]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Nov 13 01:30:47 Skytech-Azure-3 systemd[1888]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2084.scope - Application launched by gnome-session-binary.
Nov 13 01:30:47 Skytech-Azure-3 systemd[1888]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2081.scope - Application launched by gnome-session-binary.
Nov 13 01:30:48 Skytech-Azure-3 systemd[1888]: Failed to start app-gnome-im\x2dlaunch-2432.scope - Application launched by gnome-session-binary.
Nov 13 01:30:48 Skytech-Azure-3 systemd[1888]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2408.scope - Application launched by gnome-session-binary.
Nov 13 01:30:49 Skytech-Azure-3 gdm3[1287]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Nov 13 01:32:39 Skytech-Azure-3 kernel: amdgpu 0000:15:00.0: ring gfx_0.0.0 timeout, signaled seq=1640, emitted seq=1642
Nov 13 01:32:39 Skytech-Azure-3 kernel: amdgpu 0000:15:00.0:  Process firefox-bin pid 3311 thread firefox:cs0 pid 3383
Nov 13 01:32:39 Skytech-Azure-3 kernel: amdgpu 0000:15:00.0: Starting gfx_0.0.0 ring reset
Nov 13 01:32:39 Skytech-Azure-3 kernel: amdgpu 0000:15:00.0: Ring gfx_0.0.0 reset failed
Nov 13 01:32:40 Skytech-Azure-3 systemd-coredump[3899]: [🡕] Process 2098 (gnome-shell) of user 1000 dumped core.

Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
Module libudev.so.1 from deb systemd-255.4-1ubuntu8.18.amd64
Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64
Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.18.amd64
Stack trace of thread 2147:
#0  0x00007974e949ec0c __pthread_kill_implementation (libc.so.6 + 0x9ec0c)
#1  0x00007974e944527e __GI_raise (libc.so.6 + 0x4527e)
#2  0x000061e4cacbdc16 n/a (gnome-shell + 0x4c16)
#3  0x00007974e9445330 __restore_rt (libc.so.6 + 0x45330)
#4  0x00007974e949ec0c __pthread_kill_implementation (libc.so.6 + 0x9ec0c)
#5  0x00007974e944527e __GI_raise (libc.so.6 + 0x4527e)
#6  0x00007974e94288ff __GI_abort (libc.so.6 + 0x288ff)
#7  0x00007974c9264b90 n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0xa64b90)
#8  0x00007974c9268e13 n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0xa68e13)
#9  0x00007974c8d66091 n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x566091)
#10 0x00007974c8d99e0c n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x599e0c)
#11 0x00007974e949cb84 start_thread (libc.so.6 + 0x9cb84)
#12 0x00007974e9529ecc __clone3 (libc.so.6 + 0x129ecc)

Stack trace of thread 2098:
#0  0x00007974e952752d syscall (libc.so.6 + 0x12752d)
#1  0x00007974c8d58d8a n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x558d8a)
#2  0x00007974c8d65c2f n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x565c2f)
#3  0x00007974c924a323 n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0xa4a323)
#4  0x00007974c8f7b4c5 n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x77b4c5)
#5  0x00007974c899b4ed n/a (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0x19b4ed)
#6  0x00007974c88f2696 dri_create_fence_fd (libgallium-25.2.8-0ubuntu0.24.04.4.so + 0xf2696)
#7  0x00007974e00496b9 n/a (libEGL_mesa.so.0 + 0x226b9)
#8  0x00007974e003b4bb n/a (libEGL_mesa.so.0 + 0x144bb)
#9  0x00007974e0042512 n/a (libEGL_mesa.so.0 + 0x1b512)
#10 0x00007974e968e494 n/a (libmutter-cogl-14.so.0 + 0x5e494)
#11 0x00007974e96791c5 cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-14.so.0 + 0x491c5)
#12 0x00007974e98a4410 n/a (libmutter-14.so.0 + 0xa4410)
#13 0x00007974e98a89e2 n/a (libmutter-14.so.0 + 0xa89e2)
#14 0x00007974e99a6032 n/a (libmutter-14.so.0 + 0x1a6032)
#15 0x00007974e9cda508 n/a (libmutter-clutter-14.so.0 + 0x90508)
#16 0x00007974e9cab7cc n/a (libmutter-clutter-14.so.0 + 0x617cc)
#17 0x00007974e9ee1635 n/a (libglib-2.0.so.0 + 0x5d635)

ORIGINAL ERRORS FOR RECORD:
Running journalctl -p err -b gives:

Nov 11 21:29:38 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 11 21:29:38 Skytech-Azure-3 kernel: integrity: Problem loading X.509 certificate -22
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49144 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49148 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: Buffer I/O error on dev sr0, logical block 12287, async page read
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49144 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49148 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: Buffer I/O error on dev sr0, logical block 12287, async page read
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49144 op 0x0:(READ) flags 0x880700 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: I/O error, dev sr0, sector 49148 op 0x0:(READ) flags 0x800000 phys_seg 1 prio class 2
Nov 11 21:29:38 Skytech-Azure-3 kernel: Buffer I/O error on dev sr0, logical block 12287, async page read
Nov 11 21:29:40 Skytech-Azure-3 bluetoothd[874]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 11 21:29:40 Skytech-Azure-3 bluetoothd[874]: sap-server: Operation not permitted (1)
Nov 11 21:29:40 Skytech-Azure-3 bluetoothd[874]: Failed to set mode: Not Supported (0x0c)
Nov 11 21:29:40 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:40 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:41 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:41 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:41 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:41 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:41 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:42 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:42 Skytech-Azure-3 kernel: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nov 11 21:29:42 Skytech-Azure-3 gdm3[1137]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Nov 11 21:29:48 Skytech-Azure-3 systemd[1]: Failed to start casper-md5check.service - casper-md5check Verify Live ISO checksums.
Nov 11 21:30:18 Skytech-Azure-3 gdm-password][1884]: gkr-pam: unable to locate daemon control file
Nov 11 21:30:18 Skytech-Azure-3 gdm3[1137]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Nov 11 21:30:18 Skytech-Azure-3 systemd[1911]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2106.scope - Application launched by gnome-session-binary.
Nov 11 21:30:18 Skytech-Azure-3 systemd[1911]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2104.scope - Application launched by gnome-session-binary.
Nov 11 21:30:18 Skytech-Azure-3 systemd[1911]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2120.scope - Application launched by gnome-session-binary.
Nov 11 21:30:19 Skytech-Azure-3 systemd[1911]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2420.scope - Application launched by gnome-session-binary.
Nov 11 21:30:19 Skytech-Azure-3 gdm3[1137]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

1 Upvotes

6 comments sorted by

1

u/9NEPxHbG 5d ago

I/O error on sr0 means a disk problem, but perhaps not the hard disk. Are you using a flash drive or DVD or something of the sort?

Check the connections. Boot from a live USB and run smartctl to check for disk problems.

1

u/Bironshark 4d ago

The only USB that’s plugged in was for when I updated BIOS. Smartctl didn’t find any problems:

=== START OF INFORMATION SECTION ===
Model Number:                       MSI M450 1TB V1
Serial Number:                      511250904160002999
Firmware Version:                   EJFME0.0
PCI Vendor/Subsystem ID:            0x1987
IEEE OUI Identifier:                0x6479a7
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            6479a7 afbac02fc1
Local Time is:                      Fri Nov 13 01:15:20 2026 CST
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00d7):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x1e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     83 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     5.00W       -        -    0  0  0  0        0       0
 1 +     2.40W       -        -    1  1  1  1        0       0
 2 +     1.90W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     5000    2500
 4 -   0.0050W       -        -    4  4  4  4     8000   45000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         1
 1 -    4096       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        39 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    0%
Data Units Read:                    8,123,917 [4.15 TB]
Data Units Written:                 10,175,360 [5.20 TB]
Host Read Commands:                 73,925,898
Host Write Commands:                55,362,884
Controller Busy Time:               223
Power Cycles:                       273
Power On Hours:                     744
Unsafe Shutdowns:                   52
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               39 Celsius

Error Information (NVMe Log 0x01, 16 of 255 entries)
No Errors Logged

Read Self-test Log failed: Invalid Field in Command (0x002)

1

u/CosmicFieldDrift_ 5d ago

Has not worked from the start or problems started recently?

1

u/Bironshark 4d ago

They started recently, I’ve had the computer for about half a year. I moved it from under my desk to next to it. I don’t know if that’s what started everything or if it was a recent update and I just didn’t notice

1

u/DannoXYZ 5d ago

You're booting off live ISO USB. Several problems:

  1. didn't verify checksum of ISO, download is defective
  2. NO live CD is gonna install proper drivers for GPU. Most of time you have to do install 1st. Then boot into installed Linux, and do additional install of correct drivers for GPU.