Jump to content
wmchris

[GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation

1,606 posts in this topic

Recommended Posts

FYI, unsigned kext messages are normal.  It's a hackintosh it's going to have non-official kexts loading.

 

 

I’m on 10.13.3 now. I still can get my brightness controls to work.
Even after rebuilding the kernel caches.

I’m getting some complains about invalid signatures what appears to say it was allowed.

I did the commands from the guide to flush the kernel cache.
Any ideas on how to fix?

 

 

EDIT: I have  no idea what i've done. After a few flushes, the brightness control is working  again. I tried to allow unsigned code again through that spctl command. And after the last flush it seems to have fixed it. I'm not really sure.

 

Are there any advantages in going to the new Clover, also the github repo seems to have been updated with a few new things, something about nvram and aptio v3..... should i move to those?

Share this post


Link to post
Share on other sites
Advertisement

Hi Folks, seeking your advice if you will?

 

System: 9550, i7, 16gb, 4k screen, Toshiba SSD.   Install as per the GitHub repo, switching the SSD to 4k sectors, and following up with a Win10 dual-boot for games, though most of my work will be in OSX.

 

Audio - I left it 'as is', everything is fine through speakers, but I get corruption when using headphones plugged into the laptop (as expected).   None of the other options seemed particularly enticing (would rather audio disruption than kernel panics), but thought 'never mind, I'll use Bluetooth headphones'.

 

Having acquired a serviceable pair, which work perfectly with my phone, I think evening paired them with the laptop.  However, the end result isn't great (wired with corrpution is better).   They regularly (between 2 and 5 mins) disconnect, and when connected, more often than not, the sound is garbled.  When is is playing properly, it sounds great.

 

Any tips on what I should change?  System stability is priority number one, but after that, bluetooth audio trumps speaker audio if it's a trade off.

 

Many thanks.

 

Gavin.

Share this post


Link to post
Share on other sites

Hmm, they're fine on my phone and, having checked, in Win10 on the same machine, so seems to be specific to the headphone/OSX combination.

Anything I should try? or SOL?  I can't pick up a £300 pair of headphones on the off-chance it'll work ;-)

Share this post


Link to post
Share on other sites

Solved my issue:  It seems that, when connecting to a 2.4Ghz Wifi connection in OSX (not in Windows 10), my audio gets corrupted.  As soon as I switched over to a 5Ghz connection, everything was absolutely fine, so, I guess something in the card/driver is conflicting with itself.

Share this post


Link to post
Share on other sites

its not a conflict... this is normal behaviour with some bt hardware...

wifi and bt are interfering with each other. both are using 2,4ghz for transmission. it depends on quality of your used devices (router, headphones,...) and their transmission settings if the interference will be a mild side effect or a absolute non working disaster.

Share this post


Link to post
Share on other sites

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:

<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml and SSDT-XOSI.aml(thanks @goodwin_c) files inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. (Removed per author's request, if you want to know more about this version go here)

 

I2C.zip

Edited by hvolkoff
Changed attachment, removed VoodooI2C beta binary and added missing SSDT-XOSI.aml file

Share this post


Link to post
Share on other sites
15 hours ago, hvolkoff said:

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:


<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml file inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. 

I2C.zip

Could you share your IOReg with VoodooI2C working?

Share this post


Link to post
Share on other sites
19 hours ago, hvolkoff said:

So, my post was deleted due to the forum's recent changes...

Anyway, here is what you need to enable VoodooI2C on our machine (Better touchpad and touchscreen)

More info about VoodooI2C here (thanks @alexandred for the great work)

Add these two entries to Clover's config.plist at `ACPI > DSDT > Patches`:


<dict>
	<key>Comment</key>
	<string>change GPI0 device _STA to XSTA</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X1NUQQCgCZNTQlJHAA==</data>
	<key>Replace</key>
	<data>WFNUQQCgCZNTQlJHAA==</data>
</dict>
<dict>
	<key>Comment</key>
	<string>change I2C devices _CRS to XCRS</string>
	<key>Disabled</key>
	<false/>
	<key>Find</key>
	<data>X0NSUwCgDg==</data>
	<key>Replace</key>
	<data>WENSUwCgDg==</data>
</dict>

Copy the SSDT-I2CX.aml file inside the attached zip to `CLOVER > ACPI > patched`

Download the latest VoodooI2C.kext release (link) and copy both VoodooI2C.kext and VoodooI2CHID.kext files to Clover's kexts folder . The other files are not needed. (more info about them here)

Reboot and that's it.

Personally I think the performance of our's laptop touchpad is better using VoodooI2C.kext than with VoodooPS2Controller.kext. And the added gestures to the Touchscreen are a nice bonus.

P.S: Don't delete VoodooPS2Controller.kext, as it is still necessary for the keyboard to function and it is compatible with VoodooI2C.

P.S.S: Inside the attached zip I included a beta version of VoodooI2C.kext (10.13 only, based on this changes) that enable native gestures and settings for our touchpad (Just like Apple's Magic Trackpad). However this version is in current development and those willing to test should expect bugs. 

I2C.zip

Very nice, thank you for this! Do you happen to know if the pinning for the 9560 is the same?

Share this post


Link to post
Share on other sites
4 hours ago, goodwin_c said:

Thanks. That is what i was thinking - on my machine it didn't catch TPD1 device. Even, i don't see TPD1 in IOReg. Will try to debug ACPI to find out what is going on.

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Share this post


Link to post
Share on other sites
3 hours ago, wmchris said:

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Try to replace your SSDT-XOSI with next code:

DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    External (_SB.TBFP, MethodObj)
    External (USTP, UnknownObj)
    Name (CNT1, Zero)
    Method (XOSI, 1, NotSerialized)
    {
        CNT1++
        IF (CNT1 == 0x1)
        {
          \_SB.TBFP (One)
          USTP = One
        }
        Local0 = Package (0x0A)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2006.1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }
        Return ((Ones != Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}

This will:

- permanently enable TB controller (USB-C works like a charm :) )

- should make VoodooI2C attaching to TPD acpi device

Share this post


Link to post
Share on other sites

works well. thank you.

btw usb-c worked well before ;-)

@hvolkoff
does the voodooi2c native branch kext also mess up with your left click (not tap)?
most physical clicks are not recognized anymore on my system, but drag and drop works ... but sometimes doesnt register the clickUP event. dunno if configured something wrong or this is just a bug

Edited by wmchris

Share this post


Link to post
Share on other sites
7 hours ago, lebish said:

Very nice, thank you for this! Do you happen to know if the pinning for the 9560 is the same?

Hi, I don't know cause I don't have a 9560 and also don't have access to one's DSDT. But it may work, considering that some of my config is derived from @KNNSpeed's files, and I made very few changes to make them compatible with 9550.

5 hours ago, wmchris said:

same here, TPD* missing.

to be honest i'm a lil bit confused... i'm pretty sure the ELAN Touchscreen is connected with USB, not I2C...

Well... I got say that I don't understand much of how that works as well, hahaha. But, from our device DSDT you can see that in the _SB.PCI0.I2C1 bus there are two devices declared:

Scope (_SB.PCI0.I2C1) {
        Device (TPD1) {
            Name (HID2, Zero)
            Name (SBFB, ResourceTemplate () {
                I2cSerialBusV2 (0x002C, ControllerInitiated, 0x00061A80,
                    AddressingMode7Bit, "\\_SB.PCI0.I2C1",
                    0x00, ResourceConsumer, , Exclusive,
                )
            })
			
            ...
        }

        Device (TPL1) {
            Name (HID2, Zero)
            Name (SBFB, ResourceTemplate () {
                I2cSerialBusV2 (0x004C, ControllerInitiated, 0x00061A80,
                    AddressingMode7Bit, "\\_SB.PCI0.I2C1",
                    0x00, ResourceConsumer, _Y29, Exclusive,
                )
            })
	
            ...
		}

    ...
}

TPD1 is the touchpad
TPL1 should be the touchscreen

However if you check IOReg with VoodooI2C enabled:

image.thumb.png.629a57ee91bc478c75c6cabed74f3fa4.png

You can see that under I2C1 there is only TPD1 (touchpad), and on the USB controller there are some I2C nodes for the Touchscreen. So, maybe, the TPL1 device is acting as some kind of bridge between the two interfaces or something. But that is just me guessing based on my currently limited knowledge of I2C.
 

1 hour ago, wmchris said:

works well. thank you.

btw usb-c worked well before ;-)

@hvolkoff
does the voodooi2c native branch kext also mess up with your left click (not tap)?
most physical clicks are not recognized anymore on my system, but drag and drop works ... but sometimes doesnt register the clickUP event. dunno if configured something wrong or this is just a bug

Yeah physical clicks are acting weird for me too on Native and I am experience some random crashes on startup.

Share this post


Link to post
Share on other sites
2 hours ago, goodwin_c said:

Try to replace your SSDT-XOSI with next code:


DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000)
{
    External (_SB.TBFP, MethodObj)
    External (USTP, UnknownObj)
    Name (CNT1, Zero)
    Method (XOSI, 1, NotSerialized)
    {
        CNT1++
        IF (CNT1 == 0x1)
        {
          \_SB.TBFP (One)
          USTP = One
        }
        Local0 = Package (0x0A)
            {
                "Windows",
                "Windows 2001",
                "Windows 2001 SP2",
                "Windows 2006",
                "Windows 2006 SP1",
                "Windows 2006.1",
                "Windows 2009",
                "Windows 2012",
                "Windows 2013",
                "Windows 2015"
            }
        Return ((Ones != Match (Local0, MEQ, Arg0, MTR, Zero, Zero)))
    }
}

This will:

- permanently enable TB controller (USB-C works like a charm :) )

- should make VoodooI2C attaching to TPD acpi device

Damn, thanks man. I totally forgot about adding that to the post... I too did have to make changes in SSDT-XOSI, but I only had to add the newer "windows" identifiers to it. Do you mind explaining what the CNT1 bit is about?

Share this post


Link to post
Share on other sites
3 minutes ago, hvolkoff said:

Damn, thanks man. I totally forgot about adding that to the post... I too did have to make changes in SSDT-XOSI, but I only had to add the newer "windows" identifiers to it. Do you mind explaining what the CNT1 bit is about?

afaik its for triggering power to the TB device on bootup.

Edited by wmchris

Share this post


Link to post
Share on other sites
7 hours ago, wmchris said:

afaik its for triggering power to the TB device on bootup.

Yes, it is done to be sure that part inside of "if" will be triggered only once (on first call of XOSI function), as XOSI function is used few times in original DSDT.

Share this post


Link to post
Share on other sites

I have also installed the I2C Kexts but the Touchpad doesn't work for me with this Kext. Installed also the SSDT-XOSI and the Device TPD1 is also there according to IOReg. Did I something wrong or is this a Bug? The Keyboard works normal. With the ApplePS2SmartTouchPad.kext I have no problems with my Touchpad.

Share this post


Link to post
Share on other sites

My XPS 15 9550 will not boot after install.

I followed the GitHub guide, except I used [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] and Clover from tonymac. I have installed 10.13.2 onto APFS (SSD disk only)  and it boots via Clover on the USB, but will not boot on its own. No diagnostic, just a Dell blue screen comes up saying the disk won't boot.

My BIOS is 1.4.0.

Any suggestions on what to try?

Share this post


Link to post
Share on other sites
On 3/13/2018 at 10:22 PM, hitman478 said:

I have also installed the I2C Kexts but the Touchpad doesn't work for me with this Kext. Installed also the SSDT-XOSI and the Device TPD1 is also there according to IOReg. Did I something wrong or is this a Bug? The Keyboard works normal. With the ApplePS2SmartTouchPad.kext I have no problems with my Touchpad.

Same for me. Even though removing the I2C kexts it does not work. It may be due to the SSDT-XOSI or voodooPS2daemon?

I have only tried the SSDT-XOSI as @goodwin_c suggested, not using the previous one with enabling later windows as @hvolkoff stated.

I have tried both I2C 2.0.1 and the "10.13 beta" as included in zip file of original post by @hvolkoff .

The ControllerInterrupt first two hex are "10" looking at IOReg.

I've noticed that in some cases the mouse works just fine during the login screen, but shortly after logging in it stops moving, hard to do mouse clicks, essentially unusable except for scrolling. The touchscreen, however, works perfectly.

Share this post


Link to post
Share on other sites

Hey gang, did we ever get Thunderbolt working? Specifically I'm interested in the Elgato TB3 Dock and curious if anyone has had success TB3 yet.

Share this post


Link to post
Share on other sites
13 hours ago, pourhaus said:

My XPS 15 9550 will not boot after install.

I followed the GitHub guide, except I used ##### and Clover from tonymac. I have installed 10.13.2 onto APFS (SSD disk only)  and it boots via Clover on the USB, but will not boot on its own. No diagnostic, just a Dell blue screen comes up saying the disk won't boot.

My BIOS is 1.4.0.

Any suggestions on what to try?

OK, that was a quick post where I was hoping someone may have hit a similar problem.

Let me expand. As mentioned, I used U-n-i-B-e-a-s-t and Clover from t-m-86 to install _just_ the USB. That works from F12 boot menu, and is able to boot the High Sierra it installed from the SSD. I used the Clover, EFI and instructions from the GitHub repo to update/configure the High Sierra on the SSD itself (post-boot). Boot direct from the SSD does not work. I get _no_ text from the OS, it goes from BIOS boot menu to black screen for 5-10 seconds, then to Dell blue can't-boot screen.

Share this post


Link to post
Share on other sites

Just wanted to say thank you for providing the package and this tutorial for the XPS 15 9550, I found it very quick and easy to get up and running thanks to you! I ran in to 2 problems during the process which I thought I'd highlight as these were the only ones I encountered and in case anybody else is trying to do the same:

 

1) "does printf work??" - this was caused by the incorrect default "slide=0" value when using "OsxAptioFix3Drv-64.efi". Calculating the slide manually as per this tutorial fixed this for me.

 

2) "Unable to find driver for this platform" - this happened when I was using Pandora's Box to create my EFI boot USB. Manually erasing the USB to GUID structure, using the Clover installer provided in the Github package to create it and then manually installing the High Sierra installer on to the USB worked for me.

Quick question, has anybody upgraded their 10.13.3 install with the new "10.13.3 Supplemental Update" and if so, how did it go?

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 Tushark2
      Hello,
      1st my laptop spec. 
      CPU - 2.53 GHz Intel Core i3 380m
      RAM - 6 GB 1333 MHz DDR3
      GPU -  1st gen Intel HD Graphics 288 MB
      Laptop - Dell Vostro 3500 series
      BT/WIFI - AzureWave BCM94352HMB
       
      I installed Olarila Mojave 10.14.6 and managed to install 1st gen intel HD graphics but it was bit laggy bcos this gnu doest support metal and its a old machine, so I decided to move to Olarila High Sierra.
      I installed it with most of things working fine expect some issues, for that I want to make SSDT and DSDT to make it run without glitches.
       
      I am atteching my sendme.zip , can some take a look to my current settings and suggest me some changes  
      (Olarila down from few days for me )
       
      Send me MacBook-Pro.zip
    • By t3s8r8
      Hi, anyone here got those problems like me ? When I click play, the film load nothing, just show blackscreen like this (attached) or when I download an episode to the computer, it shows error (err = -11800)

      Anyone here knows a fix ? Maybe a bug or problem from Hackintosh ?


    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?f=45&t=9172
       
      ---USB---
      https://pikeralpha.wordpress.com/2016/07/13/simple-skylake-usb-fix-no-kexts-required/
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By AJackTi
      Hello everyone.
       
      I am a newbie! I just update from Mojave to the newest Catalina Hackintosh. But I cannot connect to Wifi. And I find many solutions to this problem, but it cannot help me.
       
      Anyone who helps me to see my EFI has any error. 
       
      My Wifi: BCM94322HM8L
      My info laptop: Dell M4700 i7 3720QM 
      My EFI: https://drive.google.com/file/d/1fjy6DDZuEWbxiTcYFZCX2msqO5skRCU9/view?usp=sharing
       
      Thank you so much and sorry for English grammar. 
    • By AudioGod
      I have put together this simple little guide for anybody wanting to use a Patched DSDT EFI with the same configuration as me.
      This is also a thread to discuss everything Z390 Pro and try and help where we can and maybe make things a little better for you. 
       
      A huge massive thank you to @glasgood @MaLd0n @larabee These three guys have helped me and talked me so much and are as helpful as you could ever get, Without them I wouldn't have a perfect working build like I do or be putting up this Guide & Discussion Thread sharing the hard work and countless hours that we have all put in to this.   
       
       
      This EFI and Patched DSDT have been created to work with a Gigabyte Aorus Z390 Pro, 9900k with a Vega 56 but has also been tested and verified fully working with the following Hardware using Catalina 10.15.2
       
      CPU's
      8700k, 9600k, 9700k, 9900k
       
      GPU's
      RX 560, 570, 580, 590, Vega 56, Vega 64, Radion VII, 5700, 5700 XT
      (If you have success with any different CPU or GPU's then please do let me know)
       
       
       @glasgood Has kindly put together a new simple Catalina install guide so Just Follow He's Guide For a Perfect Install.
       
       
      HARDWARE USED
      • Intel I9 9900k 
      • Gigabyte AORUS Z390 PRO
      • Sapphire Nitro+ SE Vega56 (connected to monitor with DisplayPort)
      • Corsair Vengeance Pro RGB 16GB @3200mhz (2 x 8GB)
      • Corsair RM850x 80 Plus Gold Power Supply Unit. 
      • CoolerMaster MASTERLIQUID ML360R RGB CPU Cooler
      • Samsung 970 EVO 1TB NVMe SSD macOS Mojave
      • Samsung 860 EVO 1TB SSD (2.5) Windows 10 Pro
      • ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)   
      • Lian Li PC-O11DW Dynamic ATX Case
       

       

       

       

       
       
      WORKING
      • Sound 
      • Ethernet Port
      • WiFi
      • SSD Trim
      • USB 3.0 & 2.0 (All ports Open Natively)
      • AirDrop
      • iCloud
      • Hardware Acceleration
      • iMessages
      • Facetime
      • Sleep & Wake
      • Sleep and Shutdown via the Power Button
      • Handoff
      • Netflix on Safari browser
      • Continuity
      • Sidecar
       
       
      CLOVER  FOLDER
      Use this folder with fully patched DSDT
      Current EFI 
      Updated 15/01/2020
      Aorus Z390 Pro Vega Navi VII F12d EFI .zip - Use with Bios revision F12d Only (15/01/2020 Catalina 10.15.2 Vega, Navi (5700, 5700xt), Radeon VII DSDT Installed) SMBios 19,1
      Aorus Z390 Pro RX Polaris F12d EFI .zip - Use with Bios revision F12d Only (15/01/2020 Catalina 10.15.2 RX5XX Polaris DSDT Installed) SMBios 19,1
      HD630 Z390 Pro F12d EFI.zip - Use with Bios revision F12d Only (15/01/2020 Catalina 10.15.2 HD630 IGPU Only) SMBios 18,1
       
      PLEASE NOTE - Please flash your motherboard bios to revision F11 to use my current EFI. It’s a major rework of the bios and vital changes have been made to the layout and power tables. New DSDTs have been created and installed into the new EFI’s but will not work correctly with any other bios revision.
       
      Latest Gigabyte Z390 PRO BIOS (F12d)
      mb_bios_z390-aorus-pro_f12d.zip
       
       
      CFG Unlock (MSR) F12d BIOS Profile - The Easy Way 
      Highly recommended if your using a Vega 56/64, Radeon VII or Navi GPU
       
       
      DSDT's & Older EFI’s (A big thanks to @MaLd0n for compiling these DSDT's)
       
       
      Alternative EFI - N-D-K Fork of OpenCore (16/01/2019)
       
       
      To Create Your Own Patched DSDT Message @MaLd0n using the link bellow
      https://olarila.com/forum/viewtopic.php?f=19&amp;t=1131 
      (If you want a perfect setup then getting your own patched DSDT made would be the best thing to do, Mine will work perfectly fine but different hardware no matter how small a change it is can tend to have some sort of effect on the DSDT and your setup)
       
       
      If Your Not Using File Vault Then Please Disable Hibernate
      disablehibernate.command
       
       
      ADDITONAL DOWNLOADS
      Clover
      Clover Configurator
      Kext Updater
       
       
      OPTIONAL DOWNLOADS
      BroadcomFix.zip   (Use these kexts if your Broadcom bluetooth/Wifi isn't working properly)
      FakeSMC    (Can be used instead of VirtualSMC)
      Hackintool
      IORegistryExplorer
      Native Display Brightness with MonitorControl
       
       
      BIOS SETTINGS (Bios Revision F11)
      • Enter BIOS → Press F12 → Enter Setup
      • Save & Exit → Load Optimized Defaults
       
      • Boot -> Windows 8/10 Features -> Win 8/10WHQL
      • Boot -> CSM Support -> Disabled (Can be set to Enabled if need be but try to have it set to Disabled first)
      • Favourites -> Extreme Memory Profile (X.M.P.) -> Profile1
      • Favourites -> VT-d -> Disabled (Can be set to Enabled or Disabled, Your choice)
      • Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled
      • Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot
      • Settings -> IO Ports -> Internal Graphics -> Enabled
      • Settings -> IO Ports -> DVMT Pre-Allocated -> 64M
      • Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M
      • Settings -> IO Ports -> Aperture Size -> 256MB
      • Settings -> IO Ports -> Audio Controller -> Enabled
      • Settings -> IO Ports -> Above 4G Decoding -> Enabled
      • Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Enabled
      • Settings -> IO Ports -> USB Configuration ->  XHCI Hand-off -> Enabled
      • Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled
      • Settings -> Platform Power -> Platform Power Management -> Enabled
      • Settings -> Platform Power -> ErP -> Enabled
      • Settings -> Platform Power -> RC6(Render Standby) -> Enabled
       
      • Save & Exit → Save & Exit Setup 
       
       
      SCREENSHOTS
       

       

       

       

       

       

       

       

       

       

       

       
       
       
×