Contribute
Register

[Success] AMD RX6000 Series working in macOS

This happens to me too with MSI Mech RX6600 XT, except luckily my macOS boot takes about 15 seconds and the no-signal time lasts about 5. I see the boot progress bar up to about 1/5th then screen goes no-video, then either the last 1/10th of the boot progress or the desktop appears, depending on how many apps are relaunched at startup. I've kept an eye on the foruns about this for 6 mos but never caught sight of any skinny on why or how to correct.
Mine is a Sapphire Pulse RX6600. So it seems to be something manufacture/model agnostic. Might actually be an issue related to WhateverGreen anr/or macOS's 6600 series driver.
 
I had the same problem of black screen with a rx 6600 sapphire pulse even using agdpmod=pikera on bootargs. Solved doing this after a lot of research on forums:
....
Target = 0
sorry for my late reply, I was dotting around some other documents.

saw a similar reply on another forum as well, and my choice of SMBIOS is iMac19,1 (due to frequently using sidecar and universal control)

but just like Cavid72 said and my try the situation is the same as before, just without verbose. thx your reply anyway.
Just to be clear. The card fully works for me. The issue is cosmetic, sort of speak.
At a point during the boot process it stays like 30 seconds (haven't clocked it) giving no video signal to any hdmi nor display port. Then login screen appears out of the blue.
I can live with it. Just found this post and made me want to try to correct it.
This happens to me too with MSI Mech RX6600 XT, except luckily my macOS boot takes about 15 seconds and the no-signal time lasts about 5. I see the boot progress bar up to about 1/5th then screen goes no-video, then either the last 1/10th of the boot progress or the desktop appears, depending on how many apps are relaunched at startup. I've kept an eye on the foruns about this for 6 mos but never caught sight of any skinny on why or how to correct.
mine 6600 is MSI MECH 2X OC. The delay on normal OS is around 3-10 sec beside that losing screen of apple progress bar is tourable indeed. But not so on recovery boot (especially during OS update), the "nosigal" sign on monitor is very alarming for me. Not only hard to check the progress for updates but I lost a few HW devices during reboot cycle caused by a power issue in the past.
Will try to inject some properties form iMac20s, iMacPro and MacPro, hope I cane find some lead.
 
Hi guys, I have switched from Vega 56 to RX 6900XT red devil ultimate 16GB
Wasnt just a plug n play, and needed to build a new macOS with new config.plist

Did that easily and macOS booted up, I did geekbench and had like 60k metal score or something

Afterwards, did the spoof on the GPU, restarted and geekbench shows 200k metal score and in system report>displays>I see correct Device ID 0x73bf>GPU seems to be working correctly

I have launched a game to check FPS in it and it was tanked to 20, the game supports Metal and was set to it
I thought it may be the AMD patch, as I had same issue with the Vega 56, changed it to shaneees and it when restarted and booted the game up, I was getting like 80fps but now stable.
Checked activity monitor and usage of GPU was at 6%.

Does anyone have any hint what this could be?
Cant believe that 6900xt with metal score 200k runs the game on 80fps. I have to be missing something. If anyone has any ideas or hints it would be very welcome :)
 
What resolution are you using to play the game (1920x1080, 2560x1440 or 4K)?
What other settings are you using to play the game (Medium, High or Ultra)?
Which game are you playing?
 
What resolution are you using to play the game (1920x1080, 2560x1440 or 4K)?
What other settings are you using to play the game (Medium, High or Ultra)?
Which game are you playing?
My bad, I havent mentioned. Its on 2560x1440, Medium settings, 70-80FPS, world of warcraft and it is set to use Metal.
Nothing else runs at that time. The GPU usage shows 6% thats weird. Shaneees patch helped on vega 56 and there I was getting like above 150FPS in game.
 
That level of FPS output is about on par with what I would expect from a much older AMD dGPU (RX470/480) at High or Ultra settings in WoW.

Other than Shaneee's GPU AMD Kernel Patch are you using any other AMD related booster SSDT's, Kexts, fake ID's or boot arguments?

Are you dual booting Windows 10 or 11, have you tried playing the game in Windows to see what FPS you can achieve in WoW on Windows?
 
That level of FPS output is about on par with what I would expect from a much older AMD dGPU (RX470/480) at High or Ultra settings in WoW.

Other than Shaneee's GPU AMD Kernel Patch are you using any other AMD related booster SSDT's, Kexts, fake ID's or boot arguments?

Are you dual booting Windows 10 or 11, have you tried playing the game in Windows to see what FPS you can achieve in WoW on Windows?
nothing like that in regards to amd booster ssdts, kexts nor fake ids. Boot argusments are just -redcode and amgmod=pikera.
I even found out about some framebuffer stuff today for 6900 cards and applied it to device properties ATY,Carswell but that didnt increased performance. All in all the card is being detected as 6900. Even saw in ioregistry that it loads 6900.kext, geekbench 5 shows 200k metal score and in wow its on 70-80fps when set to be on Metal and drops even more when I start to move. When I check activity monitor, cpu is at 270% but GPU at 6-8% like it would be doing nothing. Maybe some acceleration is not working as it should?
 
The correct boot argument is agdpmod=pikera.

Using the ATY,Carswell DeviceProperties with your RX6900 is probably the best method for configuring the card.

It sounds like the sensors are not being read correctly in your system. A CPU can’t work at 270%, that is a physical impossibility.
 
The correct boot argument is agdpmod=pikera.

Using the ATY,Carswell DeviceProperties with your RX6900 is probably the best method for configuring the card.

It sounds like the sensors are not being read correctly in your system. A CPU can’t work at 270%, that is a physical impossibility.
I see, yes I have that correctly in the config.plist just typed it from head hence the bad wording of pikera boot arg.
Should I still leave this boot arg in the config.plist when I already spoofed the device and it is being correctly recognised? Or it should always be there even after spoof.
Will try to install Big Sur today to see how it performs on that, noticed that there were some issues in Monterey 12.3
but those should be solved with the Carswell device property
Will also try to look for some sensor kexts for the amd ryzen 7 5800x
 
Yes keep the boot argument. The pikera boot argument is essential for your Navi GPU to work with macOS.
 
Back
Top