Jump to content
About Just Joined group Read more... ×
Cyberdevs

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

134 posts in this topic

Recommended Posts

I also get huge lags with latest drivers (UI is horribly slow, whole computer feels sluggish).

 

It does fix the UI glitches with 106 driver version. However, performances in games such as World of Warcraft are horrible when compared to 156 (after a fresh boot). Has anyone else experienced this?

Share this post


Link to post
Share on other sites
Advertisement

Patched 104/106 driver still causes micro stutters in the UI. It is definitely not as smooth as things were in Sierra 10.12.X

 

If I use 104/106 patched driver in 10.13.4 B2, I lose HDMI Audio.

 

Has anyone managed to get HDMI Audio working on 10.13.4 B2 ?

 

NvidiaGraphicsFixup.kext seems to have been broken by internal changes in the OS.

Share this post


Link to post
Share on other sites

Patched 104/106 driver still causes micro stutters in the UI. It is definitely not as smooth as things were in Sierra 10.12.X

 

If I use 104/106 patched driver in 10.13.4 B2, I lose HDMI Audio.

 

Has anyone managed to get HDMI Audio working on 10.13.4 B2 ?

 

NvidiaGraphicsFixup.kext seems to have been broken by internal changes in the OS.

Try with voodooHDA ?

Share this post


Link to post
Share on other sites

 

 

Patched 104/106 driver still causes micro stutters in the UI.

Has anyone managed to get HDMI Audio working on 10.13.4 B2 ?

Well it is a patched driver and not made for the beta 2.

 

HDMI audio is broken on the Nvidia drivers on beta 2 yes but again it's a beta using patched drivers.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Patched 104/106 driver still causes micro stutters in the UI. It is definitely not as smooth as things were in Sierra 10.12.X

 

If I use 104/106 patched driver in 10.13.4 B2, I lose HDMI Audio.

 

Has anyone managed to get HDMI Audio working on 10.13.4 B2 ?

 

NvidiaGraphicsFixup.kext seems to have been broken by internal changes in the OS.

i use it, check

http://www.insanelymac.com/forum/topic/323010-please-help-me-fix-brightness-control-nvidia-graphics-only-laptop/?p=2582830

Share this post


Link to post
Share on other sites

One thing I'm wondering is whether going back to native drivers would give improvement, for those who have GPUs supported by native.

 

My 980 Ti is not.  However I still have my previous GPU, the NVidia 760 2GB.   

 

It seems a bit weird to do such a large downgrade.  But right now I am not really doing any 3D stuff in macOS.  I would reboot into Windows when I want to play games.  Of course that means I'd have to sometimes swap out GPUs.  But I'm unlikely to play any games any time soon.

 

So, does anyone know if native NVidia drivers for previous-gen GPUs are working OK/better in 10.13 compared to NVidiaWeb?

 

Thanks.

Share this post


Link to post
Share on other sites

One thing I'm wondering is whether going back to native drivers would give improvement, for those who have GPUs supported by native.

 

My 980 Ti is not.  However I still have my previous GPU, the NVidia 760 2GB.   

 

It seems a bit weird to do such a large downgrade.  But right now I am not really doing any 3D stuff in macOS.  I would reboot into Windows when I want to play games.  Of course that means I'd have to sometimes swap out GPUs.  But I'm unlikely to play any games any time soon.

 

So, does anyone know if native NVidia drivers for previous-gen GPUs are working OK/better in 10.13 compared to NVidiaWeb?

 

Thanks.

As far as I know the Kepler series should work ok with the native drivers. I have tested several iMacs with nVidia GPUs and they have no problem with the native drivers.

Share this post


Link to post
Share on other sites

As far as I know the Kepler series should work ok with the native drivers. I have tested several iMacs with nVidia GPUs and they have no problem with the native drivers.

 

Great, thanks, I will give it a go later then.

Share this post


Link to post
Share on other sites

You're welcome, let me know how it works.

 

Right, interesting results:

  • Chrome on macOS is really laggy for me, and this was a major part of what I previously noticed as 'system lag';
  • Firefox is significantly better, to the point of being lag-free.  It also uses less CPU, especially when playing videos;
  • However, Firefox with the NVidiaWeb drivers has a major problem when playing videos (at least HTML5 videos, eg YouTube and Twitch), that renders it unusable with version 106 and highly laggy with 156 (at least with my multi-monitor/Spaces setup);
  • Therefore, I am now on Firefox with Native drivers.

Before I go into detail, I will explain my monitor setup.

 

I have the setting Mission Control->"Displays Have Separate Spaces", which alters UI behaviour in several ways. I have four screens, arranged and used in my tests as follows:

  1. 32" 1920x1080
    • 1 x browser with YouTube or Twitch (HTML5) video playback - generally full screen, but not always.
  2. 24" 1200x1920 (rotated 90°)
    • Path Finder 7, maximised;  Bottom half: Wavebox email client (based on Chromium)
  3. 40"  3840x2160:
    • Left half screen: 1 x multi-tab browser window;  Right half screen: 1 x multi-tab browser window
  4. 24" 1200x1920 (rotated 90°)
    • HWMonitor detached pane;  Activity Monitor

I started my testing between NVidiaWeb (NVW) and Native by trying to stress the system - having a 1080p60 video playing full screen in Chrome on screen 1, two copies of the Pasta WebGL demo on the two browsers on screen 3 respectively, and also loading a 4K video in VLC and sometimes having it maximised on screen 3, sometimes half or quarter screen and then moving it around.

 

This generally worked OK, except:

  • I had a repeated problem opening the Pasta GL demo on Chrome; in both NVW and Native, many times when I opened this demo it would run at 3-5 FPS and cause all other GFX activity to grind to a halt.  It was not predictable as to when this would happen, but it now appears to happen more often than not.  And it never happened in Firefox.
  • Once on NVidiaWeb driver, on an occasion where I did have Pasta GL open in both Firefox and Chrome, I re-opened the 4K video in VLC and it brought the entire system to its knees for nearly 10 minutes.   I had to wait literally 4-5 minutes before I could get the Force Quit dialogue open, then more time to select VLC and close it.  After that it was slightly faster, but still took several more minutes before I could first stop the playing YouTube video, then kill the two Pasta GL browser tabs.   At that point the GUI was fully responsive, however it then dropped to a crawl again when I next opened Pasta GL (although I did this in Chrome, so that may have been the normal Chrome issue.)  I rebooted at that point.
    • My guess is this was again the issue Chrome has with that GL demo (or all GL demos?), except this time it didn't happen when I first opened it, but later when a video was added.
    • Given that I also have the general Pasta GL problem in Native, I can't be certain that this more serious issue was specific to being in NVW.

Besides those issues, I could not notice much difference between NVW 106 and Native.  In both cases it was generally responsive, however I could repeatably create a stutter in the playing YouTube video by clicking between windows on different monitors (eg clicking away from Chrome onto Path Finder, or from Chrome to Activity Monitor.)  It also often happened when I clicked between Chrome browser tabs in either browser on monitor 3, and/or opened a new tab.

 

This stutter was sometimes very brief - a handful of frames - but sometimes it would last a whole second or two.  I wondered if it might be related to "Displays Have Separate Spaces", but I confirmed it existed also with that off.

 

Then, in the Native drivers, I repeated this test with Firefox alone, and realised it was barely happening at all.   Running the video in Firefox instead of Chrome, and having my Screen 3 browser windows be Firefox windows, caused the video on Screen 1 to continue unaffected regardless of how I clicked about in Firefox.

 

It was also unaffected when I opened Photoshop and scrolled around, when I opened the 4K video in VLC and resized and moved its window, and when I clicked from Firefox to Activity Monitor.

 

However I could still detect a small but repeatable frame-skip when I clicked from Firefox to Path Finder on Screen 2.  This was not replictated by clicking on Wavebox, the other app on that screen.  I therefore conclude this is a peculiarity of Path Finder; or at least, a peculiarity of some apps, of which Path Finder is one (more testing would be needed to see if any other apps do the same.)

 

But beside that minor quirk, Firefox in Native was perfectly responsive, with nothing affecting my full screen video and other activities - fast scrolling, resizing windows, etc - all fine.   The rest of the OS GUI - moving windows about, Cmd-Tabbing, etc - was also fine in Native.

 

Then I tried the same Firefox test in NVW 106, and found the huge problem Firefox has with these drivers; at least, on my current GeForce 760.

 

Playing my usual YouTube full screen video on Screen 1, the picture would very often have major stutters, and (on 106) also often freeze completely.    The sound would continue, but the picture would either stutter badly or freeze  This happens when I click around in other windows (regardless of what monitor they're on), including other Firefox windows.  Once the video picture froze, I had to refresh the browser tab to get it back.  Stopping/re-starting the video did not help.

 

This problem is not present in any other software I've yet tried, it seems specific to Firefox.  And it's completely absent in Native drivers.

 

I re-installed NVW 156 to test in that and it was slightly improved in the sense that I never got a YT or Twitch video to completely freeze.  However there was still major stuttering in the video as I clicked around other windows.  In 156 I also noticed some other general stuttering, eg the Pasta GL demo would sometimes stutter when I clicked to another tab (in the same window, hiding it) and back again.  And I also detected general GUI lags, eg when Cmd-Tabbing back to hidden windows and when resizing windows.  These further issues are no doubt the general lags that everyone is reporting in 156.

 

So right now, it seems clear that the best experience I can get is to ditch Chrome for Firefox for all browser usage, which further requires I stick to Native drivers and therefore that I stay on the NVidia 760.

 

The Firefox issues with NVW do seem like they must be a Firefox bug, and so might be fixed over time.  Whether a fix would also help the older 106 drivers, I don't know.  If they did get fixed for 106 as well, then based on my testing I can't see any reason why I couldn't use NVW 106 and therefore go back to my 980Ti.   Or even if Firefox only gets fixed for later NVW drivers, maybe in time there will be a later NVW release that fixes the general UI lags.

 

The final test I'm yet to do is to go back to the 980Ti and confirm this Firefox-NVW issue continues.  Seems unlikely it wouldn't, but it should be tested.

 

Failing that working, I think I can be generally happy on Native with the 760.  It won't be an issue until I find I want to play a game again, or do some other 3D stuff (Adobe Premiere Pro maybe) that would highlight the massive drop in performance of the 760 versus 980 Ti :)    I can of course swap cards out, though this is a bit more work than it might seem given it also requires using a couple of different cables (the 760 has 2 x DVI + HDMI + DP, where the 980 Ti is DVI + 3 x DP + HDMI.)   But it's doable for times when I know I'm going to spend a while needing the other card, eg when rebooting into Windows.

 

So there you go.  I would suggest that anyone experiencing lag identifies tests to see if their lag is isolated like mine was - is it all GUI windows, or is it, like for me, primarily related to browser usage?  If you currently use Chrome then I'd definitely suggest trying Firefox instead as you may find it makes a big difference, even in NVW as long as you don't play a lot of videos while continuing to use other windows in parallel.

 

Of course if you are able to use Native instead then I'd definitely do that - even it means swapping out a GFX card, as I've done.

Share this post


Link to post
Share on other sites

So many words. Just admit, nVidia making {censored} drivers. There's no actual mac with built-in nvidia cards, so no $ reason for nvidia to solve this problems.

My suggestion is to use AMD video instead of waiting years until nvidia make any decision.

 

BTW, read how really bad nvidia cards under linux.

Share this post


Link to post
Share on other sites

So many words. Just admit, nVidia making {censored} drivers. There's no actual mac with built-in nvidia cards, so no $ reason for nvidia to solve this problems.

My suggestion is to use AMD video instead of waiting years until nvidia make any decision.

 

BTW, read how really bad nvidia cards under linux.

 

Several older Macs had NVidia graphics, and Apple still support them.  Eg the Macbook Pro I had in 2013 had onboard NVidia.  That's why the Native drivers are working fine for me with the GeForce 760.

 

Both the desktop GPUs I currently own are NVidia.  I'm not going to spend significant money on buying a new GPU if I can find a way to make what I already have work.  Especially as I really don't need much 3D in macOS.

 

NVidia may make bad drivers on non-Windows platforms, but that's the point of this thread; to find a way to get it to work anyway.

 

Also why are you in an NVidia thread if you don't use and don't like NVidia cards?

Share this post


Link to post
Share on other sites

With the new nVidia web drivers the lags are still there but it's a little bit better,

 

The webgl-water web app is performing smoother but macOS UI is somewhat the same. (maybe even worse)

Share this post


Link to post
Share on other sites

Fantastic

No more lags here in WebGl water pool page :)

Maybe Nvidia tech department guys read this page!:)

 

Ps deleted previous post because I was testing before in windows (sorry) :)

Edited by fabiosun

Share this post


Link to post
Share on other sites

I might need to do a clean install because I still have the lags in the macOS UI and very small hiccups in the webgl app.

 

I'm on iMac17,1 SMBIOS.

Share this post


Link to post
Share on other sites

Thanks Kynyo.  Hmm, strange, I used the tool and it downloaded 159 OK.  But then when I rebooted, I got an NVidia popup saying "default macOS drivers have been used because your system is not compatible", and the PrefPane shows:

 

RJrWvL3.png

 

It said it was patching it for my current OS?   Maybe I should just upgrade to 17D2102 - that's the new 10.13.3 "supplemental update" I see in App Store Updates, I assume?

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • 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.x (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.  You MUST BE LOGGED-IN to download attachments from this forum.
       
      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 v15 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
       
      If you want to upgrade to 10.15.7, see instructions at this post.
       
      If you want to upgrade to 10.15.6, see instructions at this post.
       
      If you want to upgrade to 10.15.5, see instructions at this post.
       
      If you want to upgrade to 10.15.4, see instructions at this post.  
       
      Follow instructions below for 10.15.2 and 10.15.3.
       
      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 (LEGACY - NOT UEFI) on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  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. 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: Replace 3rd-party kexts in EFI/Clover/kexts/Other with those in the attached EFI folder.   Replace EFI/Clover config.plist with the attached config.plist (Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values) Replace EFI/Clover/ACPI/patched with the files in the attached EFI/Clover/ACPI/patched Replace 3rd-party kexts in /Library/Extensions with those in the attached LE folder Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method for Catalina) 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.7 CLOVER r5119 DosDude Catalina Patcher: v1.4.4 Lilu.kext 1.4.7 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) AirportBrcmFixup.kext 2.0.9 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) BrcmFirmwareData.kext 2.5.4 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) BrcmBluetoothInjector.kext 2.5.4 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) BrcmPatchRAM3.kext 2.5.4 (not yet included in the attached E6410-Catalina.zip archive.  Get latest version here) IntelMausi.kext 1.0.3 (Not IntelMausiEthernet.kext)
      EFICheckDisabler.kext 0.5
      VoodooHDA.kext 2.9.2 v15 (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
      (Not yet included in E6410-Catalina.zip archive attached to Post #1) There are new versions of acidanthera kexts as described here.  I hadn't noticed any issues with the older kexts, so the kexts are not yet included in the E6410-Catalin.zip archive attached to this first post and will be included in a future update to the E6410-Catalina.zip archive. (Solved - no further work required) Clover r5118 requires the config.plist key <key>NoDefaultProperties</key><false> to permit macOS to boot with Clover's "Inject Nvidia" = True.  See details here.  config.plist in the attached E6410-Catalina.zip archive includes this change. (Solved - no further work required) EFICheck is loaded.  Solution is to install EFICheckDisabler.kext which you can get here.  EFICheck.kext is included in the attached E6410-Catalina.zip archive. (Solved - no further work required) Some users experience display issues.  The solution is to remove Device (PNLF) from the DSDT.  Use the attached DSDT.  Removal of PNLF will disable sleep on lid closure.  Device (PNLF) can be added without modifying the DSDT by enabling the Clover PNLF ACPI patch.  The attached Clover config.plist enables the PNLF DSDT patch.  Disable the Clover PNLF patch if you experience display issues. (Solved - no further work required) USB sleep/wake power IORegistry keys are not injected (not included in Mojave's or Catalina's IOUSBHostFamily.kext).  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. (No solution yet) Brightness slider does not work in System Preferences > Displays.  Brightness is easily controlled with Dell brightness keys.  There is some work on this later in this thread, but I will not be solving this as I'm content with the Dell brightness keys (and Ambient Light Sensor works to auto-adjust brightness). (No intention to solve) Display Settings in System Preferences are "garbled" when bright slider is visible.  This is a known issue with the legacy graphics patch and does not affect laptop operation. 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. (Solved - no further work required) Brcm firmware does not update when using BrcmFirmwareRepo.kext in /Library/Extensions.  Solution is to install BrcmFirmwareData.kext and BrcmPatchRAM3.kext in E/C/k/O with Clover "Inject Kexts" = YES. (Solved - no further work required) Laptop does not sleep when closing lid.  Solution appears to be a combination of adding Notify (LID0) code to Method (BTNV) and adding Device (PNLF) in the DSDT. I am using the same EFI for High Sierra 10.13.6, Mojave 10.14.6 and Catalina 10.15.3 and it works in all three macOSes. (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 (These configuration options configure Clover for LEGACY BIOS - NOT UEFI)
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (LEGACY - NOT UEFI) 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)  
      Screenshots
       
      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-5v2.zip
    • By Ciumann
      Ho fatto l'aggiornamento sicurezza 2020-005 e all'avvio non mi carica i webdrivers. Il Webdrivers updater mi dice che non ci sono aggiornamenti per questa build (17G14033). Come posso risolvere?
      Grazie!
    • By lizdav
      Hi,
       
      I would like to ask for some advice or help even.
       
      I have had some usability issues in the past with my hackintosh so I installed Mojave for the second time but it keeps producing the same exact problem. Most of the time the system stutters and lags after login. The app icons just bounce if I want to open them and even if it does it takes forever. Another thing I picked up on is that it seems like there's no internet access whenever this occurs. The problem ceases after like 2-3 restarts and everything is back to normal. 
       
      What could cause an issue like this? I had the same thing happening with my previous install but I thought that was because of unnecessary kexts I left in the EFI. I only have the bare minimum required this time so I'm kinda lost.
       
      Computer specs:
       
      Mobo: Gigabyte B360M D3H
      Graphics: Radeon Vega 64 8OC
      CPU: Intel i7 8700k
      Ram: 32 Gig
      SSD: Samsung Evo 860 250gb
       
      I also have a separate HDD with Windows 10 installed for gaming purposes. I would greatly appreciate any kind of help, thanks in advance!
       
      –David
       
       
      config.plist
    • By IvanOnMac51
      Help!!!
       
      I was running my MacPro 5,1 happily with GeForce GTX 970 with the n-1'th versions of nvidia web driver / High Sierra for several months, when suddenly, yesterday, whilst using zoom (vidconf), system reboots with kernel panic. So,
       
      1. I tested GPU RAM and main RAM using Tech Tool Pro, all fine.
      2. I swapped in the original graphics card so I could ..
      3. install latest High Sierra (17G14019) (I had been holding off for several weeks until an nvidia update became available, you know the drill...)
      4. install latest nvidia web driver (387.10.10.10.40.138)
      5. reboot and run Heaven graphics test
       
      Heaven ran for a few minutes before the kernel panic rebooted the system (attached kernel panic report).
      I managed to get "chat" support from nVidia but the tech was useless, saying there were no drivers for GTX 9series for mac (which actually he seems to be right, as I can't find it listed in the supported cards on their website, but then I and many others have been happily using this for years...).
       
      Any ideas? The computer keeps crashing with the same kernel panic. I want to keep using my GTX 970 as the stock GPU is deadly slow on any kind of games :-(
       
      Thanks in advance for your help!
      error log.pdf
    • By ronaldduck
      Yesterday I was finally able to boot and install hackintosh on my pc but after the installation my hackintosh system won't able to detect my graphics card properly even NvidiaWeb drivers are installed(English isn't my main language)
      My Current EFI

      Kernel panic log:
      Bdmesg output:
      My system properties:
      Btw Gtx 1660 Super doesn't have any vga output.
×