Opened 2 years ago

Closed 2 years ago

#18023 closed bug (fixed)

Disable newer Radeon HD cards on R1/beta4 branch

Reported by: kallisti5 Owned by: kallisti5
Priority: blocker Milestone: R1/beta4
Component: Drivers/Graphics/radeon_hd Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by kallisti5)

We need to test where the functionality of Radeon HD cards goes downhill so they can be disabled in R1/beta4.

  • RX 480 - kallisti5
  • RX 5500 - waddlesplash
  • RX 6700 XT - kallisti5

Change History (7)

comment:1 by kallisti5, 2 years ago

Description: modified (diff)

comment:2 by smallstepforman, 2 years ago

I'd add the RX5600 (Navi 1) and the R6600M (Navi 2) to the list, both my desktop and laptop need to disable the radeon_hd package.

comment:3 by gmbroome, 2 years ago

I've got an RX 2500 U (mobile) running R1/beta4 from depot that seems to be impacted by this. On beta3 it wasn't able to find AtomBIOS so always did failsafe. With the recent patch to pull AtomBIOS info from ACPI the radeon_hd driver now loads successfully and gets as far as enumerating displays, but I ultimately end up with a black screen. Forcing failsafe video gets me going again. Glad to help troubleshoot; kernel logs available upon request.

in reply to:  3 ; comment:4 by korli, 2 years ago

Replying to gmbroome:

I've got an RX 2500 U (mobile) running R1/beta4 from depot that seems to be impacted by this. On beta3 it wasn't able to find AtomBIOS so always did failsafe. With the

which pci id?

in reply to:  4 comment:5 by gmbroome, 2 years ago

Replying to korli:

Replying to gmbroome:

I've got an RX 2500 U (mobile) running R1/beta4 from depot that seems to be impacted by this. On beta3 it wasn't able to find AtomBIOS so always did failsafe. With the

which pci id?

1002:15dd

Last edited 2 years ago by gmbroome (previous) (diff)

in reply to:  4 comment:6 by gmbroome, 2 years ago

Replying to korli:

Replying to gmbroome:

I've got an RX 2500 U (mobile) running R1/beta4 from depot that seems to be impacted by this. On beta3 it wasn't able to find AtomBIOS so always did failsafe. With the

which pci id?

For e-mail thread purposes, that's 1002:15dd - pardon the duplicate comment, Trac on a mobile browser got mad at me. Subsystem 103c:83d5, rev d1.

Last edited 2 years ago by gmbroome (previous) (diff)
Note: See TracTickets for help on using tickets.