Jump to content
Cyberdevs

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

131 posts in this topic

Recommended Posts

2 hours ago, SavageAUS said:

I built NvidiaGraphicsFixUp.kext 1.2.7 (doesn't have lag fix in it) from source and can confirm no more lag with 387.10.10.10.30.106 on 10.13.5 beta 2.

How interesting. I just checked the commit and it seems Nvidia have incorporated the lag fix into their .30.106 release. I guess this is one of the benefits of open source projects!

Share this post


Link to post
Share on other sites
Advertisement
9 hours ago, captain-j said:

How interesting. I just checked the commit and it seems Nvidia have incorporated the lag fix into their .30.106 release. I guess this is one of the benefits of open source projects!

I think you're reading way too much into that, there are tons of other binary changes in the new drivers.  The most obvious answer to me is that there was some path that performed well but had a bug, so NVIDIA had to disable it (and the kext hack re-enabled it).  Once the underlying issue was actually fixed, the path was re-enabled.  I'd be very surprised if the answer was simply "oh yeah let's swap in this old implementation of some internal function and call it a day".

Share this post


Link to post
Share on other sites
6 hours ago, Asgorath said:

I think you're reading way too much into that, there are tons of other binary changes in the new drivers.  The most obvious answer to me is that there was some path that performed well but had a bug, so NVIDIA had to disable it (and the kext hack re-enabled it).  Once the underlying issue was actually fixed, the path was re-enabled.  I'd be very surprised if the answer was simply "oh yeah let's swap in this old implementation of some internal function and call it a day".

 

This issue has been ongoing for months. I find it highly coincidental that just as soon as a third-party patch comes out to fix it that Nvidia releases a "fixed" version of their own literally a few days later.

I'm not suggesting they lifted that exact code but I do believe it has had some kind of influence on this outcome.

Share this post


Link to post
Share on other sites
15 hours ago, captain-j said:

 

This issue has been ongoing for months. I find it highly coincidental that just as soon as a third-party patch comes out to fix it that Nvidia releases a "fixed" version of their own literally a few days later.

I'm not suggesting they lifted that exact code but I do believe it has had some kind of influence on this outcome.

 

It's equally (or I would say much more) likely that NVIDIA fixed this a month ago, and was doing weeks of rigorous testing given how severe the issue was, and once they were confident the issue was actually solved they released their driver.  Nothing against the authors of NvidiaGraphicsFixup, that workaround was very impressive.  I just don't see how "if you swap this function with an older implementation the stuttering goes away" is actually that useful for NVIDIA.  Who knows.

Share this post


Link to post
Share on other sites
Posted (edited)

Here ya go... I do not see any lags on those web pages with a dual monitor setup 2560x1440. This was while playing a movie on vlc.

EFI.zip

 

I did not see it before the nvidia fix.

Edited by AppleIIGuy

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 arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.

       
      With that being said, I'll just move on to the actual tutorial.
       
      For ATI (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id) Removed com.apple.finder.plist Removed com.apple.QuickLookDaemon.plist rebuild the kextcache and reset the nvram  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot   
      More info on that here.
       
       
      For NVIDIA
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Reboot again.  
      The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      Cheers!
    • By IPN96
      Ciao mi scuso per il disturbo, io vorrei abilitare la mia scheda grafica Nvidia geforce gtx 950m per avere delle prestazioni migliori quando lavoro su after effect, la scheda Intel non è ha abbastanza memoria non so se sia possibile fare qualcosa, spero possiate aiutarmi, vi lascio delle info. 
      Sistema operativo Mac osx sierra 10.12.6 
      Modello laptop : Asus N551jx-cn043t
      Il resto è nella screen 
       
       

    • By Buildahackintosh
      Hi everyone,
       
      I was able to successfully install OS X High Sierra on a 8700k with a GTX 1080Ti
       
      Everything seems to be working fine but I've been reading on other people suggesting to make sure hardware acceleration *is* working fine.
       
       
      I installed the web drivers for nvidia (and disabled SIP after installation)
       
      Web drivers version: 387.10.10.10.35.106
      CUDA Driver version: 396.64
      OS X system version is 10.13.5 (17F77)
       
       
      After installing the latest CUDA drivers, I was able to select the GPU option in "ray-trace" in After Effects (preferences > previews > fast previews > GPU Information...)
       
      I'm not sure how else am I able to test whether the GPU acceleration in other applications is enabled and running properly?
       
      PS: I don't have final cut pro so I'm unable to test that application...
      PS 2: ig-platform-id in config.plist is set to 0x59120003
       
    • By SAMEH209
      I've successfully installed High Sierra (10.13.0) on my system using Clover:
      2x Intel Xeon E5410
      16GB Ram
      GTX 950
      Everything is running fine except the GPU. I've tried the web driver's latest version and 378.10.10.10.25.106 but both are very laggy/sluggish.
      I've also tried installing Lilu and nVidiaGraphicsFixUp kexts but they didn't change anything.
      Have someone managed to make this card work with High Sierra?
×