Jump to content
Vlada.

[HOW TO] Modification of AMD FB + Clover injection

400 posts in this topic

Recommended Posts

Advertisement

Thank you for this! Is there a chance of solving the 290x multi-screeen issues by following this?

 

Yes. Per example I got a problem with second DVI connector on Radeon 6850 HD which I was been able to fix by using this method.

Share this post


Link to post
Share on other sites

Yes. Per example I got a problem with second DVI connector on Radeon 6850 HD which I was been able to fix by using this method.

 

Well, I tried but unfortunately it seems this method is not enough for the 290x. I followed your tutorial and made a few patches for the Baladi personality (the only one in AMD8000Controller) but none of them seem to make any difference - boots fine with one screen, as soon as you plug another one in -> black screen.

 

It was worth a shot I guess :) Thanks for the effort, hopefully someone will figure this out one day.

 

I'm attaching my "notepad" from this, maybe it will be of use to someone: http://pastebin.com/zMJbg8xP

Share this post


Link to post
Share on other sites

There are several guides out there already for connector patching, but last time i had to patch a framebuffer I had to get the information from like 3 different places. Now it's all in one place. Thank you for such a comprehensive guide. 

Share this post


Link to post
Share on other sites

Well, I tried but unfortunately it seems this method is not enough for the 290x. I followed your tutorial and made a few patches for the Baladi personality (the only one in AMD8000Controller) but none of them seem to make any difference - boots fine with one screen, as soon as you plug another one in -> black screen.

 

It was worth a shot I guess :) Thanks for the effort, hopefully someone will figure this out one day.

 

I'm attaching my "notepad" from this, maybe it will be of use to someone: http://pastebin.com/zMJbg8xP

 

My 290X (ASUS 290X DirectCU II OC) results are the same as yours (came up with the exact same patch using this guide), however every time I try either DVI-D port it never works - just black screens on boot. DVI-D is the only output my monitor displays, so I'm stuck with it. What Clover settings do you use?

Share this post


Link to post
Share on other sites

My 290X (ASUS 290X DirectCU II OC) results are the same as yours (came up with the exact same patch using this guide), however every time I try either DVI-D port it never works - just black screens on boot. DVI-D is the only output my monitor displays, so I'm stuck with it. What Clover settings do you use?

 

Just barebone defaults with imac14,2 preset and trimenabler patch, no graphic injections.

Share this post


Link to post
Share on other sites

Thanks. Unfortunately, no matter what I do I can't get stable DVI-D output. Either the patch(es) cause black screens upon boot indicating the patch is a failure, or it boots normally with the glitchy DVI-D output causing me to put OS X to sleep then immediately wake it to workaround the DVI glitches.

Share this post


Link to post
Share on other sites

i dont understan in step 3,, 
where you get this code ? --- = First I’ll put the list of all types of connectors:

 

Connector Type LVDS 0 × 00000002 = 02 00 00 00 Note: Laptop Monitor

Connector Type DVIDL 0 × 00000004 = 04 00 00 00 Note: Dual Link DVI

Connector Type VGA 0 × 00000010 = 10 00 00 00

Connector Type SV 0 × 00000080 = 08 00 00 00

Connector Type DP = 0 × 00000400 00 04 00 00

Connector Type HDMI 0 × 00000800 = 00 08 00 00

Connector Type DVISL 0 × 00000200 = 00 02 00 00 Note: Single Link DVI

Share this post


Link to post
Share on other sites

Well, it seems like I am the first one to be successful and  praise your outstanding post:  (I did this for cosmetic fix in System Profiler )

 

I got an Asus R9 280x (R9280X-DC2T-3GD5), with vBIOS version: 6798HB.15.39.0.0.AS04 (113-AD47800-100) , I extracted the BIOS with GPU-Z v0.8.0. 

 

Like you calculated, i got similar results: 

Typ 1: DP:  	21 03 01 04
Typ 2: HDMI:	11 02 02 03
Typ 3: DVI-I:	12 04 03 02
Typ 4: DVI-I:	00 10 04 02
Typ 5: DVI-D:	10 00 05 06

My Graphics Card was using Futomaki before (atleast 1 Screen worked, i have a DSDT injection for the Framebuffer), so I decided to use it as well.  (But this shouldn't bother us in any way, since we are going to modify it completely anyways, right?).  Since i have two DVI- Dual-Link Screens connected, I wanted to have two DVI Lines, so my final Code was:

00040000  04030000  00010401  21030104  <- DP    (init. as last) 
04000000  14020000  00010101  12040302  <- DVI-I (init. as first)
04000000  14020000  00010200  10000506  <- DVI-D (init. as second)
00080000  04020000  00010300  11020203  <- HDMI  (init. as third) 

I used the Clover Method with Patch AMD7000Controller, and it is working like a charm. 

 

:thumbsup_anim: Thank you, thank you, thank you  :thumbsup_anim:

  

 

Share this post


Link to post
Share on other sites

Thanks for the great info..

My graphics card is Mobility Radeon 4870 on an Alienware m17xR2 .. i got it working with 10.10 Exotic pack QE/CI works .. my only issue that i can't get the HDMI connector to work thats the contents of the info.plisit file in the AMDFramebuffer.kext in S/L/E :

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>BuildMachineOSBuild</key>
<string>14A378</string>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>AMDFramebuffer</string>
<key>CFBundleGetInfoString</key>
<string>AMDFramebuffer 1.28.29 14796</string>
<key>CFBundleIdentifier</key>
<string>com.apple.kext.AMDFramebuffer</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>AMD Framebuffer</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>1.28.29</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>1.2.8</string>
<key>DTCompiler</key>
<string>com.apple.compilers.llvm.clang.1_0</string>
<key>DTPlatformBuild</key>
<string>6A280m</string>
<key>DTPlatformVersion</key>
<string>GM</string>
<key>DTSDKBuild</key>
<string>14A359</string>
<key>DTSDKName</key>
<string>macosx10.10internal</string>
<key>DTXcode</key>
<string>0600</string>
<key>DTXcodeBuild</key>
<string>6A280m</string>
<key>IOKitPersonalities</key>
<dict>
<key>Framebuffer_Personality</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.kext.AMDFramebuffer</string>
<key>IOClass</key>
<string>AMDFramebuffer</string>
<key>IOMatchCategory</key>
<string>IOFramebuffer</string>
<key>IONameMatch</key>
<string>display</string>
<key>IOProbeScore</key>
<integer>65050</integer>
<key>IOProviderClass</key>
<string>AtiFbStub</string>
</dict>
</dict>
<key>OSBundleLibraries</key>
<dict>
<key>com.apple.iokit.IOACPIFamily</key>
<string>1.2</string>
<key>com.apple.iokit.IOGraphicsFamily</key>
<string>1.3</string>
<key>com.apple.iokit.IOPCIFamily</key>
<string>1.2</string>
<key>com.apple.kext.AMDSupport</key>
<string>1.2.8</string>
<key>com.apple.kpi.bsd</key>
<string>8.0.0</string>
<key>com.apple.kpi.iokit</key>
<string>8.0.0</string>
<key>com.apple.kpi.libkern</key>
<string>8.0.0</string>
<key>com.apple.kpi.mach</key>
<string>8.0.0</string>
<key>com.apple.kpi.unsupported</key>
<string>8.0.0</string>
</dict>
<key>OSBundleRequired</key>
<string>Safe Boot</string>
</dict>
</plist>
 
 
where should i add my FB Personalities to get the HDMI to work ... Thanks in advance :)

Share this post


Link to post
Share on other sites

Thanks for the tutorial! I always wanted to know how you made your driver packs. I'm happy I can do it myself now if needed.

However, I have an Asus 270 (non-X) and have some questions about some things that were not entirely clear from your guide:

 

- I understand the device id for the 270X is already in AMD7000Controller but the one for the 270 is not. I guess I can add it manually, but I was wondering if there was an update-proof way? What if I use clover's fakeid feature to set it to the 270X id (the hardware is very similar, no?). Will this work or will things go wrong.

 

- Do I still need to enable the "Inject ATI" feature in Clover? What does it do anyway... 

 

- Do I still need something like ATYinjector.kext from your original pack? What was its purpose, is it the same as the Clover Inject ATI? I always assumed if your id was in the kext the driver would be loaded and if the framebuffer is correct it would work. But apparently you needed this for the 270X so I'm curious what it does.

 

I was hoping you could help me figure out these details so I can get my 270 working with your method.

Thanks again!

Share this post


Link to post
Share on other sites

i dont understan in step 3,, 

where you get this code ? --- = First I’ll put the list of all types of connectors:

 

Connector Type LVDS 0 × 00000002 = 02 00 00 00 Note: Laptop Monitor

Connector Type DVIDL 0 × 00000004 = 04 00 00 00 Note: Dual Link DVI

Connector Type VGA 0 × 00000010 = 10 00 00 00

Connector Type SV 0 × 00000080 = 08 00 00 00

Connector Type DP = 0 × 00000400 00 04 00 00

Connector Type HDMI 0 × 00000800 = 00 08 00 00

Connector Type DVISL 0 × 00000200 = 00 02 00 00 Note: Single Link DVI

Those lines represents definitions of all connectors inside the code. This is just example or explanation so that you know what is what! 

 

Thanks for the tutorial! I always wanted to know how you made your driver packs. I'm happy I can do it myself now if needed.

However, I have an Asus 270 (non-X) and have some questions about some things that were not entirely clear from your guide:

 

- I understand the device id for the 270X is already in AMD7000Controller but the one for the 270 is not. I guess I can add it manually, but I was wondering if there was an update-proof way? What if I use clover's fakeid feature to set it to the 270X id (the hardware is very similar, no?). Will this work or will things go wrong.

 

- Do I still need to enable the "Inject ATI" feature in Clover? What does it do anyway... 

 

- Do I still need something like ATYinjector.kext from your original pack? What was its purpose, is it the same as the Clover Inject ATI? I always assumed if your id was in the kext the driver would be loaded and if the framebuffer is correct it would work. But apparently you needed this for the 270X so I'm curious what it does.

 

I was hoping you could help me figure out these details so I can get my 270 working with your method.

Thanks again!

 

1. Clover should do the trick with fake serial number, but you'll need to patch kexts too (AMD7000Controller.kext and AMDRadeonX4000.kext). Check the Step - 4 in this tutorial.

 

2. Yes. This option injects proper FB + in your case fake serial number

 

3. No. You don't need ATYInjector.kext from the pack. Inject ATI option via Clover do the same thing, so you don't need it.

Share this post


Link to post
Share on other sites

Thanks for this topic!

 

I have a XFX DD 270X on 10.9.5. I was using the default radeon FB, but was unable to get 2560x1440 DVI DL display+ 1920x1080 DVI/HDMI display working with it.

 

Loading FB via DSDT and can confirm it is loading.

 

Why can I not get my Dual-Link DVI working at full resolution? See below. Thanks!

Is it possible to get my mini-DPs working? Any ideas?

 

 

 

I have edited Futomaki to the following:

 

00 04 00 00 04 03 00 00 00 01 03 01 12 04 01 01 :: Not working mini-DP (tested with single-link active mini-DP to DVI cable)

00 08 00 00 04 02 00 00 00 01 02 00 11 02 03 03 :: Fully working HDMI

04 00 00 00 14 02 00 00 00 01 01 01 10 00 04 06 :: Dual Link DVI-I (only working as single-link; if I plug in my dual-link DVI then screen stays black, but IOreg shows attached display here)

00 02 00 00 14 00 00 00 00 01 05 00 21 03 06 05 :: Fully Working Single Link DVI-D

 

 

Not using:

00 04 00 00 04 03 00 00 00 01 04 01 22 05 02 02 :: Another DP (did not work when tried it earlier)

04 00 00 00 14 02 00 00 00 01 01 01 00 10 05 06 :: Dual Link DVI-I Internal KLDSCP_DAC1

 

 

EDIT:

Switched Futomaki to:

04 00 00 00 14 02 00 00 00 01 01 01 00 10 05 06 :: Dual Link DVI-I Internal KLDSCP_DAC1

00 08 00 00 04 02 00 00 00 01 02 00 11 02 03 03 :: HDMI no longer hotplugs, but will work as second monitor with the Dual-Link DVI plugged in!

04 00 00 00 14 02 00 00 00 01 01 01 10 00 04 06 :: Dual Link DVI-I (Now works as Dual-Link DVI-I if replugged after loading OS X) 

00 02 00 00 14 00 00 00 00 01 05 00 21 03 06 05 :: Single Link DVI-D no longer hotplugs, does not work at all with Dual-Link DVI plugged in and prevents Dual-Link DVI from showing anything.

 

 

 

 

radeon BIOS

PCI ID: 1002:6810
Connector at index 0
Type [@offset 43056]: DisplayPort (10)
Encoder [@offset 43060]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 43184]: 0x90, OSX senseid: 0x1
Connector at index 1
Type [@offset 43066]: DisplayPort (10)
Encoder [@offset 43070]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 43211]: 0x91, OSX senseid: 0x2
Connector at index 2
Type [@offset 43076]: HDMI-A (11)
Encoder [@offset 43080]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 43238]: 0x92, OSX senseid: 0x3
Connector at index 3
Type [@offset 43086]: DVI-I (2)
Encoder [@offset 43090]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 43275]: 0x95, OSX senseid: 0x6
Connector at index 4
Type [@offset 43096]: DVI-I (2)
Encoder [@offset 43100]: INTERNAL_KLDSCP_DAC1 (0x15)
i2cid [@offset 43275]: 0x95, OSX senseid: 0x6
Connector at index 5
Type [@offset 43106]: DVI-D (3)
Encoder [@offset 43110]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 43302]: 0x94, OSX senseid: 0x5
bash-3.2# ./redsock_bios_decoder < /Users/MacPro/Dropbox/XFX\ 270X\ Editing/XFX270X.rom 
270CDF22.W8 :

Redsock

Connector Object Id [19] which is [DISPLAY_PORT]
encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [19] which is [DISPLAY_PORT]
encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true
Connector Object Id [12] which is [HDMI_TYPE_A]
encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false
Connector Object Id [2] which is [DVI_I]
encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [2] which is [DVI_I]
encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
Connector Object Id [3] which is [DVI_D]
encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x21 [duallink 0x1] enc 0x3)] linkb: true

Share this post


Link to post
Share on other sites

Well, that was bittersweet.

 

I went back to a vanilla AMD7000Controller.kext out of curiosity and the DVI Dual Link + HDMI (or SL DVI) works OOB. Turns out my version of 223x chameleon was too old to make the default radeonFB work properly (I guess) =/

 

Installed 2510 and the defaultFB just works.

Share this post


Link to post
Share on other sites

I can't get the Radeon_bios_decode or redsock_bios_decode to work in terminal. I don't know what I'm doing wrong. But, I did look at the info.plist in the AMD7000Controller.kext package. it shows the following frame buffers and what appears to be 4 ports.

 

Z77N-WIFI, Sapphire r9 270x Vapor-X, 10.10.1, latest Chameleon w/DSDT

 

Hamachi

Ikura

IkuraS

Kani

KaniS

Maguro

MaguroS

Namako

 

It shows the same thing on my real iMac 12.1 Radeon 5750,  Hackintosh 10.9.5 backup, Hackintosh 10.10.1 current installation, also iMac 12,1 definition. I'm trying to patch my DSDT to fix the speed.

With 10.9.5 I get 2850 FPS in NovaBench and 1590 Lux. With 10.10.1 I get 701 FPS in NovaBench.

 

 

Share this post


Link to post
Share on other sites

I can't get the bios decoding files to work either, terminal gives me "Permission denied".

 

OSX will only boot if I have InjectATI enabled in Clover, and even then it finds the card properly, but reports it as 7MB in "About this Mac". If InjectATI is false, OSX starts the boot sequence, but then just reboots and repeats.

 

Any help for an XFX R9 270x Double D would be appreciated. System details in signature

Share this post


Link to post
Share on other sites

Vlada- Thank you for the post.

 

But Im a little slow on this stuff. If you have a bit of time and feel like checking my calculation I thank you more. Or anyone else that knows and is quicker.

 

Last login: Wed Jan 28 17:30:45 on console

Bee11islands-iMac:~ bee11island$ /Users/bee11island/Downloads/Decoders/radeon_bios_decode < /Users/bee11island/Desktop/Tahiti.rom 

ATOM BIOS Rom: 

SubsystemVendorID: 0x174b SubsystemID: 0x3001

IOBaseAddress: 0x0000

Filename: 249L0C00.U46

BIOS Bootup Message: 

Tahiti B0 XTL C38650 GDDR5 3GB 500e/150m                                    

 

PCI ID: 1002:6798

Connector at index 0

Type [@offset 43578]: DisplayPort (10)

Encoder [@offset 43582]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 43696]: 0x90, OSX senseid: 0x1

Connector at index 1

Type [@offset 43588]: HDMI-A (11)

Encoder [@offset 43592]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 43723]: 0x91, OSX senseid: 0x2

Connector at index 2

Type [@offset 43598]: DVI-D (3)

Encoder [@offset 43602]: INTERNAL_UNIPHY1 (0x20)

i2cid [@offset 43750]: 0x92, OSX senseid: 0x3

Connector at index 3

Type [@offset 43608]: DVI-I (2)

Encoder [@offset 43612]: INTERNAL_UNIPHY (0x1e)

i2cid [@offset 43787]: 0x95, OSX senseid: 0x6

Connector at index 4

Type [@offset 43618]: DVI-I (2)

Encoder [@offset 43622]: INTERNAL_KLDSCP_DAC1 (0x15)

i2cid [@offset 43787]: 0x95, OSX senseid: 0x6

Bee11islands-iMac:~ bee11island$ /Users/bee11island/Downloads/Decoders/redsock_bios_decoder < /Users/bee11island/Desktop/Tahiti.rom 

249L0C00.U46:

 

Tahiti B0 XTL C38650 GDDR5 3GB 500e/150m                                    

 

Subsystem Vendor ID: 174b

       Subsystem ID: 3001

Object Header Structure Size: 384

Connector Object Table Offset: 48

Router Object Table Offset: 0

Encoder Object Table Offset: 118

Display Path Table Offset: 12

Connector Object Id [19] which is [DISPLAY_PORT]

encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false

Connector Object Id [12] which is [HDMI_TYPE_A]

encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true

Connector Object Id [4] which is [DVI_D]

encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false

Connector Object Id [2] which is [DVI_I]

encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false

Connector Object Id [2] which is [DVI_I]

encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false

Bee11islands-iMac:~ bee11island$ 

 

 

Futomaki 

 

00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 - DP

00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 - DP

04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 - DVI-DL

00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 - HDMI

 

patched

 

00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01 - DP

00 02 00 00 04 02 00 00 00 01 01 01 10 00 04 06 - DVI-I

04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 03 - DVI-D

00 08 00 00 04 02 00 00 00 01 04 00 22 05 02 02 - HDMI

 

 

 

Share this post


Link to post
Share on other sites

Well almost correct, but the order is wrong. You mast have 1,2,3,4 or you can switch all to zero. So change these parameters by picking one of two solutions...

 

00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01 - DP

00 02 00 00 04 02 00 00 00 01 01 01 10 00 04 06 - DVI-I

04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 03 - DVI-D

00 08 00 00 04 02 00 00 00 01 04 00 22 05 02 02 - HDMI

 

1st solution

 

00 04 00 00 04 03 00 00 00 01 04 01 12 04 01 01 - DP

00 02 00 00 04 02 00 00 00 01 01 01 10 00 04 06 - DVI-I

04 00 00 00 14 02 00 00 00 01 02 00 11 02 03 03 - DVI-D

00 08 00 00 04 02 00 00 00 01 03 00 22 05 02 02 - HDMI

 

2nd solution 

 

00 04 00 00 04 03 00 00 00 01 00 00 12 04 01 01 - DP

00 02 00 00 04 02 00 00 00 01 00 00 10 00 04 06 - DVI-I

04 00 00 00 14 02 00 00 00 01 00 00 11 02 03 03 - DVI-D

00 08 00 00 04 02 00 00 00 01 00 00 22 05 02 02 - HDMI

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By Fede1132
      Hi guys i have a problem install macOs Mojave on my PC, I have this configuration:

      CPU: Ryzen 7 2700X;
      GPU1: GTX 970 Strix(For game rendering and 144Hz Monitor);
      GPU2: GTX 750ti Strix(For 2nd monitor rendering to get 100% performances from 1st 144Hz Monitor);
      MotherBoard: MSI x470 GAMING PLUS
      Hard Disk 1 (Windows 10): Samsung EVO M.2;
      Hard Disk 2 (For Storage): RAID (1) between two hard disks;
      Hard Disk 3 (For Mojave): Kingston SSD 120GB;

      I have created my USB with this:
       
      Create Bootable USB Code: sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB -- /Applications/Install\ macOS\ Mojave.app -- nointeract && say Done. Clover Settings: Boot: Verbose; dart=0; nv_disable=0; kext-dev-mode=1; GraphicsEnabler=No; XMPDetection = No. Cpu: C6. Devices: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Inject (Full Enabled); Add ClockID (Full Enabled); FixOwnership (Full Enabled); Gui: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Enabled (Full Enabled); Screen Resolution: 1920x1080; Kernel and Kext Patches: (Not Enabled = [ ] - Enabled = [-] - Full Enabled [✓]) Apple RTC (Full Enabled); KernelPm (Full Enabled); SMBIOS: iMac(18,3); System Parameters: Inject Kexts = Yes; Inject System ID; Used Kexts: FakeSMC FakePCIID NVIDIA WEB LILU BIOS: VT-d = Disabled; XHCI Hand-Off = Enabled; Legacy USB Support: Enabled; Hard Disk: AHCI Mode; Selection Mode: Legacy + EUFI; Clover Install Log:
      Full Error Log:
       
    • By corbrink
      Hi,
      I have the following system:
      - Gigabyte Z370M-D3H M-ATX
      - Core i7-8700K Coffee Lake
      - Gigabyte Radeon RX 560 4GB
      - Crucial Ballistix 16GB DDR4
      - 960 EVO 1TB NVMe SSD
      - 850 EVO 500GB SSD
      - Crucial 500GB SSD
      - The 2 500GB SSD's run in Raid for data storage.
      - Western Digital 3TB HDD - Time machine
      - EFI here (too large to attach): EFI.zip

      Questions:
      1. I have a dual screen running from Radeon card, 1 on DP and 1 on HDMI. The one screen on DP goes randomly blank from time to time. Any ideas?
      2. I've read that the kexts should preferably be installed in /library/extensions. I would like to know what kexts should remain in the EFI. I read that you should install FakeSMC in both locations (EFI and L/E). If I follow this route must I change something in the config.plist?
      3. USB info in System Information (attached does not seem correct. I've followed the changes suggested but I'm not sure if this is the best it can be.
      4. Are there something in the EFI and config.plist I don't need or doing wrong?

      Feedback will be appreciated.


    • By 1Ale1
      Ciao a tutti, ultimamente ho deciso di mettermi al lavoro e fare un investimento a lungo termine comprando un fisso che ho assemblato pezzo dopo pezzo leggendo numerosi forum per essere bene informato sul miglior hardware che potessi ottenere per un Hackintosh ottimizzando al meglio i costi: ho finito così per comprare:
       
      Hardware:
       
       
      -Motherboard: Gigabyte Z390 Aorus Pro (Rev 1.0)
      -CPU: Intel i7 9700k raffreddato a liquido (CoffeLake)
      -GPU: AMD Radeon RX580 (avendo letto le eccellenti prestazioni a ottimo prezzo per MacOS)
      -RAM: 32GB DDR4 Crucial Ballistix Sport LT (4x8GB 3000MHz)
      -NVMe SSD Samsung 970 Evo 250GB M.2 dedicato solo a MacOS, nel secondo slot della Mobo M.2 avrei poi messo un Western Digital Blue da 250GB con Windows 10 su metà disco e per l'altra metà il Debian che sto utilizzando adesso
       
       
      Poi mi sono messo subito al lavoro per cercare di far partire questo benedetto MacOs su una macchina non ufficiale, ho tovato quindi questa guida su GitHub che era molto simile alla mia configurazione:
       
      https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md
       
      Dopo aver fatto partire una macchina virtuale per configurare la USB come comunemente viene fatto, scaricando l'applicazione e facendo il "burn/copia dei file" di macOS su pennetta esterna rendendola bootabile solamente da un pc ufficiale mac, sono passato alla configurazione di Clover (l'EFI installer, cartella che allegherò qui sotto, ma prima leggete il problema): Ho messo i driver necessari, mettendo quelli che lui menzionava sotto la sezione "building the usb installer"
       
      https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/building-the-usb-installer
       
       
      Install Clover for UEFI booting only
      Install Clover to the ESP
      Under Drivers64UEFI:
      AptioMemoryFix (the new hotness that includes NVRAM fixes, as well as better memory management) (che poi ho dovuto rimuovere, leggi sezione https://github.com/cmer/gigabyte-z390-aorus-master-hackintosh/blob/master/STEP_BY_STEP.md#fixing-kernel-panics-at-rebootshutdown)
      VBoxHfs-64.efi (or HFSPlus.efi if available) - one of these is required for Clover to see and boot HFS+ volumes. If you see the option to enable it in the installer, make sure it's selected - if you don't see it in the installer, verify that one of them exists in the EFI -> CLOVER -> drivers64UEFI folder
      ApfsDriverLoader - (Available in Dids' Clover builds - or here) this allows Clover to see and boot from APFS volumes by loading apfs.efi from ApfsContainer located on block device (if using AptioMemoryFix as well, requires R21 or newer)
       
      applicando piccole modifiche a causa di un errore già riportato da questa persona che ha scritto la guida di GitHub di sostituire AptioMemoryFix-64 (dalla cartella EFI/EFI/CLOVER/driver64UEFI) con OsxAptioFix2Drv-free2000, questa infatti riportava  quanto segue dopo aver detto di aver sostituito AptioMemoryFix-64.efi con OsxaptioFix2Drv-free2000:
       
      "I am told that there are downsides (that I don't fully understand yet) to using OsxAptioFix2Drv-free2000, so do this at your own risk."
       
      Ho configurato poi il config.plist
       
      Come diceva lui, partendo da questo file: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/config.plist-per-hardware/coffee-lake e applicando le modifiche che sotto ha descritto, del tipo:
       
      Open coffeelake_sample_config.plist with Clover Configurator (right click → Open With → Clover Configurator)   In SMBIOS: - Click the button with an up/down arrow (middle right). Chose iMac18,3. This is important since we'll be connecting our monitor to the RX580. The HDMI port on our motherboard is NOT yet working for Hackintoshes. - Make sure the serial number generated is an iMac (mid-2017) by clicking Model Lookup. - Ensure that Check Coverage reports that the serial is NOT valid. You don't want to use somebody else's serial number. - While you're here, copy your Board Serial Number to your clipboard. You'll need it soon.
      In Rt Variables: Paste your Board Serial Number in the MLB field. Set CsrActiveConfig to 0x0 which enables SIP for extra security. This should work just fine for a Vanilla Hackintosh install and is how genuine Macs ship. In Boot: Change the Custom Flags to: shikigva=40 uia_exclude=HS14 (this disables onboard Bluetooth since we'll be using an external Broadcom Wi-Fi/Bluetooth adapter) In ACPI: Click List of Patches and enable the following: Change GFX0 to IGPU In Devices: Set Inject to 16. Now to enable our headless iGPU, we need to fake the device id. To do so, Click Properties, select PciRoot(0x0)/Pci(0x2,0x0). Then, click the + button to add a property. Add the following: Property Key: device-id Property Value: 923E0000 Value Type: DATA Click the Export Configuration button (bottom left), then Save As config.plist. Copy your newly generated config.plist to /EFI/CLOVER/ on your bootable USB key.  
      Impostazioni BIOS
       
      E avendo settato nel BIOS le impostazioni che questa perona configliava all'inizio della guida,                       (N.B. la mia versione di Bios è l'ultima, F7 https://www.gigabyte.com/Motherboard/Z390-AORUS-PRO-rev-10#support-dl-bios) (a quanto risulta il giorno 7.01.2019)
       
      Load Optimized Default Settings Peripherals → USB Configuration → XHCI Hand-off : Enabled Chipset → Internal Graphics : Enabled (important for Quicklook/Preview) Please note that we will be using our internal GPU in headless mode only and this guide assumes that. This is how an iMac18,3 (what we're basing our build on) behaves. That's it! I literally didn't change anything else and it just worked.
       
      Anche per me ha funzionato. Comunque lui riportava ulteriori settaggi, aggiungendo:
       
      However, these are settings that are generally recommended. Your mileage may vary:
       
      BIOS → Fast Boot : Disabled BIOS → LAN PXE Boot Option ROM : Disabled BIOS → Storage Boot Option Control : UEFI Peripherals → Trusted Computing → Security Device Support : Disable Peripherals → Network Stack Configuration → Network Stack : Disabled Peripherals → USB Configuration → Legacy USB Support : Auto Peripherals → USB Configuration → XHCI Hand-off : Enabled (Extremely important) () Chipset → Vt-d : Disabled (non l'ho messo e parte a volte, quindi penso che se parte non ha una importanza così rilevante) Chipset → Wake on LAN Enable : Disabled (era già così) Chipset → IOAPIC 24-119 Entries : Enabled  
       
      Il sistema è partito e soltanto alcune volte dava il seguente errore:
       
      Error allocating 0x11996pages at 0x000000001d453000 alloc type 2
      Couldn't allocate runtime area.
       
      Credo che sia questo piccolo problema: la NVRAM.
      Non riesco bene a capire dove cercare per sapere con esattezza se è supportato nativamente o meno. Ho cercato di informarmi, voi potreste dirmi se è vero?
      Premendo poi Ctrl+Alt+Canc riavviavo e selezionando da Clover l'NVMe interno partiva senza dare questo errore, per cui il kernel non trova spazio perché la memoria Non Volatile ad accesso Randomico è troppo frammentata, come
       
      Questa guida riportava:
       
      Primo post:
      https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
       
      Post aggiornato nel 2016:
      https://nickwoodhams.com/x99-hackintosh-osxaptiofixdrv-allocaterelocblock-error-update/
       
      Mi sono letto tutto e ho capito che lui applicava anche delle modifiche al file: "Changes to OsxLowMemFixDrv-64.efi were simply editing 0x10000000 to 0x20000000."
       
      Ho quindi seguito il suo consiglio di mettere OsxAptiofix Emuvariable 64 e Test2-2016.efi (che lui aveva creato) ma il problema sembrava persistere, più raramente
       
      La mia cartella driver64UEFI di ora
       
      Dopo aver trovato una strada senza soluzoni anche lì mi sono rivolto a degli amici, e di questo errore ne ho parlato anche con utenti del gruppo Telegram "Hackintosh Italia" che sono stati e ancora sono molto gentili ad aiutarmi spiegandomi che si tratta di un problema di NVRAM, che nel mio caso, avendo installato questi .efi file nella cartella EFI/EFI/CLOVER/driver64UEFI (che ancora è cosi attualmente, oscillando tra couldnt allocate runtime area (anche dopo aver definitivamente staccato la corrente dopo aver spento il PC per capire se poteva aiutare) e a volta anche nessun errore)
       
       
      -ApfsDriverLoader-64.efi
      -DataHubDxe-64.efi
      -EmuVariableUefi-64.efi
      -FSInject-64.efi
      -HFSPlus-64.efi
      -NTFS-64.efi
      -NvmExpressDxe-64.efi
      -OsxAptioFix2Drv-free2000.efi
      -PartitionDxe-64.efi
      -UsbKbDxe-64.efi
       
      In più ho aggiunto gli RC Scripts (come mi è stato consigliato dai membri del gruppo telegram) sul disco interno in cui mac è installato.
       
      Togliendo quindi qualsiasi test.efi o test2- 2016.efi ed ascoltando chi ne sapeva di più. Ora mi trovo a dover affrontare diverse volte questo errore dovendo riavviare per risolverlo, cosa che mi fa dedurre che Osxaptiofix2 2000 sia un po' instabile nel pulire la NVRAM prima di avviare la macchina/ allo spegnimento di questa.
      Questo problema di couldnt allocate runtime area persiste sebbene prema F12 dalla schermata di Boot di Clover.
       
      Vi chiedo gentilmente una mano, inoltre mi è stato detto che siccome il sistema da:
       
      -"3.6 GHz unknown nella sezione "Processor"
      -non riconosce la RAM con un Vendor ID? (del tipo Ballistix dovrebbe essere?)
       
       
      Serve di rivedere il config.plist che ho creato, rivedere i DSDT e gli efi? sono a posto?, (mi hanno detto che gengik84 fare, ma accolgo volentieri l'aiuto di tutti) ,  vi mando una foto della schermata di "About this Mac" e della EFI in allegato. Quello che farò sicuramente mentre attendo vostre risposte è il downgrade da 10.14.3 Beta a 10.14.2, l'upgrade l'ho fatto pensando che magari avrei aggiustato qualcosa, ma l'errore come lo dava prima lo dà ora, non credo che questo cambi molto le cose in gioco. Comunque è meglio non essere in Beta per aggiustare gli errori.
       
       
      Grazie mille per essere arrivato a leggere fino a questo punto, lo apprezzo molto.
       
       
      Per la cartella EFI: sono 22MB zippati, in allegato non entrano...
       
      https://drive.google.com/open?id=106jXkDB0Id045lzIIzAn9F5MwnzWFv3X
       

       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       

       
       
       
       



×