Recently Browsing 0 members
No registered users viewing this page.
Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty) New!
Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr) Pascal support!!!
Nvidia Web Driver - 3188.8.131.52f01 --> build 16E195 (thanks to Lanc)
Nvidia Web Driver - 3184.108.40.206f01 --> build 16D32 (thanks to shatterhenner)
Nvidia Web Driver - 3220.127.116.11f02 --> build 16C68 (see this post)
Nvidia Web Driver - 318.104.22.168f01 --> build 16C67 (see this post)
Nvidia Web Driver - 322.214.171.124b06 --> build 16C60b/16C63a (see this post)
Nvidia Web Driver - 3126.96.36.199f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
Nvidia Web Driver - 3188.8.131.52f01 --> build 16B2555 (thanks to Moviemakergr)
Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS High Sierra.
Nvidia Web Driver - 3184.108.40.206.40.108 --> build 17G3025 (check here) New!
Nvidia Web Driver - 3220.127.116.11.15.108 --> build 17G2307 (thanks to marcozardi)
Nvidia Web Driver - 318.104.22.168.40.105 --> build 17G65 (thanks to sl0wtarget)
Nvidia Web Driver - 322.214.171.124.35.106 --> build 17F77 (check here)
Nvidia Web Driver - 3126.96.36.199.30.107 --> build 17E202 (check here)
Nvidia Web Driver - 3188.8.131.52.30.106 --> build 17E199 (thanks to BreBo)
Nvidia Web Driver - 3184.108.40.206.30.103 --> build 17E199 (thanks to ricoc90)
Nvidia Web Driver - 3220.127.116.11.25.161 --> build 17D102 (thanks to Cyberdevs)
Nvidia Web Driver - 318.104.22.168.25.160 --> build 17D2102 (thanks to Cyberdevs)
Nvidia Web Driver - 322.214.171.124.25.159 --> build 17D2012 (thanks to cyberdevs)
Nvidia Web Driver - 3126.96.36.199.25.158 --> build 17D102 (thanks to cyberdevs)
Nvidia Web Driver - 3188.8.131.52.25.157 --> build 17D2047 (thanks to cyberdevs)
Nvidia Web Driver - 3184.108.40.206.25.156 --> build 17D47 (thanks to darthsian)
Nvidia Web Driver - 3220.127.116.11.25.106 --> build 17C2205 (thanks to KGP-X99)
Nvidia Web Driver - 318.104.22.168.25.105 --> build 17C2120 (see this post)
Nvidia Web Driver - 322.214.171.124.25.104 --> build 17C205 (thanks to ReddestDream)
Nvidia Web Driver - 3126.96.36.199.25.103 --> build 17C89 (thanks to Il Francy MacPc)
Nvidia Web Driver - 3188.8.131.52.25.102 --> build 17C88 (thanks to piiggggg)
Nvidia Web Driver - 3184.108.40.206.20.109 --> build 17B1003 (see this post)
Nvidia Web Driver - 3220.127.116.11.20.108 --> build 17B1002 (thanks to BreBo)
Nvidia Web Driver -318.104.22.168.20.107 --> build 17B48 (thanks to piiggggg)
Nvidia Web Driver - 322.214.171.124.15.121 --> build 17A405 (thanks to Asgorath)
Nvidia Web Driver - 3126.96.36.199.15.120 --> build 17A405 (thanks to phi777)
Nvidia Web Driver - 3188.8.131.52.15.117 --> build 17A405 (thanks to phi777)
Nvidia Web Driver - 3184.108.40.206.15.114 --> build 17A365 (thanks to Asgorath).
Hi, I have been trying to follow @RehabMan 's guide to disable my dGPU ( https://www.tonymacx86.com/threads/guide-disabling-discrete-graphics-in-dual-gpu-laptops.163772/ ) for two days now, but haven't found a way to disable my 1080 Ti on my desktop Clover hack.
I have a dual-boot (Win/Mac) machine on a Z370 Aorus 7. Since there's no nvidia drivers for Mojave atm, I want to stick with the iGPU under Mac, but still use the 1080 Ti under Win.
The hack boots just fine when I remove the 1080 Ti, if it's plugged in via PCIe I get a kernel panic.
Please find attached my ACPI folder, my clover config.plist and the kernel panic details.
Might there even be a less hacky way than patching these ACPI files? I appreciate any kind of support! Thanks!
So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.
With that being said, I'll just move on to the actual tutorial.
New (probably better) method.
Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
Yeah, that's it.
In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread. It worked perfectly fine for me though and I didn't need to change anything else.
A simple Lilu plugin
Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
More info can be found in this post here.
In case you wanna try alternative medicine ...
The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
For ATI GPUs (curtesy of @Cyberdevs' post here).
The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)
Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.
Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well.
nvram cleanup kextcache & prelinked kernel rebuild reboot More info on that here.
For NVIDIA GPUs
This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
For MSi motherboads (check out my motherboard details in the signature)
Set your BIOS to use PEG (dedicated GPU) so you can boot.
Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.
The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
For Gigabyte motherboards
Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
DVMT Pre-Allocation -> default 64M.
DVMT Total Gfx Mem -> default 256M Save Reboot
You should do this with the cable connected to the dedicated GPU.
You will also need to patch the iGPU from Clover config.
1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
Thanks to @gjw for the tip.
*Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.