Jump to content
duduclx

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

242 posts in this topic

Recommended Posts

Can anyone tell me if this guide will work for e6510? I'm thinking same/similar hardware except screen size.

 

Audio for your Latitude E6510 (codec IDT92HD81B1C5):

 

http://www.insanelymac.com/forum/topic/293863-applehda-patch-requests/?p=2234509

Thanks to Mirone

 

"PlutoDelic

 

Check out my config.plist a few pages behind, have a look at the Graphics values, i did some EDID fixes which resulted on all Video Ports working on Dock (and laptop vga too).

 

Thanks for the AppleALC hint."

 

 

 

Thank you man, I will use your code with my graphics and post the results.

Try the AppleHDA above to your audio! S/L/E

Share this post


Link to post
Share on other sites
Advertisement

please, create specific topic for E6510 audio and other issue not directly concerned by the guide.

 

cheers

Share this post


Link to post
Share on other sites

@duduclx

 

i noticed your Sleep fix in your DSDT fixes, however, it does not look like the machine is getting any sleep. screen turns off, but machine is just as loud as working, the fans dont turn off.

 

Could it be that the fix is not intended for i5-M520 as yours is an i7?

 

Also, is any of these fixes worth it (see attachment), i noticed some of them are similar to yours, but shorter. I found it somewhere in Olarila, but cant seem to find it again.

 

PS, how come mouse movement doesnt wake the display? very odd...

Latitude E6410.txt

Share this post


Link to post
Share on other sites

Sleep is not specific to CPU model, so no, no DSDT patch would apply to an i7 whilst not applying to an i5. There's just no DSDT patch at all.

Share this post


Link to post
Share on other sites

I have a very general question regarding this machine, and i just research and found some supporting reports...bare with me.

 

People, whom received the E6410 with Bios 03 (probably the earliest versions), have reported damaged disks, and quite consistently...after a few bios updates, apparently the symptom rared but did not disappear.

 

I had the laptop with a 300GB disk inside, after 3 months of windows on it, voila, huge delays in response, and every second boot wouldnt make it, but no errors, typical I/O issues from hard drives.

Later on, i got a 500GB on it, and as i described earlier, i got rid of the Optical drive and got a caddy to use a 2nd HDD. Loaded OS X most of the time there, and never had problems, while after a while, the Windows on 500GB started to behave weird once again.

 

Being annoyed by the fact that the Optical sata interface (where the caddy is) is detected as external, i took the risk and switched the HDD's locations, OS X on official HDD place, Windows on caddy.

 

Guess what, last night i watched Deadpool, shut down the machine, turned it on again in the morning, just to see that El capitan wont boot (recovery partition works, so does the EFI as clover loads).

 

A report i read is that SSDs are not affected...

 

anyone suffered something similar, Dell officially does not acknowledge this bug.

 

EDIT: neither Recovery nor USB booting fixes this, Disk Utility is going more retarded with every release, but even FSCK is useless as it cant fix the issue

Share this post


Link to post
Share on other sites

both discs are normal or one of them is an SSD?

 

I have a very general question regarding this machine, and i just research and found some supporting reports...bare with me.

 

People, whom received the E6410 with Bios 03 (probably the earliest versions), have reported damaged disks, and quite consistently...after a few bios updates, apparently the symptom rared but did not disappear.

 

I had the laptop with a 300GB disk inside, after 3 months of windows on it, voila, huge delays in response, and every second boot wouldnt make it, but no errors, typical I/O issues from hard drives.

Later on, i got a 500GB on it, and as i described earlier, i got rid of the Optical drive and got a caddy to use a 2nd HDD. Loaded OS X most of the time there, and never had problems, while after a while, the Windows on 500GB started to behave weird once again.

 

Being annoyed by the fact that the Optical sata interface (where the caddy is) is detected as external, i took the risk and switched the HDD's locations, OS X on official HDD place, Windows on caddy.

 

Guess what, last night i watched Deadpool, shut down the machine, turned it on again in the morning, just to see that El capitan wont boot (recovery partition works, so does the EFI as clover loads).

 

A report i read is that SSDs are not affected...

 

anyone suffered something similar, Dell officially does not acknowledge this bug.

 

EDIT: neither Recovery nor USB booting fixes this, Disk Utility is going more retarded with every release, but even FSCK is useless as it cant fix the issue


please, create specific topic for E6510 audio and other issue not directly concerned by the guide.

 

cheers

 

Yes, but before, can you post your fix patches for hdmi or DP audio with more detailed information?

Mirone helped a lot with this and I was trying to understand which codecs are not supported by Applehda patches and dsdt edits.

I can only load audio driver with voodoohda.kext (including DP > Hdmi > Receiver > TV)  in the Clover's kexts folder.

Cheers!

Share this post


Link to post
Share on other sites

I dont have an SSD at all, but people noticed the different behaviour between SSD and HDD...a lot of e6410 owners report magnetic disks degrading way too rapidly.

 

I switched the disks as i wanted to see if OS X has any benefit of detecting itself as Internal and not External, so the problems came a few weeks after i put it on the HDD Shelf.

Share this post


Link to post
Share on other sites

[...] a lot of e6410 owners report magnetic disks degrading way too rapidly. [...]

Really? Never heard of such an issue affecting the E6410. Where did you get that from?

Share this post


Link to post
Share on other sites

i got everything to work exept shutdown. where should i search to find why the shutdown is not working?

Share this post


Link to post
Share on other sites

Your restarting is working?

My bet is your DSDT edit.

 

i got everything to work exept shutdown. where should i search to find why the shutdown is not working?

Share this post


Link to post
Share on other sites

Your restarting is working?

My bet is your DSDT edit.

Yes Restart is working. Just sometimes with restart during boot it crashes with a wight Screen and then Starts again and Boots properly.

 

I have taken the dsdt from the Package.

Share this post


Link to post
Share on other sites

Hibernation usually is what hangs it up for me, I posted somewhere in this thread how to disable hibernation I think

Yes i have Seen it i will try. Is there anything for WLAN in the dsdt because i have an atheros and activated it through working kext but i have not changed the dsdt.

Share this post


Link to post
Share on other sites

No idea, did not have to change anything in the dsdt to get wireless lan working

Yes i didnt and have WLAN working i just wanted to know if there is anything about WLAN in the dsdt

Share this post


Link to post
Share on other sites

Really? Never heard of such an issue affecting the E6410. Where did you get that from?

 

The machine i have, used to be from a bankrupted organization. I knew the IT guy i got it from and told me that he had to change the disk at least once a year. I did read a few threads at the dell community forums as well, mainly with bios 03 version. Ironically, he used one for himself and said that SSD weren't affected. Sounds a lot like a power failure.

 

Of course, i may be wrong, but in the last 2 years, i had 3 disks dying inside it, but it never came in to my mind that only the Main HDD slot is where the victims lay.

Share this post


Link to post
Share on other sites

someone any idea why my shutdown is not working? the display and Bluetooth and online led are still staying on.

Share this post


Link to post
Share on other sites

someone any idea why my shutdown is not working? the display and Bluetooth and online led are still staying on.

 

can you share the specs of your e6410?

 

@ thread

 

I just read that the ENCR (Latitude ON) and WWAN mPCIe interfaces have no white-listing, many people report having Windows running smoothly on it mPCIe SSD's. Does OS X support booting there? Those tiny cards have their own SATA Controllers inside, should the be normally visible to OS X/Clover just like it was for the BIOS/UEFI right?

Share this post


Link to post
Share on other sites

This is totally off topic and should be addressed elsewhere but allow me clarify this: the WLAN/WWAN slots of these older Latitude laptops are mini PCIe/USB only, not mSATA. One must therefore be extremely cautious regarding the mini SSD cards that could be installed. True mini PCIe SSDs are quite scarce these days (they also always tend to be PATA type, not SATA -i.e. much reduced performance- and of small capacity) and there is an unfortunate but sustained general confusion between mini PCIe and mSATA on the description of most advertised products. This very matter has been subject to substantial discussions all over the Net throughout the years, you can google for it, we're not going to renew this here...

 

So, mSATA SSDs will never be useable in these slots. True mini PCIe SSDs with on-board PATA or SATA controller are required. If you do find a mini PCIe (not mSATA) SSD of a decent size (say 128 to 256Go) with on-board SATA controller and at a reasonable price, please post the details. Many people will be interested, myself included. NB: you'll probably encounter mini SSD cards for Asus Eee PC but these fit an interface specific to those laptops.

 

Just to give you a recap:

E6x00 -> combo mini PCIe/USB slots only

E6x10 -> combo mini PCIe/USB slots only

E6x20 -> combo mini PCIe/USB slots only

E6x30 -> combo mini PCIe/USB slots only

E6x40 -> combo mini PCIe/USB/mSATA slots (1st time support for mSATA, undocumented by Dell)

 

I own a E6220, a E6230 and a E6440 so I can vouch for the above. One can only run an mSATA SSD on those older laptops with an adaptor off the standard SATA HDD slot or the expansion/optical disc bay.

Share this post


Link to post
Share on other sites

MacBookPro6,2

Intel Core i5  2,4 GHz

4GB Ram

ST1000LM014-1EJ164 HDD

Dell NVS 3100M

Atheros 9285: 4.0.74.0-P2P

 

i had to install AtherosWiFiInjector.kext and IO80211Family.kext to activate WLAN i think there is the problem but i don't know where to patch in dsdt

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 tonyx86
      Creating this thread to capture the procedure for installing macOS Catalina on a Dell Latitude E6410 with NVidia 3100m.  This thread will be based on the work done for Mojave in this thread.
    • By ajmcello
      The following files exist on the github:
       
      a) Clover.app-v1.11-5100.zip
      b) Clover_v2.5k_r5100.pkg
      c) CloverISO-5100.tar.lzma
      d) CloverV2-5100.zip
      e) CLOVERX64.efi.zip
       
       
      Is (a) for installing as an app on OSX? What is it for?
       
      What is (b) for, the .pkg? Not exactly familiar with .pkg. I've seen it used in UNIX, but I believe it's also a PKG format for installing packages on OSX. So, what is the difference between this (b), and (a)? (a) is labeled v1.11-5100, while (b) is labeled v2.5k_r5100.
      (c) contains only this file, Clover-v2.5k-5100-X64.iso, which I assume is a pre-bootloader.
      (d) looks like the NON ISO version, to build an ISO?
      (e) Contains CLOVERX64.efi, which is the same CloverX64.efi for Clover.app-v1.11-5100 and CloverV2-5100.zip
       
      Thanks for any explanations. 
       

       
       
       
       
    • By tonyx86
      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).
      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. 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/. 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.

      E6410.zip
    • By Dolamarv
      Hi all, I have been using an x240 thinkpad for more than 2 months as hackintosh and it is very stable. As of now I am in Catalina 10.15.1 and it’s running great until I updated it to the new clover build r5100. My laptop won’t automatically sleep when I close the lid down now. I reverted back to 5099 and close-lid automatic sleep works. I don’t know what caused the problem but I think 5100 fixed a dsdt patching of some sort that that conflicted with my config plist? Thanks in advance!
×