Black Screen After Updating to 10.12.5

[iGV]

Your Motherboard doesn't save the macOS NVRAM file between boots. Therefore, you need to do one of the following:

See Problem 6 in slim.jim's Nvidia Trouble Shooting Guide.

OR

Use the latest MultiBeast for Sierra and just select the following:
Bootloaders > Clover v2.4k r4063 UEFI Boot Mode + Emulated NVRAM <--- page 6, MultiBeast Features doc, MultiBeast Features doc
Build > Install
Then, reboot.

Ok Stork, you just through me a curveball. I haven't finished building my hack yet, and it's not even the same MB as mnsrit, but I trying to learn. So, since his board has a UEFI bios and no NVRAM, I would have thought he would use:

• Bootloaders > Clover v2.4k r4063 UEFI Boot Mode + Emulated NVRAM <--- page 6, MultiBeast Features doc

Reading the instructions, that what I would have chosen. I'd like to understand the reason for choosing Legacy Boot Mode.

 

[mnsrit]

Your Motherboard doesn't save the macOS NVRAM file between boots. Therefore, you need to do one of the following:

See Problem 6 in slim.jim's Nvidia Trouble Shooting Guide.

OR

Use the latest MultiBeast for Sierra and just select the following:

Bootloaders > Clover v2.4k r4063 UEFI Boot Mode + Emulated NVRAM <--- page 6, MultiBeast Features doc, MultiBeast Features doc
Build > Install​

Then, reboot.

Thanks - I went ahead and used MultiBeast and selected the bootloader as Clover v2.4k r4063 UEFI Boot mode + Emulated NVRAM. It works beautifully - I could see the graphic card and its RAM displayed correctly. The only issue is that I can't adjust the display resolution as the top menu bar can't be seen...is there a way to make this work?

Secondly, I'm still learning why would I use legacy if BIOS is based on UEFI? Can you help me understand why? I thought that was for older motherboards?

Thanks again!

matt

 

[darukaru]

Since MacOS doesn't have native support for nVidia latest series GPUs, does that mean when viewing HW accelerated media like YouTube videos, it'll use CPU load instead of GPU? Cz i feel like my CPU is doing more work than it should for a video and since there's no way to monitor GPU clocks, it's hard to tell also.

Yeah, as of right now there's no way to get hardware accelerated video playback. The Shiki and mpv media player devs are looking into it but I wouldn't expect it until there's another Mac with a NVIDIA card onboard.

 

[countergame]

So it seems that i'm the only one who's having problems with the 960 on Sierra? Since no one replied to my post yet. I'm now using the AMD Radeon HD 7700 with the patched verde.kext to fix the yellow screen bug. Of course it's a dramatic downgrade but Apple is using AMD videocards anyway so theoretically it should run better than any other nvidia cards on os x.

 

[alexlove99]

Yeah, as of right now there's no way to get hardware accelerated video playback. The Shiki and mpv media player devs are looking into it but I wouldn't expect it until there's another Mac with a NVIDIA card onboard.

Wait a minute...
Why is the h/w accelerated playback not working?
What do the NVidia drivers do differently to the drivers shipped by Apple?
When I was watching a blu ray with mpv a few days ago, everything was working as expected and it didn't really hit my CPU any harder than before with my HD 7950.

 

[Stork]

Ok Stork, you just through me a curveball. I haven't finished building my hack yet, and it's not even the same MB as mnsrit, but I trying to learn. So, since his board has a UEFI bios and no NVRAM, I would have thought he would use:

• Bootloaders > Clover v2.4k r4063 UEFI Boot Mode + Emulated NVRAM <--- page 6, MultiBeast Features doc

Reading the instructions, that what I would have chosen. I'd like to understand the reason for choosing Legacy Boot Mode.

...

Secondly, I'm still learning why would I use legacy if BIOS is based on UEFI? Can you help me understand why? I thought that was for older motherboards?...

OMG! You guys caught me in a Senior moment! You are correct - I copied/pasted the wrong line from the MultiBeast Features document. I have corrected the OP. ("Dunno why this happened," he mumbled.)

So, the MultiBeast method for preserving NVRAM on some motherboards is:

Bootloaders > Clover v2.4k r4063 UEFI Boot Mode + Emulated NVRAM <--- page 6, MultiBeast Features doc​

Thank you, iGV & mnsrit, for pointing this error out to me.

 

[izo1]

FYI Some motherboards have native NVRAM support so you don't need emulated NVRAM from Clover, but some BIOS updates break that, such as the one from Asus for the Gene VIII recently.

 

[bruce2008]

Waiting for 10.12.5 driver support

Use this way to run NVIDIA web drive on 10.12.5.
https://www.tonymacx86.com/threads/solving-nvidia-driver-install-loading-problems.161256/#Problem5
The build number is 16F73 .

 

[umran23]

Wait a minute...
Why is the h/w accelerated playback not working?
What do the NVidia drivers do differently to the drivers shipped by Apple?
When I was watching a blu ray with mpv a few days ago, everything was working as expected and it didn't really hit my CPU any harder than before with my HD 7950.

Don't know what they do differently but new Mac OS doesn't really detect Nvidia for video decoding in VLC or web. Since technically no new Mac hardware has it so the os doesn't even see this. In KODI while checking the resource usage for a high quality 1080 Blu ray my cpu easily is being utilised at around 30% but if I enable the on board gfx it easily drops to around 16-20% percent. An extremely high quality 60mbps 4k video shows above 200 % cpu activity in iStats when playing with QuickTime but if I use my onboard graphics it's drops to 5%.

 

[izo1]

10.12.5 drivers are out, fyi.

https://images.nvidia.com/mac/pkg/378/WebDriver-378.05.05.15f01.pkg