Jump to content
Vlada.

[HOW TO] Modification of AMD FB + Clover injection

387 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 verymilan
      Hi, i recently set up High Sierra on my AMD computer with the help of the amdosx community (i actually used an installer just to confirm that something would work in the first place before i spend hours for nothing, i can and could have downloaded High Sierra the "legal" way).
      However the graphicscard is recognized properly, the 6gig are recognized and i have no artifacts and no screen tearing with the official nvidia webdriver,
      but unfortunally, dark colors have horizontal dark stripes in them and specific bright colors like on left bar of system windows such as settings do flicker like low fps.

      I only used the clover on the flash drive for now and i'd like if it's worth digging deeper of if i should just forget about it as it is a common nvidia problem on macOS.
      Would be amazing to know.
       
      Closer machine infos:
      * High Sierra (misses a recent minor patch as my network is veeeery slow and i got this nvidia issue anyway so i mainly jumped back to linux)
      * AMD fx8350
      * Asus Sabertooth 990fx Ref. 2.0
      * NVIDIA GeForce GTX 1060 6GB
       
    • By hackintosh_builder
      Hello, I am interested in building a Hackintosh using Threadripper. Could you please recommend good motherboard(s)? Is there one that is fully compatible with the Hackintosh?
    • By zeg66
      Please help me with this 10.9.5 system. Motherboard: Gigabyte 965p-s3 rev3.3, gpu: Ati Radeon HD6450 (dvi/hdmi/vga). 
      Using any of the 3 ports on the 6450 (dvi, hdmi, vga), I see all the white letters on black background during boot but when they complete and it's time for the graphics to start I get a black screen and sometimes a restart after that. Using Clover 4411. Is there any way to get past this?
    • By abhinav
      How to install macOS 10.13 High Sierra in Vmware Workstation 14 Pro on AMD Machine
      Unlocker cmd already installed for vmware workstation 14
      vmx file edited...added smc.version="0"
       
      My System Specs
      AMD FX8120 8 Core
      Corsair Vengeance 32 GB DDR3 RAM
      Asus 990FX Sabertooth Motherboard
      Sandisk Ultra II 480 GB SSD SATA 3
      Asus STRIX 960 GTX 4 GB DCU II Model Pixel Shader 5 DirectX 12 Support
       
      Virtual Machine Specs
      16 GB RAM
      2 processors and 4 cores = 8 core processor
      SATA hard drive
      128 MB video memory

    • By M1GU5L
      Last year i tried to install Sierra but after installing it keped booting to a black screen, now i want to try with high sierra but i dont know what i have to do to get this to work.
      I heard about the whatevergreen and lilu kexts but i dont know what to do with them, can anyone help me solving this?

      my pc specs

      Intel Core i5-4460 3.20 GHz with iGPU Intel HD Graphics 4600
      Asus H81M-A
      8GB RAM Kingston Hyper x 1600 mhz
      Asus Strix R9 380 4GB
×