Kynyo Posted April 18, 2018 Share Posted April 18, 2018 Is nvidiagraphicsfixup needed anymore with this new driver? Just askin'... Link to comment Share on other sites More sharing options...
bolonia Posted April 18, 2018 Share Posted April 18, 2018 I don't know hot to enable this {censored} nvidia drivers on my system. I've installed latest drivers and it always boots in compatible mode (Default macOS Graphics Driver) instead of NVIDIA Web Driver. I tried to switch different OsxAptioFix efis, tried to boot with or without NvidiaGraphicsFixup (1.2.6). I have <key>NvidiaWeb</key><true/> in my config. What i'm doing wrong? Guys, help please. My system: H110M PRO VD, GTX 1060, macOS 10.13.4. Link to comment Share on other sites More sharing options...
Asgorath Posted April 18, 2018 Share Posted April 18, 2018 I've been seeing more and more reports that the major issues with the 387 drivers have been fixed in the latest release, so it's probably worth trying to run without the NvidiaGraphicsFixup kext to confirm. If the drivers have been fixed (or even just changed) there's no telling what the hack in that kext will do if you try and use it with the new drivers. Link to comment Share on other sites More sharing options...
corint1 Posted April 18, 2018 Share Posted April 18, 2018 6 hours ago, Moviemakergr said: Goodmorning read the guide here > https://www.insanelymac.com/forum/forums/topic/330677-successguide-glasgoods-high-sierra-coffeelake-asus-strix-z370-g-i7-8700-gtx1080ti-uhd/ thank you , but is not usefull ... dont boot ... rest in black screen and nothing happening ... only bios reset help to boot again ... Link to comment Share on other sites More sharing options...
Funky frank Posted April 18, 2018 Share Posted April 18, 2018 Vit updated his NvidiaGraphicsFixup, and it does not patch the recent driver anymore, so I guess the new driver includes his fix somehow. Link to comment Share on other sites More sharing options...
arabesc Posted April 18, 2018 Share Posted April 18, 2018 I have an issue with the 387.10.10.10.30.106 driver - Firefox stops rendering pages after some time. There was no such issue with the 387.10.10.10.25.160 driver. Link to comment Share on other sites More sharing options...
SavageAUS Posted April 19, 2018 Share Posted April 19, 2018 I've been seeing more and more reports that the major issues with the 387 drivers have been fixed in the latest release, so it's probably worth trying to run without the NvidiaGraphicsFixup kext to confirm. If the drivers have been fixed (or even just changed) there's no telling what the hack in that kext will do if you try and use it with the new drivers.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. Sent from my SM-G930F using Tapatalk Link to comment Share on other sites More sharing options...
himac59 Posted April 19, 2018 Share Posted April 19, 2018 did the 387.10.10.10.30.106 Nividia update on my 10.3.4 MacOs version and no more lag Finaly! 1 Link to comment Share on other sites More sharing options...
LockDown Posted April 19, 2018 Share Posted April 19, 2018 19 minutes ago, himac59 said: did the 387.10.10.10.30.106 Nividia update on my 10.3.4 MacOs version and no more lag Finaly! w/o NvidiaGraphicsFixup? Link to comment Share on other sites More sharing options...
Funky frank Posted April 19, 2018 Share Posted April 19, 2018 11 hours ago, arabesc said: I have an issue with the 387.10.10.10.30.106 driver - Firefox stops rendering pages after some time. There was no such issue with the 387.10.10.10.25.160 driver. Make sure your Intel Graphics runs in connector-less mode. Link to comment Share on other sites More sharing options...
tarasis Posted April 19, 2018 Share Posted April 19, 2018 Finding the new driver works well (without the fix kext installed), although not perfect. i played a WMV video file in VLC last night and had weird graphical breaks across the screen (like something hit glass at a specific point and breaking in pieces). Have a 5 sec video demonstrating it but it’s apparently too big to attach. Link to comment Share on other sites More sharing options...
tarasis Posted April 19, 2018 Share Posted April 19, 2018 (edited) Using YACReaderLibrary for a while suddenly all the comic covers were corrupt, and now so is Safari. Which on screen now looks like on my screen (swapped to mobile safari as Mac now messed up) Edited April 19, 2018 by tarasis Link to comment Share on other sites More sharing options...
scj312 Posted April 19, 2018 Share Posted April 19, 2018 8 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. Sent from my SM-G930F using Tapatalk Also good here with 1.2.6 and ngfxsubmit=0. Link to comment Share on other sites More sharing options...
MICKHAEL Posted April 19, 2018 Share Posted April 19, 2018 4 hours ago, tarasis said: Using YACReaderLibrary for a while suddenly all the comic covers were corrupt, and now so is Safari. Which on screen now looks like on my screen (swapped to mobile safari as Mac now messed up) thats art. I like it Link to comment Share on other sites More sharing options...
arabesc Posted April 19, 2018 Share Posted April 19, 2018 4 hours ago, tarasis said: Which on screen now looks like on my screen Are you sure that web driver is loaded and active? I have similar artifacts when default driver is working. Link to comment Share on other sites More sharing options...
tarasis Posted April 19, 2018 Share Posted April 19, 2018 3 hours ago, arabesc said: Are you sure that web driver is loaded and active? I have similar artifacts when default driver is working. Seems to be [21:36][rob@iMac:~]$ kextstat | grep nvidia 118 2 0xffffff7f80c1a000 0x679000 0x679000 com.nvidia.web.NVDAResmanWeb (10.3.1) 8E2AB3E3-4EE5-3F90-B6D8-54CEB8595A5F <110 101 100 12 7 5 4 3 1> 119 0 0xffffff7f815be000 0x1a7000 0x1a7000 com.nvidia.web.NVDAGP100HalWeb (10.3.1) 0CDFBF48-5CD7-3C97-A083-A7E179C25654 <118 12 4 3> 122 0 0xffffff7f81942000 0xa8000 0xa8000 com.nvidia.web.GeForceWeb (10.3.1) B4761F6B-66C5-3512-BD13-2CCC7BCC1868 <121 118 101 100 12 7 5 4 3 1> 160 0 0xffffff7f81a46000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) 4329B052-6C8A-3900-8E83-744487AEDEF1 <4 1> 3 hours ago, MICKHAEL said: thats art. I like it Yeah on the covers it was quite pretty, didn't mind it there, but once it spread to the desktop and browser it was pretty ugly and hard to work with. Link to comment Share on other sites More sharing options...
Peke Posted April 19, 2018 Share Posted April 19, 2018 3 hours ago, tarasis said: Seems to be [21:36][rob@iMac:~]$ kextstat | grep nvidia 118 2 0xffffff7f80c1a000 0x679000 0x679000 com.nvidia.web.NVDAResmanWeb (10.3.1) 8E2AB3E3-4EE5-3F90-B6D8-54CEB8595A5F <110 101 100 12 7 5 4 3 1> 119 0 0xffffff7f815be000 0x1a7000 0x1a7000 com.nvidia.web.NVDAGP100HalWeb (10.3.1) 0CDFBF48-5CD7-3C97-A083-A7E179C25654 <118 12 4 3> 122 0 0xffffff7f81942000 0xa8000 0xa8000 com.nvidia.web.GeForceWeb (10.3.1) B4761F6B-66C5-3512-BD13-2CCC7BCC1868 <121 118 101 100 12 7 5 4 3 1> 160 0 0xffffff7f81a46000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) 4329B052-6C8A-3900-8E83-744487AEDEF1 <4 1> Yeah on the covers it was quite pretty, didn't mind it there, but once it spread to the desktop and browser it was pretty ugly and hard to work with. From one of your post I saw that you are not using the new kexts? Did you install latest Nvidiagraphicsfixup and lilu? Those are mine if you want to test. Lilu ver 1.2.3 & Nvidiablabla.. ver 1.2.6 Kexts.zip Link to comment Share on other sites More sharing options...
ergot Posted April 20, 2018 Share Posted April 20, 2018 (edited) Is that a correct Nvidia startup?? Mac-Pro:~ kobi$ kextstat | grep nvidia 102 0 0xffffff7f81866000 0x3000 0x3000 com.nvidia.NVDAStartupWeb (10.3.1) AD2D7E86-4977-3447-BC96-D3C6EA88EEA8 <12 4 3> 121 0 0xffffff7f83fb6000 0x3000 0x3000 com.apple.nvidia.NVDAStartup (10.3.0) 7F5D85C5-F712-3348-B5F0-77D6EF95E071 <12 4 3> 145 2 0xffffff7f80b90000 0x679000 0x679000 com.nvidia.web.NVDAResmanWeb (10.3.1) 8E2AB3E3-4EE5-3F90-B6D8-54CEB8595A5F <133 111 109 12 7 5 4 3 1> 146 0 0xffffff7f81966000 0x15e000 0x15e000 com.nvidia.web.NVDAGK100HalWeb (10.3.1) BC0C27F0-12AF-36CA-AC52-ACD84F718B30 <145 12 4 3> 147 0 0xffffff7f8171e000 0xa8000 0xa8000 com.nvidia.web.GeForceWeb (10.3.1) B4761F6B-66C5-3512-BD13-2CCC7BCC1868 <145 133 113 109 12 7 5 4 3 1> 161 0 0xffffff7f81822000 0x2000 0x2000 com.nvidia.CUDA (1.1.0) 4329B052-6C8A-3900-8E83-744487AEDEF1 <4 1> Why "com.apple.nvidia.NVDAStartup" is loading? is that supposed to be load when Nvidia Webdrivers are loaded? it docent matter , disable Apple NVDAStartup but my system crashing when using AE plugins such as Mocha and others, also crashing in general when using HW acceleration by the GPU... When using Apple drivers everything seems to work fine no crashing however no acceleration from GPU... Edited April 20, 2018 by ergot Link to comment Share on other sites More sharing options...
tarasis Posted April 20, 2018 Share Posted April 20, 2018 12 hours ago, Peke said: From one of your post I saw that you are not using the new kexts? Did you install latest Nvidiagraphicsfixup and lilu? Those are mine if you want to test. Lilu ver 1.2.3 & Nvidiablabla.. ver 1.2.6 Cheers, I had Lilu ver 1.2.3 there but had removed NvidiaGraphicsFixup as people were reporting it working well without it. I'll give 1.2.6 and 1.2.7 a try. Note since I rebooted, the problems hasn't cropped up again yet BUT I didn't try recreating the problem again. Link to comment Share on other sites More sharing options...
createthis Posted April 20, 2018 Share Posted April 20, 2018 Someone needs to update the OP. We're up to 387.10.10.10.30.106 but it's still listing 30.103. 1 Link to comment Share on other sites More sharing options...
createthis Posted April 20, 2018 Share Posted April 20, 2018 (edited) UPDATE: in 30.106 I still get system crashes in FCPX (forced reboot) *if* I have my 6700k's iGPU enabled in the BIOS. If I disable it in the BIOS, it seems the graphical render artifacts in FCPX are gone, the crashes are gone (at least in the first 10 minutes of testing), and the stutter when playing back 2.5k video is gone. This is great! This system appears to be usable again for me. Again, I'm running dual 1080 Ti cards in an SLI config. This is a huge improvement from what I was seeing in 30.103. Thanks, nvidia devs! UPDATE2: I am still seeing graphical artifacts in the timeline in FCPX. My playback indicator (vertical red line) shows up multiple times as it scrubs along the timeline. It's failing to erase itself. Also, highlighting a clip is unreliable. Part or none of the clip will be highlighted in yellow when I click on it. However, these are relatively minor issues and I can work around them. Edited April 20, 2018 by createthis Link to comment Share on other sites More sharing options...
himac59 Posted April 21, 2018 Share Posted April 21, 2018 On 19-4-2018 at 7:43 AM, ellaosx said: w/o NvidiaGraphicsFixup? yes w/o Link to comment Share on other sites More sharing options...
al6042 Posted April 21, 2018 Share Posted April 21, 2018 Is a multi-Monitor setup now possible without NvidiaGraphicsFixup, if you're using a newer SMBIOS then iMac14,2 and don't patch the APDP? Link to comment Share on other sites More sharing options...
arabesc Posted April 21, 2018 Share Posted April 21, 2018 On 19.04.2018 at 12:15 PM, Funky frank said: Make sure your Intel Graphics runs in connector-less mode. I've checked it, it's in connector-less mode. Link to comment Share on other sites More sharing options...
UltraLaser Posted April 22, 2018 Share Posted April 22, 2018 has anyone tried the 106? Link to comment Share on other sites More sharing options...
Recommended Posts