Jump to content
obov

10.13 -- A Possible Solution to Black Screen (No Signal) before Login Involving Nvidia Graphics Card

1 post in this topic

Recommended Posts

Hello everyone!  This is a new user to InsanelyMac, although I've built my Hackintosh long ago with the information on this forum :D

But it seems like the problem I encountered has no solution posted here, I would like to share my solution to that. 

 

I have an i7 6700k, a GIGABYTE Z170 motherboard (though these two are not important at all in this problem), and a GTX970. I recently updated my Hackintosh from 10.11 to 10.13.1 (I think it should also work for 10.13) through App Store. The system was successfully installed, but I found that it was impossible to log in the system with my GTX970 plugged in -- it always led to black screen (no signal) before the login screen was shown. 

 

There are some discussion on InsanelyMac, but none of the solutions proposed worked for me. Here are my experiments:

  • Since I am using iMac 15, 1 SMBIOS, I manually modified the AppleGraphicsDevicePolicy.kext so that it would not use the "Config2," or I can't even boot into the system with my IGFX (as we all know, it causes black screen / no signal before login).  AppleGraphicsDevicePolicy.kext is NOT the cause of the problem in my case, although they have the same symptom; before using this solution, check your SMBIOS and AppleGraphicsDevicePolicy.kext.
  • I also put Lilu.kext and NvidiaGraphicsFixup.kext in my Clover, but since they do the same thing as manually modifying Info.plist, I don't think it really matters here.
  • In case of installing a broken Web Driver to my Hackintosh, I enabled SIP before the installation of Nvidia driver. It seemed like it worked: the first time I installed the Web Driver with SIP disabled, as well as after I accidentally removed a kext from /S/L/E and broke the driver, it produced a "gIOScreenLockState 3" problem. One of my guesses: the "gIOScreenLockState 3" is due to a broken or disabled (i.e. forgot to add NvidiaWeb in Clover config) web driver.
  • NVwebDriverLibValFix.kext has no effect. It changed nothing but caused reboot before login when I was using IGFX. 

At last, I tried injecting a fake ID for Nvidia (0x00000000) and it WORKS! Go to "Devices" section in Clover Configurator (if you use it) and put 0x00000000 to "NVidia" in the "Fake ID" section, or modify the text of Config.plist like this:

	...
	<key>Devices</key>
	<dict>
		...
		<key>FakeID</key>
		<dict>
			<key>NVidia</key>
			<string>0x00000000</string>
		</dict>
		...
	</dict>
	...

Then save, reboot. It should work if you have the same problem with me. 

 

Hope this help. If you have any question, leave a reply. I would be glad if I can help someone solve the problem. 

Share this post


Link to post
Share on other sites
Advertisement

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 SAMEH209
      I've successfully installed High Sierra (10.13.0) on my system using Clover:
      2x Intel Xeon E5410
      16GB Ram
      GTX 950
      Everything is running fine except the GPU. I've tried the web driver's latest version and 378.10.10.10.25.106 but both are very laggy/sluggish.
      I've also tried installing Lilu and nVidiaGraphicsFixUp kexts but they didn't change anything.
      Have someone managed to make this card work with High Sierra?
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo-10.13.x to create an USB installer. You can't just run the app downloaded from Mac App Store.
       
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).

      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      How to make 10.13 installer for MBR?
      Read HowTo-10.13.x.txt inside the zip file first, different with 10.12.
      Read HowTo Q/A Q7. How to install in different computer with only one USB partition?
      Read HowTo Q/A Q8. How to update 10.13.x combo-update to MBR without downloading the full installer app again?
      Read HowTo Q/A Q9. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
    • By fusion71au
      Clover r4542 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 14 running OSX 10.9 -->10.14 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4542 for VMware.zip". Mount Clover-v2.4k-4542-X64.iso 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.
×