Jump to content
ACDindia

[HELP] MSI GV62-7RE Laptop| Installation: Boots only with invalid GPU FakeID

18 posts in this topic

Recommended Posts

Dear All,

 

I followed the Olarila (MaLd0N's) guide and made the Mojave USB.

I had to install the system using an invalid GPU FakeID (0x12345678) to get past the KP.

Even after installation, my system going into KP if I don't use this invalid fakeid.

With the FakeID, my system reports 7mb VRAM with Intel HD630.

I am using the DSDT from my 10.13 installation.

 

Used:

Whatevergreen.kext

Tried putting different FakeIDs

Put the Whatevergreen and Lilu in /Library/Extensions

Tried without Whatevergreen. The same setup used to work with 10.13.

 

My Laptop details are in my signature.

This is the link to the last time MaLd0N helped me get 10.13 working: https://www.insanelymac.com/forum/topic/332021-msi-gv62-7re-1013-installation/

 

Please help anyone.

 

Thanking you

 

Share this post


Link to post
Share on other sites
Advertisement

Hey! Thanks for the response Hervé!

I was reading the whatevergreen article... it asked to not inject Intel ?

I think I tried the MacBookPro14,3 ID...

I will give it a try again... will revert back...

Share this post


Link to post
Share on other sites
1 hour ago, Hervé said:

I guess you'll need to apply the necessary DVMT changes/patches that apply to HD630 graphics.

I think the “Whatevergreen.kext” does include all those fixes? Is there something that I should be doing to enable the same ??

Share this post


Link to post
Share on other sites
On 8/17/2018 at 7:53 AM, ACDindia said:

I think the “Whatevergreen.kext” does include all those fixes? Is there something that I should be doing to enable the same ??

 

Go to bios menu and set DVMT or Intel GPU minimum allocated memory setting to 64mb. 

Edited by Gigamaxx

Share this post


Link to post
Share on other sites
11 hours ago, Gigamaxx said:

 

Go to bios menu and set DVMT or Intel GPU minimum allocated memory setting to 64mb. 

Hey! Thanks for the response mate!

There isn’t any option in my BIOS which says anything about DVMT it minimum allocated memory.

I checked Windows and saw that the minimum memory given is 128 MB already.

I’ve read somewhere that we should reduce 32MB from what windows shows and it’s then the minimum allocated memory.

i think it’s alright ?

rectify me if I’m wrong..

thanks again!!

Share this post


Link to post
Share on other sites
36 minutes ago, ACDindia said:

Hey! Thanks for the response mate!

There isn’t any option in my BIOS which says anything about DVMT it minimum allocated memory.

I checked Windows and saw that the minimum memory given is 128 MB already.

I’ve read somewhere that we should reduce 32MB from what windows shows and it’s then the minimum allocated memory.

i think it’s alright ?

rectify me if I’m wrong..

thanks again!!

 

A lot of laptops come with 32mb min and that is a problem for MacOS it needs 64mb to function well.    Search for “min stolen size patch”.    It’s a fix for laptops that don’t have bios that allows 64mb settings.

Share this post


Link to post
Share on other sites

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)

fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:

setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

Edited by headkaze

Share this post


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

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

I’ll give this a try... thank you so much for the effort..

I’ll report back..

Share this post


Link to post
Share on other sites
5 hours ago, headkaze said:

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

 

Thank you!

 

I verified and successfully edited the lines as suggested and now the system boots fine.

Only that my old DSDT won't work anymore.

No HDMI Display.

Any solution to that ?

 

Thanks a ton man!

 

Share this post


Link to post
Share on other sites
On 8/20/2018 at 4:00 PM, headkaze said:

I had a look at the MSI GV62-7RE BIOS (E16J9IMS.324) and it is indeed set to 32 DVMT pre-alloc.

 

We don't really recommend you use the "min stolen size patch" anymore. You should patch framebuffer-stolenmem / framebuffer-fbmem instead.

 

The other alternative (which is a bit more risky) is to follow this guide. Make sure you have the same BIOS flashed on your machine! Do this at your own risk!

 

1. Download the BIOS for your machine. If it's an .exe file you may be able to use 7zip to open it and extract the BIOS file. Eg. E16J9IMS.324
2. Download UEFITool and open the file
3. You need to find the PE32 section. To do this search for "Setup" and double click on a result that includes PE32. Right click on the PE32 section and select "Extract Body" to your desktop and call it Setup.bin
4. Download Universal-IFR-Extractor or Universal IFR Extractor.exe
5. Run "./ifrextract Setup.bin Setup.txt" using ifrextract or run Universal IFR Extractor.exe to extract Setup.bin
6. You can now use this text file to get the variable offsets for different settings
7. Download the modified GRUB Shell and extract bootx64.efi to a folder on your boot EFI partition (Eg. EFI/GRUB/bootx64.efi)
8. Boot into Clover and select "Start UEFI Shell 64" option
9. Run the following commands (assuming fs0: is your boot volume)


fs0:
.\EFI\GRUB\bootx64.efi

10. Now it should launch GRUB Shell and you can set the values found in the txt file earlier
Eg. To set DVMT-prealloc to 64 MB for E16J9IMS.324 BIOS enter:


setup_var 0x798 0x2

WARNING: variable offsets are unique not only to each motherboard but even to its firmware version. Never ever try to use an offset without checking.

 

Hey! So I tried it... inserted the required data but still don’t have any HDMI output... please help...

also, how to get the battery status ?

thank you!

Share this post


Link to post
Share on other sites
On 8/20/2018 at 6:41 PM, headkaze said:

 

 Check out this guide

 

Hey! Please guide me a bit more on this.. Couldn't get it fixed.

 

My entries are in the attached picture.

1430967450_Screenshot2018-08-22at4_04_42AM.thumb.png.e86dd23bccac335b67eaf72f9c82fed4.png

 

System boots fine and I even have 2GB of VRAM.

Still, no HDMI :( :'(

 

PLEASE HELP......

 

Thank you!!

Share this post


Link to post
Share on other sites

So I compiled a new Whatevergreen.kext with New Lily (Debug) and used it. This time when I plugged in my HDMI, the system restarted...

Share this post


Link to post
Share on other sites

I’ve figured out one thing:

by mistake my InjectIntel was ticked as yes. And that was giving me a crash.

I’ve unchecked the same and now I’m back to just nothing...

when I connect the HDMI, nothing happens.

I tried going to Settings>Display and then tried doing “Detect Display” and still got nothing..

 

please, can someone help me ?

Share this post


Link to post
Share on other sites
1 hour ago, ACDindia said:

when I connect the HDMI, nothing happens.

 

If your HDMI port is connected to your eGPU you may not be able to use it. Maybe try the mDP with an adapter instead?

 

Also you should not set framebuffer-fbmem / framebuffer-unifiedmem as you have already set your DVMT-prealloc.

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 tluck
      Lenovo T460 macOS with Clover Guide
      Latest Release on GitHub (February 2020) Updated to Clover r5104 Updated Lilu based kexts - Lilu, ALC, WEG Updated acidanthera VoodooPS2 kext v2.1.1 the older 1.9 to the Misc Folder as an option.
        Various Tweaks over Last months The zip file is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle is tested on Sierra. 
      Note: I never got the GFX fully working on El Capitan. 
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (the old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • By tonyx86
      *** I have started another thread for installing Catalina on the Dell Latitude E6410.  If you were thinking of installing Mojave, but would prefer to skip right to Catalina, click here. ***
       
      I was inspired by @duduclx post here for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5 and subsequently 10.14.6.  Everything works perfectly (including sleep).  I'm starting this thread hoping to help others install Mojave on their E6410s.  A brief installation guide is provided later in this first post.  The interested reader is encouraged to read the other posts in this thread to see how this solution evolved and to learn additional tips/details not provided in this first post (including dual-booting with macOS and Windows).
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.6 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 6 developed by @Dr. Hurt and compiled by @bronxteck), not the original version), USBInjectAll (with custom SSDT-UIAC), VoodooSDHC.kext (configured as shown here). Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      Addition of _OFF and _ON methods to _PTS and _WAK methods respectively (to control discrete graphics in order to enable sleep/wake) LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)  
      What is NOT working:
      Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      Smartcard Reader eSata (I have this disabled in my BIOS) Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS)  
      What IS working:
      SLEEP IS WORKING! Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: here) for working external VGA display. Headphone jack Display Port (tested using DP > HDMI adapter) Camera SD Card Reader  
      Known issues and their solutions (These issues have all been resolved, with the solutions incorporated into the attached config files.  The issues are listed here for historical purposes and no further work is needed unless stated otherwise).
      Laptop does not sleep on lid close.  Solution is to add Notify (LID0) code to Method (BTNV) in the DSDT.  This is solved in the attached DSDT. Leaving this for historical purposes, but the CLOVER USBFix is no longer necessary after finding that I had incorrectly applied the DSDT _DSM patch for Device (EHC1).  The CLOVER USBFix is not needed after fixing the DSDT..  AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  Thank you, @feartech, for this tip. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European. This configuration (captured in the attached config files) uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug. The assigned value of ACOS and OSYS in the DSDT are conditional on the operating system.  There is no condition for "Darwin."  The solution is to add a condition for "Darwin" (making it equivalent to one of the defined operating systems (e.g. Linux, Win7, etc).  The attached config hard-codes ACOS and OSYS values equivalent to those for Linux.  Another way to handle this (different from the method employed in the attached config files) might be to override _OSI with XOSI (defined in a custom SSDT). The portType of the Internal Bluetooth device is portType=0 which, according to Rehabman's comments in SSDT-UIAC-All.dsl, is an external USB 2 port.  This should be an internal USB port (portType=2).  I learned through trial and error that the HUB1 and HUB2 definitions in Rehabman's SSDT-UIAC-ALL.dsl apply to the ports on the EHCx USB hubs.  The solution is to include the HUB1 definition in SSDT-UIAC.dsl and change portType to 2 for HP15.  This change doesn't appear to affect/fix sleep, but it may prevent instant wake if we get sleep working. There are minor differences between a real MacBookPro6,2 IORegistry dump and this HackBookPro6,2 IORegistry dump that can be resolved with simple DSDT edits.  I am now running with these changes, but haven't found these changes to make any difference in operational behavior.
      Rename Device (AC) -> Device (ADP1) Remove UID from Device (HPET) Add compatible ID "PNP0C01" to Device (HPET) Change ADP1:_STA from 0x0F to 0xFFFFFFFF Enable Ambient Light Sensor and renamed to Device (ALS0) from Device (ALS) Add compatible ID "smc-als" to ALS0 Rename LID -> LID0 Change "name" definitions to Buffers in _DSM methods Rename Device (PBTN) to PWRB Rename Device (SBTN) to (SLPB) Change HDAU.hda-gfx from "onboard-1" to "onboard-2" Change GFX0.hda-gfx from "onboard-1" to "onboard-2" Sleep / Wake does not work with the basic DSDT edits.  I have discovered that Sleep / Wake can be made to work by adding discrete graphics _OFF and _ON methods to _PTS and _WAK methods respectively (borrowed the concept and code from a working E6430 DSDT: Credit here: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/page/6/. The Clover boot arg should be changed to "darkwake=0" for reasons explained by @holyfield in this thread.  Leaving this for historical purposes: LCD screen is blank when waking laptop by opening lid (screen is not blank when waking with power button).  Solution is to add darkwake=8 to CLOVER boot args.  Thank you @Hervé for this tip.  
      Brief Installation Guide:
      Configure BIOS (version A17) as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC: Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace: Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;  Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD.  When you run DosDude's Mojave Patcher, DO NOT install LegacyUSBInjector.kext - you're going to use Rehabman's USBInjectAll.kext.  Also, do not install the DosDude SIP kext (you're using CLOVER to manage SIP). Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original), VoodooSDHC.kext (configured as shown here). Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z After applying Mojave updates, HWMonitor may not display discrete graphics attributes.  On systems with multiple displays, a second (or third display) may not be active after applying the Mojave update.  The solution to this is to run "sudo kextcache -i /" (in a terminal window) and reboot.  This will usually fix the issue.  If the issue is not fixed, run DosDude's Post Install Utility, apply the Legacy Graphics Patch, reboot and then run "sudo kextcache -i /" if necessary.  
      Credits
      In addition to those mentioned in this first post and in subsequent posts in this thread, much of this solution for the Latitude E6410 was made possible by the numerous contributions of @RehabMan.  I hope he's doing well, wherever he is.  Hopefully he has long since forgotten what a PIA I was (and still am) as I was (and still am) learning hackOS.  
       
       


      E6410-Mojave-6v3.zip
    • By MaLd0n
      --Donations via PayPal--
      https://tinyurl.com/r2bvzm7
       
      --Original Topic--
      https://www.olarila.com/topic/6874-olarila-hackbook-lenovo-ideapad-s145-mojave-catalina-full-dsdt-patches/
       

       
      -Perfect HackBook, HDMI Audio/Video, Bluetooth, AirPlay, Sleep, Lid Sleep, Auto Sleep, Audio, etc!
      -Wifi card has been replaced with Dell DW1560!
      -I'm using a S145-15IWL Model with Intel Core i5 8265u / Intel UHD Graphics 620
      -Update bios/uefi to last version
       
      --Installation--
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Clover Folder--
      Just paste EFI folder inside EFI partition
      https://www.olarila.com/files/Clover.Folder/Lenovo IdeaPad S145.zip
      Notebooks with ELAN trackpad use it with my folder above
      IdeaPad S145 ELAN.zip
       
      Bluetooth Broadcom
      Bluetooth Broadcom.zip
       
      CPUFriend for i5-8265U
      CPUFriend i5-8265U.zip
       
      --Full DSDT Patches--
      -My DSDT
      DSDT Lenovo IdeaPad S145.zip
       
      This DSDT work on S145-14IWL, S145-15IWL, V14-IWL, V15-IWL models
      -Patches
      -FIX ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 11 ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PRWs -_DSMs -PNLF -BRIGHTNESS KEYS -I2C -NATIVE USB -ARPT -GFX0 -DTGP -kUSBCompanionIndex -io-device-location -FULL RENAMED DEVICES   --IGPU Patch--
      Video solution with HDMI Audio and Video
      <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,GfxYTile</key> <data> AQAAAA== </data> <key>AAPL,ig-platform-id</key> <data> CQClPg== </data> <key>device-id</key> <data> pT4AAA== </data> <key>enable-hdmi20</key> <data> AQAAAA== </data> <key>framebuffer-con0-alldata</key> <data> AAAIAAIAAACYAAAA </data> <key>framebuffer-con0-enable</key> <integer>1</integer> <key>framebuffer-con1-alldata</key> <data> AQEJAAAIAADHAQAA </data> <key>framebuffer-con1-enable</key> <integer>1</integer> <key>framebuffer-con2-alldata</key> <data> AgYKAAAEAADHAQAA </data> <key>framebuffer-con2-enable</key> <integer>1</integer> <key>framebuffer-fbmem</key> <data> AACQAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> <key>framebuffer-unifiedmem</key> <data> AAAAgA== </data> <key>hda-gfx</key> <string>onboard-1</string> <key>model</key> <string>Intel Corporation, Cannon Point-LP Iris Plus Graphics 655</string> </dict>   --Native USB Fix for Notebooks - No Injector/Kext Required--
      https://www.olarila.com/topic/6878-guide-native-usb-fix-for-notebooks-no-injectorkext-required/
      https://www.olarila.com/topic/6181-guide-native-usb-fix-for-desktops-no-injectorkext-required-skylake/
       
       
      -ScreenShots

































      -Links
       
       
      Clover https://github.com/CloverHackyColor/CloverBootloader
      AirportBrcmFixup.kext https://github.com/acidanthera/AirportBrcmFixup
      AppleALC.kext https://github.com/acidanthera/AppleALC
      Brcm Bluetooth https://github.com/acidanthera/BrcmPatchRAM
      Lilu.kext https://github.com/acidanthera/Lilu
      SystemProfilerMemoryFixup.kext https://github.com/Goldfish64/SystemProfilerMemoryFixup
      VirtualSMC.kext https://github.com/acidanthera/VirtualSMC
      VoodooI2C.kext https://github.com/alexandred/VoodooI2C
      VoodooPS2Controller.kext https://github.com/acidanthera/VoodooPS2
      WhateverGreen.kext https://github.com/acidanthera/WhateverGreen
      MaciASL - https://github.com/acidanthera/MaciASL
      acpica - https://github.com/acpica/acpica
      AptioMemoryFix.efi https://github.com/acidanthera/AptioFixPkg
      ApfsDriverLoader.efi https://github.com/acidanthera/AppleSupportPkg
      HFSPlus.efi https://github.com/JrCs/CloverGrowerPro/blob/master/Files/HFSPlus/X64/HFSPlus.efi?raw=true
      Hackintool https://github.com/headkaze/Hackintool
       
      -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 headkaze
      English: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md
      Russian: https://www.applelife.ru/threads/intel-hd-graphics-3000-4000-4400-4600-5000-5500-5600-520-530-630.1289648/
      Chinese: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.cn.md
    • By SniperBuddy
      Hello guys,
      I'm relatively new to the world of hackintosh.
      I'm trying to install the latest Mac OS - Catalina with the help of Opencore, however, this is the error that's displayed while booting from the USB:
       
      https://drive.google.com/open?id=1Xd4V2wZ2fEsgRyfVcXlJHXMPGa85g2s3
       
      You can take a look at my config.plist file from here - https://drive.google.com/file/d/17FZpTcVp4RFSaxdm6yW4uELkt7MaLdmt/view?usp=sharing
       
      I'm using the Acer E575 G laptop with Kabylake (i5 7200u)
       
      Any help would be gladly appreciated!
       
       
       
       
×