netkas.org forum
November 15, 2018, 06:03:51 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Information for registering users http://forum.netkas.org/index.php/topic,2246.0.html
 
   Home   Help Search Login Register  
Pages: 1 ... 13 14 [15] 16 17 18
  Print  
Author Topic: High Sierra and The Nvidia Web Driver  (Read 55760 times)
h9826790
Jr. Member
**
Offline Offline

Posts: 77


« Reply #210 on: April 15, 2018, 08:36:32 PM »

I am one of those with an unaffected system (performance wise), but I am with the genuine Mac Pro 2009 (flashed 5,1).

Hi All,

I read the whole topic to find a possible solution for my bad nVidia 1080Ti experience, mainly since Sierra / High Sierra. As noticed by members in the hackintosch scene recently on TonyMacX86 / InsanelyMac the nVidia drivers are terrible. Special the latest are almost unusable. Fallback to older versions will help but to some point they will cause problems too because they are old and not intent to be used on the latest MacOS versions.

At this moment I'm using an old version of the nVidia drivers : 378.10.10.10.25.106 together with two options "System Preferences / Accessibility / Display / Reduce Motion + Reduce Transparency the GUI responds more snappy and to some point even to an almost acceptable experience. Also Cuda performance is very good 12200GB / Host to Device and reverse. The issue looks to be GUI related only.

I am still looking to a possible solution or to find out why the hell the experience is so bad. So I bought an old R9 280X to be added in my hack. I was unlucky because the card did only one good Valley bench and after it failed and caused artefacts so this card is dead. The card was performing perfectly without issues but again its no party against the 1080Ti when it comes to gaming which I also do on my Hack from time to time. Also struggling with many GPU's in a system is also far from comfortable. I also considered to move to AMD Vega 64 but I'm to spoiled with the 1080Ti if we are talking to gaming performance in windows, especially when it comes to 4K gaming.

After reading this topic I came to a few conclusions.

  • Best is to stick to MacPro5,1 SMBios definition. This definition is supported by the nVidia WebDrivers. Other SMBios definitions are unsure to work as they should.
  • The main reason of lags can be narrowed to the latest CPU's like Skylake and newer or in combination with mainboards with the latest chipsets to drive these CPU's

Do I forget things here ˆˆˆ?

I also read comments from guys in this topic that they are fully comfortable with the drivers and don't experience any lags at all with 10xx or specific with the 1080Ti. Are they indeed on older CPU / Mainboards?
Do I miss something, and is there something to be the "Golden Tip" to solve my issue?

Because eGPU's are officially supported more people will throw in a GPU in an enclosure to profit from extra external GPU performances. Although Apple has announced that only AMD will be supported there is a chance
that nVidia will provide better drivers that their cards are supported as well. I hope this brings better drivers for us, hackintoshers as well!.

 
Logged
eVasilis
Full Member
***
Offline Offline

Posts: 146


« Reply #211 on: April 15, 2018, 09:19:49 PM »

What "2.5 GT/s" bug? If you mean the GPU cannot negotiate at 5GT/s link speed in macOS, that was fixed by Nvidia long time ago.


Just a cosmetic one in the PCI section of system report



* Screen Shot 2018-04-15 at 11.17.32 PM.png (33.04 KB, 583x316 - viewed 156 times.)
Logged
h9826790
Jr. Member
**
Offline Offline

Posts: 77


« Reply #212 on: April 16, 2018, 12:23:31 PM »

I see. Yes, that cosmetic bug still there.

What "2.5 GT/s" bug? If you mean the GPU cannot negotiate at 5GT/s link speed in macOS, that was fixed by Nvidia long time ago.


Just a cosmetic one in the PCI section of system report


Logged
Rominator
Hero Member
*****
Offline Offline

Posts: 2343



« Reply #213 on: April 17, 2018, 09:18:04 AM »

And if you put a new Vega in there I think it reports PCIE 3.0 speeds.
Logged

Before asking a question, check your "Personal Settings" and be sure that you have "Brain Services" set to "On".
eVasilis
Full Member
***
Offline Offline

Posts: 146


« Reply #214 on: April 17, 2018, 10:59:26 PM »

Driver now updated to 387.10.10.10.30.106. No clue what it does, no time to check...
Logged
lowrider
Sr. Member
****
Offline Offline

Posts: 381


« Reply #215 on: April 18, 2018, 12:23:33 AM »

Thanks - Here:

https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.30.106.pkg

Lou
Logged
h9826790
Jr. Member
**
Offline Offline

Posts: 77


« Reply #216 on: April 18, 2018, 01:35:01 AM »

Driver now updated to 387.10.10.10.30.106. No clue what it does, no time to check...

A quick test shows that the glitches in FCP X preview is fixed (this is 100% reproducible when previewing Titles, so very easy to check).

And so far, I didn't see any colour bug when Transparency is ON. I tried a lot of Finder Windows movement, but still didn't hit one. For the old V387 driver, even though still need some "luck" to see that, but usually easy to hit one within 5min.

And super smooth for about 1 hour now. So, should be quite safe to use this driver.
Logged
mysticalos
Hero Member
*****
Offline Offline

Posts: 637


« Reply #217 on: April 18, 2018, 07:16:42 AM »

Reading about update on reddit it fixes the lag issues too

Important to note about person recommending lilu and fixup. FYI the workaround they were using for lag was to force opengl mode instead of metal on windowserver. If the drivers fix bug, you WANT to be using metal not opengl. I generally avoid lilu in general too cause every macos update people update to new version and start having kernel panics until lilu is updated. It's a pretty low level kernel hack so it always needs updates too before updating macOS (and always someone doesn't listen).

It also taints nvidia driver so libval is no longer valid (which is also why fixup also does libval work around)

TLDR though, if you don't NEED lilu or any of fixups, it's best to run as vanilla as possible so libval is clean and nvidia drivers run the optimized metal path. Only use work arounds if it doesn't work otherwise, Don't use them cause everyone on and their grandma on tonymac said so.

I run a hack and it's very clean.
Logged
eVasilis
Full Member
***
Offline Offline

Posts: 146


« Reply #218 on: April 18, 2018, 01:42:04 PM »

Driver now updated to 387.10.10.10.30.106. No clue what it does, no time to check...

A quick test shows that the glitches in FCP X preview is fixed (this is 100% reproducible when previewing Titles, so very easy to check).

And super smooth for about 1 hour now. So, should be quite safe to use this driver.

That is good news. Now, if only export and render times in fcpx were improved, I would be particularly happy... oh well, I guess fcpx is only geared towards AMD.
Logged
Asgorath
Sr. Member
****
Offline Offline

Posts: 295


« Reply #219 on: April 18, 2018, 03:27:51 PM »

That is good news. Now, if only export and render times in fcpx were improved, I would be particularly happy... oh well, I guess fcpx is only geared towards AMD.

What GPU and CPU are you using?  What performance do you get with the BruceX benchmark?

FWIW I also have a very "clean" Hackintosh setup, I have SIP enabled and only inject FakeSMC and the IntelMausiEthernet driver to enable networking.  I use a USB audio device so I can avoid the audio hacks as well.
Logged
lowrider
Sr. Member
****
Offline Offline

Posts: 381


« Reply #220 on: April 18, 2018, 05:55:51 PM »


Guess you missed my post just above yours?HuhHuhHuhHuhHuh

Lou
Logged
eVasilis
Full Member
***
Offline Offline

Posts: 146


« Reply #221 on: April 18, 2018, 09:27:46 PM »

What GPU and CPU are you using?  What performance do you get with the BruceX benchmark?

FWIW I also have a very "clean" Hackintosh setup, I have SIP enabled and only inject FakeSMC and the IntelMausiEthernet driver to enable networking.  I use a USB audio device so I can avoid the audio hacks as well.

I use a 12 core 2010 mac pro, that is 2X2.66 Ghz CPUs, 48 gig or RAM and a GTX 980. The Os is on an 512 MB EVO 850. With El Capitan I could export from BruceX in 29 to 30 secs. I tried to run it with 10.3.4 and the latest nvidia drivers but I cancelled it after 2 minutes. Rest is fine.
Logged
Asgorath
Sr. Member
****
Offline Offline

Posts: 295


« Reply #222 on: April 18, 2018, 09:38:01 PM »

I use a 12 core 2010 mac pro, that is 2X2.66 Ghz CPUs, 48 gig or RAM and a GTX 980. The Os is on an 512 MB EVO 850. With El Capitan I could export from BruceX in 29 to 30 secs. I tried to run it with 10.3.4 and the latest nvidia drivers but I cancelled it after 2 minutes. Rest is fine.

By latest driver, do you mean the one that just came out this week?
Logged
eVasilis
Full Member
***
Offline Offline

Posts: 146


« Reply #223 on: April 18, 2018, 09:40:58 PM »

Precisely; it was the same with the previous one, though.
« Last Edit: April 19, 2018, 10:52:03 PM by eVasilis » Logged
mysticalos
Hero Member
*****
Offline Offline

Posts: 637


« Reply #224 on: April 19, 2018, 12:00:14 AM »

Based on comments with https://github.com/lvs1974/NvidiaGraphicsFixup/commit/9ddc07558737d5085f665002dda94b636958e47b

It seems the new web driver is forcing legacy opengl path internally? I hope that doesn't mean those who weren't having issues are suddenly using opengl instead of metal for windowserver? Hard to really say, I don't recall how to test for that. I also hope it's not a perm work around but just one nvidia is applying for now until they get the metal code more solid.
Logged
Pages: 1 ... 13 14 [15] 16 17 18
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!