[Guide] Dell Latitude E6410 (Nvidia) Hackintosh: Big Sur, Monterey, Ventura, Sonoma, Sequoia & Tahoe installations with Open Core Legacy Patching

[deeveedee]

I have uploaded my latest Open Core EFI here based on Open Core 1.0.4.  This new EFI includes the following changes from my previously posted OC 1.0.3 EFI:

• Upgraded EFI/BOOT/BOOTx64.efi
• Upgraded EFI/OC/Drivers/*.* (all except for HfsPlusLegacy.efi which did not require an upgrade)
• Upgraded EFI/OC/OpenCore.efi
• Upgraded EFI/OC/Tools/*.*
• Upgraded EFI/OC/Kexts
  • AppleALC.kext 1.9.3 -> 1.9.4
  • BlueToolFixup.kext 2.6.9 -> 2.7.0
  • BrcmBluetoothInjector.kext 2.6.9 -> 2.7.0
  • BrcmFirmwareData.kext 2.6.9 -> 2.7.0
  • BrcmPatchRAM3.kext 2.6.9 -> 2.7.0
  • VirtualSMC.kext 1.3.4 -> 1.3.6
    • SMCBatteryManager.kext 1.3.4 -> 1.3.6
• Modified config.plist
  • Add Booter > Quirks > ClearTaskSwitchBit (Boolean, False)
  • NVRAM > 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102 > OCLP-Version 2.3.0 -> 2.3.2

*** Important ***

In order to keep the Open Core EFI attachment within my 10MB upload limit, I removed IO80211FamilyLegacy.kext from the posted EFI.  After downloading my EFI, add IO80211FamilyLegacy.kext to the EFI/OC/Kexts folder from here.  

Edited April 24, 2025 by deeveedee

[deeveedee]

OCLP Devs have pointed to FeatureUnlock.kext as a source of instability in OCLP-patched Macs.  While I haven't observed any issues that I attributed to FeatureUnlock, FeatureUnlock.kext offers no value to this hack, so I will be removing it from a future posted EFI.   If you want to remove FeatureUnlock.kext from your EFI, do the following:

 

• EFI/OC/config.plist
  • Remove Kernel > Add > FeatureUnlock.kext
  • Remove NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > boot-args > -disable_sidecar_mac (FeatureUnlock argument)
• EFI/OC/Kexts
  • Remove FeatureUnlock.kext

Edited April 24, 2025 by deeveedee

[deeveedee]

Safari 18.5 is not able to load pages in Sequoia 15.5 Beta 3 and Beta 4 on this hack.  Firefox works fine.  Fixed after Apple released KDK (24F74).  Re-applying OCLP post-install patches to Sequoia 15.5 fixes the Safari 18.5 issues that I was seeing.

 

EDIT: I was reading posts in another forum (not InsanelyMac) from 2024 that attempted to help someone with their 1st Gen Intel Arrandale Laptop (same CPU architecture as this Dell Latitude E6410).  The expert in the other forum told the OP to switch to CLOVER (from OC) because "OpenCore does not provide adequate CPU power management for pre-Sandy Bridge CPUs ."  While CLOVER has some "automatic" power management settings, it does NOT provide better power management than OC for pre-Sandy Bridge CPUs. OC just requires the proper ACPI patches (and kernel/kext injections for Big Sur and later).  This Dell Latitude's dGPU and CPU power management is PERFECT when running High Sierra through Sequoia with the EFI's that I have posted. 

 

Note that I initially started with CLOVER for my Mojave and Catalina solutions, so I speak from experience.  When I first started creating a CLOVER solution, I attempted to use the CLOVER "automatic" power management, but it wasn't satisfactory for me.  I switched to static DSDT ACPI patches with CLOVER and that improved power management.  My CPU fan would occasionally run higher than it should have, so I would press <Ctrl> Z to lower the fan.  When I created this thread to attempt installation of Big Sur, I migrated the ACPI patches from my modified DSDT to hot-patching with SSDTs in Open Core.  Power management improved and I no longer ever need to press <Ctrl> Z.  The CPU fan on this hack is silent during most operations in High Sierra through Sequoia.  This laptop actually runs macOS better than it runs "natively supported" Windows 7.

Edited May 9, 2025 by deeveedee

[deeveedee]

I was looking at AppleGraphicsPowerManagement.kext in Sonoma for another hack and noticed this:

 

 

AGPM never dropped MBP6,2 (and even older)

[deeveedee]

Apple released KDK (24F74).  Re-applying OCLP post-install patches with this new KDK (auto-downloaded by OCLP) fixes the Safari 18.5 issues that I was seeing in Sequoia 15.5 RC (24F74).

Edited May 9, 2025 by deeveedee

[deeveedee]

I recently tried something that I've wanted to try on this laptop for a while... I installed an i7-740qm quad-core CPU to replace the i7-620m dual-core CPU.  I was hoping that the laptop would just boot macOS without much work, but that was not the case.  I didn't spend any time to diagnose/debug and immediately re-installed the i7-620m after this failed experiment.  No damage done during this harmless experiment and it gave me a chance to clean out the dust and replace thermal compound.  After re-installing the i7-620m, the laptop booted Sequoia 15.5 (which I'm using to post this).

 

Details

After replacing the i7-620m with i7-740qm, the laptop POSTed, but would not boot Sequoia (screen went black when progress bar reached 50%).  With the i7-740qm, the touchpad did not work in BIOS and the laptop was noticeably hotter.  I use copper shims to enhance CPU and dGPU thermal conductivity with the heat pipe, so the laptop did not experience a thermal shutdown.

 

Spoiler

 

This CPU has a HUGE 23mm x 15mm die.  

 

After replacing the originally installed i7-620m (dual-core Arrandale) with the i7-740qm (quad-core Clarksfield), the laptop booted without issues into BIOS.

 

Spoiler

 

Edited May 14, 2025 by deeveedee

[deeveedee]

Reports in MacRumors suggest that some late-version Safari issues may be resolved by disabling WebGL:

 

defaults write com.apple.Safari WebKitPreferences.webGLEnabled 0

I am not using this hack enough to find use cases that need this, so for those affected, you'll need to test it.

[deeveedee]

This is going to be my last post in this thread and one of my final posts at InsanelyMac.  There are rumors about macOS 26 (the next major release after Sequoia macOS 15).  The rumor mill indicates that at least one Intel Mac will still be supported.  If an Intel Mac is supported, I suspect that Open Core Legacy Patcher (OCLP) will provide continued support for this hack with SMBIOS MBP6,2.

 

I have thoroughly enjoyed working with those who contributed to this thread.  Thank you and good luck to all.

[deeveedee]

I thought the previous post would be my last, but I have a new EFI for macOS Tahoe and I'm addicted to InsanelyMac, so I can't resist.  I'm currently booting macOS Tahoe on this old hack and it works well (albeit, without post-install patches for Video, Audio and Wi-Fi).  After Apple releases the first non-Beta version of macOS Tahoe and after the OCLP Devs release OCLP 3.0.0 for Tahoe, I'll publish my updated EFI for the few that still follow this thread.  When I first created a working macOS solution for Mojave, I never imagined that this hack would still be able to run the last macOS version for Intel.

Edited August 17, 2025 by deeveedee

[deeveedee]

EDIT: I fixed the problem reported below by adding BluetoolFixup boot-arg -btlfxboardid.  The problem was caused by a change in BluetoolFixup.kext introduced in version 2.7.0, not a change in macOS.

 

I haven't been testing as thoroughly as I do on my "production" hacks, so I missed the fact that Bluetooth stopped working at some point in Sonoma.  I'm currently testing with Sonoma 14.7.7.  If someone wants/needs working Bluetooth on this old hack, maybe you can review my EFI and see if there is a problem with USBPorts.kext.  I'm using BrcmPatchRam (and associated kexts) version 2.7.1.

 

EDIT: The internal USB webcam works, so I don't think the problem is USB mapping.  This might be a problem with BluetoolFixup.kext (not the first time that BluetoolFixup has stopped working with a macOS upgrade). Bluetooth Transport incorrectly identified as PCIe.

 

 

EDIT: I fixed this problem by adding BluetoolFixup boot-arg -btlfxboardid

 

EDIT2: The addition of BluetoolFixup boot-arg -btlfxboardid does not affect Bluetooth operation in Ventura (in fact, it might work better), so boot-arg -btlfxboardid will become a permanent addition to my EFI.

 

boot-args: -btlfxboardid

EDIT3: With the -btlfxboardid boot-arg, Bluetooth Transport is properly detected as USB in Sonoma 14.7.7 and newer macOS.

Spoiler

 

EDIT4: @Stefanalmare I tested Sleep/Wake in macOS Sonoma and Sequoia after adding boot-arg -btlfxboardid.  Bluetooth works perfectly through sleep/wake cycles with this boot-arg (I was already using BluetoolFixup boot-arg -btlfxallowanyaddr).  Thank you for offering your custom build of BluetoolFixup.kext here, but when faced with the choice of a custom build and Acidanthera's official release, I always prefer to use Acidanthera's official release.  Since the official release works perfectly simply by adding boot-args, I'll stay with Acidanthera's version.  Thank you.

 

EDIT5: I checked the commits to BluetoolFixup.kext after version 2.6.9 and see that the automatic BoardID patch was removed AFTER BluetoolFixup.kext version 2.6.9. The -btlfxboardid boot-arg is relevant only to EFIs that use BluetoolFixup.kext version 2.7.0 and later.  This problem was caused by a change in BluetoolFixup.kext introduced in version 2.7.0, not a change in macOS.

 

See BluetoolFixup.kext 2.7.0 Change Log

Edited August 22, 2025 by deeveedee

[deeveedee]

For those who wonder whether we should be using boot-arg -no_compat_check or Open Core's Booter Patch "Skip Board ID Check", see this.  I am only using the Booter Patch on this hack because it is what the OCLP Devs use when OCLP builds Open Core EFIs.  I'll stay with the Booter Patch, but I understand why others will prefer to use boot-arg -no_compat_check.

[deeveedee]

Here's a little teaser for things to come ...

 

About This Hack: Tahoe RC1

[AlfredoM]

55 minutes ago, deeveedee said:

Here's a little teaser for things to come ...

 

About This Hack: Tahoe RC1

Yes and what does that mean... if the nVidia graphics cards (kepler) were fully supported with QE/CI, then it wouldn't be as enjoyable without it!

[deeveedee]

@AlfredoM OCLP post install patches are coming.  Just be patient.

 

EDIT: Do you know Oxygen-X1 over at MacRumors?

Edited September 10, 2025 by deeveedee

[AlfredoM]

21 minutes ago, deeveedee said:

@AlfredoM OCLP post install patches are coming.  Just be patient.

 

EDIT: Do you know Oxygen-X1 over at MacRumors?

Yes, if a new OCLP patch would also fully support nVidia Kepler cards QE/CI, then the OCLP team would have to get the Nobel Prize for developers 🙂

[AlfredoM]

On 9/10/2025 at 5:21 PM, deeveedee said:

@AlfredoM OCLP post install patches are coming.  Just be patient.

 

EDIT: Do you know Oxygen-X1 over at MacRumors?

Yes is my Brother 🙂 have the same iMac.

[deeveedee]

This HackBookPro6,2 is now running release versions of Ventura 13.7.8, Sonoma 14.8, Sequoia 15.7 and Tahoe 26.0.  Patiently waiting for OCLP 3.0.0 so that I can apply post-install patches to Tahoe.

 

 

About This Hack: Ventura 13.7.8

Spoiler

 

About This Hack: Sonoma 14.8

Spoiler

 

About This Hack: Sequoia 15.7

Spoiler

 

EDIT: Now running Sequoia 15.7.1 and Sonoma 14.8.1.  Patching with OCLP 2.4.1.

Edited October 2, 2025 by deeveedee
Added About This Hack screenshots

[jackacc]

Opencore-Legacy-Patcher >OCLP-Mod

26 Use OCLP-Mod

Please share the EFI.

[deeveedee]

@jackacc  Please read the first post in this thread.

 

EDIT: Note that OCLP-Mod may restore audio and wi-fi, but it will not restore Nvidia graphics.  Best to wait for the "official" release of OCLP 3.0.0.

Edited November 9, 2025 by deeveedee

[jackacc]

Is the Nvidia NVS 3100m driver-free? No parameters need to be injected in OC DeviceProperties.

Nvidia GT320M?

[deeveedee]

@jackacc It is free. Take some time to create your new NVidia patch and then post your solution when you figure it out.  No offense, but I won't be holding my breath while I wait.

[AlfredoM]

3 minutes ago, deeveedee said:

@jackacc It is free. Take some time to create your new NVidia patch and then post your solution when you figure it out.  No offense, but I won't be holding my breath while I wait.

Some people here seem to be joking, right?
Since when have Nvidia cards, whether Kepler or Tesla, been fully supported in Tahoe26 with full graphics?

It will probably ALWAYS remain just a dream.

[deeveedee]

@AlfredoM Please stop repeatedly posting the same negative {censored}. Your constant complaints about the lack of OCLP patches for Tahoe are not helpful. I have been patient with your statements for long enough. Not any more.

Edited November 10, 2025 by deeveedee

[AlfredoM]

20 minutes ago, deeveedee said:

@AlfredoM Please stop repeatedly posting the same negative {censored}. Your constant complaints about the lack of OCLP patches for Tahoe are not helpful. I have been patient with your statements for long enough. Not any more.

My dear friend, you, of all people, being such a super optimist... why are you getting upset about my personal opinion?
Just stay calm...

[deeveedee]

Easy upgrade from Tahoe 26.2 Beta 1 -> Beta 2. Still patiently waiting for OCLP post-install patches, but I did test a few Apple Apps just to see if they opened. FaceTime opens (and camera works), Terminal opens and is fully functional, Activity Monitor opens and works... Better than I would expect without post-install patches.