Contribute
Register

macOS Sierra PB: Need testers for new AMD Radeon drivers!

Status
Not open for further replies.
If we figure out the crucial difference between Hacks and genuine Macs it shouldn't be too difficult to implement the necessary patches in Clover
Check this thread, read metacolin's post. From his diagonosis, it seems to me that Clover does special stuffs to "Primary GPU", that special stuffs are making amd kext crash so black screen. But it works when amd is secondary gpu bcz clover isn't doing special "Primary GPU" stuff to it. My plan is to disable those primary gpu stuff codes :/ Whatevs, not jumping into that right now. 10.12.1 is here, upgrading....
 
Hi all,

I recently installed a MSI Radeon RX 470 Gaming X 4GB and installed Sierra 10.12.1 without problems. The graphics card is recolonized at the moment as an AMD R9 4GB, which runs at full resolution, but not accelerated.

I am trying to keep the install as clean as possible and have not tried editing the kext or fakesmc method.

So I guess I have to wait for new Apple drivers (as originalmagneto) or will this be addressed in a new version of Multi Beast?
 
Last edited:
I am trying to keep the install as clean as possible and have not tried editing the kext or fakesmc method.

well, the fakesmc method seems clean. you dont modify any kexts on your partition except fakesmc (and you could do that in efi partition and inject it with clover).

btw, here is my result for sapphire rx480 nitro oc for 10.12.1, not much improvement compared to last testing (but it isnt that much worse than windows 10 opengl test, which is 47,6 frames). but too bad there is no wattman on OSX -.-


Screen Shot 2016-10-25 at 13.50.03.png
 
Check this thread, read metacolin's post. From his diagonosis, it seems to me that Clover does special stuffs to "Primary GPU", that special stuffs are making amd kext crash so black screen. But it works when amd is secondary gpu bcz clover isn't doing special "Primary GPU" stuff to it. My plan is to disable those primary gpu stuff codes :/ Whatevs, not jumping into that right now. 10.12.1 is here, upgrading....
It's good to see that someone is working on this subject, but I don't think his conclusion is correct. This issue also happens with bootloaders "not to be named here", not only Clover.
I also thought about the possibility that the UEFI to OS handover goes wrong, resulting in a kernel panic, but I'm quite sure the issue will also occur when booting without any displays attached (in this case the EFI display driver shouldn't do anything).
 
Hi, can i use HD 530 with Sierra hackintosh?
 
I also thought about the possibility that the UEFI to OS handover goes wrong, resulting in a kernel panic, but I'm quite sure the issue will also occur when booting without any displays attached (in this case the EFI display driver shouldn't do anything).

Could confirm this thoughts, cause i made the following tests:

As followers of this thread know, i have a AMD R9 280x and HD5xxx and HD7970 to test in conjunction with my latest RX460 and RX480 Sapphire cards. So i tested them with AMD R9 280x (HD7970) in slot#1, RX460 (RX480) in slot#2. Have to mention, that R9 280x and HD7970 have two VBIOS modes, so i flashed them with one VBIOS including GOP, other VBIOS w/o GOP.

All owners of RX4x0 cards should know, that there is no VBIOS w/o GOP code, so we have no "legacy only" VBIOS for these cards.

So first i used GOP-free VBIOS on both R9280x as well as on HD7970.

Set PCs BIOS to CSM enabled and VBIOS to "legacy": booted just fine, RX cards get accelerated.
Set PCs BIOS to CSM enabled and VBIOS to "UEFI": booted just fine, cause R9 280x or HD7970 in slot#1 do NOT have GOP/UEFI code in VBIOS, RX cards get accelerated.
Set PCs BIOS to CSM disabled and VBIOS to "legacy": booted just fine, RX cards get accelerated.
Set PCs BIOS to CSM disabled and VBIOS to "UEFI": booted just fine, cause R9 280x or HD7970 in slot#1 do NOT have GOP/UEFI code in VBIOS, RX cards get accelerated.

Switched VBIOS of R9 280x and HD79070 to GOP coded and tried again:

Set PCs BIOS to CSM enabled and VBIOS to "legacy": booted just fine, RX cards get accelerated.
Set PCs BIOS to CSM enabled and VBIOS to "UEFI": booted into BlackScreen, cause GOP code was used for Bootsequence
Set PCs BIOS to CSM disabled and VBIOS to "legacy": booted to BLACK SCREEN, cause CSM disabled always loads GOP code from card if availlabe.
Set PCs BIOS to CSM disabled and VBIOS to "UEFI": booted to BLACK SCREEN, cause CSM disabled always loads GOP code from card if availlabe.

Now same test with RX cards in slot#1 and IGPU as primary GFX-card:
CSM enabled or disabled makes no difference, cause HD530 seems not to have any GOP code in its VBIOS, so booting was always successfull with full acceleration of RX cards cause "legacy" code was used for bootsequence.
You could verify that your HD530 will have no GOP-code by running GPU-Z under WINDOWS. Here you won't see any checkmark for UEFI feature.

Sorry, currently i am at work, so i dont have any screenshot to show what i mean, but i will make a detailed report, when i am back home.

So what i think makes a solo installed RX4x0 card to boot to black screen, is: cause there gets always the GOP code of VBIOS loaded - no matter, what kind of settings you select within your BIOS setup. I know, that RX4x0 cards do have "legacy" and "GOP" code in it's VBIOS - but i dont know, how to disable the GOP-Code while booting system with this card "one-and-only" gfx card in your hardware.
 
Last edited:
the mentioned tool in this thread does NOT support the AMD RX series cards. Also it is better to test my theorie with a legal "legacy-only" VBIOS - not a one which was "composed" by some unknown 3rd party tools ;-)
 
Status
Not open for further replies.
Back
Top