Jump to content
tonyx86

Mojave on Dell Latitude E6410

57 posts in this topic

Recommended Posts

Posted (edited)

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 except for sleep.  I'm starting this thread hoping to help others install Mojave on their E6410s and to diagnose and resolve the sleep issue.  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 (Many thanks, @duduclx !!!) 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.5 (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 (display goes blank, but power light stays on.  System cannot wake and must be forced off with power button)
  • 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)
  • Camera (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: @PlutoDelic) for working external VGA display.
  • Headphone jack
  • Display Port (tested using DP > HDMI adapter)

 

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.

 

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

 

Screen Shot 2019-06-08 at 10.19.59 AM.png

Screen Shot 2019-06-08 at 12.11.23 PM.png

CLOVER.zip

Edited by tonyx86
Revised Mojave patcher instructions

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)

EDIT: I found the suggestion mentioned by @duduclx here but it does not resolve the sleep problem for me.  The suggested solution was to apply Rehabman's PRW 0x0D patch.  This patch did not change the behavior of my laptop and did not resolve the sleep problem.  Still looking for a sleep solution.

Edited by tonyx86

Share this post


Link to post
Share on other sites

Installed BrcmPatchRam2.kext and BrcmFirmwareRepo.kext to enable Bluetooth.  Updated Post #1 to reflect the working status of Bluetooth.

Share this post


Link to post
Share on other sites

Changed audio solution to VoodooHDA (from AppleALC) to resolve slow boot issue.  Updated Post #1 to reflect change.  Only remaining issue is Sleep.  Mojave 10.14.5 is OUTSTANDING on this laptop.  Will be PERFECT when sleep is resolved.

Share this post


Link to post
Share on other sites

@tonyx86...hi how is about battery consumption ? and core frequency GPU ...my dell 6410 nvidia stuck at 405 mhz gpu frequency, cause my battery drain out prety fast...do you mind share your EFI ?, thanks

Share this post


Link to post
Share on other sites
Posted (edited)

@hackintoshmalang my EFI is shared as an attachment to the first post in this thread.  Battery life is OUTSTANDING.  With Mac Model set to MacBookPro 6,2 and LPCB._DSM.Name set to "3b09," power management works great with no CLOVER configs.  CLOVER Enable C and Enable P states actually screws up speedstep. Note my clover config.plist attached to post 1 (in the Zip file).  No CPU configs necessary.

 

Have you solved sleep?

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

@hackintoshmalang I noticed that AGPM (AppleGraphicsPowerManagement) was not loading for my GPU.  Closer inspection of the IORegistry shows that the Nvidia 3100m GPU has a device ID of 0x0a6c which does not have an entry in AppleGraphicsPowerManagement.kext for MacPro 6,2.  Injecting device-id of 0x0a29 (a device that does exist in the AGPM.kext/config.plist) causes AGPM to load.  The other device to try is 0x0a34 (it is the only other device listed in AGPM.kext for MacBookPro 6,2.  Do you know enough to experiment with DSDT injection of these device IDs?  If so, experiment with them to see if they help increase your battery life. 

 

I also renamed ECDV to EC in my DSDT to cause AppleBusPowerController to load (wasn't loading before).  Based on what I've observed of other patched DSDTs for the E6410, a lot is missing.  All the patched DSDTs that I've found for the E6410 include only applications of the basic, well-known patches (except for @duduclx 's very clever shutdown fix which I'd love to know how he figured that out).  I've only started looking at the E6410 a couple of days ago and I'm out of time for now, but will continue experimenting.  Please post your findings here.

 

EDIT: A benefit of manually patching the DSDT for Nvidia Graphics is that the Display Brightness slider now appears in the Display Preferences (see attached screenshot).  The slider doesn't work, so I have some homework to do.  Still controlling brightness with the keyboard.  I have the display brightness slider working on my Thinkpad T61 running Mojave 10.14.5, so I'm looking at my Thinkpad to see if I can figure out why the Latitude E6410 slider is visible but sliding it does not change brightness.

 

Screen Shot 2019-06-11 at 3.19.42 PM.png

Edited by tonyx86
Added comment about shutdown fix

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/11/2019 at 12:34 AM, hackintoshmalang said:

@tonyx86...hi how is about battery consumption ? and core frequency GPU ...my dell 6410 nvidia stuck at 405 mhz gpu frequency, cause my battery drain out prety fast...do you mind share your EFI ?, thanks

@hackintoshmalang I've been working on my E6410 for 3:20 and just realized my laptop is unplugged.  Battery indicator shows 23% remaining. Over 3 hours on battery from 2010 - not bad.

 

@hackintoshmalang I'm running again without the A/C adapter to get a better feel for battery life.  It appears that these items made the difference:

  • Inject device-id 0x3b09 for LPCB (in concert with selecting Mac Model MacBookPro 6,2)
  • Do not add any CLOVER CPU configs (e.g. don't enable Generate P and Generate C states)
  • ECDV -> EC rename (to get AppleBusPowerController to load)
  • injecting the device-id for Nvidia graphics (0x0a29) (to get AGPM to load)
  • Follow performance management tips I provided in Post #1 of this thread

 

My laptop fan hardly runs and battery life is outstanding.

Edited by tonyx86
Changed Nvidia graphics device-id to 0a29

Share this post


Link to post
Share on other sites

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, Bluetooth: BCM92046DG-CL1ROM -- Broadcom 2046 -- Targus). Any suggestions as to things I would have to change (Kexts/Settings/Etc) from your install guide of Mojave to make it work?

 

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

Share this post


Link to post
Share on other sites
23 minutes ago, MadHatter806 said:

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, Bluetooth: BCM92046DG-CL1ROM -- Broadcom 2046 -- Targus). Any suggestions as to things I would have to change (Kexts/Settings/Etc) from your install guide of Mojave to make it work?

 

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

 

Our systems look almost identical, except for Wi-Fi and CPU.  The CPU shouldn't make a difference.  I can't be certain that your BIOS settings are the same, so I'd strongly recommend that you extract your own ACPI files (CLOVER-F4) and patch according to @duduclx 's guide and then my changes (LPCB._DSM, ECDV rename) and inject device-id "0a29" for the Nvidia 3100m so that AppleGraphicsPowerManagement loads.  You might want to google solutions for your BCM4322 wi-fi.  It's possible that Lilu and AirportBrcmFixup 2.0.0 will work for you, too.  Use my CLOVER config.plist.  Keep me posted and definitely let me know if you get sleep to work. I'm getting ready to post an updated set of config files, so get started on yours and then we can compare notes.

Share this post


Link to post
Share on other sites

Ok. Will be grateful to attempt MacOS Mojave install on my E6410. (Also) To accommodate for testing/(fixing) sleep issues, I have a spare HDD to put in place of the SSD. [For sake of testing will also replace modular bay with optical drive -- thus dealing with only 1 storage drive and 1 optical drive]. My WiFi card was previously an almost vanilla card, so if it works great -- if not can replace to match yours (assuming it will work on Ubuntu when finished playing with Mojave install).

 

However for the remainder of this endeavor please treat me as a noob (my apologies). While I have been building computers since '97 and am extremely proficient within Windows, decently proficient within Linux, I am a beginner to "advanced" Hackintosh. I've used Apple OS nearly all my life, however most "Hackintosh" I've built have been nearly vanilla or using a simple fix method like the beast (which cannot apply here).

 

That said, what steps did you take differently from steps #1-#9 of the aforementioned El Capitan guide? (I've never done ACPI extraction before -- I assume this guide "Patching LAPTOP DSDT/SSDTs" is still a good resource?)

 

Any (& all) guidance you would be willing to lend would be appreciated! I look forward to getting the E6410 on Mojave (and with sleep/hibernate working as should be on a HDD -- sorry, still unsure of doing it on a SSD), and eventually end up with a very solid triple-boot system with all the latest OS' installed and flawlessly working.

Share this post


Link to post
Share on other sites

Also a bit of research into sleep/hibernate on a SSD led me to this: http://bit.ly/2WHOmjm

(I was using Win 7 -- prior to final release; with a first gen Kingston 30GB SSD. While this SSD has come back to life, I've never ventured into sleep/hibernate with a SSD again)

So once we can figure out the install (with a simplified installation guide for Mojave) on similar hardware E6410s and find/fix the sleep/hibernate issue, I will be more than happy to attempt replication of said on a fresh install to a SSD rather than a HDD.

 

And to be clear as crystal -- you are booting clover from UEFI not legacy right? (As current, my El Capitan is booting from Clover only in legacy; everything else is an EFI boot -- even within clover).

Share this post


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

...you are booting clover from UEFI not legacy right?

I'm booting CLOVER Legacy.  I have updated Post #1 to include CLOVER (Legacy) as part of my system configuration and I have added new EFI files with updated DSDT.aml (includes HDAU device).

 

Follow duduclx's original guide referenced in post #1 (great instructions!) and then apply my changes here to create your own EFI.

 

EDIT: @MadHatter806 If you're new, I'd suggest installing High Sierra first, since it still supports MacBookPro 6,2 without any Mojave patches.  After you get your system working with High Sierra, then we can talk about Mojave.

Edited by tonyx86

Share this post


Link to post
Share on other sites

This thread was not intended to be an installation guide.  I have a long way to go to match the outstanding instructions presented by duduclx in his original guide for install El Capitan on the E6410.  While most of my comments will remain most suitable for intermediate to advanced hackintoshers (not claiming any expertise of my own), I have added basic installation steps to post #1 of this thread.

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/11/2019 at 12:34 AM, hackintoshmalang said:

@tonyx86...hi how is about battery consumption ? and core frequency GPU ...my dell 6410 nvidia stuck at 405 mhz gpu frequency, cause my battery drain out prety fast...do you mind share your EFI ?, thanks

 

@hackintoshmalang I'm not ignoring your "stuck at 405 mhz" comment - it just hasn't been a priority for me.  My method of injecting the device-id for Nvidia gets AGPM loaded, but it's probably not the correct solution.  I re-read duduclx original El Capitan thread and saw some work on this.  See here for this analysis.  I haven't tried any of it yet.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT2: updated Clover.zip with new NVCAP is now attached to Post #1.

 

EDIT: It turns out that I only needed @PlutoDelic 's NVCAP.  It appears that I had the wrong NVCAP in my Nvidia config.  Once I changed my NVCAP to match the one specified by plutdelic, my second display started working.  I was using the NVCAP that was automatically injected by CLOVER R4961, so it looks like CLOVER was injecting the wrong NVCAP for the 3100m in the Latitude E6410.

 

Originally posted before EDIT above:

I needed a second display on my E6410 and found that external VGA wasn't working.  Take a look at @PlutoDelic 's post in the duduclx's original el capitan thread.  I copied his config.plist configuration exactly into my config.plist and my external VGA is now working.  I have more work/experimentation to do in order to see exactly what change(s) is/are required, but for now, just copying plutodelic's config works.

Edited by tonyx86

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: I found this guide for Yosemite that includes the _PTS shutdown patch in the patched DSDT.  Still no indication of how this patch was determined.

 

FYI - I'm starting to track down the sleep issue.  @duduclx's  _PTS patch (for shutdown) is incomplete for sleep in High Sierra and Mojave (not sure about previous MacOS versions).  If anyone know's how he arrived at his _PTS patch, I might be able to determine the necessary changes to get working sleep.  A clue for others who want to help find the sleep solution is that the following modification to his shutdown patch (removing the conditional if/else) enables sleep, but the laptop then wakes immediately with a black screen.  I'm fairly certain that the black screen is because we need to modify _WAK as well.  I've applied Rehabman's PRW 0x0D patch (I think I applied it correctly if someone wants to check the DSDT I attached to Post #1) which was supposed to address the immediate wake from sleep, so I'm not sure why it wakes immediately.

 

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

Share this post


Link to post
Share on other sites
Posted (edited)

I traced the _PTS shutdown fix back to the beginning of Hackintosh time here.  The patch was only ever intended to resolve shutdown (to be conditional on LEqual (Arg0, 0x05)), where Arg0 to _PTS is the sleep state.  SLPE (short for SLP_EN) appears to be a register for enabling a sleep state.  There is another register, SLP_TYPx, that defines the sleep state to assume after SLP_EN is enabled.  Somehow, SLP_TYPx must be set to 0x05 (shutdown) prior to calling _PTS.  I wonder if SLP_TYPx needs to be set to 0x03 for suspend?

 

The same _PTS shutdown patch is required for the Thinkpad T61 for those who are curious (although SLPE is at a different location on the Thinkpad T61 (NVS 140m): OperationRegion (PMRS, SystemIO, 0x1030, One) ).  Looks like sleep on the Latitude E6410 is going to be a challenge.

 

EDIT: For the interested reader, here's more about SLPE and shutdown / sleep.

Edited by tonyx86
Added link with more info...

Share this post


Link to post
Share on other sites

I noticed that AAPL,clock-id and device_type are absent from the IORegistry for EHC1 (EH01).  I don't see anything wrong with my DSDT rename/_DSM for EH01 (in DSDT.aml) and USB ports work correctly, but I'd like to eliminate any potential USB issues in order to resolve this sleep problem.  The only fix I found (thanks to @feartech) was to use CLOVER on-the-fly rename/fix for USB.  I have changed this on my system and tested it.  Unfortunately it does not resolve the sleep problem (no change in sleep behavior).  I haven't updated the attached files in Post #1 to reflect this change.

Share this post


Link to post
Share on other sites
Posted (edited)

Alps trackpad performance is lousy with the "standard" VoodooPS2Controller.kext (a known issue).  Switching to the "Refined ALPS Touchpad driver" is a big improvement.  I made the switch, but haven't updated the attached files in Post #1 to reflect this change.

 

EDIT: The "Refined VoodooPS2Controller.kext" switches keys on the keyboard.  Annoying.

 

EDIT2: Key remapping in "System Preferences > Keyboard > Modifier Keys" may do the trick.  Switch the Option and Command keys.  See attached screenshot and reply with your own suggestions.

Screen Shot 2019-06-15 at 5.17.31 PM.png

Edited by tonyx86
Having trouble attaching the screenshot

Share this post


Link to post
Share on other sites
Posted (edited)

EDIT: The DSDT changes mentioned in this post (below) do not influence my Latitude E6410's sleep behavior when the laptop is running on AC power.  These DSDT changes appear to change sleep behavior only when the laptop is running on battery power.

 

I have been able to modify my DSDT to get close to a working sleep solution for the Latitude E6410. I now believe that the solution will combine a change to _PTS and a change in _EJD (Ejected Device notification). Search for _PTS and _EJD in my attached DSDT.aml and you will see what I mean. With these changes in the attached DSDT.aml (attached to this post, not the first post), the USB device at EHC1.PRT1 generates the Ejected Device notification (not the device at EHC2.PRT3 which doesn't exist). The original DSDT has the _EJD notification in EHC2.PRT3 which doesn't have a device present and thus doesn't trigger an _EJD notification. With this change, the laptop shuts down on sleep. I feel that this is very close and I could use any help and advice. I suspect that SLPE should only be set to zero in _PTS for shutdown and that something else should be done for sleep. If I move Store (Zero, SLPE) back into the if condition (so that SLPE is only set to Zero on shutdown), the laptop does not shutdown (or sleep) when I attempt to put it to sleep, so something similar to Store (Zero, SLPE) is still required for sleep.

DSDT.zip

Edited by tonyx86
Added note about battery power vs. AC power

Share this post


Link to post
Share on other sites

I found that switching the Command and Option keys wasn't the only fix required to compensate for the Refined Alps Touchpad driver (VoodooPS2Controller.kext).  I needed to change the keyboard type to ISO European (instead of ANSI) to fix the [ ` ~ ] key to the left of the "1" (one).  With these two changes (switch modifier keys and change keyboard type to ISO European, it appears that the Latitude E6410 keyboard is back to normal after taking advantage of the improved ALPS Touchpad performance with the new VoodooPS2Controller.kext.

Share this post


Link to post
Share on other sites

Also been looking at this and wanted to share some observations/tool ideas
I found that you can follow along with sleep in the system logging if you first generate a system log like this:
log show --last 1h --debug > /tmp/boot2.log

then search for:

ScreenOn changed: on -> off

Regarding the _WAK function,  I did notice that it seems to be calling a series of EV methods.  I wonder if we switched what EV function it was calling into, if we could see more success.  
Further I noticed that if search for the Sleep() command elsewhere in my DSDT, it seems it can also be called with the parameter 

Sleep (0x01F4)

 

Haven't had any success yet but wanted to share my results before I lost track of them

 

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Dr. Monkey said:

Also been looking at this and wanted to share some observations/tool ideas
I found that you can follow along with sleep in the system logging if you first generate a system log like this:
log show --last 1h --debug > /tmp/boot2.log

then search for:

ScreenOn changed: on -> off

Regarding the _WAK function,  I did notice that it seems to be calling a series of EV methods.  I wonder if we switched what EV function it was calling into, if we could see more success.  
Further I noticed that if search for the Sleep() command elsewhere in my DSDT, it seems it can also be called with the parameter 

Sleep (0x01F4)

 

Haven't had any success yet but wanted to share my results before I lost track of them

 

It's great to have some else on the E6410/Mojave team!  From what I've gathered about Sleep(), the parameter is the sleep duration (which I imagine means that the higher the number, the longer the sleep.  The Sleep() command in DSDT.aml is not the laptop sleep, but is a time to wait before execution continues.  If someone knows differently, please chime in.

 

EDIT: Also, take a look a this. @itsworking has edited his DSDT to log events as they are executed in the DSDT.  Looks tedious, but may be an option.  Note that my display name is "deeveedee" in this other forum.  You'll see my question that I asked - not sure who's still following that other thread.

Edited by tonyx86

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 ragshion
      Hello guys,
       
      I want to install Mojave on my Laptop
      I Follow tutorial from http://olarila.com/forum/viewtopic.php?f=28&t=6257 and download Mojave Installer from https://olarila.com/forum/viewtopic.php?t=6743
       
      But during install, I got an error while macos is installing.
      Error Message is
      'macOS could not be installed on your computer'
      'an error occured installing macOS. to use apple diagnostics to check your mac hardware, shutdown, press the power button, and immediately hold the "D" key until diagnostics begins'
      'Quit the installer to restart your computer and try again'
       
      I try 3 times, and still get the same error.
       
      Thank you,.
       
      Specs :
      Asus A456URK Processor : Core i5-7200u RAM        : 12GB VGA        : Intel HD 620                            NVdia GT 930mx
       
       

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.5_18F132
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.5.zip
       
       
    • By r00tdvd
      I have E6540 working almost perfectly fine with Mojave 10.14.5 except for couple of things:-
       
      1- HDMI audio not syncing properly with TV ! I never had that issue.
      2- Webcam is not working and I need it for meetings and stuff.
       
      I have attached my fully working EFI.zip also the clover origin dump E6540_origin.zip files.
       
      I am also wondering is it possible now to get the E6540 to work with the AMD Radeon HD 8790M instead of the Intel(R) HD Graphics 4600 but also get the HDMI working the with TV?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×