Jump to content

AMD Polaris IDs on Sierra / High Sierra


870 posts in this topic

Recommended Posts

Strange   :huh:

 

Maybe all what that is confirming is that the Polaris 10 (Ellesmere) support will be only enabled through Baffin accelerator?

 

I'm tempted to believe it.  :yes:

 

It will be even strange that baffins drives an ellesmere GPU tho

  • Like 1

I agree

 

Then just lets hope Apple will add the native support in future Sierra minors updates.  -_-

 

I'm pretty sure Apple is hiding the new iMac, and it will add full Baffin and Ellesmere support only after the new iMac release. 

  • Like 1

I'm pretty sure Apple is hiding the new iMac, and it will add full Baffin and Ellesmere support only after the new iMac release. 

 

We'll see on September 7 at the keynote but I doubt we see this new iMac in the code of GM - Maybe in 10.12.2 or 10.12.3???

We'll see on September 7 at the keynote but I doubt we see this new iMac in the code of GM - Maybe in 10.12.2 or 10.12.3???

 

Quite easy, yeah, i hope for March or April 2017

  • Like 1

Same here: 

 

gi5nbBX.png

This looks like a non signed kext issue

 

Update:

I tried signing the kext that you uploaded, (because I can lol) but there is some errors in the binaries 

 

codesign says my main executable failed strict validation.
  • Your Mach-O executable does not conform to modern Mach-O layout rules.

  • You may be using a third party development product that hasn't been brought up to date, or post-processed your file in unsupported ways.

  • Like 2

Could someone try this kext and post results please 

 

https://www.dropbox.com/s/fwsv86h1b7uslw9/AMDRadeonX4000.kext.zip?dl=0

Not working w/o IGPU... but working with IGPU.

Tested with my Sapphire RX480 NITRO 8GB (67DF1002). w/o IGPU still getting blackscreen after verbose mode. Hooked up to the card ist still one DP and one HDMI monitor.

 

Kext get loaded in conjunction with IGPU set to be primary gfx:

amdradeonx4000.jpg

same screenshot in english:

amdradeonx4000_us.jpg

Not working w/o IGPU... but working with IGPU.

Tested with my Sapphire RX480 NITRO 8GB (67DF1002). w/o IGPU still getting blackscreen after verbose mode. Hooked up to the card ist still one DP and one HDMI monitor.

 

Kext get loaded in conjunction with IGPU set to be primary gfx:

amdradeonx4000_us.jpg

Do you have hardware acceleration now? Also is this on a real mac or a hack?

in conjunction with IGPU i have hardware acceleration also with the original kext.

but not working without IGPU.

 

so for me it makes no difference if using your kext or original one.

From your sig specs you must be using iMac 17,1 SMBIOS which from my research only loads the R9 3xx Series drivers without a iGPU, so this could be an issue. I ordered a Sapphire NITRO+ RX 480 8Gb myself and will be here in 3 days, will try it out in my real Mac Pro 5,1 and post results.

  • Like 2

Found that both Baffin and Ellesmere are indeed in the AMDRadeonX4000 binary:

Yes, but if you look closely you will see Ellesmere is incomplete compared to Baffin which has more "code" :)

From your sig specs you must be using iMac 17,1 SMBIOS which from my research only loads the R9 3xx Series drivers without a iGPU, so this could be an issue. I ordered a Sapphire NITRO+ RX 480 8Gb myself and will be here in 3 days, will try it out in my real Mac Pro 5,1 and post results.

No, not true. Right now i am using MacPro 5,1 as my SMBIOS settings within my config.plist. And this is not the problem, cause i tried a lot of SMBIOS-settings: iMac13,1 - iMac14,1 - iMac14,2 - iMac16 - iMac17,1 - MacBook10,1 - MacPro 5,1 and MacPro 6,1. Alle settings have been shown the same effect: only works with iGPU set to primary.

 

Also you can see, that Dev.id 67EF1002 could be found within the baffincode of binary - but 67DF1002 would not be found.

i did this already: the value should be found 6 or seven times (didn't remember). But it had no effects. Still not running native.


Look, there is much more BAFFIN code within AMDRadeonX4000 than ELLESMERE:

 

BAFFIN

baffin_code.jpg

ELLESMERE

ellesmere_code.jpg

so it seems, the concentration of apple is more on BAFFIN code, than on ELLESMERE. Maybe new MacBooks will have RX460m as dedicated Grafik

And i guess, ELLESMERE is using main code routine functions from BUFFIN for Acceleration.

 

For me it seems, that Buffin will make the main Acceleration, and the included ELLESMERE code is only for "finetuning" values for Ellesmere-based hardware. You can see this, because right now, no "AMDEllesmereGraphicsAccelration" parts could be found.

 

And always remember: in a real Apple MacPro 5,1 both cards running native (kext infoplist patching for RX480 neccesarry).


Also take a look at this (part of CLOVER 3728 bootlog):

4:624  0:000  === [ RestSetupOSX ] ======================================
4:624  0:000  EdidDiscovered size=128
4:624  0:000  00 | 00 FF FF FF FF FF FF 00 4E 16 02 92 00 00 00 00
4:624  0:000  16 | 34 15 01 03 80 50 2D 78 0A EE 91 A3 54 4C 99 26
4:624  0:000  32 | 0F 50 54 2D 4F 00 71 59 81 59 95 19 A9 59 B3 19
4:624  0:000  48 | D1 19 D1 4F 01 01 9A 29 A0 D0 51 84 22 30 50 98
4:624  0:000  64 | 36 00 98 FF 10 00 00 1E 00 00 00 FD 00 18 F0 0F
4:624  0:000  80 | 7D 0F 00 0A 20 20 20 20 20 20 00 00 00 FC 00 53
4:624  0:000  96 | 75 6E 70 6C 75 73 20 54 56 0A 20 20 00 00 00 00
4:624  0:000  112 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 B4
4:624  0:000  Unsupported ATI card! Device ID: [1002:67DF] Subsystem ID: [E347174B]
4:624  0:000  search for brothers family
4:624  0:000  ...compatible config is not found
4:624  0:000  Intel Intel HD Graphics 530 [8086:1912] :: PciRoot(0x0)\Pci(0x2,0x0)
4:624  0:000  Intel GFX revision  =0x6
4:624  0:000   RCBA disabled; cannot use it
4:624  0:000  stringlength = 2964
4:625  0:000  CurrentMode: Width=1440 Height=900
4:625  0:000  Beginning FSInjection
4:625  0:000  Blocking kext caches

Unsupported ATI card! ... compatible config NOT found <--- don't know, if this means, that injection wasn't possible.

But i have the same effects when using the "Arbitrary" routine from CLOVER. When using Arbitrary, the GRAPHIC section gets ignored. But still only working in conjunction with iGPU enabled and primary.

  • Like 2
×
×
  • Create New...