Jump to content
Cyberdevs

nVidia GPUs and the infamous lag issue, Why is that happening?

134 posts in this topic

Recommended Posts

Let's cross reference the facts and settings and find out why we have the lags with the nVidia web drivers and why some other people don't have the lags.

I have an EVGA 1070 SuperClocked GPU which is working pretty well under macOS Sierra and up to macOS 10.13.2 the last macOS update and the nVidia web driver didn't go so well.

 

So far I tried all the following options but nothing seems to work:

 

1. Used only clover's on the fly patch for the board-id to avoid the black screen issue

2. Used Lilu and nVidiaGraphicsFixUp

3. Used only AGDPFix without any other patches or kexts

4. Activated the iGPU

5. used ACPI patches to change the PEG0 to GFX0

6. Used iMacPro SMBIOS without any patches or kext

 

Nothing seems to work so far except for the patched version of the 104 or 106 web driver which has the lags but it's way better than the last drivers.

 

To all people with no lags:

 

Please share your EFI folders if you can.

 

(Please remove the serial number, MLB, UUID and all the private stuff from your config.plist and also remove "themes" and "Apple" Folder before posting it)

 

and please share your hardware specs with the firmware version (BIOS/UEFI version) 

 

Thank you all

 

You can test the following sites to see wether you have the lags or not:

 

http://madebyevan.com/webgl-water/ (thanks to @maerten)

 

or

 

http://www.bongiovi..../webgl/blossom/ (thanks to @TheBloke)

Share this post


Link to post
Share on other sites
Advertisement

I have the lags there as well:

http://madebyevan.com/webgl-water/

 

the original post can be found at: http://www.insanelymac.com/forum/topic/332311-partial-success-but-with-random-graphics-lags-video-included-coffeelake-1080-ti/?p=2583883


I have no lags in my normal usage I see a lag with site posted by @maerten (OpenGL waterpool)

Have you ever performed a ROM update on your GPU? or you are just using it with the stock ROM?

Share this post


Link to post
Share on other sites

Look @my signature :)

I have no an Extreme 1080ti..but a "flashed one" :) :)

 

I have the lags there as well:

http://madebyevan.com/webgl-water/

 

the original post can be found at: http://www.insanelymac.com/forum/topic/332311-partial-success-but-with-random-graphics-lags-video-included-coffeelake-1080-ti/?p=2583883


Have you ever performed a ROM update on your GPU? or you are just using it with the stock ROM?

Share this post


Link to post
Share on other sites

I have a gtx 960 and also experience the lags with the .157 Nvidia driver on 10.13.3 and .4 beta's.

 

I have also tried the following.

 

1. Used only clover's on the fly patch for the board-id to avoid the black screen issue

2. Used Lilu and nVidiaGraphicsFixUp

3. Used only AGDPFix without any other patches or kexts

4. Used iMacPro SMBIOS without any patches or kext (still using with older driver with no lags)

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

maybe we need to grab some firmware from macvidcards? or thats just efi patched?

Share this post


Link to post
Share on other sites

why?

 

maybe we need to grab some firmware from macvidcards? or thats just efi patched?


i mean in a hack a patched gfx for a real mac do not have a pratical use I think 

or not?

Share this post


Link to post
Share on other sites

why?

 

i mean in a hack a patched gfx for a real mac do not have a pratical use I think 

or not?

i don't know what to say)) that was just an idea) I didn't say smart idea)) i just know that it's something between osx and nvidia drivers

Share this post


Link to post
Share on other sites

maybe we need to grab some firmware from macvidcards? or thats just efi patched?

I don't think that's possible, they don't post their ROMs online the offer a service to flash your GPU with the Mac compatible ROM.

 

Besides I don't think it would be much use if you use a flashed GPU for Mac in a PC.

Share this post


Link to post
Share on other sites

Per the other thread, you might want to try taking this discussion to the official NVIDIA forums:

 

https://forums.geforce.com/default/board/132/geforce-apple-gpus

 

as NVIDIA is known to respond to discussions there.  If nothing else, it'll be very clear to them that this is an issue that is affecting a lot of people.

You are right and perhaps we should contact nVidia about the issue.

 

But the thing is I'm just curious to know why this issue is present on some hacks while others have no issue and that's beside the fact that nVidia isn't doing well in producing the proper web drivers for their GPUs.

 

Not only hacks are affected, from what I see even Macs with a nVidia GPU are affected as well.

Share this post


Link to post
Share on other sites

Hi all :)

today I have had some sparetime.. I have patched and tested all drivers produced from High Sierra from 10.13.0 to 10.13.3 in my spare beta 10.13.4 beta 2 update 1 disk

 

I have had alway success to install patched driver (with old 10.13.0 and 10.13.1 I have old reboot iogconsoleuser boot loop message solved forcing also NVDA_drv=1 in boot option (with also nvidiaweb enabled)

 

But I can't with some drivers test WEBGL link posted by cyberdevs &maerten (black screen instead waterpool inside html page..

 

then I tested also (try to test) 10.12.6 webdriver

In this case I am not able to patch and install because they need some work for install and post install script I think

 

Any of you could try to modify web driver fo old Sierra 10.12.6 (it needs to modify where drivers are installed like L/E instead S/L/E)

I would like to try if this can solve the only lag I have in that OpenGL page :)

 

For me all drivers for 10.13.x are working in the same way for performance

 

 

post-468967-0-93612500-1518800384_thumb.png

Share this post


Link to post
Share on other sites

You are right and perhaps we should contact nVidia about the issue.

 

But the thing is I'm just curious to know why this issue is present on some hacks while others have no issue and that's beside the fact that nVidia isn't doing well in producing the proper web drivers for their GPUs.

 

Not only hacks are affected, from what I see even Macs with a nVidia GPU are affected as well.

 

There are many explanations, here are two examples:

 

1) NVIDIA is incompetent and the macOS driver team is 2 guys working in a basement with no support.

 

2) NVIDIA hasn't been able to reproduce these issues in their testing.

 

You said it yourself, some Hackintoshes aren't affected, so perhaps NVIDIA only has systems in that category?  What's your definition of "proper web drivers" exactly?  Do we really have to assume that there is incompetence or malice on their part?

 

I don't know what the issue is, because my system has been running perfectly fine in the applications I use on a regular basis.  Clearly, there are many people who are having issues, so there's definitely something going wrong.  Posting in a venue where NVIDIA can work with you seems like a really good idea, in any case.

Share this post


Link to post
Share on other sites

There are many explanations, here are two examples:

 

1) NVIDIA is incompetent and the macOS driver team is 2 guys working in a basement with no support.

 

2) NVIDIA hasn't been able to reproduce these issues in their testing.

 

You said it yourself, some Hackintoshes aren't affected, so perhaps NVIDIA only has systems in that category?  What's your definition of "proper web drivers" exactly?  Do we really have to assume that there is incompetence or malice on their part?

 

I don't know what the issue is, because my system has been running perfectly fine in the applications I use on a regular basis.  Clearly, there are many people who are having issues, so there's definitely something going wrong.  Posting in a venue where NVIDIA can work with you seems like a really good idea, in any case.

Well my guess is that nVidia doesn't have the proper documentation on Metal support (may be that's Apple's fault) and the web drivers aren't fully optimized for using metal architecture that's why we have the lags in the macOS's UI and other apple developed software. (this is just my personal assumption not a fact or anything)

 

With each major update apple tends to improve the stability and performance of the macOS by changing/fine tuning so many things and that's where nVidia can't keep up with those changes.

Share this post


Link to post
Share on other sites

so far the best (and the only) answer that I have received from posting the issue at nvidia forum is a to "get a pc" to solve the issue with the web drivers.

 

Why didn't I think of that! I wonder!

Share this post


Link to post
Share on other sites

Well my guess is that nVidia doesn't have the proper documentation on Metal support (may be that's Apple's fault) and the web drivers aren't fully optimized for using metal architecture that's why we have the lags in the macOS's UI and other apple developed software. (this is just my personal assumption not a fact or anything)

 

With each major update apple tends to improve the stability and performance of the macOS by changing/fine tuning so many things and that's where nVidia can't keep up with those changes.

 

May also have to do with 10.13.4's improved eGPU support and Nvidia's attempt to improve things on their end in preparation. But the fact that real macs are also having issues with this driver suggests to me that this driver is just flawed and this is a "bad release," but Nvidia doesn't really see a point in fixing it until 10.13.4 actually drops . . .

Share this post


Link to post
Share on other sites

May also have to do with 10.13.4's improved eGPU support and Nvidia's attempt to improve things on their end in preparation. But the fact that real macs are also having issues with this driver suggests to me that this driver is just flawed and this is a "bad release," but Nvidia doesn't really see a point in fixing it until 10.13.4 actually drops . . .

Well it doesn't make sense, releasing a {censored} product and just dropping all further support because of some future update or the next the release, how long is it gonna take?  :blink:

 

When the 10.13.4 is gonna be released? Next month, two months? :rofl:

Share this post


Link to post
Share on other sites

Well it doesn't make sense, releasing a {censored} product and just dropping all further support because of some future update or the next the release, who long is it gonna take?  :blink:

 

When the 10.13.4 is gonna be released? Next month, two months? :rofl:

 

Considering how small the user base is and how easily Apple can break things, it probably does make sense to just wait. ;p

 

AFAIK, 10.13.4 is in second beta. And there's some pressure to release sooner rather than later since it fixes the Indian text bug on the Mac side.

 

https://www.macrumors.com/2018/02/15/telugu-crashing-bug-fixed-ios-11-3-macos-10-13-4/

Share this post


Link to post
Share on other sites

Considering how small the user base is and how easily Apple can break things, it probably does make sense to just wait. ;p

 

AFAIK, 10.13.4 is in second beta. And there's some pressure to release sooner rather than later since it fixes the Indian text bug on the Mac side.

 

https://www.macrumors.com/2018/02/15/telugu-crashing-bug-fixed-ios-11-3-macos-10-13-4/

Well according to this article Apple is going to release the 10.13.4 in about 40 days or so. But yet that's a long time to deal with a laggy system and if that's the case I might jus swap my GPUs on my rigs, the lag is really annoying and I'm not able to perform my day to day tasks properly.

Share this post


Link to post
Share on other sites

Hi all
 
I am on 10.13.3 with a 980Ti, and I was noticing disappointing performance - for example, skipped frames in a 1080P YouTube video, and stuttering scrolling when I scrolled fast through a Chrome page.
 
Today I was told about this script on Github:  https://github.com/Benjamin-Dobell/nvidia-update
 
From the description:

 

This script installs the best (not necessarily the latest) official nVidia web drivers for your system.

 

Specifically, it does the following:

- Checks for official driver updates for your version of macOS.

- Cross-references against a list of blacklisted drivers, that it'll avoid installing (by default).

- Properly uninstalls old drivers.

- Downloads and installs the latest non-blacklisted drivers.

- On-the-fly patches driver packages so they can be installed on your version of macOS (if necessary).

- Patches drivers that you've already installed, if they no longer match your macOS version i.e. post macOS update. 

 
 
I ran the script and it downgraded my drivers from 378.10.10.10.25.156 to .106 (same as cyberdevs has just tried.)

 

Since then, I think things are improved.  I watched a few videos and couldn't see any skipped frames.  I've scrolled very fast through some Chrome pages and it seems smooth.
 
It's too early to say 100% it's fixed, but it definitely seems improved.  I also got 1% higher Compute benchmarks in GeekBench4 (both OpenCL and Metal), although this is close enough to be within margin of error.
 
Anyway, I would recommend trying this script if you have problems.  You can always revert back to latest NVidia drivers using the NVidia Preference Pane if it doesn't work out.


Today I also tested the 106 and it seems to be performing ok on my rig but I still have some minor lags.

Specially in the following site:
http://madebyevan.com/webgl-water
 

 

Thanks, I just tried that site also on 106, and on Chrome it was mostly fine.  Occasionally I could tell it had skipped/lagged.  It was almost like there was a 'flash', like it had gone black for a fraction of a second.

 

Then I tried it in Firefox and it was slightly worse - the 'flash' happened a little more often.

 

But at least in Chrome I may not have noticed it if I hadn't been looking for it, and I'm sure it's much better than it would have been on 156 given that even a 1080P YouTube video would regularly stutter in that mess of a driver.

Share this post


Link to post
Share on other sites

Hi all

Hi there,

 

Thanks for the update :)

 

We all (I mean the ones with the lag issue) have to use web drivers that were released prior to the 156 or 157.

 

I have tested the 104 and 106 and both work almost ok, but the lags are still there from time to time.

 

The thing is that I really would like to know why on some systems the web drivers work flawlessly and why on others we have the lags.

 

--

 

To all people with no lags:

 

Please share your EFI folders if you can.

(remove the serial number, MLB, UUID and all the private stuff from your config.plist and also remove "themes" and "Apple" Folder before posting it)

and please share your hardware specs with the firmware version (BIOS/UEFI version) 

 

Thank you all

Share this post


Link to post
Share on other sites

This WebGL demo has quite noticeable lag/stuttering in both Chrome and Firefox, even with 106 drivers:  http://www.bongiovi.tw/experiments/webgl/blossom/

 

Again, it is worse in Firefox, where I can quite often see the flying leaves slow down for 0.25-0.5 seconds.

 

However, in Safari it is perfect.  No lag, stuttering or slowdown.  Even when I increase numParticles, speed and range to maximum and rotate the animation as it plays.  And even in Full Screen.

 

So tests using web browsers could be impacted by which browser - and Apple Safari is working better (not surprising since they have full access to the APIs and OS!)

 

I think it might be helpful if we had an objective test to run, so then for people who report "no lag" can also run it and we can compare how it runs for them?  Otherwise it can sometimes be the case that some people really notice lag, others do not.   But if we had objective confirmation, it might make comparing specs/EFI/etc more helpful.

 

Does anyone know of a good, free non-browser application to test GPU rendering and performance?    Games could work, especially with an FPS counter, but unless they are free not everyone could run and test them.   There's GeekBench but this just gives an overall number - really it needs to be an app that renders something in 3D, which can be watched for lag and also check an FPS counter.

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 TomZanna
      Hi, I'm trying to install Mac Os Catalina on a HP 550-132NL.
      The system has:
      i7-6700
      RAM 12 GB
      GT 730
      LAN Realtek RTL8161
      ALC3863
       
      It passes the verbose phase but after the Apple logo goes away, it gets stuck on a grey screen and I can only move the pointer.
      Can I try to boot with the iGPU?
       
      origin.zip
      CLOVER_dGPU_USB_3.zip
    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.3 (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v14 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Your EFI Clover/kexts/Other folder needs only FakeSMC.kext, IntelMausiEthernet.kext, USBInjectAll.kext and VoodooPS2.kext.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder.  NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here: Update Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /Library/Extensions) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. NOTE: These instructions assume installation of Brcm kexts in /Library/Extensions.  Read the Brcm install instructions if you're installing kexts in EFI/Clover/kexts/Other, since your installation and at least one kext WILL BE DIFFERENT. Update IntelMausiEthernet.kext Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.3 CLOVER v2.5k r5103 DosDude Catalina Patcher: v1.3.0 Lilu.kext 1.4.1 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareRepo.kext 2.5.1 BrcmBluetoothInjector.kext 2.5.1 BrcmPatchRAM3.kext 2.5.1 IntelMausiEthernet.kext 2.5.0
      VoodooHDA.kext 2.9.2 v14 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (No solution yet) Brightness slider does not work in System Preferences > Displays (can control brightness with Dell brightness keys).  Working on a solution later in this thread. I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Work-around - no permanent solution yet) Cannot turn on Bluetooth after shutting-down with Bluetooth off.  Work-around is to leave Bluetooth on.  I don't use Bluetooth and don't mind, so this will likely be solved by someone else.  If you experience this issue and can't turn-on Bluetooth, I have found that putting the laptop to sleep (Fn-F1) and then waking the laptop restores proper operation of Bluetooth.  I have posted a problem description, logs and problem reporting files in this thread for help with this problem. (Solved later in this thread, but not yet added to this first post) Laptop does not sleep when closing lid.  Solution is to implement Rehabman's lid polling mechanism.  This is implemented later in this thread and the laptop sleeps when the lid closes and wakes when the lid is opened. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (legacy) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       

      AppleHWSensor.kext.zip

      gen_debug
      E6410-Catalina-3v3.zip
    • By tonyx86
      *** I have started another thread for installing Catalina on the Dell Latitude E6410.  If you were thinking of installing Mojave, but would prefer to skip right to Catalina, click here. ***
       
      I was inspired by @duduclx post here for installing El Capitan on a Dell Latitude E6410, so I decided to install Mojave 10.14.5 and subsequently 10.14.6.  Everything works perfectly (including sleep).  I'm starting this thread hoping to help others install Mojave on their E6410s.  A brief installation guide is provided later in this first post.  The interested reader is encouraged to read the other posts in this thread to see how this solution evolved and to learn additional tips/details not provided in this first post (including dual-booting with macOS and Windows).
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) MacOS: Mojave 10.14.6 (APFS) (Patched with DosDude Mojave Patcher 1.3.3) MacModel: MacBookPro 6,2 (LPCB._DSM.Name "pci8086,3b09") Kexts: Lilu 1.3.6, VoodooHDA 2.9.2, AirportBrcmFixup 2.0.0, IntelMausiEthernet 2.4.1d1, ACPIBatteryManager 1.90.1, BrcmPatchRam2.kext, BrcmFirmwareRepo.kext, VoodooPS2Controller (the "Refined ALPS Touchpad" version - release 6 developed by @Dr. Hurt and compiled by @bronxteck), not the original version), USBInjectAll (with custom SSDT-UIAC), VoodooSDHC.kext (configured as shown here). Wi-Fi: Broadcom BCM 94352HMB (with AirportBrcmFixup.kext) CLOVER (Legacy): R4961  
      Configuration items that may be different from what you have seen in other E6410 configurations
      Addition of _OFF and _ON methods to _PTS and _WAK methods respectively (to control discrete graphics in order to enable sleep/wake) LPCB._DSM patched with device-id "3b09" AND "name", "pci8086,3b09" for native Nehalem power management with MacBookPro 6,2 ECDV renamed to EC so that AppleBusPowerController loads AGP.VID._DSM patched with device-id "0a29" so that AppleGraphicsPowerManagement loads No CLOVER Generate P or Generate C States (with the correct LPCB._DSM and MacBookPro 6,2, these CLOVER options are unnecessary for this architecture and only limit max multiplier and reduce number of P states) DSDT patched to include HDAU device (device-id 0x0be3)  
      What is NOT working:
      Display brightness can be controlled with keyboard keys, but cannot be controlled with slider in Display settings. Graphics Power Management - AGPM loads (because 10de,0a29 device is injected), but there's no evidence that 3100m frequency and voltage is changing.
        What is NOT tested:
      Smartcard Reader eSata (I have this disabled in my BIOS) Firewire Port (it does appear in the Network settings, just haven't tried it) Microphone Jack PC Card Slot (I have this disabled in my BIOS)  
      What IS working:
      SLEEP IS WORKING! Everything else not mentioned above.   Speedstep/CPUPowerManagement is perfect, system temps are low, CPU multiplier operates as expected, battery life is long Shutdown is fast Display/graphics acceleration is perfect (thanks to DosDude's Mojave patcher) Brightness (adjusted with brightness keys on keyboard) works perfectly Battery Manager works (battery status is displayed in menu bar) simply by installing ACPIBatterManager.kext. Wi-Fi (after changing to Broadcom BCM94352HMB and installing AirportBrcmFixup.kext) Audio (volume adjustable, volume indicator appears in menu bar).  Switched to VoodooHDA from AppleALC after AppleALC caused slow boot due to "IOHDACodecFunction timeout." Ethernet port (with IntelMausiEthernet.kext) Broadcom BCM20702A0 Bluetooth (with BrcmPatchRam2.kext and BrcmFirmwareRepo.kext) Optical Drive External VGA (with corrected NVCAP.  Need NVCAP 04000000 00000100 0E000000 00000007 00000000 (credit: here) for working external VGA display. Headphone jack Display Port (tested using DP > HDMI adapter) Camera SD Card Reader  
      Known issues and their solutions (These issues have all been resolved, with the solutions incorporated into the attached config files.  The issues are listed here for historical purposes and no further work is needed unless stated otherwise).
      Leaving this for historical purposes, but the CLOVER USBFix is no longer necessary after finding that I had incorrectly applied the DSDT _DSM patch for Device (EHC1).  The CLOVER USBFix is not needed after fixing the DSDT..  AAPL,clock-id and device_type do not appear in IORegistry for EHC1.  Solution is to use CLOVER on-the-fly patching/fixing/renaming for EHC1 and EHC2.  Thank you, @feartech, for this tip. ALPS trackpad performance is not good with the "standard" VoodooPS2Controller.kext that I initially used.  Switching to the "Refined ALPS TouchPad driver" is a big improvement.  I've implemented and tested this on my system.  The ALPS version of VoodooPS2Controller.kext mixes up a few keys.  Need to switch the Command and Option keys (System Preferences > Keyboard > Modifier Keys) and change keyboard type to ISO European. This configuration (captured in the attached config files) uses an injected device-id (10de,0a29) for NVidia 3100m to get AGPM to load.  While I haven't observed any performance differences, a better approach may be to inject AGPM properties for device 10de,0a6c (the actual device-id for the 3100m).  This AGPM method is discussed later in this thread.  I have briefly tested this "FakeSMC.kext method" for injecting AGPM attributes without any noticeable changes in laptop/graphics behavior. IOHWControl is not loaded under AGPM (Should be AGP > VID > NVDA,Display-A@0 > NVDATesla > AGPM > gpu-control > IOHWControl as viewed in IORegistryExplorer).  It is loaded on a real MacBookPro6,2 running Mojave and is loaded on this Dell Latitude E6410 running High Sierra.  If I "Inject NVidia" via CLOVER, IOHWControl loads properly. The Dell Latitude DSDT (BIOS A17) has a bug in Method (GNOT).  In the method, the expression  If (LOr (LGreater (OSYS, 0x07D0), LLess (OSYS, 0x07D6))) always evaluates to TRUE, so the patched DSDT has no dependency on the value of OSYS.  I suspect that LOr should be replaced with LAnd, so that this expression is TRUE for variants of Windows 2001 and False for any other OS.  While this may have no affect on MacOS, it makes one wonder how such an obvious bug made it through Dell QA and is still present in BIOS A17.  Also makes one wonder whether the sleep problem (which no one has solved) was fixed in Windows to address another DSDT bug. The assigned value of ACOS and OSYS in the DSDT are conditional on the operating system.  There is no condition for "Darwin."  The solution is to add a condition for "Darwin" (making it equivalent to one of the defined operating systems (e.g. Linux, Win7, etc).  The attached config hard-codes ACOS and OSYS values equivalent to those for Linux.  Another way to handle this (different from the method employed in the attached config files) might be to override _OSI with XOSI (defined in a custom SSDT). The portType of the Internal Bluetooth device is portType=0 which, according to Rehabman's comments in SSDT-UIAC-All.dsl, is an external USB 2 port.  This should be an internal USB port (portType=2).  I learned through trial and error that the HUB1 and HUB2 definitions in Rehabman's SSDT-UIAC-ALL.dsl apply to the ports on the EHCx USB hubs.  The solution is to include the HUB1 definition in SSDT-UIAC.dsl and change portType to 2 for HP15.  This change doesn't appear to affect/fix sleep, but it may prevent instant wake if we get sleep working. There are minor differences between a real MacBookPro6,2 IORegistry dump and this HackBookPro6,2 IORegistry dump that can be resolved with simple DSDT edits.  I am now running with these changes, but haven't found these changes to make any difference in operational behavior.
      Rename Device (AC) -> Device (ADP1) Remove UID from Device (HPET) Add compatible ID "PNP0C01" to Device (HPET) Change ADP1:_STA from 0x0F to 0xFFFFFFFF Enable Ambient Light Sensor and renamed to Device (ALS0) from Device (ALS) Add compatible ID "smc-als" to ALS0 Rename LID -> LID0 Change "name" definitions to Buffers in _DSM methods Rename Device (PBTN) to PWRB Rename Device (SBTN) to (SLPB) Change HDAU.hda-gfx from "onboard-1" to "onboard-2" Change GFX0.hda-gfx from "onboard-1" to "onboard-2" Sleep / Wake does not work with the basic DSDT edits.  I have discovered that Sleep / Wake can be made to work by adding discrete graphics _OFF and _ON methods to _PTS and _WAK methods respectively (borrowed the concept and code from a working E6430 DSDT: Credit here: https://osxlatitude.com/forums/topic/9248-working-sleep-on-intel-hd-and-nvidia-nvs-on-dell-latitude-e6430-optimus-enabled-or-disabled/page/6/. The Clover boot arg should be changed to "darkwake=0" for reasons explained by @holyfield in this thread.  Leaving this for historical purposes: LCD screen is blank when waking laptop by opening lid (screen is not blank when waking with power button).  Solution is to add darkwake=8 to CLOVER boot args.  Thank you @Hervé for this tip.  
      Brief Installation Guide:
      Configure BIOS (version A17) as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC: Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace: Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;  Create your MacOS installer USB (Use DosDude's Mojave Patcher for Mojave) (start with High Sierra and not Mojave if you're new to hackintosh). Install CLOVER (Legacy) on installer USB using attached EFI as your guide for patched ACPI, kexts and config.plist Install MacOS to your SSD.  When you run DosDude's Mojave Patcher, DO NOT install LegacyUSBInjector.kext - you're going to use Rehabman's USBInjectAll.kext.  Also, do not install the DosDude SIP kext (you're using CLOVER to manage SIP). Install the following kexts in /Library/Extensions:  ACPIBatteryManager.kext, AirportBrcmFixup.kext, BrcmFirmwareRepo.kext, BrcmPatchRAM2.kext, FakeSMC.kext, FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_GPUSensors.kext, FakeSMC_LPCSensors.kext, IntelMausiEthernet.kext, Lilu.kext, USBInjectAll.kext, VoodooPS2Controller.kext (the "Refined ALPS Touchpad driver," not the original), VoodooSDHC.kext (configured as shown here). Switch Command and Option keys to compensate for Refined ALPS driver issue (System Preferences > Keyboard > Modifier Keys).  Also change keyboard type to ISO European to fix the [ ` ~ ] key (to the left of the "1" (one) key. Install VoodooHDA Install HWMonitor application  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z After applying Mojave updates, HWMonitor may not display discrete graphics attributes.  On systems with multiple displays, a second (or third display) may not be active after applying the Mojave update.  The solution to this is to run "sudo kextcache -i /" (in a terminal window) and reboot.  This will usually fix the issue.  If the issue is not fixed, run DosDude's Post Install Utility, apply the Legacy Graphics Patch, reboot and then run "sudo kextcache -i /" if necessary.  
      Credits
      In addition to those mentioned in this first post and in subsequent posts in this thread, much of this solution for the Latitude E6410 was made possible by the numerous contributions of @RehabMan.  I hope he's doing well, wherever he is.  Hopefully he has long since forgotten what a PIA I was (and still am) as I was (and still am) learning hackOS.  
       
       


      E6410-Mojave-6v2.zip
    • By NoEnd
      Hi team,
       
      I'm looking for the best route to achieve this upgrade, so I have been stuck with HS since Nvidia drivers stopped being supported on newer MacOS releases. Now I'm having an AMD 5700 xt on the way and want to plan the upgrade properly. I have added some information below and questions that might help with your recommendation.
       
      Current GPU 1080 ti with Nvidia webdrivers installed. So should I uninstall the webdriver before adding the new GPU? Clover is being used and EFI attached. Any kext must be removed? or parameters adjusted MacOS HS 10.13.6, should I upgrade before using the new GPU? CPU: 9900K Motherboard:ROG MAXIMUS XI HERO (WI-FI) Dual Monitors I have a Time machine backup, Do you recommend a fresh install? and If I did, will I be able to restore my data/apps as-is?  
      Please let yourself free to explore further aspects to considers.
      EFI-20200204.zip
    • By mrwlkr
      Hello everyone, I've an Acer Aspire E5-574 running Mojave at last update, everything is fine, except by the laggy mouse, as the attached, when the system needs the graphic card (Intel HD 520) it's generates a lag.
       
      Thanks

      final_5e2761c58c6b910015da7cf6_967905.mp4 Send me MacBook-Pro-de-Murilo.zip
×