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

Advertisement

Before the downtime I posted to ask if anyone had thought of trying 10.13.4 in case that might fix NVidia issues?  I know that 10.13.4 contains some changes and fixes for AMD, and it's not impossible it includes general graphical improvements that maybe help NVidia?

Also 161 was released in the time that the forum has been gone.  I upgraded to it on my 760 and I thought it maybe seemed a little better.  Hard to say because I didn't have really glaring problems with the 760 anyway, but it did seem OK.  If anyone with glaring problems didn't notice it was out, then it might be worth trying.  (Though I see it's been added to the nvidia-update.sh blacklist so I guess it's certainly not a major fix.)

Anyway I'm now using an AMD 7970 which, like cyberdevs said, is unquestionably an improvement over any NVidia I've tried :)  Earlier in this thread I got annoyed at someone who said "forget NVidia, go to AMD" but, err..  that is actually what I ended up doing :)

I won't go into great detail as this remains an NV thread, but I will just say that everything is smooth including all UI animations while a full screen video (or two) is running;  CPU usage is lower (even compared to the 760); I can select native/Metal acceleration in Photoshop; and I can connect 6 monitors at once!  All for a cost of only about £50, once I've sold my 760.  Oh and that's for a 3GB versus the 2GB I had before.   Only downside is that I did in fact have to give up a PCIe slot, because the Asus 7970 cards are 2.5 width instead of 2.  But I can live with that - I wasn't really getting any benefit from my LSI controller anyway.

Share this post


Link to post
Share on other sites
45 minutes ago, fabiosun said:

Also with new GFX and new drivers (161) no lags here and better performance with TitanXp

I'm gonna give it a try later to see if it resolves the issue on my 1070 as well. I just swapped my GPUs so at the moment I have my old R9 270X in my main system.

Share this post


Link to post
Share on other sites

I have stutter on the blossom page, about once per 30 seconds, so not sure if that is from looping or gpu.

 

I have a similar issue with playerunknown's battlegrounds on the windows side of my hack, but that started after the last driver update that claimed a 7% gain, which was released around the same time as the driver for Mac which also has a stutter when I use something from the dock, some apps.

 

This leaves me to believe it is just an issue with the driver, I've tried using different available bios versions for my card and the version it shipped with is the latest and seems to loose 4-5 fps compared to an older version on the manufacturers website, which eliminates that being my issue, so again I believe it is the driver and the latest version just installed so perhaps I will be one of the fortunate and everything works as expected. Rolling the :dice:

 

Edit:

It seems a little better, dock items stuttered and lagged after boot, now smoothing out with some stutter,  Franz preferences loaded a bit faster with less lag, but it is still present.

 

I have a Gigabyte GTX 1050 Ti G1 Gaming, interesting the forums no longer show my signature or other useful items it once had...

Share this post


Link to post
Share on other sites

Well the webgl demo is working much better but the UI is still laggy. I guess that's gonna be the point for me that I was afraid of, I'm really considering to move to AMD all together!

As much as I love my 1070 but it breaks my hart that I can't really use that great GPU with my current build so... :blowup:

Share this post


Link to post
Share on other sites
26 minutes ago, Kynyo said:

Try to install driver .161 with latest nvidiagraphicsfixup 1.2.3 which has been updated two days ago. Im using GTX 1060 and i dont have UI lag anymore and webGL its working good.

Nope that didn't help solve my problem the UI still stutters and the web GL is showing small laps and lags with the new nVidiaGraphicsFixUp :(

Share this post


Link to post
Share on other sites

Yeah I already swapped my GPUs, I'm currently using my R9 270X and you won't believe the difference! nVidia on macOS really SU*KS!!!!!!!

Share this post


Link to post
Share on other sites

As I see it the lag might be caused by a huge memory leak affecting at least the window server. I really fell from my chair when I saw that at some point, WindowServer process was using 30GB(!!!) of RAM. Also might explain why some are having lags and others not. As soon as your available RAM is eaten away bc of this leak, swapping will occur, and if that does happen with the window server process, no wonder why the UI starts to stutter. If you have lots of RAM, it might take a bit longer until you notice such problems. Also seems like Pascal GPUs are more effected than older chipsets.

Not sure if that really was the case, but might be an explanation. But, latest 161 drivers seem to have fixed this leak problem (at least for me), so in theory lags should go away as well then.

Share this post


Link to post
Share on other sites
1 minute ago, frankiee said:

As I see it the lag might be caused by a huge memory leak affecting at least the window server. I really fell from my chair when I saw that at some point, WindowServer process was using 30GB(!!!) of RAM. Also might explain why some are having lags and others not. As soon as your available RAM is eaten away bc of this leak, swapping will occur, and if that does happen with the window server process, no wonder why the UI starts to stutter. If you have lots of RAM, it might take a bit longer until you notice such problems. Also seems like Pascal GPUs are more effected than older chipsets.

Not sure if that really was the case, but might be an explanation. But, latest 161 drivers seem to have fixed this leak problem (at least for me), so in theory lags should go away as well then.

Well in my experience the lags are not happening because of the amount of the RAM I have in my rig, I have 32 GB of RAM and the stutters are happening at the very beginning when I type in my password the spinning wheel under the password box starts to act up and then the dock loads with the lag and so forth, from what I see Maxwell and Pascal GPUs are affected and I've read somewhere some users with Kepler also have this problem.

The only thing that I haven't tested yet is the nVidiaGraphixFixUp 1.2.3 and Lilu 1.2.2 I tested nVidiafixup 1.2.3 but my lilu was 1.2.1. and honestly I'm really tired of plugging my 1070 in and out form the system just to see if the lag is fixed or not, I think I'm gonna stay with my AMD as long as I'm 100% sure that the issue is fixed once and for all and heck, I might just ditch my 1070 for an AMD RX580 or Vega but the cost of Vega is honestly too high right now :(

Share this post


Link to post
Share on other sites

Yeah, definitely not a WindowServer memory leak in any of my experiences.  When I booted with my 980Ti the lag was immediately noticeable within just a minute of logging in, no time at all for a RAM leak to build.  In any case I have Activity Monitor open at all times and definitely haven't seen WindowServer use much RAM - it's usually around 100MB.

I did associate increased CPU usage of windowserver with the issues, however.  When I used the 980Ti I regularly saw WindowServer using 20+% CPU, and averaging around 10%, where with the 760 it was ~5% and now on AMD it's more like 2%.  (Except when Im running Duet to add an iPad screen, where it does sometimes use more.)

So @frankiee I would think you probably have some other issue causing that vast RAM usage.  Or at least, it's not the common cause of all the issues people are seeing.

Edited by TheBloke

Share this post


Link to post
Share on other sites

Guys. Its possible that someone can record their desktop lag and upload the file so we can see how bad it is? 

As I read I got the idea that you can´t even use yours hackintosh and sincerely my system works acceptable. Of course I got the lag in the webgl water. It lags ever 2-3 seconds and thats disappointing, but in the blossom there is no lag.

No problems in safari or youtube or seeing movies, videos or even tampering with FCPX

So or my eyes are screwed or this is something related (in the los worrisome cases) outdated kexts, clover. etc.

That's why I think is good to someone upload a file to have as a standard so people can say "yes I got the same lag" or not. Because beside Nvidia underdeveloped drivers maybe others variables are involved and so would be easier to check configuration and test.

 

Edited by Peke

Share this post


Link to post
Share on other sites
9 hours ago, Peke said:

Guys. Its possible that someone can record their desktop lag and upload the file so we can see how bad it is? 

You can see the video about the lag in this post, and things get worse sometimes. The overall performance is also affected.

 

http://www.insanelymac.com/forum/topic/324195-nvidia-web-driver-updates-for-macos-high-sierra-update-03062018/?do=findComment&comment=2589395

Edited by Cyberdevs

Share this post


Link to post
Share on other sites
43 minutes ago, Cyberdevs said:

You can see the video about the lag in this post, and things get worse sometimes. The overall performance is also affected.

Did you mean to include a link?

Share this post


Link to post
Share on other sites
1 hour ago, TheBloke said:

Did you mean to include a link?

Sorry I edited the post above, I forgot to paste the link to the video I uploaded to another topic.

 

The thing is that the lag is getting worse in the macOS UI and Safari, the WebGL and the benchmarks are much better but since we use the macOS UI and the applications inside the macOS environment it's really disappointing.

Share this post


Link to post
Share on other sites
21 hours ago, Cyberdevs said:

Well in my experience the lags are not happening because of the amount of the RAM I have in my rig, I have 32 GB of RAM and the stutters are happening at the very beginning when I type in my password the spinning wheel under the password box starts to act up and then the dock loads with the lag and so forth, from what I see Maxwell and Pascal GPUs are affected and I've read somewhere some users with Kepler also have this problem.

The only thing that I haven't tested yet is the nVidiaGraphixFixUp 1.2.3 and Lilu 1.2.2 I tested nVidiafixup 1.2.3 but my lilu was 1.2.1. and honestly I'm really tired of plugging my 1070 in and out form the system just to see if the lag is fixed or not, I think I'm gonna stay with my AMD as long as I'm 100% sure that the issue is fixed once and for all and heck, I might just ditch my 1070 for an AMD RX580 or Vega but the cost of Vega is honestly too high right now :(

NvidiaGraphicsFixup isn't going to fix it, no matter what version. At this point, if the Webdriver that comes out with 10.13.4 doesn't match or beat the 10x series of drivers in terms of UI performance, I'm going to come up with a way to plug in both my RX 480 and my 1080ti at the same time and not use the 1080ti in macOS (using Inject-Nvida to inject bogus data via the same method laptops with Optimus use if necessary) to get around the High Sierra bugs with multiple dGPUs. This way I can use the 1080ti in Windows for games, but it's a big PITA because I'll have to swap monitor connections around and 4K KVMs I've run across are too expensive to be feasible. On the bright side, my Linux install would also benefit from AMD graphics . . .

Edited by ReddestDream

Share this post


Link to post
Share on other sites

Today I received my new RX 580 GPU and I'll be switching to AMD. I'm really tired of all the hassles that comes with the web drivers and all the lags and the shi**y UI performance.

I'll be keeping an eye on this topic to see how the things go.

Good luck all

Share this post


Link to post
Share on other sites
6 minutes ago, Cyberdevs said:

Hoy recibí mi nueva GPU RX 580 y cambiaré a AMD. Estoy realmente cansado de todas las molestias que vienen con los controladores web y todos los rezagos y el rendimiento shi ** y UI.

Estaré atento a este tema para ver cómo van las cosas.

Buena suerte a todos

sleep / wake up going well with AMD?

Share this post


Link to post
Share on other sites
59 minutes ago, camillionario said:

sleep / wake up going well with AMD?

Yes, with the WEG or SSDT it works just fine. Actually I just woke my system up from sleep and typing this answer :)

Share this post


Link to post
Share on other sites

Has anyone here tried running both an AMD and an Nvidia GPU at once, hiding the Nvidia GPU from macOS's VESA driver using Inject Nvidia and bogus properties to avoid the gioscreenlockstate bug in High Sierra when a headless dGPU is present? Such a method works on Optimus laptops, but I'm not sure if it would on a Desktop quite the same way. I have been able to use it to hide the Nvidia card in order to use only the Intel graphics on my Desktop. But I'm wondering if anyone has tried it in an Nvidia+AMD dual dGPU config . . .

If I am forced by Nvidia's horrible drivers to use AMD in macOS and Linux, at least this way I can keep my Nvidia card for gaming in Windows . . . :/

https://github.com/RehabMan/OS-X-Clover-Laptop-Config/commit/9b8610f32098ce224af044c4e482d2b3da2abae0

Edited by ReddestDream

Share this post


Link to post
Share on other sites
3 minutes ago, ReddestDream said:

Has anyone here tried running both an AMD and an Nvidia GPU at once, hiding the Nvidia GPU from macOS's VESA driver using Inject Nvidia and bogus properties to avoid the gioscreenlockstate bug in High Sierra when a headless dGPU is present? Such a method works on Optimus laptops, but I'm not sure if it would on a Desktop quite the same way. I have been able to use it hide the Nvidia card in order to use only the Intel graphics on my Desktop. But I'm wondering if anyone has tried it in an Nvidia+AMD dual dGPU config . . .

If I am forced by Nvidia's horrible drivers to use AMD in macOS and Linux, at least this way I can keep my Nvidia card for gaming in Windows . . . :/

https://github.com/RehabMan/OS-X-Clover-Laptop-Config/commit/9b8610f32098ce224af044c4e482d2b3da2abae0

I haven't, but I could test it if you like.  I'm on an AMD 7970 now and could also install my 980Ti or 760 for testing.

I don't know anything about hiding GPUs with InjectNVidia.  But would that definitely be necessary?  if the card is Maxwell or later and no NVidiaWeb drivers are installed, then only the VESA driver would be loaded, and if no monitor is plugged in, then it wouldn't show in Displays.  And if another GPU is present, eg AMD, wouldn't the OS just use that and ignore the extra VESA adapter?

Or is it known that having an extra VESA adapter definitely causes problems?

Share this post


Link to post
Share on other sites
19 minutes ago, TheBloke said:

I haven't, but I could test it if you like.  I'm on an AMD 7970 now and could also install my 980Ti or 760 for testing.

I don't know anything about hiding GPUs with InjectNVidia.  But would that definitely be necessary?  if the card is Maxwell or later and no NVidiaWeb drivers are installed, then only the VESA driver would be loaded, and if no monitor is plugged in, then it wouldn't show in Displays.  And if another GPU is present, eg AMD, wouldn't the OS just use that and ignore the extra VESA adapter?

Or is it known that having an extra VESA adapter definitely causes problems?

AFAIK, Maxwell and later cards do show in Displays, at least on Sierra, even with no driver or monitor installed. They have incomplete info because of the missing driver, but they do appear to be detected by the VESA driver and they can operate in VESA mode w/o the Webdriver.

Also, AFAIK, the bug is caused by having a discrete VESA adapter that is not attached to a monitor. And all the reports I've read of people on Reddit and elsewhere attempting AMD+Nvidia configs on High Sierra have ended in gioscreenlockstate bug tears. I believe that hiding the card is necessary, at least on 10.13-10.13.3. Not sure if 10.13.4 has improved anything. I believe it is in fact a bug new in High Sierra in the VESA detection process that leads to the gioscreenlockstate lockup. It did not happen prior to High Sierra AFAIK.

To perform the hiding you must add the Nvidia properties here, turn on Inject Nvidia, and make the AMD card primary in the BIOS, and have no monitors attached to the Nvidia card, only the AMD one. You'll need WhateverGreen/RadeonDeInit or whatever you use because the Nvidia card won't be able to help you since it will disappear as soon macOS sets up the graphics.

https://github.com/RehabMan/OS-X-Clover-Laptop-Config/commit/9b8610f32098ce224af044c4e482d2b3da2abae0

See the question is, I'm not sure if bogus properties + Inject Nvidia will make the VESA driver hang up on /all/ dGPUs or just that Nvidia one if it detects the Nvidia card first. I can only fit the Nvidia card in my first slot and the AMD one in my second . . . :/

Edited by ReddestDream

Share this post


Link to post
Share on other sites

OK fair enough.  I'll give it a go when I have some time to get the case open, probably tomorrow.

My 7970 is detected natively by macOS so I don't need anything to boot - although I do use WEG because without it, sleep/resume was broken in 10.13.3 and in 10.13.4 beta I occasionally fail to reach the login screen ('white screen on boot') which WEG seems to fix.

Unfortunately I can no longer test it easily on 10.13.3, it will have to be 10.13.4 as I upgraded my backup SSD to .4 last night and my main SSD today.  So I won't be able to confirm if there's any difference between those versions.

Edited by TheBloke

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.
×