Jump to content
tonyx86

Catalina on Dell Latitude E6410 (Nvidia Graphics) With Working Sleep

107 posts in this topic

Recommended Posts

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.3 (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 v14 for sound.

 

Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)

  1. Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings)
  2. If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar)
  3. Download Catalina Installer
  4. Download DosDude Catalina Patcher
  5. Use DosDude Patcher to create Catalina USB Installer
  6. 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
  7. 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)
  8. 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.
  9. 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)
    1. turn-off your laptop
    2. remove A/C power and main battery
    3. press and hold the power button for 30 seconds
    4. restore A/C power and battery
  10. Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8.
  11. 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).
  12. Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading)
  13. 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)
  14. After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB
  15. Select the Post Install Patcher utility
  16. Select only the following Post Install Patches (no other patches / options)
    • Install Patch Updater
    • Legacy Video
  17. After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration
  18. Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext
  19. If you are performing a fresh installation of Catalina:
    • Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  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.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT.
    • 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
  20. 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:
    • Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT.
    • Update IntelMausiEthernet.kext
    • Remove VoodooSDHC.kext from /Library/Extensions
    • Re-install VoodooHDA if necessary (I installed using the Classic method)
  21. 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.
  22. Reboot from your new/upgraded Catalina partition
  23. Welcome to macOS Catalina!
  24. Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type)
  25. Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys)
  26. 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.3
  • CLOVER v2.5k r5103
  • DosDude Catalina Patcher: v1.3.0
  • Lilu.kext 1.4.1
  • AirportBrcmFixup.kext 2.0.6
  • BrcmFirmwareRepo.kext 2.5.1
  • BrcmBluetoothInjector.kext 2.5.1
  • BrcmPatchRAM3.kext 2.5.1
  • IntelMausiEthernet.kext 2.5.0

  • VoodooHDA.kext 2.9.2 v14 (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

  • (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).
  • 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.
  • (Work-around - no permanent solution yet) Cannot turn on Bluetooth after shutting-down with Bluetooth off.  Work-around is to leave Bluetooth on.  I don't use Bluetooth and don't mind, so this will likely be solved by someone else.  If you experience this issue and can't turn-on Bluetooth, I have found that putting the laptop to sleep (Fn-F1) and then waking the laptop restores proper operation of Bluetooth.  I have posted a problem description, logs and problem reporting files in this thread for help with this problem.
  • (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), adding Device (PNLF) and adding the definition for pwm-info in the DSDT.  No surprise that the Latitude E6410 has yet another incomplete ACPI implementation.  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 in the ESP
  • Boot Sectors
    • Install boot0af in MBR
  • Clover for BIOS (legacy) 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)

 

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 :).

 

 

Screen Shot 2019-12-19 at 6.53.51 AM.png

AppleHWSensor.kext.zip

Screen Shot 2020-02-03 at 9.50.18 AM.png

gen_debug

E6410-Catalina-3v5.zip

Edited by tonyx86
Updated attached E6410-Catalina.zip to support sleep on lid close

Share this post


Link to post
Share on other sites
Advertisement
On 12/13/2019 at 12:52 PM, vbmota said:

Theres a chance to use HFS+ and not APFS on Catalina?

You'll have to search and try.  My macOS installations are all in APFS containers.  My Catalina upgrade worked on the first try following the steps in the first post of this thread.  The upgrade proceeded without any issues.  So far, this upgrade seems to have been uneventful and painless.

 

EDIT: After brief testing, I've noticed a couple of issues that I started documenting at the bottom of the first post in this thread.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Slow boot and slow Wi-Fi acquisition are resolved by updating to latest Lilu.kext, BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext, BrcmPathRAM3.kext.  With these updates, system boots fast and Wi-Fi acquisition is immediate.

 

Edit: an added bonus - shutdown is also fast with these updates.

 

Edit 2: External USB ports are now available after sleep with updated Lilu and Brcm kexts.

 

Edit 3: I needed to remove VoodooSDHC.kext from /Library/Extensions, since it was causing Catalina to freeze upon wake.  I can live without the SD Card slot and welcome any SD Card solutions that work with Catalina.

Edited by tonyx86

Share this post


Link to post
Share on other sites

With the exception of the SD Card slot (which no longer works after having to remove VoodooSDHC.kext), it appears to me that the Latitude E6410 (NVidia 3100m) runs better with Catalina than it did with Mojave.  This laptop is a perfect macOS platform!

Share this post


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

With the exception of the SD Card slot (which no longer works after having to remove VoodooSDHC.kext), it appears to me that the Latitude E6410 (NVidia 3100m) runs better with Catalina than it did with Mojave.  This laptop is a perfect macOS platform!

 

I agree. My attempts to install Catalina on Dell devices were all less painful and faster than with the Mojave version.
My only concern was that minor updates and bug fixes would come out.

Also, I would prefer to continue using HFS +, but I have rethought and accepted the challenge of finally using APFS Containers.

Share this post


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

The VGA port on the Latitude E6410 continues to work perfectly in Catalina, thanks to injection of the correct NVCAP as described in the Mojave Thread.  

Screen Shot 2019-12-22 at 4.58.41 PM.png

Great. Did you test to boot with vga monitor connected or it was connected after boot? In my Sierra E6410 I got KP with it and only can use VGA after login process stops.  

Only to check, I am installing Catalina within these days and though about plug a second monitor with VGA. Thanks.

Edited by vbmota
Edit system used

Share this post


Link to post
Share on other sites
32 minutes ago, vbmota said:

Great. Did you test to boot with vga monitor connected or it was connected after boot? In my Sierra E6410 I got KP with it and only can use VGA after login process stops.  

 

I'm booting High Sierra, Mojave and Catalina with the VGA monitor connected (all 3 OSes work fine).  If I boot without the VGA monitor connected, the monitor is not detected if it is connected after booting.  I have no KP issues, but I don't run Sierra.  If you're using NVidia Web Drivers in Sierra, try uninstalling the Web Drivers.

 

My graphics configurations for each OS are as follows (my laptop boots all of these OSes using same config.plist (attached to first post of this thread) and same kexts in EFI/Clover/kexts/Other (attached to first post of this thread):

 

  • High Sierra: using native High Sierra Drivers - no web drivers
  • Mojave: DosDude Mojave patcher 1.3.3 (I believe there was a DosDude legacy video update that I applied after installing with patcher 1.3.3)
  • Catalina: DosDude Catalina patcher 1.3.0
Edited by tonyx86

Share this post


Link to post
Share on other sites

I upgraded to Clover v2.5k r5101 and added Clover install instructions at the bottom of the first post in this thread.  The Clover options that I select may be different from what you've seen in other EFI folders (for example, I select only two BIOS drivers and no UEFI drivers for my Clover installation).

 

Note that I am using the same EFI for triple-booting High Sierra, Mojave and Catalina.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Hi, I am trying to download the E6410-Catalina.zip file but the link is broken, where can I get it?

Share this post


Link to post
Share on other sites

About my laptop, configuration when bought:

  • i3-370M; 3GB RAM; 250GB 7k; dead battery; 65w Power Supply

upgrades I've done so far:

  • 90w Power Supply; 500GB (seccond HDD with caddy); 8GB (2x4GB) RAM; Fingerprint Sensor :frantics:; i5-540M; CoolerMaster MasterGel Maker (11W/m.K)

I'm very pleased with the current configuration - using Windows 10 - I got a fast and almost no-bottleneck system (installing SSD, WiFi A/C + BT4 or 5 card and i7-620m/i7-640m CPU are the missing "pampering" so of course, when I get a nVidia GPU board, I will certainly use a 45w or 55w i7 (whichever is best). I also want to install a PCIExpress54 card with 3x USB3.0 and a backlit keiboard.

 

I did not intend to try to install MacOS until I changed the board with GPU nVidia, but I saw a video today and was instigated, researched and saw it running on an i7 with Intel graphics, this prompted me to try ...

I am studying and tomorrow I will start my attempts, I will try to make it work on my integrated i5 GPU (which is the same as the i7-620m).

I have doubts about catalina running on this Intel 1st IGPU, maybe with DSDT, SSDT ...

Share this post


Link to post
Share on other sites
6 hours ago, imasov said:

... I will try to make it work on my integrated i5 GPU (which is the same as the i7-620m).

I have doubts about catalina running on this Intel 1st IGPU, maybe with DSDT, SSDT ...

 

@imasov If you're saying what I think you're saying, I admire your courage.  Everything you read will show you that no one has succeeded in getting Intel 1st Gen graphics working with acceleration on the Dell Latitude E6410.  That didn't stop me either when I got sleep working on the E6410 for Mojave (and now Catalina).  Since this thread is dedicated to the E6410 with Nvidia discrete graphics, please feel free to start a separate thread for your 1st Gen Intel experiment and post your link here.  I firmly believe that people who do the impossible didn't know it was impossible.

 

If you do install a 45w quad core CPU in your E6410, could you post your Geekbench 4 score?  Good luck!

Edited by tonyx86

Share this post


Link to post
Share on other sites

Some notes from my experience. Partly to add to this post and partly related to an E6410 with Intel graphics.

 

Dell E6410 i5 M560 with Intel Graphics.

 

Some of the information in the steps above is a bit light on in detail, perhaps because I was unable to find any posts to fill in the blanks.

Downloads section: (add)

Download clover installer (currently Clover_v2.5k_r5101.pkg).

Download Clover Configurator (not strictly necessary, but handy for modifying config.plist).

 

Install Clover section:

Not really clear what steps to follow within this section. Perhaps there is a post elsewhere, but I couldn't readily find it. Found a different guide, noted below, which helped.

Install clover bootloader legacy:

Follow guide “[Guide] How to Boot macOS Installer on Laptops using Clover (UEFI/Legacy)“ from elitemacx86. Assume this is correct. Not really clear either. Main issues are which options to choose in the Installer.

Copy the files in the EFI folder from E6410-Catalina.zip into the EFI folder on the USB. Go through each level of folders and copy the files from the .zip to their corresponding folders on the USB. Assume this is correct. Again not really clear. Perhaps someone could fill in the details for this step or post a link which does.

 

For each of the boots from “Boot your Latitude E6410 from the Catalina USB Installer” TO “After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina disk and complete the macOS configuration”:

You boot from the USB drive (which goes into Clover) and select the appropriate partition to start from, either on the USB (external) or the hard drive (internal). The USB loads the boot loader which is required until you are able to boot from your hard drive with the clover boot loader installed on it much later in the process. This is why the boot order is set to USB initially.

 

After post install patcher there are issues, basically the installer screens can’t be seen. This is due to AppleIntelHDGraphics.kext and AppleIntelHDGraphics.kext in System/Library/Extensions on the Catalina hard disk according to “[GUIDE] 1st Generation Intel HD Graphics”.

 

I went back and reformatted the volume to MacOS Extended Journaled, and reinstalled Catalina on it. Once after the post install patcher, I was able to remove the disk and mount it on a Sierra system and remove these kexts from System/Library/Extensions, reinstalled it in the E6410 and rebooted allowing me to complete Catalina OS configuration and first logon. 

If you have an APFS capable OS then you wouldn’t need to reformat. I didn’t hence the reformat to OSE(J). Interestingly the Catalina drive now says it is APFS under GUID and shows containers. Certainly Sierra can’t read APFS so how this happened I don’t know.

 

I'm guessing there is some other way to remove these. Quite possibly using Terminal, but it showed up as a READ-ONLY file system. No idea why.

 

Again installing Clover on the Catalina disk was an issue as the options to use are not really clear, and different from the USB install. I didn’t have “Install Clover in the ESP” selected (as that was not checked on startup) and that failed the install, checking this and removing the UEFI drivers adding boot0af and similar options to the first install, although I can’t remember them and what they were, managed to install. Then it was not clear about copying the contents of the EFI and LE folders to the EFI partition and the system volume. I did so to both, as well as config.plist to both EFI volume and system volume. Perhaps there is a guide somewhere on this, again I didn't find it.

 

I didn’t install the VoodooHDA as I thought I had read it didn’t work. Now I can’t find that reference, so some more research on that to see if it works. There is currently no sound, so it is probably needed.

I turned off sleep, and I also noticed the screen saver control panel didn’t work (although desktop did). Now that I try it again, it seems to have worked and I was able to choose a screensaver and it works.

Whether the Intel HD graphics acceleration actually works is another matter, but I can at least use Catalina on the E6410. The display is normal, and appears to work normally.

 

I’m guessing the WiFi doesn’t work as it has the Intel WiFi. Have yet to investigate that matter.

The config.plist is different to the Nvidia one described here, and I have attached it.

config.plist

Share this post


Link to post
Share on other sites

@g_unt Thank you for pointing out the fact that I was not clear about this being a thread for the Dell Latitude E6410 WITH NVIDIA GRAPHICS.  I have modified the first post in this thread to make that clear.  Installation with HD Graphics is completely different from the steps described in this thread which necessitates a different thread.  The steps I list in the first post will not help you to install on a Latitude E6410 without Nvidia graphics.  Please start a new thread if you intend to work on an HD Graphics solution and feel free to post your link to that thread here.  

 

Not only are the steps in Post #1 incorrect/incomplete for the HD Graphics implementation, but the DSDT that I have attached to post #1 is VERY SPECIFIC to the Nvidia Graphics solution and elements required for Intel Graphics are not present in the DSDT.  Methods in the DSDT have been modified from the original DSDT to incorporate functions needed for Nvidia graphics.  I have no idea what these DSDT mods do to a system with only HD Graphics.

 

Thank you.

Edited by tonyx86

Share this post


Link to post
Share on other sites

I upgraded to CLOVER v2.5k r5102 (from r5101) and briefly tested High Sierra, Mojave and Catalina.  The Latitude E6410 seems to be running perfectly when booting all three of these macOS versions with the EFI attached to post #1 in this thread.  This will be my baseline until the production version of Catalina 10.15.3 is released.  This old laptop is impressive. 

Share this post


Link to post
Share on other sites

Hi everyone!

I'm on windows 10.

Anyone can help me, how to creat the install USB, from this tutorial?

Anyone can help me in Facebook messenger?

Share this post


Link to post
Share on other sites
Just now, arany0218 said:

Hi everyone!

I'm on windows 10.

Anyone can help me, how to creat the install USB, from this tutorial?

Anyone can help me in Facebook messenger?

 

I suggest you to use a Virtual Machine with OSX installed and proceed dosdude1 Patching dmg file.

It will only run in a macOS system.

Search for vmware or virtualbox OSX images, download, run and good luck.

Share this post


Link to post
Share on other sites

@tonyx86 I saw that you also changed your wifi card for one made for mac, correct? how did you turn on the antennas? My Broadcom is inherited from a Macbook Air and has very small connectors and in fact left it badly adapted. Oh, I'm happy to say that I bought a battery for this notebook to live even longer. Cheers

Share this post


Link to post
Share on other sites
Posted (edited)
18 hours ago, vbmota said:

@tonyx86 I saw that you also changed your wifi card for one made for mac, correct? how did you turn on the antennas? My Broadcom is inherited from a Macbook Air and has very small connectors and in fact left it badly adapted. Oh, I'm happy to say that I bought a battery for this notebook to live even longer. Cheers

Congrats on the new battery.  Hopefully we keep the E6410 alive for much longer.  

 

I purchased the Broadcom BCM 94352HMB which is NOT specific to Mac - it is a Windows PC laptop card.  Google it and you'll probably find it on Ebay or an Amazon seller.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Attached is an updated DSDT for the Latitude E6410.  This new DSDT names the FRWR (Firewire) device (purely cosmetic).  I'm not going to add this to Post #1 (yet) until I need to change my baseline (possibly for a future version macOS).

 

Also, I had read somewhere that it was sufficient to add only the "compatible" property to _DSM for IOName matching and that the addition of the "name" property is not necessary if "compatible" is used.  I noticed that without the "name" property in LPCB._DSM, com_apple_driver_eficheck matches IOName "3b07" instead of "3b09."  I don't think this matters other than to show that macOS driver discovery does behave differently (at least in one case) if the "name" property is eliminated and only the "compatible" property is specified.  You'll note that my DSDT specifies both the "name" and "compatible" properties in some Device _DSMs - I'll be leaving it this way after discovering this one difference.

E6410 DSDT - Add FRWR.zip

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 rodrinico19
      Hola a todos, primero que nada estoy muy contento de a ver econtrado un foro de español sobre hackintosh.
      Mi problema consesite en que descargue unos drivers de esta pagina: https://github.com/chris1111/Wireless-USB-Adapter-Clover
      Seguí los pasos instale los kets en la carpeta EFI/CLOVER/OTHERS todo tal cual como dice ahi la instalación. luego segui los pasos de configurar la red dentro de configuracion del sistema etc.
      Lo cual el nombre me quedo en en0.
      El driver o kets funciona bien es reconocible por el S.O de hecho conecta la red, pero me dice que no tiene IP AUTO ASIGNADA Y LA OTRA QUE HAY UNA DESCONEXION A CADA RATO(como que desconectaras y conectaras el dispositvo usb a cada rato)
      Me gustaria que me ayuden con eso si es posible, Muchas Gracias!!
    • By DI2edd
      Hi,
       
      I'm writing from a Catalina QEMU/KVM VM which, I must say, works pretty damn well besides the fact that rebooting just doesn't work. But first, a bit of background:
      I'm using OpenCore 0.5.5 through DuetPkg because I'm forced on SeaBIOS (legacy boot) because of legacy IGD passthrough (OVMF doesn't support the semi-hack that's needed for it to function), and that works well enough; I switched from Clover because it didn't allow me to use the "host" cpu model on QEMU, which OpenCore did, and so far so good.
       
      The problem is that, whenever i attempt a reboot, the screen would just turn black and thats's it. I can even see that every 30 seconds it polls the battery's status through ACPI (I modified QEMU for that and left some debugging printfs).
      On the other hand, shutting down works as expected. One thing I noticed is that, on shutdown, I can see the last line of verbose output on the screen is "CPU_HALTED", whereas on reboot I don't get that (don't even know if that's to be expected).
       
      The point is that I'm not even sure this is a bootloader issue, because I booted a Fedora live ISO through OpenCore, and that rebooted with no problems, but at the same time I remember that with Clover I didn't have such an issue. Perhaps it was one of Clover's "Fixes" that is not automatic with OpenCore?
       
      Anyway, I attached my config.plist.
       
      Thank you.
      config.plist
    • By SniperBuddy
      I'm trying to install Codec Commander in Catalina.
      While copying the hda-verb file in /usr/bin , I'm getting an error that the file system is read only.
      Is there any way to complete this install?

    • 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
×