Contribute
Register

Need Help with Asus X99-E WS & ASUS R9 380 STRIX

Status
Not open for further replies.
Joined
Dec 28, 2012
Messages
154
Motherboard
ASRock X299 CREATOR
CPU
i9-7920X
Graphics
RX 6900 XT
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Just a little update for all of you:

recently i switched to ASUS X99-E WS motherboard and Intel I7 5820k cpu. And this board and cpu is a hassle for a hackintosh. Took me a whole weekend to make OS X 10.10.5 and OS X 10.11.1 running on this board. GFX-card still the same ASUS R9 380 STRIX with 2GB RAM running in PCI Slot #3 (have to move it to that slot, cause Thunderbolt card needs to be plugged into Slot #2 for best results). BIOS is the latest 1302 for this board and i still use my ASUS ThunderboltII EX card in PCI slot #2. First i got memory allocation error when trying to boot. Gladly i found a working "OsxAptioFixDrv-64.efi" driver, so now i am able to boot with latest CLOVER 3305.


Now here is the problem:

tried almost every framebuffer with this card. Under YOSEMITE no problem: all of my injected fb-patches work like a charm: OS X will boot in verbose mode, when booting to desktop, all connected monitors (1 DP, 1 HDMI and 1 DVI) stop responding for about 90 seconds. After that period of time they will come back and all monitors are showing the desktop (with full acceleration). So i can live with that amount of delay when booting to desktop.

But no chance to make it working with latest EL CAPITAN 10.11.1 - same effect: booting verbose mode is ok, than all monitors turn black and... no response anymore! But machine still seems to be working, cause i could connect to filesharing of EL CAPITAN machine (i enabled it to test, if machine still is responding) and also responds to ping requests. Using Apple Remote Desktop Admin client, i can see also, that EL CAPITAN machine ist still alive, but it says "ARD not ready" and when i try to connect via ARD i will get a timeout message: "EL CAPITAN not responding. Verrify, if Firewall is blocking the ports" or something similar like that.

When i delete the "AMDRadeonX4000.kext" from System/Extensions, i could boot into desktop, but without acceleration. IORegistryExplorer shows me correct patched framebuffer with all 4 ports connected and correctly assigned to their order (port 4 still has no monitor connected). You can see in attached Screenshot. Also DPCIManager shows, that RADEON has the Framebuffer accepted successfully.

In my example i choose to modify GREYHOUND framebuffer from


Greyhound original:

00040000040300000001010710000103
00040000040300000001020720010204
00040000040300000001030711020301
00040000040300000001040721030402
00040000040300000001050712040505
00040000040300000001060722050606

000400000403000000010107100001030004000004030000000102072001020400040000040300000001030711020301000400000403000000010407210304020004000004030000000105071204050500040000040300000001060722050606

Greyhound patched:

00040000040300000001000711020401
00080000040200000001000021030403
00020000140200000001000010000405
04000000140000000001000012040406
00040000040300000001000010000402
00020000140200000001000010000404


000400000403000000010007110204010008000004020000000100002103040300020000140200000001000010000405040000001400000000010000120404060004000004030000000100001000040200020000140200000001000010000404


And now for the strange thing when patching the framebuffers: they only work, when i set "04" for the HotPlugID to all defined connectors! If i set the HotPlugID in a normal order like 01 for DP, 02 for HDMI, 03 for DVI-I and 04 for DVI-D (05 and 06 for the last defined connectors) i will allways get errors on reboot, when system tries to show desktop on the connected monitors (w/o connector #4, which is still working correctly). Then, when i try to connect remotly to desktop with ARD from my Macbook, i can see in IORegistryExplorer, that the connectors are still in the right order, but still have no monitor connected (w/o defined port #4).


So when i change the HotPlugID of patched framebuffer all to "04", all Monitors will be correctly recognized and are showing their desktops. VERY WEIRED !!!


Could anyone explain this to me? Also i found out, that i could define the order of connectors by switching the following entries in framebufferpatch:


00040000040300000001001711020401
00080000040200000001002021030403
00020000140200000001003010000405
04000000140000000001004012040406
00040000040300000001005010000402
00020000140200000001006010000404


Changing these values in thier order, will change the connectors order in IORegistryExploer as well. JUST TESTED AND CONFIRMED. So why do i have to change these values instead of the HotPlugID values?
And why does changing the HotPlugID makes my setup broke?


Any explanations to this are welcome.


So far... regards. Hope this will help all the other owners of a RADEON R9 380 gfx-card.



PS: all AMD9000.kext framebuffers could be patched with the above patch. BASSET still get the first 4 rows patched, cause this is a 4 connectors framebuffer. All the others use 6 connectors. When i try to use patched BALADI or EXMOOR, they will change to default RADEONFRAMEBUFFER after boot. All the others got accepted: BASSET, GREYHOUND, OPM, LABRADOR (only in 10.11.1, cause it isnt availlable in 10.10.5)
 

Attachments

  • CLOVER Config.txt
    7.5 KB · Views: 257
  • DPCIManager.jpg
    DPCIManager.jpg
    150.4 KB · Views: 96
  • IORegistryExplorer.jpg
    IORegistryExplorer.jpg
    263.4 KB · Views: 97
The HotPlugID is not meant for sorting the connectors, they have to match the corresponding hotplug ID of your vBIOS.
Have a look at the Radeon sticky thread in this section for details, I've attached an improved version of that radeon bios utility there.

Just to get this straight: Which ports are you using, which are working with your mod? Did you verify them one by one? I guess they'll all work if all have a screen attached, but stop working when you remove the screen hooked up to the port with HotPlugID=4.
Does your mod work with full acceleration or are you booting without X4000.kext?
 
Dear Florian,

yes, when using the patched framebuffers under YOSEMITE, all connected monitors work flawlessly.
Right now i am using only three of them: DP, HDMI and DVI-I. When using FB-patch under El CAPITAN and installed AMDRadeonX4000.kext, monitors lost connection after verbose mode just before system boots to desktop. Under El Capitan with deinstalled AMDRadeonX4000.kext, patched framebuffers also work and system could boot to desktop with all connected monitors working - just w/o accelleration.


EDIT: with that radeon_bios_decode tool i can see the HOTPLUGIDs: DP = 04, HDMI = 05, DVI-I = 06 and DVI-D = 01. Will try that when i come home. Maybe thats the solution !!! Will keep you informed.

So i will try to patch the selected framebuffer this way:

00040000040300000001001711020401 <-- DP
00080000040200000001002021030503 <-- HDMI
00020000140200000001003010000105 <-- DVI-D
04000000140000000001004012040606 <-- DVI-I
00040000040300000001005010000202 <-- not used
00020000140200000001006010000304 <-- not used
 

Attachments

  • radeon_bios_decode.jpg
    radeon_bios_decode.jpg
    128.4 KB · Views: 106
Ah okay. Actually I think adjusting the hotplug IDs won't fix your problem, since it's already matching for your DP port (which doesn't work either with X4000 in place, correct?).

There's something wrong with the injection and/or auto init on Tonga cards on El Capitan. I've read many positive reports on setting the iGPU as primary, which somehow circumvents the problem. Obviously that isn't possible for your X99 system...
 
Yes, you are right. Had the same issues on my Z97 board. Enabling onboard gfx solved the problem there, too. Correct HPID for DP port is right, but maybe the problem is in that moment, that the other ports with connected monitor don't match to their HPID.

Will test it when coming home from work later... and will keep you informed. Thanx for ya help so far.
 
Just arrived @ home and edited my framebuffer patches for GREYHOUND, LABRADOR, OPM and BASSET to the following Settings:

00040000040300000001000711020401 <-- DP
00080000040200000001000021030503 <-- HDMI
00020000140200000001000010000105 <-- DVI-D
04000000140000000001000012040606 <-- DVI-I (* just the first 4 connectors for BASSET, since it is just a 4 connectors framebuffer)
00040000040300000001000010000202 <-- not used (cause Radeon R9 380 STRIX only has 4 physical ports)
00020000140200000001000010000304 <-- not used (cause Radeon R9 380 STRIX only has 4 physical ports)

Working all great with YOSEMITE. All patches will be accepted and every monitor will show correct desktop afte complete bootsequence. BALADI and EXMOOR still changed to "ATY,RadeonFramebuffer"
May work also with EL CAPITAN - but still having the "monitor did not respond" after bootsequence (while machine still responds to filesharing requests, but not to screensharing requests from my MacBook).
blush.png


Have to explain, that all patches work also on EL CAPITAN, if i remove the AMDRadeonX4000.kext from /System/Library/Extensions folder, <-- all connected monitors responds with the correct desktop, but w/o accelleration.

With AMDRadeonX4000.kext active it seems, that EL CAPITAN still boots into any "virtual desktop" with the effect, that all connected monitors reporting "No Signal" and went to stand-by mode.
Same effect with my old ASUS Z97 DeLuxe board when disabled the onboard Haswell INTEL GFX or setting PCIe-GFX to primary GFX. EL CAPITAN boots succesfully, when INTEL GFX is enabled and set to primary gfx.

Have no more idea on how to get it work. For me it seems, we need a "AMDRadeonX4000.kext"-patch.

Also want to mention, that i tried every possible CLOVER v3305 configuration: Inject EDID on/off, Load VBIOS on/off, patch VBIOS on/off, Dual Link set to off/0/1 <--- all w/o any noticable effect.

But i don't give up: next test plugging in my old Sapphire Radeon R7 260X as second GFX-Card with using the R9 380 as primary card as usual, then lets see, what happens.
So stay tuned and don't miss the next episode of this show...

regards,
Mork vom Ork
 
Sorry guys,

can't make it work! Even with a Radeon R7 260X (66581002) as secondary gfx, system still doesn't show any monitor activity.

System starts w/o any problems, if just installed the R7 260X, so the Radeon R9 380 (TONGA chipset) seems to make problems with AMDRadeonX4000.kext. And there seems to be no solution so far... so i stay with the R7 260X right now.


But will test again, if i get my hands on 10.11.2 beta update.

So long...
 
Status
Not open for further replies.
Back
Top