There are a few radeon cards that are supported by both the radeon and the amdgpu driver.
The amdgpu driver is supposed to be more stable and is newer, but the older radeon driver is listed as supporting that hardware means whichever driver loads first takes care of the card (when the amdgpu option is there, without the amdgpu option the amdgpu driver ignores SI). Once you set the radeon option to 0 that tells the old driver to ignore the SI variant (southern islands radeon chipset) so the amdgpu driver can then get control of and support a SI card. I believe everyone did not want to replace the (though to be working) radeon driver on the older chipsets so left it enabled in radeon and disabled in amdgpu. If the amdgpu is working then keep using it, it is newer and I don't know that anyone will be willing to fix anything in the radeon driver since it is only needed to support chipsets older than southern islands and SI was released about 14 years ago. On Sun, Feb 1, 2026 at 12:05 PM <[email protected]> wrote: > > "radeon.si_support=0 amdgpu.si_support=1" resolves the problem, whereas just > "amdgpu.si_support=1" does not. > > And after some additional Google guided troubleshooting, found this: > > user@localhost:~$ sudo dmesg | grep -i error > [sudo] password for user: > [ 0.459270] acpi PNP0A08:00: _OSC: platform retains control of PCIe > features (AE_ERROR) > [ 0.985526] RAS: Correctable Errors collector initialized. > [ 17.299444] Bluetooth: hci0: Error reading debug features > [ 51.658906] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait > timed out. > [ 51.659201] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed > testing IB on ring 5 (-110). > [ 51.659510] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: > failed to schedule ib (-12). > [ 51.659761] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to > get create msg (-12). > [ 51.660019] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed > testing IB on ring 6 (-12). > [ 51.660269] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: > failed to schedule ib (-12). > [ 51.660490] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to > get create msg (-12). > [ 51.660706] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed > testing IB on ring 7 (-12). > [ 104.074642] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait > timed out. > [ 104.074940] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed > testing IB on ring 5 (-110). > [ 135.716914] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test > failed (scratch(0x850C)=0xCAFEDEAD) > [ 135.717202] [drm:si_resume [radeon]] *ERROR* si startup failed on resume > > Suggestions? Appreciate the help. > -- > _______________________________________________ > users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://forge.fedoraproject.org/infra/tickets/issues/new -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
