Jump to content
fantomas1

Nvidia Web Driver updates for macOS Sierra (UPDATE December 7, 2018)

1,054 posts in this topic

Recommended Posts

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

config.plist.zip

Share this post


Link to post
Share on other sites
Advertisement

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Share this post


Link to post
Share on other sites

 

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

 

Can you post your Clover config because it seems to me you got some nvram issues thats not related to web drivers

Share this post


Link to post
Share on other sites

Can you post your Clover config because it seems to me you got some nvram issues thats not related to web drivers

 

Here is all my clover, i only deleted the sn-bsn-smuuid

 

this is my situation : 1 ssd with el capitan + sierra

CLOVER.zip

Share this post


Link to post
Share on other sites

 

 

$ nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

Why don't you just add required parameter to boot arguments ? BTW attaching my config without smb

 

with your config i have the same result :

$ sudo nvram nvda_drv
nvram: Error getting variable - 'nvda_drv': (iokit/common) data was not found$ sudo nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found$ sudo csrutil status
System Integrity Protection status: disabled.

$ sudo nvram -p
bootercfg (%00
prev-lang:kbd it:0
efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>721EA2C3-D885-4B9D-96CB-ACF8B3B93760</string></dict></dict></dict></array>
security-mode none
EmuVariableUefiPresent Yes
fmm-computer-name iMac
efi-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%04%00%00%00%f0;Q%09%00%00%00%00x%b0%94%04%00%00%00%00%c3%a2%1er%85%d8%9dK%96%cb%ac%f8%b3%b97`%02%02%7f%ff%04%00
csr-active-config g%00%00%00

 

I just posted config in order to demonstrate how argument should be added. BTW I don't use any efi driver beside of aptiofix. For example "EmuVariableUefi" I don't know if it's a causing that ? You should follow what Pavo recommends.

Share this post


Link to post
Share on other sites

Here is all my clover, i only deleted the sn-bsn-smuuid

 

this is my situation : 1 ssd with el capitan + sierra

Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this:

kA23MIs.png

You should remove the following and test:

CsmVideoDxe-64.efi

EmuVariableUefi-64.efi

DataHubDxe-64.efi

OsxAptioFix2Drv-64.efi

VBoxHfs-64.efi

Share this post


Link to post
Share on other sites

Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this:

kA23MIs.png

You should remove the following and test:

CsmVideoDxe-64.efi

EmuVariableUefi-64.efi

DataHubDxe-64.efi

OsxAptioFix2Drv-64.efi

VBoxHfs-64.efi

He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader.

Share this post


Link to post
Share on other sites

Ok seems like you thought you was using the correct efi files, because you only had a few refi drivers in drivers32UEFI but in your drivers64UEFI you have this:

 

You should remove the following and test:

CsmVideoDxe-64.efi

EmuVariableUefi-64.efi

DataHubDxe-64.efi

OsxAptioFix2Drv-64.efi

VBoxHfs-64.efi

 

 

He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader.

 

@Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with :

 

- VBoxHfs-64.efi

- PartitionDxe-64.efi

- OsxFatBinaryDrv-64.efi

- OsxAptioFixDrv-64.efi

- FSInject-64.efi

 

But still remaining the nvram prob.

I think isn't a clover problem...

 

@Doublepranks i run an Asus Z97i (Mini Itx)

Share this post


Link to post
Share on other sites

He should never remove OsxAptionFix2Drv running non gigabyte motherboard it will entirely break the bootloader.

What's that ? Im using "OsxAptioFixDrv-64.efi" not "2" and it's pretty much not breaking anything (MSI-Z97).

Share this post


Link to post
Share on other sites

What's that ? Im using "OsxAptioFixDrv-64.efi" not "2" and it's pretty much not breaking anything (MSI-Z97).

 

You can either use one or the other just the matter you have at least one of them. V2 is a simplified version of the first one.

It has to do with Aptio Bioses support for Clover, be my guest try and remove this, you'll be stuck at boot.

Share this post


Link to post
Share on other sites

@Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with :

 

- VBoxHfs-64.efi

- PartitionDxe-64.efi

- OsxFatBinaryDrv-64.efi

- OsxAptioFixDrv-64.efi

- FSInject-64.efi

 

But still remaining the nvram prob.

I think isn't a clover problem...

 

@Doublepranks i run an Asus Z97i (Mini Itx)

Try disabling EmuVariableUEFI - don't think you need it with most EFI boards...

Share this post


Link to post
Share on other sites

@Pavo : without DataHubDxe-64.efi i can't see any 'mac' at boot, only windows. I tried with :

 

- VBoxHfs-64.efi

- PartitionDxe-64.efi

- OsxFatBinaryDrv-64.efi

- OsxAptioFixDrv-64.efi

- FSInject-64.efi

 

But still remaining the nvram prob.

I think isn't a clover problem...

 

@Doublepranks i run an Asus Z97i (Mini Itx)

Try using PartitionDxe-64.efi instead of DataHubDxe-64.efi

Share this post


Link to post
Share on other sites

That's weird... I am using driver 367.10.10.05b01 (the latest, and the same driver released for PB3) on PB4 (16A286a) with no issue... I wonder why you guys are having issues and are seeing new drivers...

Public Beta build (mine) is 16A284a, I think 16A286a is the Developer Preview build. Using the "DP4 & PB3" drivers work for me, the "DP5 & PB4" driver doesn't.

Share this post


Link to post
Share on other sites

How curious! I'm definitely running public beta, 16A286a, but it wouldn't be too surprising if Apple released different revisions (maybe different revisions for different SMBIOS?).

 

post-644221-0-05576500-1471235802_thumb.jpg

 

I just downloaded both versions of the driver from the front page, unpacked them and:

claes2:~ claes$ diff -r /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a
claes2:~ claes$ diff /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a
Common subdirectories: /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f/1.5-81-367.10.10.05b01-NVWebDrivers and /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a/1.5-81-367.10.10.05b01-NVWebDrivers
Common subdirectories: /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f/NVPrefPane and /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a/NVPrefPane
claes2:~ claes$ diff -qr /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A270f /Users/claes/Downloads/WebDriver-367.10.10.05b01.16A286a
claes2:~ claes$

The difference, if one exists (diff says there is none), between the driver revisions shouldn't matter as they're both prepared for "16A" in general according to NVDAStartupWeb.kext (both have same GetInfoString and ShortVersion, too):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>BuildMachineOSBuild</key>
	<string>11A511</string>
	<key>CFBundleDevelopmentRegion</key>
	<string>English</string>
	<key>CFBundleExecutable</key>
	<string>NVDAStartupWeb</string>
	<key>CFBundleGetInfoString</key>
	<string>NVDAStartupWeb 10.13.59 (367.10.10.05b01)</string>
	<key>CFBundleIdentifier</key>
	<string>com.nvidia.NVDAStartupWeb</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>NVDAStartupWeb</string>
	<key>CFBundlePackageType</key>
	<string>KEXT</string>
	<key>CFBundleShortVersionString</key>
	<string>10.13.59</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>10.1.3</string>
	<key>IOKitPersonalities</key>
	<dict>
		<key>NVDAStartup</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.nvidia.NVDAStartupWeb</string>
			<key>IOClass</key>
			<string>NVDAStartupWeb</string>
			<key>IOMatchCategory</key>
			<string>IOFramebuffer</string>
			<key>IOPCIClassMatch</key>
			<string>0x03000000&0xff000000</string>
			<key>IOPCIMatch</key>
			<string>0x000010de&0x0000ffff</string>
			<key>IOProbeScore</key>
			<integer>200000</integer>
			<key>IOProviderClass</key>
			<string>IOPCIDevice</string>
			<key>NVDARequiredOS</key>
			<string>16A</string>
			<key>NVDAType</key>
			<string>Web</string>
		</dict>
	</dict>
	<key>OSBundleLibraries</key>
	<dict>
		<key>com.apple.iokit.IOPCIFamily</key>
		<string>1.0b1</string>
		<key>com.apple.kpi.iokit</key>
		<string>7.0</string>
		<key>com.apple.kpi.libkern</key>
		<string>8.0d0</string>
	</dict>
	<key>OSBundleRequired</key>
	<string>Safe Boot</string>
</dict>
</plist>

Wonder what could've broke for so many of you between the two revisions...

Share this post


Link to post
Share on other sites

How curious! I'm definitely running public beta, 

BOTH 16A284a and 16A284a are BETAS!

 

To Be CLEAR:

 

160284A is Public Beta 4

160286A is Developer Preview 5.

 

For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers 

Share this post


Link to post
Share on other sites

BOTH 16A284a and 16A284a are BETAS!

 

To Be CLEAR:

 

160284A is Public Beta 4

160286A is Developer Preview 5.

 

For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers 

 

I'm not a developer, I'm running a public beta :

 

Beta 10.12 (16A286a)

Share this post


Link to post
Share on other sites

I'm not a developer, I'm running a public beta :

 

Beta 10.12 (16A286a)

Are you running into any glitch aside from the ones you've sorted out?

Share this post


Link to post
Share on other sites

Interesting thing: my secondary monitor got screwed up colors after the 10.12 update. Worked fine in 10.11, works fine in W10… Tried a different cable, different port from the graphics card… Other monitor works just fine (in both ports and with both cables). Weeeeirdest thing. Basically, blues are yellows, yellows are blues, and reds are blues too… It's like my red channel got screwed up! :X SOO WEIRD! I tried checking the accessibility option to invert colors, but it's not it: whites and blacks are not inverted. I also tried switching to a different color profile… No help!

 

Any idea? Anybody running into similar issues?

 

PS: When booting with nv_disable=1 (aka no Nvidia driver), colors are perfectly fine! ¯\_(ツ)_/¯

 

IMG_1058.jpg

Share this post


Link to post
Share on other sites

BOTH 16A284a and 16A284a are BETAS!

 

To Be CLEAR:

 

160284A is Public Beta 4

160286A is Developer Preview 5.

 

For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers 

 

Source? As you can see from my screenshot, Mac App Store says I've downloaded the public beta.

 

I am aware of there being a difference between the developer and public betas, but my post was more concerned with the fact that some PB4 users are having issues with PB4/DP5* drivers that they weren't having with PB3, while it appears that the drivers are identical between PB3/DP4 and PB4/DP5 (well, at least the drivers linked to by the OP). It would not seem related to the OS as these cards didn't work without the drivers in any case, which makes me curious as to where these issues are occurring (in non-NVRAM cases where a user's card was working in PB3/DP4, at least).

 

*I am also aware that these are likely different revisions, just want to connote that the nvidia driver release is the same for both the developer and public betas that were released together. :)

Share this post


Link to post
Share on other sites

BOTH 16A284a and 16A284a are BETAS!

 

To Be CLEAR:

 

160284A is Public Beta 4

160286A is Developer Preview 5.

 

For those of us with GTX 750 Ti Cards it seems that the latest drivers will load for the Developer Preview but there are a lot of issues, They will not load however on The Public Beta and on reboot default or Mac OSX drivers 

 

I am with 750ti and the default is always web drivers, i had problem with glitches and it was fixed by enabling reduce transparency under system pref->accessibility 

I can watch youtube / MKV etc. but not working with editing SW like resolve and others that using CUDA because CUDA still not working in 10.12

Share this post


Link to post
Share on other sites

Nvidia Web Driver 367.10.10.05b01 has been updated to support the last macOS Sierra beta 6  and Public Beta 5 (16A294a)

 

Check the first page, #1.

 

Regards

Any luck with Pascal support?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
      I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
       
      Hardware
      Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
      Chipset Intel 7 series, no patches needed
      Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
      LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
      Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
      SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
      USB3.0 works natively if not disabled in DSDT
      PS2 keyboard and touchpad works with VoodooPS2.
      WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
      LCD Screen 1366x768
      BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
      For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
       
      WiFi
      It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
      I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
      As well a patch for channels.
      I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
       
      VideoCards
      In Bios we can set Optimus = Enable/Disable
      If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
      If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
      But here there is contradiction with WiFi with required Board-ID from MacBookAir.
      So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
      Set BoardID like iMac13,2 to make Nvidia working.
      Patch BoardID in Brcm4360 to make WiFi working.
      Now I have
      Inject->
      ->Intel=YES
      ->Nvidia=YES
      and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
      For Intel graphics there is a patch against 8 apples at start.
       
      Brightness
      No special kexts.
      The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here  #72 
       
      DSDT and SSDT
      This is very long story and finally I have working sleep in both cases Intel or Nvidia.
       
      Sensors
      I use my HWSensors3 with FakeSMC 3.5.0.
      I got monitoring:
      CPU temperature
      GPU temperature
      GPU main frequency
      GPU shader frequency
      Battery state % full, time to charged or time to empty.
      Battery voltage dinamically.
      Battery amperage dynamically. I can see it changes on heavy games.
      HDD temperature.

       
      Audio
      I like VoodooHDA and have no problems with it.
      The sound is clear, loud, and switchable between internal speaker and headphone.
      Mic is working.
       
      Bluetooth
      Just tested with BTFirmwareUpdate.kext and it works. I not needed it so switched off by wireless switch at right side.
       
      Keyboard, Touchpad and Touchstick
      Post #14
       
      My config, ACPI files and kexts are in attachment.
      05.12.2017
      EFI.7z
       
      EDITED:
      Better DSDT in the post #6.
      Sleep working even when AC inserted.
       
      EDITED 06.12.2018
      Now I have HighSierra and this is my EFI folder
       

       
       
      Welcome to discussion!
      EFI-E6430.7z
    • By gengik84
      First beta is out... build 18D21c
    • By fantomas1
      macOS Mojave 10.14.3 beta (18D21c)
    • By fusion71au
      Clover r4799 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4799 for VMware.zip". Mount Clover-v2.4k-4799-X64 by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fantomas1
      Hi InsanelyMacaliens    
       
      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS High Sierra.
       
      10.13.6
      Nvidia Web Driver - 387.10.10.10.40.113 --> build 17G4015 (thanks to flowrider)  New!
      Nvidia Web Driver - 387.10.10.10.40.108 --> build 17G3025 (check here)
      Nvidia Web Driver - 387.10.10.15.15.108 --> build 17G2307 (thanks to marcozardi)
      Nvidia Web Driver - 387.10.10.10.40.105 --> build 17G65 (thanks to sl0wtarget)
       
      10.13.5
      Nvidia Web Driver - 387.10.10.10.35.106 --> build 17F77 (check here)
       
      10.13.4
      Nvidia Web Driver - 387.10.10.10.30.107 --> build 17E202 (check here)
      Nvidia Web Driver - 387.10.10.10.30.106 --> build 17E199 (thanks to BreBo)
      Nvidia Web Driver - 387.10.10.10.30.103 --> build 17E199 (thanks to ricoc90)
       
       
      10.13.3
      Nvidia Web Driver - 387.10.10.10.25.161 --> build 17D102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.160 --> build 17D2102 (thanks to Cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.159 --> build 17D2012 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.158 --> build 17D102 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.157 --> build 17D2047 (thanks to cyberdevs)
      Nvidia Web Driver - 387.10.10.10.25.156 --> build 17D47 (thanks to darthsian) 
       
       
      10.13.2
      Nvidia Web Driver - 378.10.10.10.25.106 --> build 17C2205 (thanks to KGP-X99)
      Nvidia Web Driver - 378.10.10.10.25.105 --> build 17C2120 (see this post)
      Nvidia Web Driver - 378.10.10.10.25.104 --> build 17C205 (thanks to ReddestDream)
      Nvidia Web Driver - 378.10.10.10.25.103 --> build 17C89 (thanks to Il Francy MacPc) 
      Nvidia Web Driver - 378.10.10.10.25.102 --> build 17C88 (thanks to piiggggg)
       
       
      10.13.1
      Nvidia Web Driver - 378.10.10.10.20.109 --> build 17B1003 (see this post)
      Nvidia Web Driver - 378.10.10.10.20.108 --> build 17B1002 (thanks to BreBo)
      Nvidia Web Driver -378.10.10.10.20.107 --> build 17B48 (thanks to piiggggg) 
       
       
      10.13.0
      Nvidia Web Driver - 378.10.10.10.15.121 --> build 17A405 (thanks to Asgorath)
      Nvidia Web Driver - 378.10.10.10.15.120 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.117 --> build 17A405 (thanks to phi777)
      Nvidia Web Driver - 378.10.10.10.15.114 --> build 17A365 (thanks to Asgorath).
×