- Joined
- Jul 24, 2015
- Messages
- 2,191
- Motherboard
- MSI H81i
- CPU
- i5-4570
- Graphics
- RX 580
Clover kext patch for NVIDIA Web Drivers
This patch disables the OS version check present in NVIDIA's web drivers
Name:
How to Add
Credits: @bogdanw @Pavo
FakePCIID audio fix: @toleda @RehabMan
Notes
This patch disables the OS version check present in NVIDIA's web drivers
- Permits rolling back drivers
- Persistent after updates (no need to repatch)
- Accelerated graphics on beta/early release macOS
Name:
Find:NVDAStartupWeb
Replace:4e56444152657175697265644f5300
Comment:000000000000000000000000000000
Disable NVDARequiredOS
How to Add
- Web Driver Manager
- Clover Configurator
- Property list editor (Xcode, PlistPro etc)
- Manual XML edit (TextMate, TextWrangler etc)
- NVIDIA repackager
- Removes installation checks from NVIDIA installer packages, drop a package onto its icon to activate
- Remove NVIDIA helper script
- Uninstalls NVIDIA preference pane + menu bar app
Credits: @bogdanw @Pavo
FakePCIID audio fix: @toleda @RehabMan
Notes
- The Preference Pane App
- may report that the 'default macOS drivers' are in use. If you have acceleration you can ignore this - or the preference pane and status app can be removed. The attached remove-NVIDIA-helper.command automates removal.
- nvda_drv NVRAM Variable
- As usual, the drivers only start when this is set. The installer sets this variable when you install, after which it might be controlled by:
- the 'NvidiaWeb' Clover config.plist setting
- the Clover entry menu (press space at the boot screen, check/uncheck Nvidia option)
- NVIDIA preference pane/menu bar app
- Web Driver Manager menu bar app
- Apple's nvram system command (see #32)
- Clover sets nvda_drv=1 every boot when NvidiaWeb is true (in SystemParameters, config.plist). Not needed as long as NVRAM is working.
- Removing NvidiaWeb from your config.plist does not unset the nvda_drv variable - though pressing F11 at the Clover boot menu should.
- As usual, the drivers only start when this is set. The installer sets this variable when you install, after which it might be controlled by:
- NVRAM Problems
- Setting any NVRAM variable is useless if the variable store is not persistent after a reboot. For many motherboards the only way to accomplish pseudo-persistent NVRAM storage has been to install the Clover RC scripts + the EmuVariableUEFI driver.
- These 2 work together, the RC scripts writing a subset of variables to a file on shutdown, Clover reading them back from disk at boot - with the EmuVariableUEFI driver providing the runtime variable support instead of your motherboard's firmware.
- Recent improvements in bootloader components required for booting macOS eliminate the need for EmuVariableUEFI.
- If you've been using emulated NVRAM as described above these developments may make your life easier. For more information read about 'Clover Emulated NVRAM Uninstaller' + Standalone Clover Builds
- NVRAM problems are not specific to the kext patch
Attachments
Last edited: