Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Frequently Asked Questions About NVIDIA PC (non-EFI) Graphics Cards

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Status
Not open for further replies.
Thanks Flowrider. I haven't updated to the latest drivers and security update yet.

I've been having these same problems for 12 months now with various nvidia drivers and OSX versions. I've swapped out the RAM, CPUs, GPU and still haven't managed to get a stable system. I just can't figure it out at all. It's killing me because it's my main workstation and I need the nvidia card for GPU rendering (Redshift/Octane).
 
vel0city said:
Thanks Flowrider. I haven't updated to the latest drivers and security update yet.

I've been having these same problems for 12 months now with various nvidia drivers and OSX versions. I've swapped out the RAM, CPUs, GPU and still haven't managed to get a stable system. I just can't figure it out at all. It's killing me because it's my main workstation and I need the nvidia card for GPU rendering (Redshift/Octane).
Click to expand...

Please post the full panic log, you are missing some crucial information (i.e. all the first lines).
 
Thanks Asgorath:

Anonymous UUID: 9639F676-E0A3-B222-77B7-2BDF9D4F1C05

Sun Dec 23 10:37:53 2018

*** Panic Report ***
panic(cpu 1 caller 0xffffff80162867e4): "thread_invoke: preemption_level 1, possible cause: blocking while holding a spinlock, or within interrupt context"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.71.13/osfmk/kern/sched_prim.c:2231
Backtrace (CPU 1), Frame : Return Address
0xffffff874b343720 : 0xffffff801626b1c6
0xffffff874b343770 : 0xffffff8016393a74
0xffffff874b3437b0 : 0xffffff8016385d44
0xffffff874b343820 : 0xffffff801621d1e0
0xffffff874b343840 : 0xffffff801626ac3c
0xffffff874b343970 : 0xffffff801626a9fc
0xffffff874b3439d0 : 0xffffff80162867e4
0xffffff874b343a50 : 0xffffff801628566f
0xffffff874b343aa0 : 0xffffff801627a52e
0xffffff874b343ae0 : 0xffffff80162b73ec
0xffffff874b343c10 : 0xffffff801624cc76
0xffffff874b343c40 : 0xffffff801624d863
0xffffff874b343c90 : 0xffffff8016270e52
0xffffff874b343cd0 : 0xffffff7f96b98945
0xffffff874b343d10 : 0xffffff7f96beff71
0xffffff874b343d30 : 0xffffff7f96ca84e6
0xffffff874b343d80 : 0xffffff7f96ced9d4
0xffffff874b343da0 : 0xffffff7f9758019f
0xffffff874b343e10 : 0xffffff7f96bf7164
0xffffff874b343ed0 : 0xffffff8016898e35
0xffffff874b343f30 : 0xffffff80168975a2
0xffffff874b343f70 : 0xffffff8016896bcc
0xffffff874b343fa0 : 0xffffff801621c557
Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000->0xffffff7f97209fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000
dependency: com.apple.iokit.IONDRVSupport(519.21)[8E0EE518-0D53-38C0-B308-2C6CD9EC5B7B]@0xffffff7f96b75000
dependency: com.apple.iokit.IOGraphicsFamily(519.21)[E5B53C5D-BF6E-3D72-9091-A80DFE5426C9]@0xffffff7f96b1f000
dependency: com.apple.AppleGraphicsDeviceControl(3.20.14)[D3CF5F89-2DA6-3F73-995D-F5DDE191E192]@0xffffff7f96b85000
com.nvidia.web.NVDAGP100HalWeb(10.3.3)[66B299E8-CBF2-398B-A290-781A4F8C589C]@0xffffff7f97438000->0xffffff7f975defff
dependency: com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
17G3025

Kernel version:
Darwin Kernel Version 17.7.0: Wed Oct 10 23:06:14 PDT 2018; root:xnu-4570.71.13~1/RELEASE_X86_64
Kernel UUID: 4C560F2C-3F3C-3423-B806-2C4D39D570A0
Kernel slide: 0x0000000016000000
Kernel text base: 0xffffff8016200000
__HIB text base: 0xffffff8016100000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 319479043185663
last loaded kext at 67585640450001: com.apple.driver.AppleUSBMergeNub 900.4.1 (addr 0xffffff7f99721000, size 12288)
last unloaded kext at 96418284956876: com.apple.driver.AppleUSBMergeNub 900.4.1 (addr 0xffffff7f99721000, size 12288)
loaded kexts:
com.nvidia.CUDA 1.1.0
com.nvidia.web.NVDAGP100HalWeb 10.3.3
com.nvidia.web.GeForceWeb 10.3.3
com.nvidia.web.NVDAResmanWeb 10.3.3
com.apple.filesystems.smbfs 3.2.3
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleTopCaseHIDEventDriver 135
com.apple.driver.AppleTyMCEDriver 1.0.3d2
com.apple.driver.AGPM 110.23.37
com.apple.filesystems.autofs 3.0
com.apple.AGDCPluginDisplayMetrics 3.20.0
com.apple.driver.AppleMikeyHIDDriver 131
com.apple.driver.AppleUpstreamUserClient 3.6.5
com.apple.driver.AppleHV 1
com.apple.driver.AppleMCCSControl 1.5.5
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleMikeyDriver 281.52
com.apple.driver.AppleHDA 281.52
com.apple.iokit.IOBluetoothSerialManager 6.0.7f11
com.apple.driver.pmtelemetry 1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleLPC 3.1
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleUSBDisplays 380
com.apple.filesystems.apfs 748.51.0
com.apple.filesystems.hfs.kext 407.50.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.driver.AppleFWOHCI 5.5.9
com.apple.driver.AirPort.Brcm4331 800.21.30
com.apple.driver.Intel82574LEthernet 2.7.2
com.apple.driver.AppleAHCIPort 329.50.2
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 6.1
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 6.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 220.50.1
com.apple.nke.applicationfirewall 183
com.apple.security.TMSafetyNet 8
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 220.50.1
com.apple.driver.AppleActuatorDriver 1614.1
com.apple.driver.AppleMultitouchDriver 1614.1
com.apple.driver.AppleInputDeviceSupport 1614.11
com.apple.driver.AppleHSBluetoothDriver 135
com.apple.driver.IOBluetoothHIDDriver 6.0.7f11
com.apple.kext.triggers 1.0
com.apple.iokit.IOAVBFamily 683.1
com.apple.plugin.IOgPTPPlugin 680.15
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.driver.AppleSSE 1.0
com.apple.driver.DspFuncLib 281.52
com.apple.kext.OSvKernDSPLib 526
com.apple.iokit.IOAcceleratorFamily2 378.26
com.apple.iokit.IOSurface 211.15
com.apple.iokit.IOSerialFamily 11
com.apple.driver.AppleSMBusController 1.0.18d1
com.apple.iokit.IONDRVSupport 519.21
com.apple.AppleGPUWrangler 3.20.0
com.apple.AppleGraphicsDeviceControl 3.20.14
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.driver.AppleHDAController 281.52
com.apple.iokit.IOGraphicsFamily 519.21
com.apple.iokit.IOHDAFamily 281.52
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IOFireWireIP 2.2.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.driver.AppleHIDKeyboard 205.1
com.apple.driver.usb.IOUSBHostHIDDevice 1.2
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.7f11
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.7f11
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.7f11
com.apple.iokit.IOBluetoothFamily 6.0.7f11
com.apple.iokit.IOAHCIBlockStorage 301.40.2
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.filesystems.hfs.encodings.kext 1
com.apple.iokit.IOFireWireFamily 4.7.2
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.corecapture 1.0.4
com.apple.driver.usb.AppleUSBXHCIPCI 1.2
com.apple.driver.usb.AppleUSBXHCI 1.2
com.apple.iokit.IOAHCIFamily 288
com.apple.driver.usb.AppleUSBEHCIPCI 1.2
com.apple.driver.usb.AppleUSBUHCIPCI 1.2
com.apple.driver.usb.AppleUSBUHCI 1.2
com.apple.driver.usb.AppleUSBEHCI 1.2
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 480.60.1
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 439.70.3
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.iokit.IOUSBMassStorageDriver 140.70.2
com.apple.iokit.IOSCSIBlockCommandsDevice 404.30.2
com.apple.iokit.IOSCSIArchitectureModelFamily 404.30.2
com.apple.iokit.IOStorageFamily 2.1
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.2
com.apple.driver.usb.AppleUSBCommon 1.0
com.apple.driver.AppleBusPowerController 1.0
com.apple.driver.AppleSEPManager 1.0.1
com.apple.driver.IOSlaveProcessor 1
com.apple.iokit.IOReportFamily 31
com.apple.iokit.IOTimeSyncFamily 680.15
com.apple.iokit.IONetworkingFamily 3.4
com.apple.driver.AppleACPIPlatform 6.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.Libm 1
com.apple.kec.corecrypto 1.0

EOF
 
Okay, so that's not a read error panic, which is usually an indication of a hardware problem. Might be worth posting about that on the GeForce forums, I think there's still a macOS forum over there?
 
Thanks for looking at the panic report Asgorath, appreciated. I did post on the GeForce forum but didn't get a reply. I've also contacted Nvidia directly, no reply.

Do you think that it is likely a software issue? Anything you can think of that I can disable/uninstall to test, please?
 
vel0city said:
Guys, I've asked all over the internet but have never resolved the ongoing Kernel Panics with my 4,1 flashed 5,1 with GTX1080ti. Any help with this would be really greatly appreciated.

Are the Mac Nvidia drivers known to cause kernel panics/freezes? Ever since I had the 1080 installed I get regular KPs that always look like this:

Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000->0xffffff7f97209fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000
dependency: com.apple.iokit.IONDRVSupport(519.21)[8E0EE518-0D53-38C0-B308-2C6CD9EC5B7B]@0xffffff7f96b75000
dependency: com.apple.iokit.IOGraphicsFamily(519.21)[E5B53C5D-BF6E-3D72-9091-A80DFE5426C9]@0xffffff7f96b1f000
dependency: com.apple.AppleGraphicsDeviceControl(3.20.14)[D3CF5F89-2DA6-3F73-995D-F5DDE191E192]@0xffffff7f96b85000
com.nvidia.web.NVDAGP100HalWeb(10.3.3)[66B299E8-CBF2-398B-A290-781A4F8C589C]@0xffffff7f97438000->0xffffff7f975defff
dependency: com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000


I'm totally at the end of my rope with this machine. Are the KPs just something that Mac users on Nvidia cards endure, or is there any way to solve the crashes? I'm on 10.13.6 (17G3025), 387.10.10.10.40.108, CUDA 410.130. I have one GPU installed, a GTX1080ti, and two Apple Cinema Displays connected to the card.

If anyone can suggest a fix I will happily paypal you the money for a decent bottle of wine or whatever your poison is. Thanks.
Click to expand...

Which 1080Ti? Reference card? How you powered it? Did you try force install other driver version? (.e.g. V378 series rather than the V387 driver)
 
h9826790 said:
Which 1080Ti? Reference card? How you powered it? Did you try force install other driver version? (.e.g. V378 series rather than the V387 driver)
Click to expand...

It's powered with six and eight pin connectors. The company that installed the card for me did it at the same time as flashing to 5,1 and upgrading processors and RAM. I don't know what you mean about force installing other drivers, sorry, is that something I should try? Thank you for your help.

From System Information:

NVIDIA GeForce GTX 1080 Ti:
Chipset Model: NVIDIA GeForce GTX 1080 Ti
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 11263 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x1b06
Revision ID: 0x00a1
ROM Revision: VBIOS 86.02.39.00.90
Metal: Supported, feature set macOS GPUFamily1 v3
 
vel0city said:
It's powered with six and eight pin connectors. The company that installed the card for me did it at the same time as flashing to 5,1 and upgrading processors and RAM. I don't know what you mean about force installing other drivers, sorry, is that something I should try? Thank you for your help.

From System Information:

NVIDIA GeForce GTX 1080 Ti:
Chipset Model: NVIDIA GeForce GTX 1080 Ti
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 11263 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x1b06
Revision ID: 0x00a1
ROM Revision: VBIOS 86.02.39.00.90
Metal: Supported, feature set macOS GPUFamily1 v3
Click to expand...

Is it possible for you to open the side panel and take a photo? (about the 1080Ti and how it is powered).

Or if you should not touch that (e.g. due to warranty from that company), then you better go back to the store.

In any case, you should contact them if they gave you a machine that has KP frequently.

I used a PNY XL8 1080Ti in my cMP before, never experience any KP due to the GPU or web driver.
 
Thanks h9826790, here's a couple of pics:

IMG_6457.JPG
IMG_6458.JPG

The company has been helpful but they're out of ideas as to why the KPs are happening now. It's frustrating for both of us.
 
vel0city said:
Thanks h9826790, here's a couple of pics:

View attachment 812380 View attachment 812381

The company has been helpful but they're out of ideas as to why the KPs are happening now. It's frustrating for both of us.
Click to expand...

It looks like a 6+8 pin card, and the 8pin is directly connected to a single mini 6pin only.

In general, a cMP user should not do that.

If you run Furmark now, it may shut down your cMP.

If they are running out of idea, they should at least try another GPU and see if the same crash still happen.
 
I don't have Windows installed on this machine, so I can't run Furmark unfortunately.

I did try Valley which ran fine, but I guess is out of date now.

Is there any way of confirming that the card is powered incorrectly please? If I go back to the company and explain what you said, would they be able to put it right?
 
vel0city said:
I don't have Windows installed on this machine, so I can't run Furmark unfortunately.

I did try Valley which ran fine, but I guess is out of date now.

Is there any way of confirming that the card is powered incorrectly please? If I go back to the company and explain what you said, would they be able to put it right?
Click to expand...

In macOS, Furmark is hide inside GPUTest.

https://www.geeks3d.com/gputest/

Furmark WX7100.jpg
 
vel0city said:
Thanks Flowrider. I haven't updated to the latest drivers and security update yet.
Click to expand...
vel0city said:
I've been having these same problems for 12 months now with various nvidia drivers and OSX versions. I've swapped out the RAM, CPUs, GPU and still haven't managed to get a stable system. I just can't figure it out at all. It's killing me because it's my main workstation and I need the nvidia card for GPU rendering (Redshift/Octane).
Click to expand...
The software you need to have is HardwareMonitor to find Power supply problems for Graphic card ask h9826790 for details he is an expert and helped me out.

If the power problems are out of the questions and You have Driver Problems try to go backwards with the driver version.
1st You need to disable SIP.
Afterwards you can install older drivers with an script provided on the web page from post #189.

You open terminal and insert some lines of code and it downloads older Nvidia drivers and changes the certificates so that they can be used with your current MacOS Build.
[doublepost=1545600929][/doublepost]
Speedstar said:
Again trouble with NVIDIA WebDriver because of Beta or new update, still want to use CUDA, go back SIP off and create your own Nvidia Development driver release for your current macOS build number see that post for details:

https://forums.macrumors.com/thread...graphics-cards.1440150/page-193#post-26798269
Click to expand...

With This Workaround I have MultiGPU 3x6PIN Power on 2 Graphic cards stable running on Sierra. On high Sierra I always had log In issue with WebDriver on Kepler and Maxwell nVidia Cards running them together or Maxwell alone.

PS: I always try Octane and Redshift Demos on each update ...
 
Last edited:
Asgorath said:
I guess you haven't actually been reading my posts, especially for the last few years, or you just have me confused with someone else. If you check the FAQ, you'll see that I do not recommend anyone buy an NVIDIA GPU for macOS at this point, at least until the driver quality improves and releases happen in a timely manner.

The thing I continue to object to is people like you posting your opinions or theories as if they are fact. You (and I) do not know why NVIDIA hasn't released a driver for Mojave, or why Apple hasn't enabled eGPU support for any NVIDIA GPU. I still maintain that Metal 2 has absolutely nothing to do with eGPU support, but we can agree to disagree. You are welcome to your opinion of course. Apple could've allowed NVIDIA GPUs to work with eGPU for High Sierra, before the Mojave debacle, but they chose not to. Could this be they were unhappy with NVIDIA's driver quality? Absolutely. However, they could've also enabled it for the cards that are supported by the stock drivers, even if they were not happy with Maxwell/Pascal.

No matter what, we are all just guessing as to what's going on between Apple and NVIDIA. I'd just prefer if you stopped posting your theories as fact, especially in my FAQ thread.
Click to expand...



ok here history lesson for us (maybe another thesis or theory)
Why exactly does Apple use AMD graphic cards instead of NVIDIA?
https://www.quora.com/Why-exactly-does-Apple-use-AMD-graphic-cards-instead-of-NVIDIA
[doublepost=1545606218][/doublepost]
vel0city said:
Guys, I've asked all over the internet but have never resolved the ongoing Kernel Panics with my 4,1 flashed 5,1 with GTX1080ti. Any help with this would be really greatly appreciated.

Are the Mac Nvidia drivers known to cause kernel panics/freezes? Ever since I had the 1080 installed I get regular KPs that always look like this:

Kernel Extensions in backtrace:
com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000->0xffffff7f97209fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000
dependency: com.apple.iokit.IONDRVSupport(519.21)[8E0EE518-0D53-38C0-B308-2C6CD9EC5B7B]@0xffffff7f96b75000
dependency: com.apple.iokit.IOGraphicsFamily(519.21)[E5B53C5D-BF6E-3D72-9091-A80DFE5426C9]@0xffffff7f96b1f000
dependency: com.apple.AppleGraphicsDeviceControl(3.20.14)[D3CF5F89-2DA6-3F73-995D-F5DDE191E192]@0xffffff7f96b85000
com.nvidia.web.NVDAGP100HalWeb(10.3.3)[66B299E8-CBF2-398B-A290-781A4F8C589C]@0xffffff7f97438000->0xffffff7f975defff
dependency: com.nvidia.web.NVDAResmanWeb(10.3.3)[92230D7F-69C4-34B2-9B37-2BA3E8131CE1]@0xffffff7f96b91000
dependency: com.apple.iokit.IOPCIFamily(2.9)[D02EA6D7-7A0E-3F9D-B179-75AC2228E449]@0xffffff7f96a94000


I'm totally at the end of my rope with this machine. Are the KPs just something that Mac users on Nvidia cards endure, or is there any way to solve the crashes? I'm on 10.13.6 (17G3025), 387.10.10.10.40.108, CUDA 410.130. I have one GPU installed, a GTX1080ti, and two Apple Cinema Displays connected to the card.

If anyone can suggest a fix I will happily paypal you the money for a decent bottle of wine or whatever your poison is. Thanks.
Click to expand...

You wrote You do not use Windows so You did not accidentally run Firmware Update for 1080 Ti with Displayport specifications updated which has conflict with MacVidia Efi right ?
 
Last edited:
personally https://vulgo.github.io/nvidia-drivers/ seems for me to be easier because of copy paste, and you can choose VARIOUS versions from website.I tried with this method over 15 drivers for Multi-GPU usage on (high)Sierra.

Benjamin Dobells script makes last driver usable after update but I am not sure..._(o..O)_

with vulgo you get pkg-file you can use overtime without a script if SIP is deactivated, maybe Benjamin's script
works without SIP disabled.

PS: only Kext signing has to be turned of with vulgo script...
 
SIP need to be disabled and keep disabled if use Benjamin's script.

And it will only automatically install the latest version that on the white list. Not necessary the best version to fix some abnormal issues.

If suspect Nvidia web driver issue in High Sierra with the associated V387 drive. I will suggest use Benjamin’s script to force install the latest V378 driver. That often can fix some annoying small issue. However, with little bit performance penalty. When I use my 1080Ti, I can tell that the desktop is smoother with the V387 driver (3840x1080 HiDPI @144Hz).
 
Last edited:
Thanks very much both of your for your suggestions, I have to do Christmas family stuff now but will follow up asap. Hope you both have a great Christmas.
 
People, just pop in Radeon - no drivers to install, no web drivers and no need for boot scripts - don't torture yourselves it is not even funny
 
  • Like
Reactions: rafarataneneces
  • Like
Reactions: vel0city and h9826790
Anybody knows why (since Mac computers have Nvidia GPUs) Apple doesn’t allow their own customers to upgrade to Mojave?

With Sierra I remember it took 6 months or more to get drivers m.
 
rafarataneneces said:
Anybody knows why (since Mac computers have Nvidia GPUs) Apple doesn’t allow their own customers to upgrade to Mojave?

With Sierra I remember it took 6 months or more to get drivers m.
Click to expand...
Well, you could upgrade to Mojave, e.g. if you got an MBP 15“ 2013. But no Webdrivers in that case, therefore no CUDA.

And not to my knowledge. A number of theories is out there as to why there is no driver - some blame Apple, some blame nVidia - as well as some contradictory forum posts (some claiming Apple won‘t approve, others Apple is working with nVidia), but no official information seems to exists.
For now, no drivers, no information explaining why.
 
Last edited:
vel0city said:
Thank you for the suggestion. On your original post you said "On the PowerLink I replaced an 8-pin with a 6-pin-connector, and I connected the normal Mac Pro Mini-6-pin cables to the PowerLink" - does this mean that you modified the Powerlink adaptor?
Click to expand...

The PowerLink has two 8 pin connectors factory-installed, replace one 8 pin with the enclosed 6 pin connector (marked in red, pic 1). Than just connect the normal 6 pin to 6 pin cables to the PowerLink (pic 2):

IMG_1514.jpg IMG_1542.jpg
 
  • Like
Reactions: Reindeer_Games and vel0city
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back