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

So, seems like 158 fixes the lag on everything but Skylake and newer, regardless of card or card generation.

 

And it also seems like maybe the lag is somewhat improved on Skylake and newer, but it's still present.

 

I've found that when 158 is not lagging, it actually seems to perform better on my 7700K/1080ti hack than 104 did . . .

Share this post


Link to post
Share on other sites

So, seems like 158 fixes the lag on everything but Skylake and newer, regardless of card or card generation.

 

And it also seems like maybe the lag is somewhat improved on Skylake and newer, but it's still present.

 

I've found that when 158 is not lagging, it actually seems to perform better on my 7700K/1080ti hack than 104 did . . .

The webgl performance is definitely improved but overall performance specially in macOS UI and Safari is worse in my experience.

 

Is there any news from you guys? I decided to switch to AMD for now because I can't get any work done with the lags.

Share this post


Link to post
Share on other sites

Waiting for my High Sierra partition test to install: curious to see if there is any improvements in Cinebench OpenGL. Last time I tried (from .104 to .156), I had 20 fps lower than 10.12.6 with my GTX 950.

 

I'm on Haswell Refresh i7 4790 and GA Z97-UD3H for the record.

Share this post


Link to post
Share on other sites

The webgl performance is definitely improved but overall performance specially in macOS UI and Safari is worse in my experience.

 

Is there any news from you guys? I decided to switch to AMD for now because I can't get any work done with the lags.

 

Out of interest, can you describe the nature and severity of the lags you see?

 

I'm still using my 760 but I've been back on the Web drivers since 159 came out.   I do sometimes see little lags, but definitely nothing that I would describe as preventing me from getting work done (with one isolated exception, described below, when I was experimenting in Final Cut Pro.)

 

I think a good test of general desktop performance is opening Mission Control.  I use BetterTouchTool to map multiple gestures to my Magic Trackpad, and I have a three-finger-swipe-upwards assigned to "Mission Control & immediately show desktop preview".  This simultaneously opens Mission Control and also expands the row of Desktops at the top, allowing immediate dragging of windows to any Space/Desktop. Having this on a gesture lets me open it quickly and easily at any time, and I do it frequently.

 

I think this is a good test of lag because it causes all windows on all screens to resize and move, as well as animating the expansion of the desktop row at top.  So it's quite a lot of movement at once.  

 

Another test, though with less movement, is just to move left or right a space, causing the whole desktop contents to slide to one side.

 

Performing these actions is usually fast and fluid for me, even with an in-browser video playing on one screen.  But now and then it will stutter just a little.

 

It's been long enough since I used a real Mac that I have no idea if such micro-lags are unusual or not.  Maybe a real Mac would do the same with 4 x monitors and a full screen video playing?   Actually it's five monitors now, because I've added my iPad as an extra screen using Duet.  And when I did have a real Mac, I never used it with more than three screens total, and never with a 4K screen as I have now.  So I'm pushing this Hack more than I ever did a real Mac - though the Hack also has superior hardware versus my last Mac, the early-2013 MacBook Pro with NVidia 650M.

 

So from what you and others have said, I'm thinking I'm not getting the sort of lag you guys are seeing.  Even when I get stuttering, it's not nearly bad enough to stop me working. 

 

That one exception I mentioned, the only recent time I have had really bad lag, was when I was playing about in Final Cut Pro, adding multiple effects to a sample video. I had my usual full screen video playing on another screen.  At one point as I scrolled through the FCP video, everything suddenly froze for a good minute or so, including the mouse pointer.  However audio from the YouTube video continued.  It did recover, but took long enough that I wondered if maybe it wasn't going to come back. 

 

This might be an instance of very bad stutter, or maybe it's just Final Cut Pro being flaky; again, I don't know what a real Mac would do in this situation.  And I've never used FCP before, so I have no prior experience of its performance.  But it does seem unlikely that a real Mac would get into a all-screens-frozen-for-over-a-minute situation when using Apple's own video editing software.

Share this post


Link to post
Share on other sites

Out of interest, can you describe the nature and severity of the lags you see?

 

I'm still using my 760 but I've been back on the Web drivers since 159 came out.   I do sometimes see little lags, but definitely nothing that I would describe as preventing me from getting work done (with one isolated exception, described below, when I was experimenting in Final Cut Pro.)

 

I think a good test of general desktop performance is opening Mission Control.  I use BetterTouchTool to map multiple gestures to my Magic Trackpad, and I have a three-finger-swipe-upwards assigned to "Mission Control & immediately show desktop preview".  This simultaneously opens Mission Control and also expands the row of Desktops at the top, allowing immediate dragging of windows to any Space/Desktop. Having this on a gesture lets me open it quickly and easily at any time, and I do it frequently.

 

I think this is a good test of lag because it causes all windows on all screens to resize and move, as well as animating the expansion of the desktop row at top.  So it's quite a lot of movement at once.  

 

Another test, though with less movement, is just to move left or right a space, causing the whole desktop contents to slide to one side.

 

Performing these actions is usually fast and fluid for me, even with an in-browser video playing on one screen.  But now and then it will stutter just a little.

 

It's been long enough since I used a real Mac that I have no idea if such micro-lags are unusual or not.  Maybe a real Mac would do the same with 4 x monitors and a full screen video playing?   Actually it's five monitors now, because I've added my iPad as an extra screen using Duet.  And when I did have a real Mac, I never used it with more than three screens total, and never with a 4K screen as I have now.  So I'm pushing this Hack more than I ever did a real Mac - though the Hack also has superior hardware versus my last Mac, the early-2013 MacBook Pro with NVidia 650M.

 

So from what you and others have said, I'm thinking I'm not getting the sort of lag you guys are seeing.  Even when I get stuttering, it's not nearly bad enough to stop me working. 

 

That one exception I mentioned, the only recent time I have had really bad lag, was when I was playing about in Final Cut Pro, adding multiple effects to a sample video. I had my usual full screen video playing on another screen.  At one point as I scrolled through the FCP video, everything suddenly froze for a good minute or so, including the mouse pointer.  However audio from the YouTube video continued.  It did recover, but took long enough that I wondered if maybe it wasn't going to come back. 

 

This might be an instance of very bad stutter, or maybe it's just Final Cut Pro being flaky; again, I don't know what a real Mac would do in this situation.  And I've never used FCP before, so I have no prior experience of its performance.  But it does seem unlikely that a real Mac would get into a all-screens-frozen-for-over-a-minute situation when using Apple's own video editing software.

 

The issue appears to be CPU Generation-dependent (Mostly affecting Skylake and newer). What CPU do you have in this hack that you say is not lagging?

Share this post


Link to post
Share on other sites

The issue appears to be CPU Generation-dependent (Mostly affecting Skylake and newer). What CPU do you have in this hack that you say is not lagging?

 

Old: Westmere generation, Intel X5670 (X58 architecture).  So yeah that would definitely explain it then.

Share this post


Link to post
Share on other sites

 

So, I was reading and some MBP owners have also had Nvidia lag on High Sierra:
 
 
Some users there are also reporting that the 104 Web driver is the best driver they've had too . . .
 

 

 

Well that's good - it won't get fixed unless it affects 'official' users. 

 

So 104 is better than 106?  It was 106 I was using before I went to the latest 159, that's what the nvidia-update shell script installs by default.

 

Though maybe it doesn't matter for me if I'm not getting the big issue anyway.

Share this post


Link to post
Share on other sites

Well that's good - it won't get fixed unless it affects 'official' users. 

 

So 104 is better than 106?  It was 106 I was using before I went to the latest 159, that's what the nvidia-update shell script installs by default.

 

Though maybe it doesn't matter for me if I'm not getting the big issue anyway.

 

AFAIK, 104, 105, and 106 are identical save for the changed build number for iMac Pro.

 

Also, 158 and 159 are only different by build number too.

Share this post


Link to post
Share on other sites

VoodooHDA has strange audio lag/stuttering and is far inferior to native HDAudio.

Yes I also prefer Native HD Audio, but I do not have any lag in the sound with voodoo! In fact, I do not even notice a difference, since I always edit the output levels of voodoo in the plist so that they have a similar output to AppleHDA.

About Web Driver, 159 is working fine on my system as expected! No lag!

Share this post


Link to post
Share on other sites

@TheBloke 

 

 

Well the main lags are appearing in the macOS UI, Dock, Safari and while switching between windows specially when I minimize them to the dock and vise versa.

 

I've been using macOS for many years on many computers (Macs and Hacks) but ever since macOS High Sierra came out the overall experience is really bad in my view (even on Apple Computers).

 

I've been using AMD GPUs for a long time and whit the "Black Screen" issue on macOS Sierra I decided to switch to nVidia and it was a pretty good experience at the time.

 

Short after, @Mieze found a solution to solve the problem on AMDs GPU (Booting to black screen).

 

Last night I've been thinking that the same thing might possibly be used to solve the lags on nVidia GPUs. I'm thinking that using a SSDT for nVidia GPUs might be useful to address the issue on the current problem.

 

I have to investigate more in the matter to see wether it can help solve the problem or not.

 

The base for this conclusion is on the fact that the lags are happening mostly on 100, 200 and the 300 series (SkyLake and newer architecture).

 

If anyone has a suggestion and/or can test my hypothesis please let me know how it worked out.

 

Cheers

Share this post


Link to post
Share on other sites
 
I can confirm that with 10.13.3 (17D102) and driver 158, I do not have lags in webGL.
I've updated from sierra and the graphics very well so far. The installation has been without DSDT in Patch, only SSDT for sound, USB, graphics, CPU and Bluetooth.
I can say that in this way I have not had lags in the graphics, while using DSDT yes.
 
post-887245-0-35345500-1519587330_thumb.png

 

Share this post


Link to post
Share on other sites

Waiting for my High Sierra partition test to install: curious to see if there is any improvements in Cinebench OpenGL. Last time I tried (from .104 to .156), I had 20 fps lower than 10.12.6 with my GTX 950.

 

I'm on Haswell Refresh i7 4790 and GA Z97-UD3H for the record.

 

Answering to myself: Cinebench the same on my Dell Optiplex 9020 and GT 1030 (75 fps) but definitely 15 to 20 fps lower than Sierra with the Maxwell GTX 950. Anyone has Cinebench comparison between Sierra and HS for Maxwell?

 

Thanks,

 

Patrice

Share this post


Link to post
Share on other sites

Answering to myself: Cinebench the same on my Dell Optiplex 9020 and GT 1030 (75 fps) but definitely 15 to 20 fps lower than Sierra with the Maxwell GTX 950. Anyone has Cinebench comparison between Sierra and HS for Maxwell?

 

Thanks,

 

Patrice

I guess with the last macOS update (10.13.3) and with the latest supplemental update the drop in performance is unavoidable, they had to issue the Meltdown and the Spectre bugs which definitely took a toll on the performance of the CPU and the GPU.

Share this post


Link to post
Share on other sites

158 is good, no lags :yes:


 

 
I can confirm that with 10.13.3 (17D102) and driver 158, I do not have lags in webGL.
I've updated from sierra and the graphics very well so far. The installation has been without DSDT in Patch, only SSDT for sound, USB, graphics, CPU and Bluetooth.
I can say that in this way I have not had lags in the graphics, while using DSDT yes.
 

 

DSDT/SSDT is for the best hackintosh experience
 
if the opposite happens to you, something wrong

Share this post


Link to post
Share on other sites

The issue appears to be CPU Generation-dependent (Mostly affecting Skylake and newer). What CPU do you have in this hack that you say is not lagging?

The base for this conclusion is on the fact that the lags are happening mostly on 100, 200 and the 300 series (SkyLake and newer architecture).

I have now also found that the issue is noticeably worse with a later gen Maxwell NVidia card.  Or rather, for me the issue exists in my Maxwell card where it mostly did not in my Kepler.

 

I spent the last week or so using my old 760, originally to test Native but I carried on with Web 159 for a couple of days. 

 

Today I got around to reverting back to my 980Ti, and within minutes of booting I could see things were noticeably laggy again.

 

Moving left/right a space mostly still smooth, as is Minimising/Restoring a window to Dock.  But "open mission control & display desktop previews" was noticeably slower. And everything just feels.. lagged. Like even clicking into a window on another monitor sometimes seems to take a moment before it registers.

 

My ever-present full-screen YouTube video is once again regularly skipping frames when I perform actions elsewhere, like activating browser tabs in other windows (when it causes a screen re-draw), and sometimes when moving left/right a space on a different screen. And there's often a noticeable lag when I hit the "full screen" button on a YouTube video which wasn't there before.

 

I also find graphics are using more CPU. For example, that YouTube video was for a while showing 50-60% of a CPU in VTDecoderXPCService, macOS' video rendering daemon  Before it was 30-40%.   Also quite noticeable is that I am often seeing WindowServer towards the top of Activity Monitor's CPU list, sometimes as high as 35%. I don't ever remember seeing that regularly before.

 

As a result, Activity Monitor is showing my "Idle" as 88-90% as I type this. Before I reverted I was seeing 95+%, with exactly the same apps/tabs open. Not a huge difference, but there shouldn't be any difference. If there was no lag then it wouldn't matter, but as it stands this is another symptom.

 

Therefore I think that separate from CPU issues, there's also a GPU difference: if you have a Maxwell card you may well have a worse experience than Kepler and prior. Which sucks.

 

Later update:

 

I then tried going to driver 106, and from boot things seemed a bit better.  And mostly they have remained a little better  -  Mission Control has mostly been smooth, and while playing a video I'm not seeing such high CPU, though I do see WindowServer averaging around 9%.  But it's clearly still not right, as occasionally I get massive judders, and once again the YouTube video is very easily skipped by any other graphical activity on the system.  And trying to scroll a Facebook tab in Firefox was terrible, major juddering on every scroll.

 

I'm going to stick with this GPU for another 12-24 hours, if for no other reason than it's hassle switching GPU again.  I'll continue seeing how it performs on both 106 and 158/159, and see if anything at all can improve it.

 

But it seems most likely that I will have to go back to the NV 760, because this level of lag is annoying.  It sucks to use a mid-level 2013 graphics card when I have a high-end 2017 card gathering dust.  I even briefly thought about selling it.   But I will want to play games in Windows again at some point, so I guess I'm stuck with this two-GPU situation unless the drivers/macOS ever fix this issue.

 

Unless I sold the 980Ti to buy an AMD RX580.  But that's a pretty big downgrade from the 980Ti, and I think isn't even really capable of 4K in games.   And the RX Vega cards are far too expensive.

Share this post


Link to post
Share on other sites

I tried the 980Ti for a day and it was horrible.  I'm back on the 760 (with NV drivers 158) and the difference is night and day. 

 

Besides the obvious screen lag, the problems were clearly obvious and quantifiable by looking at CPU usage:  playing a full-screen video on one screen while typing this, with three Firefox windows wih a dozen or so tabs, plus Path Finder, Activity Monitor, HWMonitor and a few iTerm 2 windows, my Idle is 94-95%, where before it was 85-90%.   VTDecoderXPCService is using 15% CPU to decode the video, where with the Maxwell card it was 30-60%.  WindowServer is still always visible towards the top of Activity Monitor (I guess it always was and I didn't notice before), but it's averaging 5% instead of 9+%.  

 

Window operations are again smooth, in particular Mission Control  and left/right a space.  Sometimes these operations do cause a slight pause in the playing full-screen video, but it's just for the duration of the screen operation; there's no continued frame skip/juddering of the video after the operation, as there was before.  And it doesn't skip as a result of normal operations like clicking around in other windows or activating other Firefox tabs.

 

So my experience is that Maxwell cards are bust :(  Those drivers must be really bad to cause a knock-on effect of high CPU in processes accessing the displays.  I guess I will make a post on the NVidia forums, but I have no hope of it doing any good any time soon.

Share this post


Link to post
Share on other sites

 

But it seems most likely that I will have to go back to the NV 760, because this level of lag is annoying.

 

 

FWIW, I'm running a 770 and I get the lag… :(

Share this post


Link to post
Share on other sites

@TheBloke

 

 

Well the main lags are appearing in the macOS UI, Dock, Safari and while switching between windows specially when I minimize them to the dock and vise versa.

 

I've been using macOS for many years on many computers (Macs and Hacks) but ever since macOS High Sierra came out the overall experience is really bad in my view (even on Apple Computers).

 

I've been using AMD GPUs for a long time and whit the "Black Screen" issue on macOS Sierra I decided to switch to nVidia and it was a pretty good experience at the time.

 

Short after, @Mieze found a solution to solve the problem on AMDs GPU (Booting to black screen).

 

Last night I've been thinking that the same thing might possibly be used to solve the lags on nVidia GPUs. I'm thinking that using a SSDT for nVidia GPUs might be useful to address the issue on the current problem.

 

I have to investigate more in the matter to see wether it can help solve the problem or not.

 

The base for this conclusion is on the fact that the lags are happening mostly on 100, 200 and the 300 series (SkyLake and newer architecture).

 

If anyone has a suggestion and/or can test my hypothesis please let me know how it worked out.

 

Cheers

I don't think the Nvidia lag is anything like the AMD black screen issue, which was an issue with the init state the macOS AMD drivers expect the card to be in. Fixes like WhateverGreen and RadeonDeInit work by putting the card in the state the driver expects.

 

In fact, Linux users are also having lag issues with their latest Nvidia driver, so I think Nvidia just dropped the ball somewhere internally, maybe with the Spectre/Meltdown mitigations, and didn't test properly or didn't have time on non-Windows OSes. Like the macOS drivers, the Linux drivers are also tied to particular kernel versions and people are modding the older drivers to work on newer kernels in the meantime:

 

https://bbs.archlinux.org/viewtopic.php?id=234241

 

In fact this is all so bad, I've been tempted to try to put my old RX 480 in alongside my 1080ti and only use the 1080ti in Windows . . .

Share this post


Link to post
Share on other sites

I don't think the Nvidia lag is anything like the AMD black screen issue, which was an issue with the init state the macOS AMD drivers expect the card to be in. Fixes like WhateverGreen and RadeonDeInit work by putting the card in the state the driver expects.

 

In fact, Linux users are also having lag issues with their latest Nvidia driver, so I think Nvidia just dropped the ball somewhere internally, maybe with the Spectre/Meltdown mitigations, and didn't test properly or didn't have time on non-Windows OSes. Like the macOS drivers, the Linux drivers are also tied to particular kernel versions and people are modding the older drivers to work on newer kernels in the meantime:

 

https://bbs.archlinux.org/viewtopic.php?id=234241

 

In fact this is all so bad, I've been tempted to try to put my old RX 480 in alongside my 1080ti and only use the 1080ti in Windows . . .

I know that the boot to black screen issue on AMD GPUs is totally another story, what I meant by that statement was based on the fact that almost all the system prior to 100 chipset are working without the lag. So that got me thinking that it must have been related to way that the BIOS is addressing the GPU and this is beside the fact that it might have been totally related to the web drivers themselves. This was just a hunch!

 

I assure you if you use your RX 480 just for few minuted you will see the difference between the AMD and nVidia (only if you suffer from the lag on nVidia as well).

 

My 7790 1GB (an ancient GPU in comparison to my 1070) is performing much better as if I just upgraded from a 8086 pc to modern one :D

FWIW, I'm running a 770 and I get the lag… :(

You are not alone brother! We all have the lag with the nVidia GPUs!

Share this post


Link to post
Share on other sites

Having said that it's much better on my 760.. well, it is better than the 980Ti.  But it's certainly not fixed.

Since yesterday I've been using Lightroom and Photoshop and that's re-introduced lots more lag.  Just having Photoshop open as I have now, with a video playing on another screen, and performance is very variable. Sometimes OK, sometimes noticeable stutters on things like Mission Control (MC).   Last night was even worse - MC sometimes taking a couple of seconds before it fully animated. 

 

This is frustrating because I use Mission Control a lot as a window switcher - rather than Alt or Command Tab, I swipe three fingers upwards on the trackpad which activates MC and I can see all windows in the current space side by side.  If it's fast this is a great way to choose another window, especially if I haven't used it recently.  But only if it's fast.

 

I don't think this is general system slowness, because Activity Monitor shows the system at 85+% idle, and I've got plenty of free RAM.

 

And in fact just now I was in a position where I couldn't full-screen a sports video in Firefox, on a site that uses Adobe Flash, without it suttering horribly.  I had to close and re-open the tab and site before it worked OK.  It shouldn't be like this.

 

So as discussed in other threads, I'm now seriously considering going AMD instead.  If I get confirmation that I can use all five or six outputs on an AMD EyeFinity card, I'll definitely sell this 760 and get a 7970 instead.   (I also noticed that Photoshop won't let me enable Metal acceleration with my current NVidia.  I don't know exactly why as other apps seem to use Metal OK.  But I'm hoping this might work better with AMD.)

 

 

 

Last night I've been thinking that the same thing might possibly be used to solve the lags on nVidia GPUs. I'm thinking that using a SSDT for nVidia GPUs might be useful to address the issue on the current problem.

 

You mentioned SSDTs also in my thread, with regard to AMD cards.  Could you elaborate on this?

 

I had thought SSDTs were only related to SpeedStep and power management?  Is that not correct?  Or do you think our issues are related to power management somehow - interfering with the graphics somehow?

 

I did notice that when I had my 980Ti in, according to HWMonitor it either ran at 900Mhz or 1100Mhz.  Whereas the max speed of the card is 1350Mhz, and that's what I'd see it maxing at in Windows.   I wasn't sure if that was a reporting/monitoring error, or if the card was really never using its full performace.

 

Not that that should explain the lag - a 980Ti at 1100mhz should be capable of doing normal UI animations dozens of times over!

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