Radeon 5500 XT problem

[laurent]

Hello,
I'm having an issue with my Radeon 5500 XT OC 8GB graphics card.
When the computer is idle, after about 8 minutes, the graphics card temperature gradually rises—and the fans ramp up their speed accordingly—but as soon as I touch the mouse or keyboard, everything returns to normal. I reinstalled the graphics card's VBIOS, but nothing changed.
Tahoe 26.7, OpenCore 1.0.7, AMD Ryzen 5 3600 msi b450 tomahawk
I can't figure out if the graphics card is failing or if there's a problem with my configuration.

 

[Edhawk]

It is unlikely to be an issue with your setup, but saying that you are using USBMapDummy.kext, when you should be using USBMap.kext. USBMapDummy.kext is normally only used while undertaking the USB port discovery, not as the end product of your custom USB configuration.

When the system is idle which background processes are running?

Test: Have Activity Monitor open, leave the system to idle and see which if any processes are running to make the dGPU fan and temperature ramp up.

Have you thought about dismantling the dGPU and replacing the thermal paste and pads used to cool the card?

 

[Edhawk]

Looking in your /EFI/OC/Kexts folder I would try running with the RadeonSensor.kext and SMCRadeonGPU.kext disabled and see if that makes any difference. These sensor kexts can often be problematic in macOS.

In your config.plist you have enabled the 2 x Fix PAT Kernel Patches created by Shaneee/Zormeister. Have you tried switching to the alternative Kernel Patches by Algrey/Zormeister? Does this effect the way the dGPU behaves when the system idles?

Further to your USBMapDummy.kext, I note that both USB controllers (PXTH & XHC0) are set to work with 26 x ports, which will always cause an issue in macOS. As the most any one USB controller can activate is 15 x ports.

1. Under PXTH 9 of the 26 x ports have been disabled (UK03 to UK11), so 17 x ports are being activated!
2. Under XHC0 all 26 x ports are being activated!
3. In both cases only the first 15 x ports will be activated by macOS. This marries up with the 15 x port limit imposed by Apple for each USB controller.

 

[laurent]

Looking in your /EFI/OC/Kexts folder I would try running with the RadeonSensor.kext and SMCRadeonGPU.kext disabled and see if that makes any difference. These sensor kexts can often be problematic in macOS.

In your config.plist you have enabled the 2 x Fix PAT Kernel Patches created by Shaneee/Zormeister. Have you tried switching to the alternative Kernel Patches by Algrey/Zormeister? Does this effect the way the dGPU behaves when the system idles?

Further to your USBMapDummy.kext, I note that both USB controllers (PXTH & XHC0) are set to work with 26 x ports, which will always cause an issue in macOS. As the most any one USB controller can activate is 15 x ports.

1. Under PXTH 9 of the 26 x ports have been disabled (UK03 to UK11), so 17 x ports are being activated!
2. Under XHC0 all 26 x ports are being activated!
3. In both cases only the first 15 x ports will be activated by macOS. This marries up with the 15 x port limit imposed by Apple for each USB controller.

I disassembled the GPU, replaced the thermal pads and thermal paste of processor gpu, and fixed the USB ports, but the problem persists. Activity Monitor shows mediaanalysisd (PID 2192) using 72% of the CPU, accompanied by VTDecoderXPCService. It seems the primary culprit, mediaanalysisd, is part of the macOS Tahoe codebase. The Ryzen processor's AMD architecture lacks an integrated Intel graphics chip (iGPU)—a tool macOS normally uses to handle these AI tasks seamlessly in the background. For now, I’ve set the screen to turn on a screensaver after 5 minutes, and that seems to be working. I think I’ll have to either replace the GPU or revert to Sequoia—do you have any other ideas?

 

[Edhawk]

You should be using a System Definition that doesn’t have or expect an Intel IGPU to be present, I.e. MacPro7,1 SMBIOS with your AMD Hack. If you are using an iMac20,x SMBIOS, which expects an Intel IGPU you need to change it.

Changing the GPU for another compatible card sounds like a good idea.

 

[laurent]

This problem is really weird. Basically, I get a black screen when using the HDMI output connected to a TV via an HDMI-to-DVI adapter (which isn't faulty) at 1360x768 resolution; however, if I unplug it and connect a DisplayPort-to-DVI adapter instead, it works fine—even though the graphics card's HDMI output works perfectly in Windows.
AMD 5500 XT OC 8GB, running Tahoe 26.7.1 and OpenCore 1.0.8.
I've tried everything: with or without WhateverGreen and with or without agdpmod=pikera.
In fact, if I boot without WhateverGreen and without agdpmod=pikera, I can reach the desktop using the DisplayPort-to-DVI adapter.
I'm completely stumped.

 

[Edhawk]

Having a TV with a DVI connection is fairly unusual, most have HDMI and some older models had VGA/PC connections.

A HDMI to DVI cable or adapter not working with macOS isn’t unusual. There are a lot of adapters and adapter cables on the market that don’t work with macOS but work perfectly fine in Windows. Your HDMI to DVI cable being a prime example.

There are two types of adapter/cable ‘Passive’ and ‘Active’. I have found that I had more joy using ‘Active’ cables and adapters in macOS.

Passive cables and adapters are used to pass like for like signals between two complimentary devices, such as your HDMI to DVI cable. Where there is no requirement to alter the signal, just the connector used. They tend to fall short when the distance between the PC and TV is more than 2m. If the distance between your two devices is more than 2m, then using an Active adapter or cable might resolve the current black screen issue as the active ‘chip’ will boost the signal between the sender and receiver device.

Active cables and adapters are used to pass a signal between two different ports/connections, such as your DP to DVI cable. These cables and adapters change the signal passed as well as the connectors. They normally have a chip mounted along the length of the cable or within one end of the adapter that changes the signal. These types of cable and adapters are more likely to work when passing a signal between a Mac or Hack and a TV.

You also need to be aware that most cables are designed to only work one way, I.e. a HDMI to DVI cable won’t necessarily work when used to pass a signal from a DVI to HDMI connector, or visa versa. This could be part of the issue you are facing, but without knowing the make and model of the cable you are using this is simply a guess on my part.

I would recommend that you continue with the DP to DVI cable, as this active cable works. Unless of course you need the DP out connection from the RX 5500 XT for another display. If that is the case I would look for an Active HDMI to DVI cable or adapter to replace the non working cable.