Jump to content
fantomas

Nvidia Web Driver updates for macOS Sierra (UPDATE Sept 27, 2019)

1,064 posts in this topic

Recommended Posts

Hi ergot

No, no NVIDA inject in EFI/CLOVER/config.plist

 

Did you use bootflag nv_disable=1 until Webdrivers where installed ?

I suppose you did an Webdriver install before using nvda_drv=1 ?  latest is here

This app.can update and search new drivers and download and then install them automaticaly !

 

Understand that a clean Sierra PB2 install contains already Nvidia drivers but your card is not natively recognized !

The alternative Webdrivers you need are beta

My Clover folder doesn't help you beacause we have very different hardware and the Webdriver are not in EFI/CLOVER !

 

Good luck

Share this post


Link to post
Share on other sites
Advertisement

@Faun, thanks to your Nvidia web driver for PB1 as it works perfectly with my system. Any chance you will have Nvidia web driver for Public Beta 2 soon? 

Share this post


Link to post
Share on other sites

For those having success with latest web driver and PB1, does this include Pascal support? Anyone having success with the 10xx series cards?

Share this post


Link to post
Share on other sites

Hi ergot

No, no NVIDA inject in EFI/CLOVER/config.plist

 

Did you use bootflag nv_disable=1 until Webdrivers where installed ?

I suppose you did an Webdriver install before using nvda_drv=1 ?  latest is here

This app.can update and search new drivers and download and then install them automaticaly !

 

Understand that a clean Sierra PB2 install contains already Nvidia drivers but your card is not natively recognized !

The alternative Webdrivers you need are beta

My Clover folder doesn't help you beacause we have very different hardware and the Webdriver are not in EFI/CLOVER !

 

Good luck

 

Thanks

I have the latest web drivers, i did not used nvda flag until installing web drivers...nothing helped...

Share this post


Link to post
Share on other sites

@ergot I haven't read all of the thread, so this might be a repeat.

 

For one there is/was a problem with nvda_drv in config.plist. It has to be in the nvram and you might need the nvram emulation efi driver to get it working.

 

Second. I use my GTX970 since 10.11.3 with the corresponding Webdrivers. I alway uses DP to connect.

 

With DP3 and the latest Webdriver, It doesn't work anymore - but it does if I use HDMI.

 

Probably one or the other might help.

Share this post


Link to post
Share on other sites

New Web Driver is out, presumably for 10.12 DB4 (PB3?).

d38QtMk.png

This new Nvidia Web Driver not working for GTX-980 display card yet in my hackintosh.

Anyone got it working for GTX-980 or GTX-970 in 10.12 beta 2 to beta 4 ?

Share this post


Link to post
Share on other sites

Indeed σomething strange is happening to these drivers.

On DispalyPort and just updating have "negative" colors.

i change on HDMI and working nice again.

DP 4 ~ GTX 960 X99 chipset

Share this post


Link to post
Share on other sites

This new Nvidia Web Driver not working for GTX-980 display card yet in my hackintosh.

Anyone got it working for GTX-980 or GTX-970 in 10.12 beta 2 to beta 4 ?

 

GTX 970 here. New driver working fine in DP 4. I use the display port. 

Share this post


Link to post
Share on other sites

Indeed σomething strange is happening to these drivers.

On DispalyPort and just updating have "negative" colors.

i change on HDMI and working nice again.

DP 4 ~ GTX 960 X99 chipset

There seems a change in the underlying data structure, but the already saved values of the screen preferences are not updated to that data structure.

 

Change resolution or orientation of the monitor in question forth and back.

It will rewrite the values and the display will be ok again.

Share this post


Link to post
Share on other sites

There seems a change in the underlying data structure, but not the already saved values of the screen preferences are not updated to that data structure.

 

Change resolution or orientation of the monitor in question forth and back.

It will rewrite the values and the display will be ok again.

u have right bro.. fixed.

Thanks

Share this post


Link to post
Share on other sites

Anyone that has GT610 working on Sierra DP4? It doesn´t work since DP1 on Sierra, only "works" if I put nv_disable=1 on Clover, but it doesn´t have QE/CI.

I tried with InjectNvidia and with Web drivers, but it stucks in a black screen.

Best regards.

Share this post


Link to post
Share on other sites

Just upgraded over an existing 10.11.6 installation yesterday to PB3 but can't get these kexts to load with my GTX 970, with or without nvda_drv=1. Any reason this might be?

 

The only change I made to Clover was an update from 3333 to 3676 and SMBIOS from MacPro3,1 to imac11,2, imac11,3, imac14,2, and macpro5,1, but no luck with any of them.

Share this post


Link to post
Share on other sites

update to PB3 with the latest web drivers i still cannot get full acceleration with my GPU...in boot i use nada_drv=1 but even if i don't use this boot flag i still can boot the system...

Is there a place where i need to "clean" boot arguments or something like this?

nvram -xp don't show nvda_drv , even when adding one sudo nvram nvda_drv=1 i still cannot boot properly

any suggestion will be appreciated  

thanks

Share this post


Link to post
Share on other sites

update to PB3 with the latest web drivers i still cannot get full acceleration with my GPU...in boot i use nada_drv=1 but even if i don't use this boot flag i still can boot the system...

Is there a place where i need to "clean" boot arguments or something like this?

nvram -xp don't show nvda_drv , even when adding one sudo nvram nvda_drv=1 i still cannot boot properly

any suggestion will be appreciated  

thanks

i think nvidia webdriver no longer expose nvda_drv=1. I noticed that when upgraded today. So just added that to clover boot arguments, that's all. Everything works properly for now.

Share this post


Link to post
Share on other sites

i think nvidia webdriver no longer expose nvda_drv=1. I noticed that when upgraded today. So just added that to clover boot arguments, that's all. Everything works properly for now.

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

 

PIOXz15.png

Share this post


Link to post
Share on other sites

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

 

 

Incidentally, I'm not able to assign boot arguments to the nvram, which seemed like it might be the solution, and get this error:

claes2:~ claes$ sudo nvram boot-args="nvda_drv=1"
nvram: Error setting variable - 'boot-args': (iokit/common) general error

Any reason this might be?

 

 

P.S. On legacy PBR, here are my nvram parameters according to terminal:

bootercfg	(%00
fmm-computer-name	claes
prev-lang:kbd	en:0
security-mode	none
Clover.KeepBackupLimit	0
SystemAudioVolumeDB	%f2
SystemAudioVolume	0
LocationServicesEnabled	%01
csr-active-config	%03%00%00%00
Clover.NVRamDisk	Yes

CSR Status (does this even matter?):

System Integrity Protection status: enabled (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Any thoughts on why my installation won't load the web drivers?

 

Here's my boot.plist if it helps:

 

 

<?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>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddDTGP_0001</key>
				<true/>
				<key>FixHDA_8000</key>
				<true/>
				<key>FixHPET_0010</key>
				<true/>
				<key>FixIPIC_0040</key>
				<true/>
				<key>FixUSB_1000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>PatchAPIC</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>Generate</key>
			<false/>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>dart=0 nvda_drv=1</string>
		<key>Debug</key>
		<true/>
		<key>DefaultVolume</key>
		<string>osx</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>2</integer>
		<key>XMPDetection</key>
		<string>Yes</string>
	</dict>
	<key>CPU</key>
	<dict>
		<key>UseARTFrequency</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>1</string>
		</dict>
		<key>FakeID</key>
		<dict>
			<key>IMEI</key>
			<string>0x0</string>
			<key>LAN</key>
			<string>0x0</string>
			<key>NVidia</key>
			<string>0x0</string>
			<key>SATA</key>
			<string>0x0</string>
			<key>WIFI</key>
			<string>0x0</string>
			<key>XHCI</key>
			<string>0x0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>FixOwnership</key>
			<false/>
			<key>Inject</key>
			<false/>
		</dict>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>CustomIcons</key>
		<true/>
		<key>Hide</key>
		<array>
			<string>henrietta</string>
			<string>EXTRA</string>
			<string>frederick</string>
			<string>Windows</string>
			<string>\EFI\BOOT\BOOTX64.EFI</string>
		</array>
		<key>Language</key>
		<string>en:0</string>
		<key>Mouse</key>
		<dict>
			<key>DoubleClick</key>
			<integer>500</integer>
			<key>Enabled</key>
			<true/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Kernel</key>
			<string>All</string>
			<key>Legacy</key>
			<string>First</string>
			<key>Linux</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>
		<key>ScreenResolution</key>
		<string>1920x1080</string>
		<key>Theme</key>
		<string>mac</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelHaswellE</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>t1-AppleHDA/Resources/xml>zml</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				eG1sLnps
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				em1sLnps
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.12-AppleHDA/Realtek ALC...</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ihnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				AAAAAA==
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.12-AppleHDA/Realtek ALC889</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ixnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				iQjsEA==
				</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x3</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>10/07/10</string>
		<key>BiosVendor</key>
		<string>Apple Inc.</string>
		<key>BiosVersion</key>
		<string>MP51.88Z.007F.B03.1010071432</string>
		<key>Board-ID</key>
		<string>Mac-F221BEC8</string>
		<key>BoardManufacturer</key>
		<string>Apple Inc.</string>
		<key>BoardType</key>
		<integer>11</integer>
		<key>ChassisAssetTag</key>
		<string>Pro-Enclosure</string>
		<key>ChassisManufacturer</key>
		<string>Apple Inc.</string>
		<key>ChassisType</key>
		<string>06</string>
		<key>Family</key>
		<string>Mac Pro</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Mobile</key>
		<false/>
		<key>ProductName</key>
		<string>MacPro5,1</string>
		<key>SerialNumber</key>
		<string>XB20274SEUH</string>
		<key>Trust</key>
		<false/>
		<key>Version</key>
		<string>1.0</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Detect</string>
		<key>InjectSystemID</key>
		<true/>
	</dict>
</dict>
</plist>

 

 

 

 

Original post:

 

 

Just upgraded over an existing 10.11.6 installation yesterday to PB3 but can't get these kexts to load with my GTX 970, with or without nvda_drv=1. Any reason this might be?

 

The only change I made to Clover was an update from 3333 to 3676 and SMBIOS from MacPro3,1 to imac11,2, imac11,3, imac14,2, and macpro5,1, but no luck with any of them.

 

 

 

Share this post


Link to post
Share on other sites
System Integrity Protection status: enabled (Custom Configuration).

Configuration:
	Apple Internal: disabled
	Kext Signing: disabled
	Filesystem Protections: disabled
	Debugging Restrictions: enabled
	DTrace Restrictions: enabled
	NVRAM Protections: enabled
	BaseSystem Verification: enabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Well since you have NVRAM Protections: enabled then I would say yes it matters

Share this post


Link to post
Share on other sites

Thank you - I think I have found a solution! Hopefully it works for others!

 

First, I changed my the Rt Variable "CsrActiveConfig" from 0x03 to 0x67 in Clover, as per these instructions (useful resource as SIP management is more nuanced now than it was). This allowed me to add boot arguments to the nvram:

sudo nvram boot-args="nvda_drv=1"

Checked with nvram -p and the change had been committed! So, I reboot, but still no Nvidia kexts!

 

Then, I used this command, as per a forum post that can not be named:

sudo nvram nvda_drv

Which produced these results with nvram -p:

boot-args	dart=0 nvda_drv=1
bootercfg	(%00
Clover.KeepBackupLimit	0
nvda_drv	1
prev-lang:kbd	en:0
SystemAudioVolumeDB	%02
security-mode	none
Clover.NVRamDisk	Yes
fmm-computer-name	claes
csr-active-config	g%00%00%00
SystemAudioVolume	%01
LocationServicesEnabled	%01

Rebooted and the kext has loaded! Thanks for all of the help!

Share this post


Link to post
Share on other sites

nothing helped me...i think the boot arg nvda_drv is not saved or clear in reboot in plist file.

anyone know how to edit this file manually?

 

UPDATE

 

Make it work! bcuz nvram did not saved my string I installed EMU driver in clover folder and script by clover, used nvram boot-args='nvda_drv=1' and after boot I had black screen..good so far meaning its working but since I am using SMBIOS macpro6,1 I used AGDPfix and now I have full acceleration with web drivers :)

post-474300-9372_thumb.png

Share this post


Link to post
Share on other sites

Sure it does, running GTX 970 on MacPro 5,1 right now with macOS 10.12 DP4 with web drivers and working fine

 

 

 

So you didn't manually add this argument and nvidia web driver automatically added that when you installed correct ? It was a case with El Capitan, however same behaviour cannot be seen for Sierra. It's strange, argument also appears in my nvram right now but it's because of clover i think.

 

@drowsyhaze

 

Also thank you for detailed instructions.

 

 

2016_08_07_15_07_47.png

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 Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By Prasanth_1991
      I recently installed Hackintosh Sierra. I don't have dedicated graphics card so I just used Intel integrated graphics which is Intel HD 4600 but since the Mac OS Sierra graphics acceleration not supported by native VGA output I'm left out options. I tired many things but nothing works. It's 2020 I'm pretty sure many people probably have better solution for this, if yes please help me.   Details PC Spec  i7 4790k HD 4600 Motherboard Gigabyte B85M-D3H-A
    • By Sagnik Ganguly
      Hello I'm Sagnik Ganguly, I'm trying to dual boot macOS 10.14 and Windows 10 (already installed) on a PC with Legacy BIOS. I've two hard drives one in where the windows is installed and another which is converted to GPT to install macOS Mojave 10.14 with a partion of Mac OS Extended (Journal) or APFS but when I went to the Install Disk Selection page, I'm selecting the partition but it says "This version of macOS 10.14 cannot be installed on this computer." can you help me please? 
      P. S. My motherboard doesn't support UEFI. 
      I'm attaching some pictures of the screens.


    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

       
      After Testing:
       
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
       
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
       
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
       
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
       
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
       
      Install:
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
       
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
       
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
       
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip
    • By rodrinico19
      Hola a todos, primero que nada estoy muy contento de a ver econtrado un foro de español sobre hackintosh.
      Mi problema consesite en que descargue unos drivers de esta pagina: https://github.com/chris1111/Wireless-USB-Adapter-Clover
      Seguí los pasos instale los kets en la carpeta EFI/CLOVER/OTHERS todo tal cual como dice ahi la instalación. luego segui los pasos de configurar la red dentro de configuracion del sistema etc.
      Lo cual el nombre me quedo en en0.
      El driver o kets funciona bien es reconocible por el S.O de hecho conecta la red, pero me dice que no tiene IP AUTO ASIGNADA Y LA OTRA QUE HAY UNA DESCONEXION A CADA RATO(como que desconectaras y conectaras el dispositvo usb a cada rato)
      Me gustaria que me ayuden con eso si es posible, Muchas Gracias!!
×