[SOLVED] GTX Geforce 1050 not being detected

[Shoikan]

To start off: I didn't read the whole thread -very- closely, so if I'm mentioning things you've already done or tried, forgive me

I've got an MSI Z170A SLI Plus mobo and an MSI GTX 1050 2G OC card, so pretty close to what you have. I ran into the same 'fight' as you did, it seems: lockups, no entry signs, kernel panics, the works. So far I've found that there are a variety of (not necessarily related) causes for each of them:

• You most definitely need the NVRAM fix. The bootflags seem to cause problems once you get to the stage where you're trying to run the Nvidia webdriver. Before you get to that point, it at least doesn't sit in the way, so you can get it up and running from the start.
• Secondly, -many- of the 'no entry sign' problems I had were to not being able to find enough memory pages (or words to that effect). You can see that error when you boot with the -v flag. This seems to be caused by (at least in my case) an interesting combination of mobo and components scattering their firmwares at random throughout the memory. I also use OsxAptioFix2Drv-free2000.efi from https://github.com/koush/EFI-X99/tree/master/CLOVER/drivers64UEFI (I believe that was the source anyway, you need a file with that name though). This cleans out the first GBs of memory the hard way, alleviating the problem. I haven't encountered adverse effects, which is not saying there aren't any.
  
• In BIOS I have set the following:
  • Settings/Advanced/PCI Subsystem Settings/Above 4G Decoding: Enabled (not sure if this helps, but it can't hurt)
  • Settings/Advanced/Integrated Peripherals/Intel Serial IO: Enabled (fairly sure this isn't related to nvidia or mem issues though)
  • Settings/Advanced/Integrated Graphics Configuration/Initiate Graphics Adapter: PEG (this will cause your 1050 to be 'primary' graphics adapter, and the onboard intel to be secondary)
  • Settings/Advanced/Integrated Graphics Configuration/IGD Multi-Monitor: Disabled (this will cause the 1050 to be the -only- used graphics adapter, so you will need to hook up your monitor to the 1050 after changing this)
    
  • Settings/Advanced/Super IO Configuration: turn everything off here. I'm sure you haven't used a real serial or parallel port in about 10-15 years.... No idea why the hell this is still here.
  • Settings/Advanced/Windows OS Configuration: Unless you're dual booting to windows, I'd turn all of this off too.
  • Don't forget the CPU related stuff all the howtos tell you about! On my board they were in the OC section.
• I found out I was doing too much configging in Clover, which caused a lot of problems. So I advise using the standard config.plist from unibeast as a starting point and only add stuff you're 100% sure of you need. I currently have the following items that are related to the 1050 set:
  • Graphics Injector: Inject NVidia enabled
  • Graphics Injector: Use NVidia Web drivers enabled (note that I believe this should be set automatically if you've got the NVRAM stuff fixed and have installed the web drivers)
  • On the boot options (space while at the Clover screen, hovering on the 'boot macOS from <volume>'), I have -nothing- selected.

If after you have installed the webdrivers, you can see the nvidia icon in the top right corner once you are in OSX, but you're still getting the slow and sluggish performance, there are two possible causes:

• You don't have the NVRAM fix running (can be setup from multibeast at the bootloaders tab, bottom option), or
• You have the nv_disable or nvda_drv flags set at boot. These will interfere with loading the driver.

Note that all the items you do in clover manually will have to be saved in the config.plist, of course. Unless you enjoy doing it manually every time

 

[WonkeyDonkey]

@CKellyCarroll, from who / where did you get that config.plist ?

 

[CKellyCarroll]

@Shoikan Thanks for the tips! I'll give them a try when I get home from work tonight.

@WonkeyDonkey, I got that config.plist from my local machine. What seems to be wrong with it?

 

[WonkeyDonkey]

It has more flags enabled than I think ive ever seen, plus some flags not enabled that should be. It certainly isnt the same as the one you posted previously.

 

[CKellyCarroll]

It has more flags enabled than I think ive ever seen, plus some flags not enabled that should be. It certainly isnt the same as the one you posted previously.

That is correct- they are different configs. Since I was unable to boot into macOS previously, I decided to blow it away and try again (which seems to be a pattern as of late, unfortunately). I may end up doing it again since I am getting a kernel panic at boot and @Shoikan 's suggestions for MSI mobos.

I apologize if I was not clear earlier. But do you think it's "kosher" to just wipe the drive if I'm in somewhat of a gridlock? I'm really open to suggestions and best practices for building and maintaining Hackintoshes (as this is my first build).

 

[WonkeyDonkey]

You could wipe it but unless you first find the source of the issue, that may be in vain.

In the 'Kernel and Kext Patches' of your config.plist file, you should probably enable 'Asus AICPUPM' and 'KernelPM'.

 

[CKellyCarroll]

You could wipe it but unless you first find the source of the issue, that may be in vain.

In the 'Kernel and Kext Patches' of your config.plist file, you should probably enable 'Asus AICPUPM' and 'KernelPM'.

I'll give that a try tonight- under matchOS, should I also add 10.12? Just remembering from the kernel panic, it said match os version: not yet set. Could that have something to do with it?

 

[WonkeyDonkey]

No. Thats simply telling you it hasnt got far enough into the boot process to establish the os version, from my understanding anyway.

 

[CKellyCarroll]

Gentlemen...or ladies...compatriots,

I have made some progress. One last thing appears to be in my way. @Shoikan, your suggestions worked for the most part. I no longer get the no entry sign (yay!). I was able to at least get the graphics card recognized in the system information, however the problem appears to be with the NVRAM (as you explained before). However, when I make the change through MultiBeast for UEFI+Emulated NVRAM, I am able to boot into the drive but the login screen (and everything else for that matter) come out super pixelated. Has anyone run into this same issue?

 

[Tater71]

I was wonder if anyone had experienced this problem, when Sierra boot up and I go to About This Mac the Nvidia GeForce GTX 1050 identifies itself as "Display 7 MB). I have installed the latest Nvidia drivers and set the flag in clover for NvidiaWeb, but the computer always defaults to "OS X Default Graphics Driver".

Thanks in advance.

MOBO: GA-H170M-DS3H
Graphics: Nvidia GeForce GTX 1050 OC