Jump to content
tonyx86

Mojave on Dell Latitude E6410

111 posts in this topic

Recommended Posts

Advertisement

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 3:44 PM, Dr. Monkey said:

Do you know how I would check what the permissible values to SLPE would be?

@Dr. Monkey I'm correcting an old answer now that I know more.  SLPE is a 1-bit R/W register, so values are 0 and 1.  0 enables the sleep state defined in another register.  See my explanation of this later in this thread.

 

On 6/17/2019 at 3:59 PM, Dr. Monkey said:

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

From a previous post in this thread:   My method of injecting the device-id for Nvidia gets AGPM loaded, but it's probably not the correct solution.  I re-read duduclx original El Capitan thread and some work on this.  See here for this analysis.  I haven't tried any of it yet.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 3:59 PM, Dr. Monkey said:

sorry to double post,  but I also wanted to ask if you were able to get speedstepping going on Nvidia 3100m?  I can’t help but wonder if there is a relation between sleep and GPU power management and it would be good to rule that out

@Dr. Monkey- I just reread the thread that I linked above.  I haven't made this a priority yet and would love to know what you find.

Edited by tonyx86

Share this post


Link to post
Share on other sites

so I’ve been through the AGPM guide a few times,  and AGPM loads for me.  However I still only show a frequency of 400 MHz with the extremely infrequent dip to 250MHz,  and I am unable to see anything in the system.log

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 9:30 PM, Dr. Monkey said:

so I’ve been through the AGPM guide a few times,  and AGPM loads for me.  However I still only show a frequency of 400 MHz with the extremely infrequent dip to 250MHz,  and I am unable to see anything in the system.log

 

You made more progress than I did.  I just tried the suggestion (if I read it correctly).  I created a new entry for Device 10de,0a6c under MacBookPro 6,2 in AppleGraphicsPowerManagement.kext/Contents/info.plist and I set control-id to 18 (I also tried control-ids 16 and 17).  I don't see GPU Core/Memory clock changing at all - stuck on 405MHz.  What was your method for getting the frequency to make the "extreme infrequent dip to 250MHz?"

 

Note that I confirmed that AGPM loaded with the control-id I specified in info.plist for each of the cases control-id = 16, 17 and 18.  HWMonitor doesn't show any GPU Core/Mem clock changes.  

 

Could it be that HWMonitor isn't showing the GPU state changes?

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2019 at 8:19 PM, tonyx86 said:

@Dr. Monkey- I just reread the thread that I linked above.  The methodology looks very promising and should be applicable to the E6410.  I haven't made this a priority yet and would love to know what you find.

@Dr. Monkey I found one of your original discussions here.  I can see that you've looked at the AGPM throttling issue much more than I have, so I'll defer to you on this. After a bit of reading, I am using the FakeSMC.kext method to inject AGPM properties for the 10de,0a6c.  If you have anything you'd like me to try, let me know.  If you can post your DSDT.aml, config.plist and kexts for comparison, that would be very helpful.  Thanks!  

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: IOHWControl does not load properly under AGPM.  There's something "wrong" with my _DSM for discrete graphics (AGP.GFX0._DSM) in my DSDT.  If I enable "Inject NVidia" in CLOVER config plist, IOHWControl loads immediately.  Still testing this and have not updated the files attached to Post #1.

 

IOHWControl should load under AGPM as shown in the attached HighSierraAGPM.png.

HighSierraAGPM.png

MojaveAGPM.png

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT:  Deleting this post.  IOHWControl is not loaded because there's something wrong with the discrete graphics _DSM in my DSDT.  Currently testing a modified DSDT combined with enabling "Inject NVidia" in CLOVER config.plist and have not posted revised configuration files yet.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

I found a bug in the E6410 DSDT for BIOS A17.  In Method (GNOT), the expression 

 

    If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6)))

 

always evaluates to TRUE regardless of the value of OSYS (so the first branch ( Notify (\_SB.PCI0, Arg1) ) is always executed.  I suspect that LOr should be LAnd so that the expression reads

 

    If (LAnd (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6)))

 

which executes the first branch ( Notify (\_SB.PCI0, Arg1) ) if the Operating System is a Windows 2001 variant and the second branch ( Notify (\_SB.PCI0.VID, Arg1) ) for any other operating system.

 

While this bug may have no affect on MacOS (especially since the patched Method (HPET) has no dependency on OSYS), the real problem with this bug is that it's obvious, should never have made it through Dell QA and should not be in BIOS version A17.  This same bug appears in the BIOS for other Latitude models.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: Deleting this post.  See previous posts about why IOHWControl is not loading.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: deleting this post.  See previous posts for why IOHWControl is not loading.

Edited by tonyx86

Share this post


Link to post
Share on other sites

@MadHatter806  - I'd like to try UEFI booting my E6410.  I've tried creating a UEFI-bootable USB drive with CLOVER, but my E6410 doesn't appear to recognize the USB as bootable.  Do you have any advice for creating a UEFI-bootable device for the E6410?  Here's what I tried:

  • Format USB (GUID partition map)
  • Install CLOVER on USB in ESP (UEFI boot)
  • Configure E6410 BIOS for UEFI boot (Change mode from Legacy to UEFI, don't configure a boot file)
  • Attempt to boot from USB (F12 -> Boot Menu -> UEFI USB)

My E6410 doesn't boot from the USB.  Instead, it shows a strange boot screen.  

 

Any advice for getting the E6410 to UEFI boot would be appreciated.  Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)

It appears that I incorrectly applied the patch that duduclx referred to as "Intel GMA Ready," because in my DSDT, the patch contents are in Device (IGPU) instead of in Method (_DSM) within Device (IGPU).  MaciASL didn't complain about this and it doesn't appear to have had any affect.  I made this correction to my DSDT but haven't updated the files in Post #1.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/25/2019 at 7:44 AM, tonyx86 said:

@MadHatter806  - I'd like to try UEFI booting my E6410.  I've tried creating a UEFI-bootable USB drive with CLOVER, but my E6410 doesn't appear to recognize the USB as bootable.  Do you have any advice for creating a UEFI-bootable device for the E6410?  Here's what I tried:

  • Format USB (GUID partition map)
  • Install CLOVER on USB in ESP (UEFI boot)
  • Configure E6410 BIOS for UEFI boot (Change mode from Legacy to UEFI, don't configure a boot file)
  • Attempt to boot from USB (F12 -> Boot Menu -> UEFI USB)

My E6410 doesn't boot from the USB.  Instead, it shows a strange boot screen.  

 

Any advice for getting the E6410 to UEFI boot would be appreciated.  Thanks!

 

Sorry I've been out of town and didn't take this laptop with me to play with.

 

However, when I initially asked it was because I could never get clover to work UEFI, and was thinking maybe you had. (It seems perhaps some of the issues might be easier to resolve with UEFI as it gives the OS more information to work with for the components.)

 

I did however try a Yosemite (Only full installer I had available at the time) install USB formatted GPT with Clover (EFI -- Fat32).

Booting, was unable to boot from it. Had to use El Capitan Legacy boot to clover. In clover chose Yosemite install. When it came to reboot, the legacy clover was unable to launch from HDD (didn't have spare SSD to install to). Still could not get Yosemite USB to initialize clover.

 

Tried this:

Removed all drives

Left Yosemite (UEFI) & El Capitan (Legacy) plugged in.

Launched clover from Legacy USB -- launched shell -- removed Legacy USB.

Listed all disks, found the efi partition. Created a boot config for it. Rebooted, tried to f12 launch, no success. Then tried adding boot option in BIOS (manually point to clover efi). Also no bootable device detected.

 

From research it appears due to EFI being second partition on the drive, unlike Linux or Windows where it is generally first.

Did find an article where someone claimed to get UEFI boot working on an E6410. Will edit this post and link article later (if I can find it again) as maybe you will understand what steps they might have taken based on the comments in order to replicate results.

 

https://www.reddit.com/r/hackintosh/comments/74xhka/latitude_e6410_with_1013_booting_from_filevaulted/

Edited by MadHatter806
Link to reddit article

Share this post


Link to post
Share on other sites
Posted (edited)

Interesting that Windows 10 users have sleep / shutdown issues:  https://www.dell.com/community/Windows-10/Solved-Laptop-won-t-shutdown-completely-in-Windows-10/td-p/4624985/page/14

 

According to this thread which is linked in the above thread: 

 

https://www.dell.com/community/Windows-10/E6410-Win-10-1803-update-UEFI/m-p/6141447

 

the Windows 10 shutdown issue is resolved by switching from UEFI to Legacy boot and using an MBR disk format instead of GPT.  I don't have any experience with UEFI booting on the E6410, but the Windows 10 problems suggest that staying with Legacy boot is preferable.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

I made statement #2 below before learning about how to override _OSI with XOSI via a customer SSDT (credit Rehabman).  I suspect that creating a custom SSDT-XOSI is a better way to patch OS identification in the Latitude E6410 DSDT. I'm still learning about XOSI and will provide more details as I learn.  If anyone has used the XOSI / _OSI override on their Dell Latitude E6410 or similar laptop, please comment.  Thank you.

 

I noticed a couple of "errors" in my DSDT that I corrected, but don't appear to have had any affect on system behavior:

  1. The devices IDs of the EHCI devices are wrong in the DSDT (according to the Intel Series 5 Chipset specification).  Since the DSDT defines only the EHCI device-id (and not "name" or "compatible," Mojave is still correctly discovering the device identity (ignoring the device-id defined in the DSDT).  The detected device identifier for EHC1 and EHC2 can be observed in IORegistryExplorer.  I corrected the device-ids in my DSDT. EHC1: 3b34.  EHC2: 3b3c.
  2. The value of ACOS depends on _OSI, but is missing a conditional for "Darwin."  I set the conditional for "Darwin" to be equivalent to Linux (same as I did for OSYS).

Neither of these "fixes" appear to have had any affect (on sleep or otherwise). My system is currently running with these fixes which are not yet reflected in the files attached to Post #1.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: I noticed that my CPU temps were climbing (not a lot, but a few degrees) after performing the procedure below.  I removed the heatsink only to find that the AS5 compound was still applied to both surfaces (the die and the copper heatsink pad), so there isn't any pressure being applied by the copper pad directly on the CPU die.  I added a .3mm copper shim on the CPU and also a .3mm copper shim on the 3100m die (which now has a copper shim on the die and a Fujipoly pad on the heatsink) and will report back after the surfaces have a chance to mate and the AS5 settles / spreads.

 

EDIT 2: Copper shims have restored temps back to the ranges that I was observing before.  I suspect temps will get better as surfaces mate.

 

EDIT 3: After about a week with the copper shims, the laptop fan hardly runs and when it does run, it's very quiet.  I suspect that the heat transfer from the CPU and Graphics dies is much better.

 

I removed the heatsink/heatpipe to thoroughly clean my fan / heatsink fins.  While at it, I replaced the CPU thermal pad with Arctic Silver 5 and replaced the GPU thermal pad with a Fujipoly 11w/mk thermal pad.  Temps for the CPU and GPU are now lower by a few degrees C.

Screen Shot 2019-07-06 at 9.22.26 AM.png

Edited by tonyx86
Added copper shim

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: I'm still learning about ACPI and DSDT patching and just learned about overriding _OSI with an XOSI SSDT (credit Rehabman).  My comments/observations below do not reflect this new knowledge of XOSI as evidenced by my rather naive statement about Methods IINI and OSID.  I don't know enough about the use of XOSI to apply it to the Dell Latitude E6410, but I suspect that a custom XOSI SSDT is the best way to "patch" _OSI in the E6410 DSDT.  Will provide more detail as I learn about this and I welcome any comments, especially from others who have used the XOSI / _OSI override on their Latitude E6410 or similar laptops.

 

After further review of the Dell Latitude E6410 DSDT (BIOS A17), I'm noticing a programming style that is inconsistent ( see OS Identification differences in Method (IINI) and Method (OSID) ) and flawed (note coding error in Method (GNOT) ), so I'm suspicious of the code's quality.  Call me paranoid.  I would appreciate other opinions on these suspicious items in the DSDT that may actually be nothing to worry about - just checking:

  1. Not a problem, but Method (ECR1) and Method (ECW1) each include a series of IF conditions, such that the methods always evaluate every IF condition, even if the first evaluates to TRUE.  It would have been very easy to return immediately upon a TRUE IF condition.
  2. ACOS is used in Method (ECIN) without first initializing ACOS.  Note the way ACOS is used in Method (STOS)
  3. Mutex (WMIX) is acquired in Method (WSVP) and Method (WVCU) and is never released at the end of the methods.  All other methods that acquire a mutex release the mutex before exiting.
  4. Method (ECW1) does not support writing to every EC register (note that ECR1 supports reading from every EC register).

I have addressed each of these in my DSDT and am currently running with these updates as I continue to look for reasons why the E6410 does not sleep.  So far, I haven't noticed any difference in behavior.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

Hi guys.

 

Just installed Mojave at my Dell Latitude E6510 (almost the same hardware and identical graphics - Core i7-620m, Nvidia 3100M, 8GB DDR3, 480GB SSD, 1920x1080p display, BIOS A16).

 

Id follow the duduclx guide for El Capitan and Sierra with success but without edit DSDT etc. (very complex to me) and the performance was nice.

 

But now, inside Mojave, theres something with my nVidia 3100m that shows me some artifacts and slows animations.

Someone can help here?

Edited by vbmota
hardware update

Share this post


Link to post
Share on other sites
Posted (edited)

@vbmota Welcome to the discussion!  You mentioned Sierra - did you also try High Sierra?  If your graphics worked fine in High Sierra, my first guess would be that you didn't apply Dosdude's legacy graphics patch (or you did and it didn't install correctly for some reason).  Also, are you running HWMonitor and if so, can you see your GPU temps?

 

EDIT: Also, did you follow my performance improvement tips listed in the first post of this thread?

 

If you're confident in the legacy graphics patch, GPU temps are reasonable and you followed my performance improvement tips in the first post of this thread, are you able to post the following items for review (in a single zip file)?  If you don't know how to produce these items, Google 'GENERATE PROPER PROBLEM REPORTING FILES BlackDragon' to use Black Dragon's problem reporting tool and post the zip file in this forum.  The files you should post are:

  • DSDT (I'd prefer your DSDT.dsl, but DSDT.aml is ok)
  • IORegistryExplorer dump
  • CLOVER config.plist
  • list of kexts in your CLOVER/kexts/Other folder
  • output of 'sudo kextcache -i /'
  • CLOVER preboot.log (generated by pressing F2 in CLOVER bootloader screen. File located in EFI/CLOVER/misc)

 

 

Edited by tonyx86

Share this post


Link to post
Share on other sites
18 hours ago, tonyx86 said:

@vbmota Welcome to the discussion!  You mentioned Sierra - did you also try High Sierra?  If your graphics worked fine in High Sierra, my first guess would be that you didn't apply Dosdude's legacy graphics patch (or you did and it didn't install correctly for some reason).  Also, are you running HWMonitor and if so, can you see your GPU temps?

 

EDIT: Also, did you follow my performance improvement tips listed in the first post of this thread?

 

If you're confident in the legacy graphics patch, GPU temps are reasonable and you followed my performance improvement tips in the first post of this thread, are you able to post the following items for review (in a single zip file)?  If you don't know how to produce these items, Google 'GENERATE PROPER PROBLEM REPORTING FILES BlackDragon' to use Black Dragon's problem reporting tool and post the zip file in this forum.  The files you should post are:

  • DSDT (I'd prefer your DSDT.dsl, but DSDT.aml is ok)
  • IORegistryExplorer dump
  • CLOVER config.plist
  • list of kexts in your CLOVER/kexts/Other folder
  • output of 'sudo kextcache -i /'
  • CLOVER preboot.log (generated by pressing F2 in CLOVER bootloader screen. File located in EFI/CLOVER/misc)

 

 

No I didnt try High Sierra.

Thank you for answer. As soon as possible I will post the results.

By the way, I installed the nvidia webdrivers following some kind of youtube guide and appears to be ok.

I will get some time to see the dosdudes post install and be back here. 

Cheers!

Share this post


Link to post
Share on other sites
Posted (edited)

@vbmota If you didn't apply Mojave patches for legacy graphics, that's your issue.  Do the following:

 

  1. BACKUP YOUR DISK!!!
  2. Remove the NVidia Web Drivers
  3. Create a patched Mojave installer USB using Dosdude's latest Mojave patcher
  4. Boot your laptop from the patched Mojave installer USB
  5. When you reach the installer GUI, ignore the Mojave install dialog (you've already installed Mojave) and select "macOS Post Install" from the Utilities menu
  6. Set your Mac Model to 6,2.  This will select the patches for your laptop and should include the Legacy Graphics Patch
  7. Review the patches to see if you don't need any of them and uncheck those you don't need (I'm not sure what you have already applied to your laptop).  I'm not looking at the macOS Post Installer at the moment, so I'm going by memory, but I think you'll want to uncheck anything to do with SIP (I suspect you're already handling that with CLOVER) and USB (I suspect you already have your own preferred USB kext).  If there's any doubt about what options to enable, uncheck everything except for Legacy Graphics so that you have only the Legacy Graphics patch checked.
  8. Follow instructions to apply the patch(es) and reboot.
  9. You should now have working graphics.
Edited by tonyx86

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 fusion71au
      Clover r5050 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5050 for VMware.zip". Mount Clover-v2.5k-5050-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil IGPU = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Adjusting the brightness on a laptop
      1. Method 1
      Enable Clover DSDT fix AddPNLF. Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.
      2. Method 2
      Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml
      Do not use both methods at the same time!
       
      Digital Audio (HDMI / DVI / DP)
      To enable digital audio it is necessary to set the necessary properties and, usually, patch the connectors.
      To enable audio in general and HDMI in particular use WEG along with AppleALC.kext.
      On 10.10.5 and above, WEG automatically changes the connector-type of DP (00040000) to HDMI (00080000) if no custom patches are used.
      The actual connection may be of any type (HDMI / DVI / DP), but for the digital audio to function the connector-type must explicitly be HDMI.
       
      VGA support
      In most cases with Intel Skylake and newer it works by default.
      For Ivy Bridge and possibly other generations there are the options to patch your connectors with the following:
      06020000 02000000 30000000 // Option 1
      06020000 01000000 30000000 // Option 2
      On OS X 10.8.2 and newer it is impossible to have VGA on Ivy Bridge systems.
      Hot-plugging VGA usually does not work.
      In case this doesn't help - there are no other known solutions at this time.
       
      EDID
      EDID is usually correctly identified, so no actions are required. In rare cases, EDID needs to be injected manually.
      An EDID dump can be obtained, for example, with Linux. The correct EDID must be put into *AAPL00,override-no-connect* property for IGPU, where the second 0 stands for the display number.
      In some cases the EDID dump may be incompatible with macOS and leads to distortions. For some EDID in such cases you can use this script, which corrects a provided EDID and saves it to your desktop.
       
      HDMI in UHD resolution with 60 fps
      Add the enable-hdmi20 property to IGPU, otherwise you will get a black screen. Or instead of this property use the boot-arg -cdfon
       
      Disablng a discrete graphics card
      Add the disable-external-gpu property to IGPU. Or instead of this property, use the boot-arg -wegnoegpu
       
      Fix the invalid maximum link rate issue on some laptops (Dell XPS 15 9570, etc.)
      Add the enable-dpcd-max-link-rate-fix property to IGPU, otherwise a kernel panic would happen due to a division-by-zero. Or instead of this property, use the boot-arg -igfxmlr.
      You could also manually specify a maximum link rate value via the dpcd-max-link-rate for the builtin display.
      Typically use 0x14 for 4K display and 0x0A for 1080p display. All possible values are 0x06 (RBR), 0x0A (HBR), 0x14 (HBR2) and 0x1E (HBR3). If an invalid value is specified, the default value 0x14 will be used instead. If this property is not specified, same as above.  
      Fix the infinite loop on establishing Intel HDMI connections with a higher pixel clock rate on Skylake, Kaby Lake and Coffee Lake platforms
      Add the enable-hdmi-dividers-fix property to IGPU or use the -igfxhdmidivs boot argument instead to fix the infinite loop when the graphics driver tries to establish a HDMI connection with a higher pixel clock rate, for example connecting to a 2K/4K display with HDMI 1.4, otherwise the system just hangs (and your builtin laptop display remains black) when you plug in the HDMI cable.  
      1. General Notes
      For those who want to have "limited" 2K/4K experience (i.e. 2K@59Hz or 4K@30Hz) with their HDMI 1.4 port, you might find this fix helpful. For those who have a laptop or PC with HDMI 2.0 routed to IGPU and have HDMI output issues, please note that this fix is now succeeded by the LSPCON driver solution, and it is still recommended to enable the LSPCON driver support to have full HDMI 2.0 experience.  
      (You might still need this fix temporarily to figure out the connector index of your HDMI port. See the LSPCON section below.)
      LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU
      1. Brief Introduction
      Recent laptops (Kaby Lake/Coffee Lake-based) are typically equipped with a HDMI 2.0 port. This port could be either routed to IGPU or DGPU, and you can have a confirmation on Windows 10. Intel (U)HD Graphics, however, does not provide native HDMI 2.0 output, so in order to solve this issue OEMs add an additional hardware named LSPCON on the motherboard to convert DisplayPort into HDMI 2.0.
      LSPCON works in either Level Shifter (LS) or Protocol Converter (PCON) mode. When the adapter works in LS mode, it is capable of producing HDMI 1.4 signals from DisplayPort, while in PCON mode, it could provide HDMI 2.0 output. Some onboard LSPCON adapters (e.g. the one on Dell XPS 15 9570) have been configured in the firmware to work in LS mode by default, resulting a black screen on handling HDMI 2.0 connections.
      Starting from version 1.3.0, WhateverGreen now provides driver support for the onboard LSPCON by automatically configuring the adapter to run in PCON mode on new HDMI connections, and hence solves the black screen issue on some platforms.
       
      2. Before you start
      LSPCON driver is only applicable for laptops and PCs with HDMI 2.0 routed to IGPU. LSPCON driver is necessary for all newer platforms unless the new IGPU starts to provide native HDMI 2.0 output. Supported Intel Platform: Skylake, Kaby Lake, Coffee Lake and later.
      Skylake Case: Intel NUC Skull Canyon; Iris Pro 580 + HDMI 2.0 with Parade PS175 LSPCON.
      Coffee Lake Case: Some laptops, e.g. Dell XPS 15 9570, are equipped with HDMI 2.0 and Parade PS175 LSPCON. If you have confirmed that your HDMI 2.0 is routed to IGPU and is working properly right now, you don't need to enable this driver, because your onboard LSPCON might already be configured in the firmware to work in PCON mode.
      3. Instructions
      Dump your kernel log and you should also be able to see something simillar to lines below.
       
      // When you insert the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] Found the LSPCON adapter: Parade PS1750. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] The current adapter mode is Level Shifter (DP++ to HDMI 1.4). igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has detected the onboard chip successfully. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has been initialized successfully. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x01. igfx @ (DBG) SC: LSPCON::setMode() DInfo: [FB2] The new mode is now effective. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] The adapter is running in preferred mode [Protocol Converter (DP++ to HDMI 2.0)]. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. // When you remove the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver (at 0xffffff802ba3afe0) has already been initialized for this framebuffer. igfx @ (DBG) SC: LSPCON::setModeIfNecessary() DInfo: [FB2] The adapter is already running in Protocol Converter (DP++ to HDMI 2.0) mode. No need to update. igfx @ (DBG) SC: LSPCON::wakeUpNativeAUX() DInfo: [FB2] The native AUX channel is up. DPCD Rev = 0x12. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. Additionally, you can find these properties injected by the driver under the corresponding framebuffer.
      (Only available in DEBUG version)
       
      fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.
      fw-framebuffer-preferred-lspcon-mode indicates the preferred adapter mode. 1 is PCON, and 0 is LS.
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      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!
×