Jump to content
Vlada.

[HOW TO] Modification of AMD FB + Clover injection

411 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 BlitzPanzer
      Catalina 10.15.3, OC 0.5.5

      Follow the OpenCore AMD Vanilla Guide, everything works fine iMessage, Siri, FaceTime, Continuity, Airdrop, Audio, WiFi
      But here is the problem
      Once I restart or shutdown and reboot, I will have kernel panic, so i have to reboot once again, then no more kernel panic, straight back to the system.
      Down below are the 3 kernel panic reports I got after I am back to the system, also provided specs, kexts, drivers and config.plist I used.
      Please someone help me with the problem
      Thanks in advanced   

      System Specs
      CPU: Ryzen R5 3600
      MOBO: MSI B450 Mortar Max
      RAM: Kingston HyperX Fury 16GB*2 3200MHz DDR4
      SSD: Kingston A2000 500GB NVMe PCIe
      GPU: Gigabyte RX 570 Gaming 4G v2.0
      PCIe: BCM943602CS Kexts:
      AppleALC
      AppleMCEReporterDisabler
      BrcmBluetoothInjector
      BrcmPatchRAM3
      HDMIAudio
      Lilu
      MacProMemoryNotificationDisabler
      NightShiftUnlocker
      NVMeFix
      RealtekRTL8111
      VirtualSMC
      WhateverGreen Drivers:
      ApfsDriverLoader
      AppleUsbKbDxe
      FwRuntimeServices
      VBoxHfs config.plist:
      https://drive.google.com/file/d/1M22Tvn7W-Zf_b_-J52oLcfjECj5qAcp6/view

      Kernel Panic Report 1
      panic(cpu 0 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9f212fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffa3ce87c000, CR3: 0x00000000263ba000, CR4: 0x00000000003406e0 RAX: 0xffffffa3ce87c000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffffa3ce75bb60, RBP: 0xffffffa3ce75bb80, RSI: 0xffffff806d3141c0, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805cc7c900, R13: 0xffffff835806f000, R14: 0x0000000000000000, R15: 0xffffff8068d2da50 RFL: 0x0000000000010246, RIP: 0xffffff7f9f212fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffa3ce87c000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffa3ce75b5c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffffa3ce75b610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffffa3ce75b650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffffa3ce75b6a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75b6c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffffa3ce75b7c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffffa3ce75b810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffffa3ce75b880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffffa3ce75ba00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffffa3ce75ba50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75ba70 : 0xffffff7f9f212fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffffa3ce75bb80 : 0xffffff7f9f24a795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffffa3ce75bba0 : 0xffffff7f9f212ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffffa3ce75bbe0 : 0xffffff7f9f2325c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffffa3ce75bc30 : 0xffffff7f9f1b8adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffffa3ce75bc70 : 0xffffff7f9f1b64be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffffa3ce75bd00 : 0xffffff7f9f128534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffffa3ce75bd80 : 0xffffff7f9f1b488e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffffa3ce75bde0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffffa3ce75be40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffffa3ce75bef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffffa3ce75bf50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffffa3ce75bfa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000->0xffffff7f9f1b2fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c185000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c228000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9f1b3000->0xffffff7f9f6f7fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 47565362999  
      Kernel Panic Report 2
      panic(cpu 10 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9e629fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d25d2000, CR3: 0x0000000029068000, CR4: 0x00000000003406e0 RAX: 0xffffff83d25d2000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d14c3b60, RBP: 0xffffff83d14c3b80, RSI: 0xffffff805f6adb80, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805fba2580, R13: 0xffffff835b02e000, R14: 0x0000000000000000, R15: 0xffffff80631191e0 RFL: 0x0000000000010246, RIP: 0xffffff7f9e629fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff83d25d2000, Error code: 0x0000000000000002, Fault CPU: 0xa, PL: 0, VF: 1 Backtrace (CPU 10), Frame : Return Address 0xffffff83d14c35c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d14c3610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d14c3650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d14c36a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c36c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d14c37c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d14c3810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffff83d14c3880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d14c3a00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d14c3a50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c3a70 : 0xffffff7f9e629fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d14c3b80 : 0xffffff7f9e661795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d14c3ba0 : 0xffffff7f9e629ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d14c3be0 : 0xffffff7f9e6495c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d14c3c30 : 0xffffff7f9e5cfadb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d14c3c70 : 0xffffff7f9e5cd4be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d14c3d00 : 0xffffff7f9e52a534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d14c3d80 : 0xffffff7f9e5cb88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d14c3de0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d14c3e40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d14c3ef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d14c3f50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d14c3fa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000->0xffffff7f9e5b5fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c3f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c09f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9e5ca000->0xffffff7f9eb0efff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 38416992755  
      Kernel Panic Report 3
      panic(cpu 8 caller 0xffffff801da652fa): Kernel trap at 0xffffff7fa084dfe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d44cd000, CR3: 0x000000002b260000, CR4: 0x00000000003406e0 RAX: 0xffffff83d44cd000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d319bb60, RBP: 0xffffff83d319bb80, RSI: 0xffffff8066659c00, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff8061f35280, R13: 0xffffff835d231000, R14: 0x0000000000000000, R15: 0xffffff806189db90 RFL: 0x0000000000010246, RIP: 0xffffff7fa084dfe3, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0xffffff83d44cd000, Error code: 0x0000000000000002, Fault CPU: 0x8, PL: 0, VF: 1 Backtrace (CPU 8), Frame : Return Address 0xffffff83d319b5c0 : 0xffffff801d93bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d319b610 : 0xffffff801da734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d319b650 : 0xffffff801da64f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d319b6a0 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319b6c0 : 0xffffff801d93b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d319b7c0 : 0xffffff801d93b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d319b810 : 0xffffff801e0d2aa9 mach_kernel : _panic + 0x61 0xffffff83d319b880 : 0xffffff801da652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d319ba00 : 0xffffff801da64ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d319ba50 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319ba70 : 0xffffff7fa084dfe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d319bb80 : 0xffffff7fa0885795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d319bba0 : 0xffffff7fa084def0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d319bbe0 : 0xffffff7fa086d5c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d319bc30 : 0xffffff7fa07f3adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d319bc70 : 0xffffff7fa07f14be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d319bd00 : 0xffffff7fa074e534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d319bd80 : 0xffffff7fa07ef88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d319bde0 : 0xffffff801e01b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d319be40 : 0xffffff801e01adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d319bef0 : 0xffffff801e01a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d319bf50 : 0xffffff801e01c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d319bfa0 : 0xffffff801d8e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000->0xffffff7fa07d9fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9e5f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9e29f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7fa07ee000->0xffffff7fa0d32fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001d600000 Kernel text base: 0xffffff801d800000 __HIB text base: 0xffffff801d700000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 27776834167  
      config.plist
    • By NoEnd
      Hi team,
       
      I'm looking for the best route to achieve this upgrade, so I have been stuck with HS since Nvidia drivers stopped being supported on newer MacOS releases. Now I'm having an AMD 5700 xt on the way and want to plan the upgrade properly. I have added some information below and questions that might help with your recommendation.
       
      Current GPU 1080 ti with Nvidia webdrivers installed. So should I uninstall the webdriver before adding the new GPU? Clover is being used and EFI attached. Any kext must be removed? or parameters adjusted MacOS HS 10.13.6, should I upgrade before using the new GPU? CPU: 9900K Motherboard:ROG MAXIMUS XI HERO (WI-FI) Dual Monitors I have a Time machine backup, Do you recommend a fresh install? and If I did, will I be able to restore my data/apps as-is?  
      Please let yourself free to explore further aspects to considers.
      EFI-20200204.zip
    • By neoskateur
      Hello team!

      I have a small issue wiith my RX580 MSI on High Sierra, only one DP is working, no hdmi... Any clue?

      Supermicro X8DTL-6F
      2 x Xeon X5650
      RX580 MSI
    • By marras
      Hi, I've an old machine (see the signature) that I want to use for xcode , when I'm too lazy to take my macbook pro. I tried install Sierra, and worked surprisingly well, but sadly it doesn't support the latest version of xcode. I tried to update to High Sierra, but in the first boot everything goes black. So I tried a clean install, and had the same result. Tried Mojave with the telemetry plugin hack (as I've not SSSE 4.2), and the installation went smooth, but in the first login, I've a mouse pointer (which moves!) over a blinking screen, gray and black, and seems stuck. Tried several SMBIOS, changing the Display port, HDMI, LILU with WhateverGreen, but with these 2 the verbose freezes pretty soon (if needed I can make a screenshot). So I know that this card should work OOB, but I've also seen that several people had this problem, but honestly I didn't figured it out how to continue. My pc doesn't have any integrated gpu.
      Please help me, I'm stuck!
      Thank you
    • By gusbemacbe
      Hello,
       
      I am a former user of MacBook and Mac mini. Both died. One in 2014 and another last year.  I will think of giving my Hackintosh-compatible laptop to my brother that I purchased years ago, because he wants to play more than one computer, so he is a Twitch/YouTube streamer and a hardcore gamer and I will not need to lend him many times. If he wants, from my former laptop I will take only one 240GB SSD Samsung Evo with installed Arch Linux and leave one 500GB HDD for him. In the future, I will purchase a new Alienware laptop.
       
      As I got newly graduated, I moved to a new super PC with AMD Ryzen™ 7 2700X CPU and with NVIDIA GeForce™ 1660 Ti GPU. More details, you can see my signature below, that provides the complete details. I own an external SSD m.2 2280 with installed Windows 10.
       
      I will reconsider purchasing 4th drive – an external 480GB SSD m.2 2280 SATA WD Green 545MB/s or an external 1TB SSD SATA WD Green 545MB/s – for installing Hackintosh. But purchasing, I need to make sure.
       
      1. Is it worth to install Hackintosh on an external SSD m.2 2280? If I partition two partitions, one for Insansely's MyHack/Chameleon/Clover and another for Hackintosh and my new super-PC boot is natively BIOS and Grub, is it worth? Maybe I will try to install reFind on Arch Linux to replace the Grub if it is worth.
      2. I know that it will run on macOS High Sierra, Mojave and Catalina, but if I need Metal 2 to run the latest version of Sketch (the which I own an original licence) and of other apps the which I own original licences? Is NVIDIA GeForce™ 1660 Ti compatible with Metal 2?
      3. Since it be an external SSD, will I able to run Hackintosh as a portable OS in other computers?
       
       
×