Jump to content

Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]

fantomas

By fantomas,
in New Releases and Updates

 Share
670 posts in this topic

Recommended Posts

polyzargone
polyzargone
Posted
Posted

That's normal. From what I've observed, some betas was incompatible with webdrivers, mainly because very specific OS Build version numbers was present in NVDAStartup.kext, requiring edits to match the current installed build.

 

But recently, newest versions of webdrivers just needed to have 14E in NVDARequiredOS. In the meantime, recent betas and final version had overwritten the NVDAStartup.kext and replaced it by stock Apple's NVDAStartup.kext.

 

So manual edit of the kext didn't work anymore since even modified, the NVDAStartup.kext was still Apple's one, not it's webdrivers version. Hence, re-installing the webdrivers was necessary if not mandatory for Maxwell based cards owners.

 

I'll just patiently wait until there is proper Maxwell support.

 

I wouldn't bet on it… El Capitan shows no progress on that matter and Apple seems more interested in AMD than in NVIDIA.

 

But who knows… :rolleyes:

Link to comment
Share on other sites
joaodrp
joaodrp
Posted
Posted

Hi,

 

I'm on yosemite 10.10.4 (clover, asus z97i-plus, gtx 970, boot flags: nvda_drv=1, kext-dev-mode=1) after upgrading my web driver to build .03f01, my hackintosh reboots randomly on boot and eventually at one of the times it boots up successfully.

 

After enabling verbose flag on boot, before the reboot/boot I see several logs of "GeForceSensors: Waiting for accelerator to start..." and another "chipset error..."

 

w52r3rp.jpg

 

Does anyone have the same issue?

Link to comment
Share on other sites
brlock
brlock
Posted
Posted

A shout out for other people that might be in need.

 

I was having trouble using the HDMI port with  a Samsung 4k TV. I am using a Nvidia 970 with Web drivers.

 

Running the mac pixel clock pacher made the HDMI 2.0 port work normaly defaulting in 3840x2160@60Hz with scaling options. Thank you Floris497 for keeping the script updated.  The fix is confirmed working in 10.10.1 to 10.10.4

https://github.com/f...el-clock-patch/

 

 

Before the screen was defaulting to 7680 x 4050 @ 24Hz  and would accept 3840x2160@30Hz without scaling options.

 

It was not a problem of bandwidth since 7680 x 4050 @ 24Hz requires more than 3840x2160@60Hz does. But I did notice that none of the available resolutions would have a pixel clock above 297MHz. 4K@60Hz requires a pixel clock of 594MHz in this screen.

 

DVI was already working and DP is not tested.

  • Like 1
Link to comment
Share on other sites
Faradis
Faradis
Posted
Posted

Do i need to add open cl patch after installing Web driver my Graphics card is Msi GTX 560ti running 10.10.4 with clover

if i have to apply the open CL patch can any one give me that for clover on the fly patch pls some one inform me 

i am little confused about should i apply the patch or not  :(  :(

Link to comment
Share on other sites
xenophex
xenophex
Posted
Posted

Quick question, I setup my Asus X99 Deluxe as a MacPro6,1 and modified the distribution to allow me to install it.  I have a PNY 970GTX 4GB w/ 3 mini displayport outputs, mini-HDMI and a DVI. 

 

DVI seems to operate as primary on boot connected to a 2560x1440 monitor.

Mini Displayport works but the 2 between don't.  I haven't tried the HDMI yet.

 

I tried a iMac14,2 and MacPro5,1 profile but it had no effect.  Is there any other tricks to getting the ports to recognize?  I've got 2 Apple Cinema Displays I'd like to run.

 

I also notice the Web Driver preference pane doesn't seem to retain the Web Driver setting, but it appears to be using the drivers as the monitors are at full resolution and animations work.

 

Thanks,

Mark

 

[sOLVED] I had checked "Nvidia" in Clover.  I unchecked it and bang all the monitors came up.

Link to comment
Share on other sites
  • 2 weeks later...
Asgorath
Asgorath
Posted
Posted

I keep getting core graphic crashes.  iMessage and Safari both crash repeatedly on f02.  

Reverted to f01, rebuilt caches, back to normal.

 

Can you post your crash logs?  I updated and everything has been running fine for me.

Link to comment
Share on other sites
Asgorath
Asgorath
Posted
Posted

Same problem here, random crashes.

 

Messages:

 

Crashed Thread:        0  Dispatch queue: com.apple.main-thread
 
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000004f25d8
 
VM Regions Near 0x4f25d8:
--> 
    __TEXT                 000000010ed3b000-000000010ef72000 [ 2268K] r-x/rwx SM=COW  /Applications/Messages.app/Contents/MacOS/Messages
 
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib             0x00007fff8838cd12 dispatch_source_set_timer + 33
1   com.apple.AppKit               0x00007fff8e4701b5 ____NSHysteresisBlock_block_invoke160 + 252
2   com.apple.AppKit               0x00007fff8e431eb0 -[NSPersistentUIManager acquireDirtyState] + 348
3   com.apple.AppKit               0x00007fff8e430cb1 -[NSResponder(NSPersistentUISupport) invalidateRestorableState] + 58
4   com.apple.AppKit               0x00007fff8e588b09 -[NSSplitView _autosaveSubviewLayoutIfNecessary] + 225
5   com.apple.Foundation           0x00007fff8a40241b __NSFireDelayedPerform + 364
6   com.apple.CoreFoundation       0x00007fff8f0572e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
7   com.apple.CoreFoundation       0x00007fff8f056f73 __CFRunLoopDoTimer + 1059
8   com.apple.CoreFoundation       0x00007fff8f0ca53d __CFRunLoopDoTimers + 301
9   com.apple.CoreFoundation       0x00007fff8f012608 __CFRunLoopRun + 2024
10  com.apple.CoreFoundation       0x00007fff8f011bd8 CFRunLoopRunSpecific + 296
11  com.apple.HIToolbox           0x00007fff8da0456f RunCurrentEventLoopInMode + 235
12  com.apple.HIToolbox           0x00007fff8da042ea ReceiveNextEventCommon + 431
13  com.apple.HIToolbox           0x00007fff8da0412b _BlockUntilNextEventMatchingListInModeWithFilter + 71
14  com.apple.AppKit               0x00007fff8e4918ab _DPSNextEvent + 978
15  com.apple.AppKit               0x00007fff8e490e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
16  com.apple.AppKit               0x00007fff8e486af3 -[NSApplication run] + 594
17  com.apple.AppKit               0x00007fff8e403244 NSApplicationMain + 1832
18  com.apple.iChat               0x000000010ed3e9e9 0x10ed3b000 + 14825
19  libdyld.dylib                 0x00007fff8aaa85c9 start + 1
 
Safari:
 
Crashed Thread:        26
 
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000002e6928
 
VM Regions Near 0x2e6928:
--> 
    __TEXT                 00000001036c2000-00000001036c3000 [    4K] r-x/rwx SM=COW  /Applications/Safari.app/Contents/MacOS/Safari
 
...
 
Thread 26 Crashed:
0   libdispatch.dylib             0x00007fff91ad6af1 _dispatch_source_probe + 33
1   libdispatch.dylib             0x00007fff91ae53e3 _dispatch_queue_wakeup_with_qos_slow + 30
2   libdispatch.dylib             0x00007fff91adee63 dispatch_source_cancel + 54
3   com.apple.CoreFoundation       0x00007fff987c388e __CFRunLoopModeDeallocate + 238
4   com.apple.CoreFoundation       0x00007fff98708e8e CFRelease + 526
5   com.apple.CoreFoundation       0x00007fff98718b92 __CFBasicHashDrain + 498
6   com.apple.CoreFoundation       0x00007fff98708e8e CFRelease + 526
7   com.apple.CoreFoundation       0x00007fff987c31d2 __CFRunLoopDeallocate + 306
8   com.apple.CoreFoundation       0x00007fff98708e8e CFRelease + 526
9   com.apple.CoreFoundation       0x00007fff987c2cf4 __CFTSDFinalize + 100
10  libsystem_pthread.dylib       0x00007fff8ee4178a _pthread_tsd_cleanup + 182
11  libsystem_pthread.dylib       0x00007fff8ee41451 _pthread_exit + 117
12  libsystem_pthread.dylib       0x00007fff8ee406cd _pthread_wqthread + 879
13  libsystem_pthread.dylib       0x00007fff8ee3e40d start_wqthread + 13
 

 

So it's not crashing in the driver in either case.

Link to comment
Share on other sites
nekonoko
nekonoko
Posted
Posted

Also, what GPU are you using?  Looks like xenophex was using a 970?

 

I'm using a 680 myself, but am experiencing the same Safari crashes after the update. I switched over to OS X Default Driver in NVIDIA Driver Manager for now; crashes are gone.

Link to comment
Share on other sites
xenophex
xenophex
Posted
Posted

Also, what GPU are you using?  Looks like xenophex was using a 970?

Yeah its my PNY 970GTX 4GB.  I tried to figure out what was making iMessage crash.  Seemed to be when someone was typing and right as I got the message.

Safari was just random but matched your crash report.

Link to comment
Share on other sites
Asgorath
Asgorath
Posted
Posted

Yeah its my PNY 970GTX 4GB.  I tried to figure out what was making iMessage crash.  Seemed to be when someone was typing and right as I got the message.

Safari was just random but matched your crash report.

 

Any particular websites that would consistently crash?  Both Messages and Safari are working fine for me so far.

Link to comment
Share on other sites
J0hny
J0hny
Posted
Posted

Now save picture works fine Preview.app (driver: 346.02.02f02) (GT610)

 

 

But Safari crash repeatedly   :wallbash: iMessage also

So delete this driver, I have the same video card, and now I'm using official os x driver, and it's just fine. I think gt 610 video card is not so strong and official driver will be good enough, especially if you look at the benchmarks - there are not so many differences between the web and official driver.

  • Like 1
Link to comment
Share on other sites
lord_webi
lord_webi
Posted
Posted

new Nvidia Drivers (346.02.02f02) are buggy, keep or reinstall older beta driver (346.01.03b01) in 10.10.4 !

 

346.01.03f01 is also not recommended !

  • Like 2
Link to comment
Share on other sites
J0hny
J0hny
Posted
Posted

new Nvidia Drivers (346.02.02f02) are buggy, keep or reinstall older beta driver (346.01.03b01) in 10.10.4 !

 

346.01.03f01 is also not recommended !

I agree, even with 346.01.03f01 sometimes I had problems with sound delay on youtube.

  • Like 1
Link to comment
Share on other sites
horizoli
horizoli
Posted
Posted

Hi

 

So delete this driver, I have the same video card, and now I'm using official os x driver, and it's just fine. I think gt 610 video card is not so strong and official driver will be good enough, especially if you look at the benchmarks - there are not so many differences between the web and official driver.

 

@ImmortalSoulL

Try it, it works perfectly...:  :yes: (346.02.02f03)

oh God another release hope they fixed all the bugs ;)

 

Please Fantomas update, thanx

 

http://us.download.nvidia.com/Mac/Quadro_Certified/346.02.02f03/WebDriver-346.02.02f03.pkg

 

@Vampirexx thanks for sharing  :wink_anim:

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...