Jump to content
duduclx

[GUIDE] Dell Latitude E6410 Nvidia El Capitan Clover [ENG]

242 posts in this topic

Recommended Posts

Advertisement

Hi Duduclx; I have followed everything for my E6410, but after configuring the clover file and putting the config.plist in efi/clover, I get stuck with the following screen shots; the second screen shot shows the circle sign with mutulated text...

 

What do you recommend me to do ? Will try to give the config.plist file as well here.

 

Thanks for baring with me  B)

 

Bart

I cannot upload the content of my usb stick because in compressed form it is 20 MB which is too big :(

I was successful boot into installer without any error. Put Fake.SMC.kext", "ApplePS2SmartTouchPad.kext", "NullCPUPowerManagement.kext", "VoodooHDA.kext" (If needed) and "VoodooPS2Controller.kext" in "Other" Folder and delete everything, just leave folder "Other"

Share this post


Link to post
Share on other sites

I was successfully boot into the installer without any error during boot. Here how. 

 

1) Extract The Archive

2) Extract All

3) Copy "DSDT.aml" into EFI/Clover/ACPI/patched

4) Copy "config.plist" into EFI/Clover

5) Go to EFI/Clover/kexts and delete everything,  just leave "Other" folder

6) Copy kexts in EFI/Clover/kexts/Other

 

Done, unplug the drive and go to your PC

 

1) Start up your PC and hit F2 for BIOS Setup

2) Select "Load Default"

3) Go on "System Configuration>SATA Operation and change SATA mode from "RAID" to "AHCI Mode"

4) Save and Exit

5) Press F12 on startup

6) Select Your USB drive

7) At Clover screen, go to options

8) Set the following boot_args: -v slide=0 nv_disable=1 kext-dev-mode=1

9) Go to Binaries Patching Menu and set the following FakeCPUID: 0x000206A0

10) Hit Exit

11) Go to your USB Drive, hit space (DO NOT HIT ENTER)

12) Select Boot Mac OS X in verbose mode

13) Once You reach to the installer, follow the tutorial

 

 

 

Hope this help you

Solution Fix.zip

Share this post


Link to post
Share on other sites

Hi all! Wow time flies; Is anybody interested in getting High Sierra installed and working on the E6410. I still love this machine and it is now very affordable. Best 'Bang for the Buck'  :yes: . Please let me know. 

 

Cheers, Bart

Share this post


Link to post
Share on other sites

I am very interested in getting high sierra working on the e6410. Love this machine. Only thing that bothers me is it’s a dual core i7. Not exactly great for video production but still pretty decent.

Share this post


Link to post
Share on other sites
On 10/15/2017 at 1:46 PM, bartrap said:

Hi all! Wow time flies; Is anybody interested in getting High Sierra installed and working on the E6410. I still love this machine and it is now very affordable. Best 'Bang for the Buck'  :yes: . Please let me know. 

 

Cheers, Bart

I actually done it on dell E6410 High Sierra 1 year ago

Share this post


Link to post
Share on other sites
Posted (edited)
On 11/21/2016 at 3:00 AM, duduclx said:

With my setup and guide, battery and battery management and shutdown are working perfectly.

About sleep, Hervé did the trick.

 

One thing upsetting me is to debug what person did and help him to do what i have write.

 

So i prefer skip the "support" part and move to a tool / dev project.

 

I'm happy to see people enjoying hackintosh using one of my guide, or people getting way over (like @midi on the ativ pro).

But i can't spend my time.

 

I prefer install kexts by myself Than using app, to install it where i want and give people some skills.

 

I still think than hackintosh need to learn and use OS X (and unix system) from a certain time.

 

I've started my first hackintosh on an Asus with os x 10.5.1.

About 9 years i use only hackintosh laptop and servers.

 

Hope people will understand what was in my mind and will continu it without me.

 

Learn, test, do, compare and more is up to you !

 

Cheers

@duduclx...can you give me link how @herve do the trick for sleep/wake on this machine ?...best regards

 

Edited by hackintoshmalang

Share this post


Link to post
Share on other sites

I know this is an old thread, but I followed this guide exactly to patch my E6410 DSDT and created a Mojave installer using DosDude's Mojave Patcher.  I just booted the installer and was able to get to the install GUI, but that's as far as I've gotten (need to make time to continue).  Anyone interested in getting Mojave to work on this E6410?

Share this post


Link to post
Share on other sites
Posted (edited)

I started a new thread for Mojave on Dell Latitude E6410 here: 

 

Edited by tonyx86
Refreshed link to new thread

Share this post


Link to post
Share on other sites
Posted (edited)

Just curious - does anyone have sleep working on the Latitude E6410 (with Nvidia NVS 3100m graphics) on ANY version of MacOS?  If so, what version of MacOS and what was the trick?  I'm at the point where my E6410 dual-booting High Sierra / Mojave is working perfectly with the exception of sleep.  Attempts to sleep in both High Sierra and Mojave turn off the display, but the laptop is still on and the only way to recover is to force power-off with the power button.  Thank you for any help.

 

BTW - I did try @Hervé 's suggestion on Page 9 of this thread to apply Rehabman's PRW 0x0D patch (returning 0x0D, 0x00 instead of 0x0D, 0xXX), but that did not work for me.  Even with Rehaman's patch sleep doesn't work for me.  If anyone else has successfully implemented @Hervé's or another sleep suggestion, can you share it?  Thank you.

Edited by tonyx86

Share this post


Link to post
Share on other sites

I currently do not use sleep on my Latitude E6410. I use (x2) ssd(s) on my laptop. [Currently drive #1 is MacOS El Capitan -- following this guide, with several issues I have yet to take the time to resolve; Drive #2 is a dual boot drive with Windows 10 1903 & Ubuntu desktop 18.04] SSD & Sleep/Hibernate (maybe only used to???) kill an ssd drive. (Really don't want to take that chance).

 

A side note, as per your specs on your post of Mojave install, my E6410 is similar in build to yours. Mine is: Dell Latitude E6410 (i5-520m, NVS 3100M, 8GB DDR3 -- Dual 4GB Sticks, 1x OCZ-Vertex 120GB SSD -- MacOS & 1x Corsair Force GT 120GB SSD -- Windows 10 1903/Ubuntu Desktop 18.04, 1440x900 display, BIOS: A17, Wi-Fi: Broadcom  BCM4322 -- Dell Wireless 1510). Any suggestions as to things I would have to change from your install guide of Mojave to make it work? (I will also post this question on that thread)

 

Thanks for your help in keeping this awesome little laptop current!

Share this post


Link to post
Share on other sites
Posted (edited)
On 3/22/2016 at 5:52 AM, PlutoDelic said:

A quick general question on this one.

 

I have installed Clover on the EFI partition in the first disk where Windows resides. I have found out that the only way to detect an UEFI Clover and boot is through the Windows EFI and not the standard one. That being said, i can run Clover without any issue, and this time it even injected the boot options in to the UEFI/BIOS, which i never could before.

 

I need to know if i can avoid having Clover on the USB at all, since it will detect the USB with the OS X installer inside.

 

PS, a year a go i made some config.plist changes which resulted in VGA and DP Port working in Mavericks and Yosemite, it worked through the Dockin Stations as well, although i never got audio from the DP. have a look at the attachment...

 

EDIT: here's the proof of research and trail...

config.plist_VGA+DP.zip

 

@PlutoDelic I'm experimenting with VGA-out on my Latitude E6410 with Mojave.  Your Nvidia configuration in CLOVER config.plist enabled my external VGA port (not working without it).  It turns out that the only thing required from your configuration (at least for me) is the NVCAP.  I was using the wrong NVCAP (the one automatically injected by CLOVER R4961) and yours fixed it!  It looks like CLOVER R4961 injects the wrong NVCAP for 3100m graphics in the Latitude E6410.  Nice work!

Edited by tonyx86

Share this post


Link to post
Share on other sites

@duduclx - I'm not sure, but I'm hoping you might still be paying attention to this thread.  I'm impressed with your shutdown patch in _PTS.  Nice work!!!  I think that your patch may offer a clue to sleep.  Can you please explain how you arrived at your _PTS shutdown patch?  I have reviewed sleep fixes for other Latitude models and they all involved modification of _PTS (and _WAK).  In the other cases, they called _OFF and _ON methods that were defined in SSDTs.  The E6410 doesn't have these _OFF and _ON methods, so I believe the key is to manually set the correct register(s) like you have done for shutdown.  If you can explain how you arrived at your shutdown solution (below), that would be a big help.  Thank you!!!  And thanks for this guide - VERY NICE WORK!

 

    

    OperationRegion (PMRS, SystemIO, 0x0430, One)
    Field (PMRS, ByteAcc, NoLock, Preserve)
    {
            ,   4,
        SLPE,   1
    }

 

 

    Method (_PTS, 1, NotSerialized) 
    {
        If (LEqual (Arg0, 0x05))
        {
            Store (Zero, SLPE)
            Sleep (0x10)
        }
        Else
        {
            APTS (Arg0)
            EV5 (Arg0, Zero)
        }
    }

 

Share this post


Link to post
Share on other sites
Posted (edited)

@duduclx I have proof that your _PTS logic is key to sleep.  I removed the conditional as shown below and sleep "works," but the system wakes immediately with a black screen.  I suspect that your _PTS logic requires some modification and that there is "inverse" logic that needs to be applied to _WAK.  I'm happy to look at this if you can provide insight into how you arrived at your _PTS logic.  Thank you!

 

    Method (_PTS, 1, NotSerialized) 
    {
            Store (Zero, SLPE)
            Sleep (0x10)
    }
Edited by tonyx86

Share this post


Link to post
Share on other sites

I got sleep working on the E6410.  My solution may be helpful to those still running El Capitan on their E6410.  See my solution here: 

 

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 ErmaC
      Slice is glad to present a new EFI bootloader.

      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      https://sourceforge.net/projects/cloverefiboot/?source=directory
      There is a WIKI 
      http://clover-wiki.zetam.org/
      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      Post#2 CloverGrower - create Clover by yourself Post#3 Downloads Post#4 Installation of the bootloader Post#5 How to do UEFI boot Post#6 How to use - common words Post#7 Calculator for Automatic DSDT fix Post#8 Instructions for GraphicsInjector Post#9 ATIConnector patching Post#10 Any kexts patching with some Samples Post#11 CustomEDID Post#12 Hiding unnecessary menu entries Post#13 Instruction for DSDT corrections to do DeviceInjection works Post#14 Development Post#15 Themes Post#16 About kexts injection Post#17 Instructions for P- and C-states generator Post#18 Patching DSDT to get Sleep working Post#19 CPU settings and geekbench Post#20 ACPI tables loading Post#21 DSDTmini Post#22 Custom SMBios Post#23 F.A.Q. Post#24 iCloudFix Post#25 Using mouse. Post#26 How to make orange icons to be metallic Post#27 How to make software RAID (by Magnifico) Post#28 How to modify InstallESD.dmg (by shiecldk) Post#29 Config.plist settings Post#30 Using extra kexts and skipping kernelcache Post#31 Choosing EFI drivers Post#32 Configuration files Post#33 Automatic config.plist creating Post#34 Custom DSDT patches Post#35 How to do sleep/wake working with UEFI BOOT Post#36 DeviceID substitution (FakeID) Post#37 Using Custom OS Icons Post#38 Hibernation Post#39 Floating regions Post#41 Property List Editor Post#42 Blocking Bad Kext Post#43 AAPL,slot-name Post#44 FakeCPUID for unsupported CPU Post#45 Multiple Boot Options - to write into UEFI BIOS boot menu Post#46 How to install Windows UEFI Post#47 How to speedup Clover boot Post#48 Info.plist patching Post#49 Arbitrary device injection Post#50 Non-Standard Legacy Boot Files Post#51 Reboot to Windows UEFI from Mac OSX Post#52 Deprecated Features Post#53 Using UDK2018 Post#54 Device Properties Post#55 Scalable themes Post#56 How to search Clover mistakes (bisection) -----------------
       
      Slice:
      I edited all posts in the thread to correspond to actual Clover revision.
      Please install Clover at least 2652 and use new instructions.
    • By tonyx86
      I was inspired by @duduclx post for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5.  Everything works perfectly (including sleep with the solution described later in this thread).  I'm starting this thread hoping to help others install Mojave on their E6410s.  This thread is not currently intended to be an installation guide and is better suited to the intermediate/advanced hackintosher.  Eventually, it may evolve into a guide.
       
      I started with this thread and ended up with the system captured in the attached files.  The keys were to change the LPCB._DSM.Name to "3b09" and remove all CLOVER configs not necessary for Mojave, plus some other items mentioned below.
       
      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 5, not the original version), USBInjectAll (with custom SSDT-UIAC) 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
      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:
      Sleep is not working with the files attached to this first post, but I have found the solution for sleep/wake.  Read Known Issues below. Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings.  The slider appears in Display settings (because of the backlight DSDT injection in AGP.VID._DSM), but the slider doesn't work (yet).  Haven't spent time to figure this out, but would love help. 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:
      SD Card Slot 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:
      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  
      Known issues and their solutions
      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.  This has been completed and tested, but does not fix the sleep behavior.  This fix is not reflected in the attached files. 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.  The updated VoodooPS2Controller.kext is not reflected in the attached files. This proposed configuration 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 and have not updated attached files to reflect this change. 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.  I have made this change and am testing it on my system, but have not updated the attached configuration files. 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 DSDT patch that duduclx refers to as "Intel GMA Ready" in his El Capitan Guide is not applied correctly to the DSDT attached to this post.  Somehow, the contents of patched _DSM are located in the PCI0.VID device instead of in Method (_DSM) within the PCI0.VID device.  MaciASL didn't complain about this, so it went unnoticed, but it doesn't appear to have had any affect.  I have completely removed this "Intel GMA Ready" patch from my DSDT since it is not necessary for Dell Latitude E6410's with NVidia 3100m, but have not updated the attached DSDT. The assigned value of ACOS in the DSDT is 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), analogous to the assignment of OSYS.  I made this change in my DSDT (not yet reflected in the attached files), but have not observed any behavioral differences (sleep or otherwise).  EDIT: Another way to handle this might be to override _OSI with XOSI (defined in a custom SSDT).  Still learning about XOSI and haven't yet drawn a conclusion.  I'm currently experimenting with ACOS and OSYS equivalent to Win7 and Linux (manually patched in my DSDT which has not yet been updated as a new attachment to this post). 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.  I believe that this should be an internal USB port (portType=2).  My custom SSDT-UIAC.dsl is wrong.  I just 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.  I have not attached an updated SSDT-UIAC.aml to this first post, but my current EFI includes an updated SSDT-UIAC.aml with ports HP15, 16 17 and 18 set to internal (portType = 2).  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.  These changes are not reflected in the attached DSDT.
      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/.  I currently have sleep working on my Latitude E6410 and am continuing to test it.  The solution is documented later in this thread, but files are not yet attached to this first post.  
      Brief Installation Guide (for the experienced Hackintosher):
      Follow duduclx's guide for BIOS config 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) 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

      CLOVER.zip
×