Jump to content
wmchris

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

1,738 posts in this topic

Recommended Posts

Advertisement

Hi @All,

 

About data corruption on XPS Skylake series, I want to clarify something we(@darkhandz, @gujiangjiang @shixuev5 @lzt7star ...) discussed here in GitHub[in Chinese].

 

4 brief conclusions:

  • data corruption has nothing to do with HWP(syscl and @darkhandz have experienced data corruption even with GenerateC/PState)
  • data corruption has nothing to do with specific hard disks, because Toshiba XG3, Hynix PC300 have same issue 
  • data corruption seems to be triggered when we put macOS into sleep, but data corruption will not always happen when we put computer to sleep
  • data corruption has nothing to do with system version, both El Captain and Sierra have the data corruption issue

@darkhandz has captured some important screenshots after data corruption indicating AppleFSCompression error. But Pike didn't think this log is sufficient to pinpoint the issue. Some suggestion from Pike can be referred here[see posts part]

 

We need more information, so guys don't hesitate to upload or share your experiences once the data corrupt. Thank you!

 

syscl

Share this post


Link to post
Share on other sites

Hi everybody,

 

sorry if this question is too obvious or alarmist, but i the case of a sudden data corruption 

 

- are you able to recover from the recovery partition via time machine or do you have to make a reinstall and then use time machine

- or do you have to have some kind of cloned image ready 

 

My XPS is running very well thanks to you guys and i really like to keep using it. But the threat of a sudden data corruption makes me a little nervous, because i wanted to use the XPS as my main frontend development machine to do client work.

 

thank you for any tip.

Share this post


Link to post
Share on other sites

Hi everybody,

 

sorry if this question is too obvious or alarmist, but i the case of a sudden data corruption 

 

- are you able to recover from the recovery partition via time machine or do you have to make a reinstall and then use time machine

- or do you have to have some kind of cloned image ready 

 

My XPS is running very well thanks to you guys and i really like to keep using it. But the threat of a sudden data corruption makes me a little nervous, because i wanted to use the XPS as my main frontend development machine to do client work.

 

thank you for any tip.

If you shutdown XPS(Skylake) instead of putting it into sleep, I think your data will be safe. I want sleep to be fully functional, thus I want to figure out the issue.

 

Anyway, booting from solid state disk is pretty fast.

 

syscl

Share this post


Link to post
Share on other sites

Hi everybody,

 

sorry if this question is too obvious or alarmist, but i the case of a sudden data corruption 

 

- are you able to recover from the recovery partition via time machine or do you have to make a reinstall and then use time machine

- or do you have to have some kind of cloned image ready 

 

My XPS is running very well thanks to you guys and i really like to keep using it. But the threat of a sudden data corruption makes me a little nervous, because i wanted to use the XPS as my main frontend development machine to do client work.

 

thank you for any tip.

most of the time you can recover it from within the recovery system. Only if this fails you have to reinstall directly from a time machine backup. But dont forget: not all XPS15 suffer from this issue. I only read about it here, never seen it in real life and i've multiple machines.

Share this post


Link to post
Share on other sites

Hi @all,

Today I have notice strange battery issue. I don't know if it is caused by the BIOS update, but it appears under Windows 10 & 10.12.3. My battery is only charging to 88% and battery indicator shows that battery is fully charged, I have downloaded app called battery monitor an its shows that the full capacity of my battery is 6,519 mAH and designed capacity is 7,368 mAH. As far as I know my XPS comes with 84whr battery (84whr * 11.1 = 7.567), does anybody have the same issue with battery?

Share this post


Link to post
Share on other sites

Interesting note: when changing SMBIOS (both in Clover and kext) to MBP13,3, onboard HDMI and HDMI via the USB-C adapter stop working entirely.

 

I can leave the kext alone (still MBP13,3) but change the Clover config back to MB9,1 and both ports start working again.

 

What changes other than obvious SMBIOS settings like serial and board ID did you make to get the MBPro 13,3 definition to work? I couldn't get it to run more than two minutes without a KP just testing out the default definition. I really need to get a working laptop system definition because the iMac definition won't let me control the screen auto-dimming or give me access to advanced battery settings.

Thanks

Share this post


Link to post
Share on other sites

Hi @all,

Today I have notice strange battery issue. I don't know if it is caused by the BIOS update, but it appears under Windows 10 & 10.12.3. My battery is only charging to 88% and battery indicator shows that battery is fully charged, I have downloaded app called battery monitor an its shows that the full capacity of my battery is 6,519 mAH and designed capacity is 7,368 mAH. As far as I know my XPS comes with 84whr battery (84whr * 11.1 = 7.567), does anybody have the same issue with battery?

same here. The battery just wears off very fast, so i would say it's "normal" after a decent amount of time in usage. Mine is at 6218mAh after 192 load cycles. i suggest changing the charge behaviour in the EFI to "always on AC" to reduce stress on the battery.

Share this post


Link to post
Share on other sites

same here. The battery just wears off very fast, so i would say it's "normal" after a decent amount of time in usage. Mine is at 6218mAh after 192 load cycles. i suggest changing the charge behaviour in the EFI to "always on AC" to reduce stress on the battery.

 

Could you please put it into the guide? Cheers ;)

The Dell XPS 9550 is ALMOST PERFECT, right? Just few things to make it the PERFECT hackintosh:

- Audio!! Without the known glitches.

- Thunderbolt (just to make sure it works).

- Hibernation (and maybe sleep).

- SD reader (who cares).

- Every patch in SSDT instead DSDT. Would make it more robust for bios changes. And easier to make it work for everyone (and maybe something automated).

 

This is almost perfect!! Good Job ;)

Share this post


Link to post
Share on other sites

Upon booting into the OS X Installer, I am not given a choice of global display language.  The language defaults to Chinese, which is difficult for me as I really only speak English.  I'm able to use DiskUtil and start the installation from memory, because I've done it before - but I'd love to know what caused this and whether I'll end up with a Chinese version of OS X installed somehow.  Any clues?

Share this post


Link to post
Share on other sites

Upon booting into the OS X Installer, I am not given a choice of global display language.  The language defaults to Chinese, which is difficult for me as I really only speak English.  I'm able to use DiskUtil and start the installation from memory, because I've done it before - but I'd love to know what caused this and whether I'll end up with a Chinese version of OS X installed somehow.  Any clues?

You can easily switch the system language after finishing the setup. I also had a Chinese setup somehow.

Share this post


Link to post
Share on other sites

Upon booting into the OS X Installer, I am not given a choice of global display language.  The language defaults to Chinese, which is difficult for me as I really only speak English.  I'm able to use DiskUtil and start the installation from memory, because I've done it before - but I'd love to know what caused this and whether I'll end up with a Chinese version of OS X installed somehow.  Any clues?

 

You can change the language into clover configuration file (config.plist): https://clover-wiki.zetam.org/configuration/gui#gui_language

Share this post


Link to post
Share on other sites

Could you please put it into the guide? Cheers ;)

The Dell XPS 9550 is ALMOST PERFECT, right? Just few things to make it the PERFECT hackintosh:

- Audio!! Without the known glitches.

- Thunderbolt (just to make sure it works).

- Hibernation (and maybe sleep).

- SD reader (who cares).

- Every patch in SSDT instead DSDT. Would make it more robust for bios changes. And easier to make it work for everyone (and maybe something automated).

 

This is almost perfect!! Good Job ;)

- I'm curious to know what audio glitches you have. Can you go into detail a bit more? The only problem thus far is that when you wake from sleep, sometimes the audio doesn't work and you have to plug in a headphone and remove it to get the speakers working again. 

 

- SD Reader: Not likely that there's going to be a driver, however I'm really considering hiring a developer through freelancer who can create us a working driver.

Share this post


Link to post
Share on other sites

You can easily switch the system language after finishing the setup. I also had a Chinese setup somehow.

accidentally it was on chinese in the installation config.plist. i changed it to en_US in the git.

Share this post


Link to post
Share on other sites

Thanks wmchris,

 

I upgraded from El Capitan via your repo files to Sierra 10.2.3 :)

Steps I took:

  1. Downloaded Sierra installer running my old el cap install
  2. Ran the installer in el cap to prepare the install partition
  3. totally failed using my config.plist and kext set for 10.2
  4. switched to your install set and created a usb-stick with the sierra installer
  5. followed your guide to get your CLOVER files on it
  6. rebooted
  7. fixed the language ;)
  8. rebooted and installed sierra
  9. followed your steps to get the fresh install to boot
  10. created a new hacknvme kext
  11. rebooted with your post-install config.plist with my smbios edited in
  12. works!

 

Then I noticed:

  1. Touchpad is not properly recognized
  2. I don't like your HWP setting, the CPU is scaling to much upwards
  3. the GPU does not appear to be a great accelerated as it was under el cap
  4. Sound is not working. Not with the proper SSDT, AppleALC.kext and CodecCommander - still investigating

 

I adjusted your config.plist to not use your SSDT hotpatching at all, but my trusted set of pre-patched SSDTs. It works! But still the same thing, I don't like HWP and GPU speed. The CPU package draws more power than with el cap.

 

Maybe it's a fix in the config.plist, a patch or whatnot. But sierra is a go :)

Share this post


Link to post
Share on other sites

think i said before i'm using the toshiba and never had one corruption so far. So i doubt it has something to do with the SSD itself.

 

 

i used the HWP kext for months in the past with ElCap and had no corruption at all. Additionally i dont think that this simple command in the kext is able to make the SSD corrupt. If you want to use the kext see gymnaes 10.11 tutorial for the 9550. He has published a script for reloading HWP after sleep. I personally suggest using the clover flag -> much easier and from the same developer.

 

they're are two different KP. 1. if you use a different SMBIOS you should always be sure to set it correctly and 2. if you use a skylake smbios (which provides cpu informations) you should not provide additional CPU informations as ssdt

 

so to be clear setting HWPEnable=true in clover automatically reloads HWP after sleep with no additional configuration?

And what do you mean by 'set SMBIOS correctly'? I used clover configurator wizard to generate a new SMBIOS for MacBookPro13,3. Boots fine and runs with HWP. When I try generate an SSDT with SSDTprgren (with HWP disabled in clover and no kext) then I get KP. I set proper frequency vectors with Piker's frequenyvector edit script- same issue.

Can anyone really confirm that GPU power management fully works with HWP? Rehabman said X86platformplugin doesn't load with HWP enabled which means GPU power management isn't fully implemented. 

Share this post


Link to post
Share on other sites

so to be clear setting HWPEnable=true in clover automatically reloads HWP after sleep with no additional configuration?

And what do you mean by 'set SMBIOS correctly'? I used clover configurator wizard to generate a new SMBIOS for MacBookPro13,3. Boots fine and runs with HWP. When I try generate an SSDT with SSDTprgren (with HWP disabled in clover and no kext) then I get KP. I set proper frequency vectors with Piker's frequenyvector edit script- same issue.

Can anyone really confirm that GPU power management fully works with HWP? Rehabman said X86platformplugin doesn't load with HWP enabled which means GPU power management isn't fully implemented. 

 

Nope, for met with el cap at least the cover flag did not automatically reload HWP after sleep, hence the script. The kext, clover flag and script are not mutually exclusive and it doesn't hurt to have them all.

Share this post


Link to post
Share on other sites

Hello! 

 

One week and no data corruption! But now, i'm using time machine xDD

 

Well, now i have another problem, hdmi video output not work and, when i plug my Dell DA200 into usb-c port nothing happend. I try hdmi, vga, usb and ethernet and nothing recogniced D:

 

I have the same SMBIOS like config at first post (iMac 5K 27") maybe i need to change to macbook pro?

 

Thanks for all.

 

 

 

EDIT:

 

 

 

Fixed, i change my smbios to macbook13,3, added my board-id to kext and now HDMI / VGA works hot-plug. But usb in da200 not work D:

Share this post


Link to post
Share on other sites

After some fiddling now I got all working, Audio via AppleALC and normal boot.

 

But overall the system is not as snappy as it was with El Capitan, the fan spins up more, more heat is generated. Something is not right yet. Maybe "too" many fixes?

I'm using the same HWP settings as with el Capitan, so unless whmchris's plist introduces fixes which slower the system, it's Sierra itself. Did not expect that

 

But Sierra works.

Share this post


Link to post
Share on other sites

After some fiddling now I got all working, Audio via AppleALC and normal boot.

 

But overall the system is not as snappy as it was with El Capitan, the fan spins up more, more heat is generated. Something is not right yet. Maybe "too" many fixes?

I'm using the same HWP settings as with el Capitan, so unless whmchris's plist introduces fixes which slower the system, it's Sierra itself. Did not expect that

 

But Sierra works.

 

There are plenty real MacBook users on internet forums who report more fan noise and heat after installing Sierra in comparison to El Capitan. It's either macOS is more demanding on CPU or it is a bug that needs to be fixed in future updates. Who knows.

Share this post


Link to post
Share on other sites

There are plenty real MacBook users on internet forums who report more fan noise and heat after installing Sierra in comparison to El Capitan. It's either macOS is more demanding on CPU or it is a bug that needs to be fixed in future updates. Who knows.

 

That wouldn't be too surprising given Apple's track record. In the past waiting for the first point release was enough :) Could also be all the background services, which are just getting more and more

Share this post


Link to post
Share on other sites

There is this weird hiccup now, which could pertain the touted data corruption.

 

My EFI partition contains files with 0 byte size, illegal characters and which are undeletable. I had to rename the "10.12" kext folder, create a new version and copy the needed kexts from my USB bootstick into it. This setup lasts for 1-2 boots or so - then the EFI files become corrupted again. I cannot tell which files do become corrupted, but so far replacing the kexts did it. I consider the EFI parition to be at fault, hence I rance fsck_msdos via single user mode and it yielded an endless stream of errors, which all were fixed. The files, though, are still there.

 

Tonight I'll use SystemRescueCD to re-check the EFI parition with its tools, try to delete these files and if nothing helps, salvage what is good and reformat the EFI parition and reimage it. This problem only occured while upgrading to 10.12 - or maybe it only became visible. 

 

The HFS+ parition of OS X also shows errors which the normaly fsck did not fix, but which were fixed with

/sbin/fsck_hfs -drfy /dev/disk0s2

I do hope this does not indicate a corrupted drive.

Share this post


Link to post
Share on other sites

There is this weird hiccup now, which could pertain the touted data corruption.

 

My EFI partition contains files with 0 byte size, illegal characters and which are undeletable. I had to rename the "10.12" kext folder, create a new version and copy the needed kexts from my USB bootstick into it. This setup lasts for 1-2 boots or so - then the EFI files become corrupted again. I cannot tell which files do become corrupted, but so far replacing the kexts did it. I consider the EFI parition to be at fault, hence I rance fsck_msdos via single user mode and it yielded an endless stream of errors, which all were fixed. The files, though, are still there.

 

Tonight I'll use SystemRescueCD to re-check the EFI parition with its tools, try to delete these files and if nothing helps, salvage what is good and reformat the EFI parition and reimage it. This problem only occured while upgrading to 10.12 - or maybe it only became visible.

 

The HFS+ parition of OS X also shows errors which the normaly fsck did not fix, but which were fixed with

/sbin/fsck_hfs -drfy /dev/disk0s2
I do hope this does not indicate a corrupted drive.

Similar thing happened to me couple of days ago. Had hwp enabled. Xps went to sleep/hibernation? Then efi corrupted. Tried to rescue it but no luck. Had to format the efi from windows. Then booted the macos partition from usb and reinstalled Clover and efi files

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.

Announcements

  • Similar Content

    • By Raffay1234
      I'm transitioning from Clover to Opencore. I thought the process will be simpler but it turns out it isn't. I have created a bootable Catalina USB with Opencore but stuck at this error. I have attached my EFI and the verbose output. Anyone please provide some guidance please?
       
      The laptop is HP Pavilion 15 Gaming:
      Intel Core i7-9750H
      16GB RAM
      256GB SSD + 1TB SSD
      PS2 Keyboard + I2C Trackpad
       

      EFI.zip
    • By tlefko
      Version Info
      This build is compatible up to Big Sur Beta
      Now Compatible with macOS 11 Please leave feedback with issues or w/o Comitted to Updating up to OS 11 MULTITOUCH TOUCHSCREEN SUPPORT Latest Release Notes
      Fixed Bluetooth and Wifi Stability Issues Improved Preformance and Power Managements Can Provide Files for Display Overrides Additional Patches for 3K Display updated for 15.4 rev 1 if using unsupported wifi card disable it in bios use config.plist not HD520 Perfect Sleep/Wake for 1080P Model no-touch, still bugs for 3K Exact same functionality as Catalina Notes
      Never tested USB C except for charging, works great USB devices eject on sleep (not really an issue) 4K model has minor sleep wake issues occasionally, 1080P is fully functional 4K sleep has been heavily improved however and glitches are rare, fixed by reopening lid POST
      run sudo pmset -a hibernatemode 0 If on 3K disable sleep completely for maximum stability If no mouse, install all voodoo kexts using Kext Utility Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. You can easily view all the SSDT patches along with configuration files for the bootloader as they are all documented clearly in the files. This does include a copy of Clover, which of course I do not contribute to and am only responsible for the provided files, patches, and kext placements This guide provides a working setup with little knowledge of the topic and without "optimization" (because often they can break things). But, it is fully functional and preforms properly and is stable
      Make sure you are using DW1560 for wifi or else KP. If not using remove BRCM kexts from CLOVER>kexts>other. BIOS Setup
      Set all SATA operation as AHCI Disable Secure Boot, Fast Boot For Coil Whine improvement disable C-States Enable UEFI Booting INSTALL (VERY IMPORTANT)
      Due to structural changes in the setup of apple's Big sur, this EFI cannot boot the installer it can only boot into a system / device that has already been created and setup. To do this, you need to install Big Sur to a virtual machine (lots of guides online) and then create an dmg of that system, and restore it onto your HDD using the 'dd' command There are various guides online how to get this virtual machine setup complete. You can then use the attached EFI folder to boot and use macOS big Sur You can use this video to show you how to get your macOS pre-installed onto your hard drive https://www.youtube.com/watch?v=HMU3nhcbWHw Boot Entry Setup
      Boot into the BIOS of the computer, then navigate to the Boot setup (or entries (not sure what it is called exactly, but it will be a list of the options your computer selects to boot) Click add new, and make sure the USB isn't plugged in. Select the only option that is avaiable, and in FS0 navigate to Boot/BOOTx64. Add this as an entry, then select this as whatever priority you would like. Messages and Facetime
      Gnerate your own Serials, Board Numbers, MLB There are various guides online to do this and as default they're set to essentially Null (Fakeserial) This is fairly straightforward and there is lots of external recourses, or you can contact me for support. Headphones and Audio
      All audio from speakers should work perfectly along with Bluetooth and USB audio To resolve headphones static issue (wired) install combojack Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions. Donations
      Send me a coffee lefkotyler@gmail.com  
      Latest releases hosted here https://github.com/tlefko/XPS-13-9350-Big-Sur/ along with faster replies
      EFI.zip
    • 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 am no longer maintaining the installation files in this first post.  Refer to my Catalina thread for the latest guidelines / files for installing macOS on this Latitude E6410 with Nvidia graphics ***
       
      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).
      (Solution to this issue is to remove Device (PNLF) from the DSDT): Some users experience display issues.  Solution is to remove Device (PNLF) from the DSDT.  The attached DSDT currently still includes Device (PNLF), so you will need to edit the DSDT to remove PNLF. USB sleep/wake power IORegistry keys are no longer provided in IOUSBHostFamily.kext after High Sierra 10.13.6.  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. 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 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.  
      Screenshots
       
       
      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-v4.zip
    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.x (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured 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;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v15 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
       
      If you want to upgrade to 10.15.5, see instructions at this post.
       
      If you want to upgrade to 10.15.4, see instructions at this post.  
       
      Follow instructions below for 10.15.2 and 10.15.3.
       
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER (LEGACY - NOT UEFI) on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here: Replace 3rd-party kexts in EFI/Clover/kexts/Other with those in the attached EFI folder.   Replace EFI/Clover config.plist with the attached config.plist (Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values) Replace EFI/Clover/ACPI/patched with the files in the attached EFI/Clover/ACPI/patched Replace 3rd-party kexts in /Library/Extensions with those in the attached LE folder Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method for Catalina) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.5.02 CLOVER r5118 DosDude Catalina Patcher: v1.4.4 Lilu.kext 1.4.5 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareData.kext 2.5.3 BrcmBluetoothInjector.kext 2.5.3 BrcmPatchRAM3.kext 2.5.3 IntelMausi.kext 1.0.3 (Not IntelMausiEthernet.kext)
      EFICheckDisabler.kext 0.5
      VoodooHDA.kext 2.9.2 v15 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (Solved - no further work required) Clover r5118 requires the config.plist key <key>NoDefaultProperties</key><false> to permit macOS to boot with Clover's "Inject Nvidia" = True.  See details here.  config.plist in the attached E6410-Catalina.zip archive includes this change. (Solved - no further work required) EFICheck is loaded.  Solution is to install EFICheckDisabler.kext which you can get here.  EFICheck.kext is included in the attached E6410-Catalina.zip archive. (Solved - no further work required) Some users experience display issues.  The solution is to remove Device (PNLF) from the DSDT.  Use the attached DSDT.  Removal of PNLF will disable sleep on lid closure.  Device (PNLF) can be added without modifying the DSDT by enabling the Clover PNLF ACPI patch.  The attached Clover config.plist enables the PNLF DSDT patch.  Disable the Clover PNLF patch if you experience display issues. (Solved - no further work required) USB sleep/wake power IORegistry keys are not injected (not included in Mojave's or Catalina's IOUSBHostFamily.kext).  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. (No solution yet) Brightness slider does not work in System Preferences > Displays.  Brightness is easily controlled with Dell brightness keys.  There is some work on this later in this thread, but I will not be solving this as I'm content with the Dell brightness keys (and Ambient Light Sensor works to auto-adjust brightness). (No intention to solve) Display Settings in System Preferences are "garbled" when bright slider is visible.  This is a known issue with the legacy graphics patch and does not affect laptop operation. I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Solved - no further work required) Brcm firmware does not update when using BrcmFirmwareRepo.kext in /Library/Extensions.  Solution is to install BrcmFirmwareData.kext and BrcmPatchRAM3.kext in E/C/k/O with Clover "Inject Kexts" = YES. (Solved - no further work required) Laptop does not sleep when closing lid.  Solution appears to be a combination of adding Notify (LID0) code to Method (BTNV) and adding Device (PNLF) in the DSDT. I am using the same EFI for High Sierra 10.13.6, Mojave 10.14.6 and Catalina 10.15.3 and it works in all three macOSes. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      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 (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options (Install Clover LEGACY - NOT UEFI)
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (LEGACY - NOT UEFI) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Screenshots
       
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       
      AppleHWSensor.kext.zip
      gen_debug
      E6410 Catalina-5v2.zip
×