Jump to content

tonyx86

Just Joined
  • Content Count

    233
  • Joined

  • Last visited

1 Follower

About tonyx86

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

2,645 profile views
  1. My observed lid-sleep times are as follows. These are the times (in seconds) that it takes for my Dell Latitude E6410 to sleep after closing the lid. Catalina 10.15.3: 32 seconds Mojave 10.14.6: 5 seconds High Sierra 10.13.6: 5 seconds
  2. You indicated that Wi-Fi is working as intended. Do you mean that the delay is fixed? If so, what did you change to fix this (from your previous post)? Also, I'll continue to recommend that you stay with the same baseline (including Lilu.kext), since it will help to minimize variables as we're chasing problems. If you do make a change from the baseline, it would be best to clearly note the change when you post requests for help (explaining why you made the change).
  3. Below is my progress on getting the Brightness Slider to work. I would welcome any help if you're interested - specifically, find the correct brightness key mapping. This solution is almost working. The only issue appears to be that the brightness slider expects the brightness keys to be Fn-F12 (brightness up) and something else for brightness down, so the slider is mapped to the wrong keys. I suspect that if we modify the DSDT to map the slider to the correct keys, the slider will be working. There are plenty of key mapping posts, so this should be the "easy" part. My work is as follows (and attached): DSDT is modified as mentioned a few posts ago for the lid sleep. Also added since my last post are "@0,backlight-control" and "AAPL,backlight-control" which are from the E6430 thread but I suspect are unnecessary. DSDT is modified with a new pwm-info (from a real MBP6,2). We won't know which pwm-info to use until the slider is working and we can determine whether the slider range fully adjusts the display brightness. DSDT is modified with the addition of a new thermal zone (Scope (_TZ) { ThermalZone (THM) }) borrowed from the E6430 DSDT here. This adds a new "Thermal Zone 1" to the HWMonitor temps (nothing to do with display brightness, just playing). AppleBacklightInjector.kext generated using @onejay09's technique here. To make onejay09's patch.sh script work for this patched Catalina 10.15.3 installation, I needed to modify onejay09's script, replacing "AppleDisplay" with "AppleBacklightDisplay". Steps to install this partial solution (still needs brightness keys mapped for slider to work): Replace your DSDT in EFI/Clover/ACPI/patched with the attached DSDT Remove FakeSMC_LPCSensors.kext (it doesn't appear to add any info in HWMonitor for the Latitude E6410) Keep FakeSMC_ACPISensors.kext (it is required to read the new Thermal Zone temp which is now available because of the DSDT mod borrowed from the E6430 DSDT - again, nothing to do with brightness) Generate and install your own AppleBacklightInjector.kext using the instructions below. Install Rehabman's ACPIPoller.kext for lid sleep (as per my previous post) Make sure kexts are properly installed and reboot AppleBacklightInjector.kext You should generate your own AppleBacklightInjector.kext by following onejay09's instructions here. Make sure you replace "AppleDisplay" with "AppleBacklightDisplay" in his patch.sh script. My AppleBacklightInjector.kext is attached as an example. After completing the steps above, press Fn-F12 and you will see that the slider "works" but is connected to the wrong keys. Note that when you close the lid, you'll need to wait 30 seconds for the laptop to sleep. Also note that the laptop wakes properly when the lid is opened. Looks like this lid sleep/wake solution works perfectly. EDIT: Here a good read about brightness keys: https://www.insanelymac.com/forum/topic/305030-guide-how-to-fix-brightness-hotkeys-in-dsdt/ ACPIPoller.kext.zip DSDT.zip AppleBacklightInjector.kext.zip
  4. I took a quick look and can look again tomorrow. My first observations are: Lilu.kext 1.4.2? Where did you get version 1.4.2? Where is AirportBrcmFixup.kext? Maybe I missed it? EDIT: Remove the IntelBacklight.kext that you installed. This is not the correct backlight kext for Nvidia. The correct backlight kext (if we find one that works) will be based on this thread.
  5. @unilock and others that might be interested, I was working on something else related to the display and quickly implemented what I believe are the necessary elements for sleep on lid close (as implemented by Rehabman). I did try it and it "works" (only tried once), so I'm not sure I did this correctly (didn't spend much time on it). If you're interested, take my work below/attached and test it yourself. I don't know if this breaks something else (again, didn't test extensively). Please report your findings in this thread if you do test this. The basic elements (attached) are as follows: Add Method (PNLF) to DSDT (not sure this was necessary - I was playing with something else) Add pwm-info to GFX0._DSM to DSDT (not sure this was necessary - I was playing with something else) Add Device (LIDP) to DSDT (required for Rehabman's ACPIPoller.kext) Install ACPIPoller.kext (I installed in /L/E) EDIT: Remove the following kext (appears to be unnecessary) FakeSMC_LPCSensors.kext To try this, you just need to replace your DSDT in /EFI/Clover/ACPI/patched with the attached DSDT and properly install the ACPIPoller.kext (I installed in /L/E) and reboot. You'll noticed that the Display Brightness Slider appears in System Preferences > Display. The slider doesn't work (this would be another project if you're interested). References: Rehabman's ACPIPoller.kext: https://github.com/RehabMan/OS-X-ACPI-Poller Rehabman's Device (LIDP): https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/misc/misc_LidPoll.txt Implementation of Lid Polling on Dell Latitude E6430: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/ If I remember correctly, you may find a Brightness Slider solution in the E6430 thread. I would recommend reading this thread, since it's what I used to derive the sleep solution for the Latitude E6410. FrostyTheSnowMan did a great job with the E6430. DSDT.zip ACPIPoller.kext.zip
  6. Thank you, @headkaze. I agree that a USB configuration issue is a logical place to look. In an attempt to resolve this Bluetooth issue, I have been playing with Clover USB fixes and have also been looking at my DSDT patches in my Latitude E6410 thread. My original post in this BrcmRamPatch2 thread (which included my Clover config.plist at the time) included Clover's USB Ownership fix. Since then, I have revised some of my DSDT patches and have disabled all Clover USB fixes (including disabling the Clover USB Ownership fix). This Bluetooth issue remains in Catalina 10.15.3 with and without Clover's USB Ownership Fix and Bluetooth continues to work fine with and without the Clover USB Ownership fix in High Sierra 10.13.6 and Mojave 10.14.6 (I'm still using BrcmFirmwareRepo.kext 2.2.10 and BrcmRamPatch2.kext 2.2.10 in /L/E for High Sierra and Mojave). Attached are my most recent boot log for BrcmPatch, my current Clover config.plist and my problem reporting files collected with BlackDragon74's gen_debug script. Note that for the attached files, I enabled Clover's USB FixOwnership. Thank you very much for continuing to think about this. Please let me know if you have any other questions or suggestions. brcm_boot.log config.plist debug_2195.zip
  7. Attached is the GeekBench5 score for my HackBookPro6,2 (i7-620m). The GeekBench4 score is attached to Post #1 in this thread. Performance of this Latitude E6410 with Catalina is virtually identical to performance with Mojave.
  8. tonyx86

    Mojave on Dell Latitude E6410 With Working Sleep

    EDIT: This new DSDT is now included in the E6410-Mojave.zip attachment in Post #1 of this thread. Kexts have not been updates, so if you update your Mojave installation with the new EFI attached to Post #1, you will still need to follow all of the Catalina upgrade instructions (including new kexts) if you upgrade to Catalina in this thread. A new DSDT for the Latitude E6410 is attached. Replace your DSDT in EFI/CLOVER/ACPI/patched with the DSDT attached to this post. Details below. I found an incorrectly applied patch in my Latitude E6410 DSDT. This DSDT has been incorrect since I first applied patches for Mojave and explains why I originally thought I needed to enable USBFix in CLOVER config.plist (which I ended up not having to do). I had incorrectly applied the _DSM patch for Device (EHC1). This _DSM patch was nested inside of Device EHC1.RHUB1 instead of up one level in Device EHC1. This error doesn't appear to have affected USB behavior, but I haven't finished testing. Please replace your Latitude E6410 DSDT (in EFI/CLOVER/ACPI/patched) with this new one. I will eventually update the EFI attached to Post #1 in this thread and to the Catalina Thread. DSDT.zip
  9. EDIT: This updated DSDT is now included in the new E6410-Catalina-3v3.zip attached to Post #1 in this thread. A new config.plist is also included in the E6410-Catalina-3v3.zip attached to Post #1. This new config.plist removes the CLOVER USB fixes which are no longer necessary. A new DSDT for the Latitude E6410 is attached. Replace your DSDT in EFI/CLOVER/ACPI/patched with the DSDT attached to this post. Details below. I found an incorrectly applied patch in my Latitude E6410 DSDT. This DSDT has been incorrect since I first applied patches for Mojave in this thread and explains why I originally thought I needed to enable USBFix in CLOVER config.plist (which I ended up not having to do). I had incorrectly applied the _DSM patch for Device (EHC1). This _DSM patch was nested inside of Device EHC1.RHUB1 instead of up one level in Device EHC1. This error doesn't appear to have affected USB behavior, but I haven't finished testing. Please replace your Latitude E6410 DSDT (in EFI/CLOVER/ACPI/patched) with this new one. I was hoping that this error explained the Bluetooth behavior in Catalina, but I haven't found that any behavior changes after applying this fix. I will eventually update the EFI attached to Post #1 in this thread and to the Mojave Thread. DSDT.zip
  10. @feli_solis thank you very much for your suggestion! I have already renamed the ECDV device to EC in my DSDT and AppleACPIEC is loading with IONameMatch PNP0C09. Thank you for checking!
  11. The new baseline that I attached a couple of posts ago is working extremely well for me. I have added the following as a known issue in Post #1: 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 (my tested baseline will always be attached to Post #1), 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.
  12. tonyx86

    Mojave on Dell Latitude E6410 With Working Sleep

    Too close to call. If there is a difference, I think Catalina performs better.
  13. tonyx86

    Mojave on Dell Latitude E6410 With Working Sleep

    @vbmota Here's my Latitude E6410's GeekBench5.1 score when running Mojave 10.14.6. My Latitude E6410 has an i7-620m.
  14. EDIT: I should mention that I still prefer the original HWMonitor and will be staying with the original HWMonitor in my baseline. I am posting this only for those who might be curious about HWMonitor alternatives. I've been interested in possible replacements for HWMonitor, specifically in the packages posted at https://sourceforge.net/projects/hwsensors3.hwsensors.p/files/ If you want to try this alternate HWMonitor, follow the steps below. The required files and a screenshot of the sensor display are attached. This installation of a new HWMonitor assumes that you have installed the E6410 Catalina baseline as per Post #1 in this thread. Remove the following kexts from /Library/Extensions ACPIBatteryManager.kext FakeSMC_ACPISensors.kext FakeSMC_CPUSensors.kext FakeSMC_GPUSensors.kext FakeSMC_LPCSensors.kext FakeSMC.kext Remove FakeSMC.kext from EFI/Clover/kexts/Other Copy all kexts in the attached LE folder to /Library/Extensions Note that AppleHWSensor.kext from Mojave 10.14.6 is included. I'm still experimenting with this, so you may or may not want to install this. Copy FakeSMC.kext from the attached LE folder to /EFI/Clover/kexts/Other Remove HWMonitor from Applications Copy HWMonitorSMC from the attached Applications folder to Applications Ensure PROPER kext installation 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. Restart your HackBookPro Run HWMonitorSMC NewHWMonitor.zip
×