Search results

Waaaaait... hold up. @kingkongw24 Ignore my previous post. You've not copied the complete command. Please copy and paste the complete command.

Your error actually has nothing to do with nvidia-update, curl isn't working. Unfortunately, if you can't get curl to work then your system is likely in a pretty bad state. I'd suggest launching Disk Utility and running "First Aid" on your disk. Hopefully it's just a permissions issue...

I guess it's somewhat subjective, presumably the new drivers fix or improve something. However, based on user feedback, the general consensus is yes, they're bad. Hence why they've been added to the blacklist.

By any chance are you using a shell other than bash or zsh? If so, first launch bash (by simply typing bash and pressing enter), then paste the command again.

.160 and .161 have been blacklisted, thanks to Github user chazeon for the patch.

Thanks. Your Clover setup is quite a bit different than mine, of course it's hard to tell, because so is your hardware. However, the main thing that stood out to me was that "Inject NVidia" is presently false. Would you mind rolling back to .106 and enabling it? For testing purposes you don't...

Hmm, interesting. Would you two mind sharing your Clover configurations?

Not quite. We have already been provided with valid code signing certificates with kext signing permissions and can sign whatever we want. However, we're bound by Apple's developer agreement etc. so don't want to accidentally do anything that may get us in trouble. So as I've said, the kext...

Excellent, I've linked to your codeless kext here, so if I do end up trying that approach we can avoid duplication of work. The company I run (Glass Echidna Pty Ltd) has code signing permissions. I may be prepared to sign the kext. However, I can only do so if it's handled in a way that won't...

Ah, I certainly do like the sound of that a lot more than some of the alternative approaches. Nonetheless, it still sounds like a multi-step procedure and requires a fair bit of knowledge about what you're doing (which drivers will work etc.) However, I can't find the applet in post #11 you...

Nice! I actually really like the idea of approaching this issue from Clover. However, the solution may not be for everyone as you have to know what you're doing with Clover. Well, and use clover (this driver issue affects real Macs too). Another issue with a pure Clover approach is that what...

@bogdanw I did consider that but seems as new drivers are nVidia certified for an OS release, they should at the very least "work", although as we can see they may have performance issues. Where is it's possible a OS update might cause the system to be totally incompatible with old drivers. So...

@michelb76 Nice observation, I was just about to suggest keeping an eye on what hardware is involved. It's a bit of a juggling act with so many hardware setups but I'd like to keep nvidia-update's BLACKLIST in a state that works well for everyone. Or else I'm going to need to update the script...

Hmm, we're getting contradictory claims about 387.10.10.10.25.158. Some users are saying they're laggy, whilst others are saying they're fine. It's significantly easier to report failure (observation of an abnormality) than it is success (no observation of an abnormality). The former is...

@Nautipuss Actually, I've just pushed a new version. No need to disable SIP. Tested on my Late 2013 15" MBPR, everything works nicely. Somewhat to my surprise, kext signing is not broken, because I've only modified Info.plist (a text file) and not the kext binaries.

You'll need to disable SIP, but otherwise, yes. It's necessary to disable SIP because only the 387.10.10.10.25.156 kext will run on 10.13.3 without patching the macOS version requirement. Patching the kext is performed automatically, however once the kext it patched it's no longer signed. This...

For DVI to work the cable and the GPU will need to support Dual-link DVI: https://seriousseverity.wordpress.com/2013/10/10/monitor-connections-explained/ EDIT: Not sure if it'll actually reach 144Hz, 120Hz maybe?

@Guillou How have you installed drivers in the past, just from the nVidia website and "NVIDIA Driver Manager" updates? Or have you used other third-party tools like webdriver.sh? EDIT: Oh, and make sure you've got SIP disabled.

Unfortunately you'll need to get a new GPU that supports 144Hz. I believe HDMI 2.1 supports 144Hz at 1080P, but if your graphics card is old enough that it doesn't have DisplayPort then it almost certainly doesn't support HDMI 2.1.

@minahan your sudoer issue is unrelated to graphics cards. However, I happen to have just recently helped someone with a similar problem. Please refer to the following thread: https://www.tonymacx86.com/threads/unable-to-open-nvidia-driver-manager.245278/