Jump to content

clover issue with nvidia, relates to shutdown and blank screen issues

sailor25462

By sailor25462,
in OSx86 10.10 (Yosemite)

 Share
21 posts in this topic

Recommended Posts

sailor25462
sailor25462
Posted
Posted

Dear All,

 

I need your support to setup clover correctly for my nvidia GT640 card.

 

Normally, this card should be (and used to be) natively supported.

 

With Yosemite there is unfortunately an issue to shutdown completely. Without using clover's graphics injection, 99,9% of all shutdowns will result in a reboot, thus not turning off the system.

 

As soon as NVIDIA injection is ticked, the shutdown process works well.

 

I do not know whether this is a clover problem or something (new) caused by Yosemite, but at least the graphics injection seems to solve this.

 

Now, my specific problem is that when I use the injection, after the initial boot, the used DVI port seems to be deactivated and only the VGA port is used. "Pre-Boot" happens correctly on the DVI port, but then, after this first "phase", it switches off the DVI port and activates the VGA port. Login screen in then shown on that screen. However, the screen attached to the DVI port is not available as a 2nd monitor.

 

I tried a couple of different NVCAP settings, but so far no success. So, who could help me to solve this?

 

My system looks as follows:

 

GA-Z68AP D3 (rev. 2) UEFI (Ua9), DSDT.aml attached

i5-2500 3,31 GHz

 

clover r2953

 

Nvidia GT640 (vendor: 10de, device-id: 0fc1, version-id: 00a2), ROM extracted with clover and attached.

Ports: VGA, DVI, HDMI

 

Apple Cinema Display 20" with DVI

 

When booted without graphics injection, ioregistry will show 4 displays. 

NVCAP <05 00 00 00 00 00 ff ff ff ff 00 00 00 00 00 0e 00 00 00 00>

Model name is NVIDIA GeForce GT 640

 

For the first 3 displays (A@0 to C@2) the port numbers are correctly shown (00 to 02). The 4th display has no port number. Display-cfg is ff ff ff ff for all displays. av-signal-type for the first display is 02. 01 for the 2nd display and none for the third one.

 

 

With injection only 2 displays are shown, also NVCAP is different:

NVCAP <04 00 00 00 00 00 03 00 0c 00 00 00 00 00 00 07 00 00 00 00>

Model name is Palic GeForce GT 640

 

First display has an additional marking as boot-up screen in ioreg (so the DVI port?), however this can not be found in the normal bootup.

 

When I finally ran NVCAP Maker on the extracted ROM, the following value was given back:

<04 00 00 00 00 00 01 00 04 00 00 00 00 00 00 07 00 00 00 00>

 

 

I read a lot about this "black screen" or "blank screen" issue, I can only guess that many of them might have a similar behavior, so maybe this will potentially help to sort those out as well?

 

If you need any other additional info, please let me know and I will try to add asap.

 

Would be great if someone could help me to sort this out!

ga-z68AP D3.zip

Link to comment
Share on other sites
dudu_qc
dudu_qc
Posted
Posted

Hello, I can't help you but I think I find my solution for my bug. When I boot Yosemite, I have a black screen 5 s. and after that the desktop appear with some error messages tell me my computer have problem blablabla. I will try nvidia injection when will go back to home

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

Thanks Maniac, this is what I tried for 2 days :-)

Amoung a few others I tried the feeds from my initial post. None of them worked.

Interestingly I found 4 displays in ioreg, one without a port. So I tried also nvcaps calculated on 4 ports as well as 3 ports, whereas clover proposes only 2 ports for the injection.

It also turns out that using the injection, only 2 displays are shown in ioreg. This is independent from the ports setting and the used nvcaps.

 

So my feeling is that Yosemite may somehow ignore the nvcaps, although they find their way into the ioreg. Strange.

Link to comment
Share on other sites
Maniac10
Maniac10
Posted
Posted

Then you’ve got to figure out what Clover does exactly when graphics injection is enabled, then apply those fixes manually and try to find what solves the shutdown problem without overriding the NVCAP. Dump an ioreg and DSDT with and without the graphic injection if you can.

 

And have you tried loading the dumped vbios with Clover?

Link to comment
Share on other sites
alx1101
alx1101
Posted
Posted

I was having similar issues - just ended up disabling the nvidia drivers with "nv_disable=1" in clover, then installing the nvidia webdrivers (had to use Pacifist to force it because the webdrivers won't install unless you boot with an nvidia driver(!)). Reboot without nv_disable and problem solved.

 

Just putting nvda_drv=0 did not help - it had to be nv_disable=1.

 

The yosemite nvidia builtin drivers were working all through the beta including GM3. Final upgrade broke them for me (on a GTX 980).

  • Like 2
Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

I was having similar issues - just ended up disabling the nvidia drivers with "nv_disable=1" in clover, then installing the nvidia webdrivers (had to use Pacifist to force it because the webdrivers won't install unless you boot with an nvidia driver(!)). Reboot without nv_disable and problem solved.

 

Just putting nvda_drv=0 did not help - it had to be nv_disable=1.

 

The yosemite nvidia builtin drivers were working all through the beta including GM3. Final upgrade broke them for me (on a GTX 980).

 

I can confirm this changed somewhere after PB1/PB2 or so.

Don't recall it exactly, but before I had no issues with the shutdown.

 

I shall look into the web driver and pacifist install procedure, as I have never down it before.

Ok, so here comes the requested ioreg and dsdt files. Without and with (single) injection.

I did not put in any further parameters, such as model or NVCAP. I hope this is what is needed.

 

Edited.

 

 

ioreg and dsdt.zip

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

I was having similar issues - just ended up disabling the nvidia drivers with "nv_disable=1" in clover, then installing the nvidia webdrivers (had to use Pacifist to force it because the webdrivers won't install unless you boot with an nvidia driver(!)). Reboot without nv_disable and problem solved.

 

Just putting nvda_drv=0 did not help - it had to be nv_disable=1.

 

The yosemite nvidia builtin drivers were working all through the beta including GM3. Final upgrade broke them for me (on a GTX 980).

 

OK, this was great help and it did work well as far as I can see after a few successful shutdowns.

Thanks' alx1101 for this input!

I can’t open those ioreg files. Try with an older ioreg app, iojones or DarwinDumper’s ioreg utility. And I can see 2 DSDTs on each zip, which is the one loaded?

 

None of these DSDT's have been used by clover settings. Those were dumped using the F2 option into the "origin" folder.

I have included all files for good orders sake. I just renamed the DSDT.aml to DSDT without.aml, etc.. (I thought I would only send the DSDT.aml, but then changed my mind, so renaming was not so very clever after all I guess :-) ) Wouldn't the other one be the auto patched version?

 

As for the ioregs, I will check and send new ones.

I am using IORegistryExplorer in version 3.0.2, though.

 

Edit: Can you please try to use IORegistryExplorer? after installing the nvidia web drivers, ioregs are completely different. Would need to uninstall web drivers completely :-(

 

Although, for me the problem is solved, I still think there's something wrong with the injection as well as with the native driver in Yosemite.

 

Edit2: attached ioreg from iojones with nvidia web driver installed and active. (as reference)

iojones ioreg dump with nvidia web driver.zip

  • Like 1
Link to comment
Share on other sites
Retsckor
Retsckor
Posted
Posted

Hi I have the exact same problem with the gt 640. Would you mind posting the procedure? And I link to the exact nvidia web driver? Am I supposed to boot with the inject nvidia ticked at the clover configurator? Or just the default?

 

Do I tick inject nvdia and boot with nv_disable=1? Install the driver and still boot with inject nvdia ticked ?

 

Sorry I'm not that familiar with clover yet

 

Hope you can help

 

Thanks

Link to comment
Share on other sites
BNZfive
BNZfive
Posted
Posted

I had similar issues after DP3. My machine (h61n-usb3, 2500k, EVGA GT640) would go through the boot process, there would be no errors. Yet, when it came time to launch the login screen/desktop, my two monitors went "no signal" as if they were sleeping. The computer continued to run. Nothing I could do (unplug replug monitors, try onboard output) would get me a signal. 

 

Here's what worked for me. I took all the NVDA labeled kexts in DP1 and, with the help of some kext insertion software, installed them into everything from DP4 onto Official Release Build, and bingo both screens would come on again.

 

 

GraphicsEnabler=No

Link to comment
Share on other sites
Retsckor
Retsckor
Posted
Posted

Tried installing your kexts however when I have the inject nvdia ticks, the monitor would still look like it's sleeping.. What do you have ticked in clover configurator?

If I don't have the inject nvdia box ticked in clover configurator, I have shutdown issues..

Link to comment
Share on other sites
dudu_qc
dudu_qc
Posted
Posted

I can confirm this is not exactly what I experience. My primary screen (DVI) is switched off. Only VGA is working.

Nevertheless it'd be interesting to hear about the injection from you!

DVI work well for me whit or whit out nvidia injection. But I think I find the origin of my problem. When I use the audio_cloverALC script for my alc892, he make something with HDMI audio and I think is that make error. I see AAPL error in my nvram. Need more investigation on AAPL.

Link to comment
Share on other sites
Retsckor
Retsckor
Posted
Posted

DVI work well for me whit or whit out nvidia injection. But I think I find the origin of my problem. When I use the audio_cloverALC script for my alc892, he make something with HDMI audio and I think is that make error. I see AAPL error in my nvram. Need more investigation on AAPL.

I have the same problem as you. We're you able to fix the your computer shut down because of a problem box at startup? If so how were you able to fix it?

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

I had similar issues after DP3. My machine (h61n-usb3, 2500k, EVGA GT640) would go through the boot process, there would be no errors. Yet, when it came time to launch the login screen/desktop, my two monitors went "no signal" as if they were sleeping. The computer continued to run. Nothing I could do (unplug replug monitors, try onboard output) would get me a signal. 

 

Here's what worked for me. I took all the NVDA labeled kexts in DP1 and, with the help of some kext insertion software, installed them into everything from DP4 onto Official Release Build, and bingo both screens would come on again.

 

 

GraphicsEnabler=No

 

Makes sense. Indeed it looks like something went wrong with the native nvidia drivers.

Tried installing your kexts however when I have the inject nvdia ticks, the monitor would still look like it's sleeping.. What do you have ticked in clover configurator?

If I don't have the inject nvdia box ticked in clover configurator, I have shutdown issues..

 

If you install the nvidia web drivers, you need to tell clover that you use them. (That has nothing to do with the nvidia pref pane where you can also select the native driver or web driver! In any case you need nvda_drv=1). So my boot options start like this:

<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>darkwake=no nvda_drv=1 kext-dev-mode=1</string>

Hi I have the exact same problem with the gt 640. Would you mind posting the procedure? And I link to the exact nvidia web driver? Am I supposed to boot with the inject nvidia ticked at the clover configurator? Or just the default?

 

Do I tick inject nvdia and boot with nv_disable=1? Install the driver and still boot with inject nvdia ticked ?

 

Sorry I'm not that familiar with clover yet

 

Hope you can help

 

Thanks

 

step 1:

 

disable the nvda driver by adding nv_disable=1.

 

This will result in a non accelerated graphics system, so don't expect this to run smoothly and shiny. It's only to get around the error message from nvidia that you can't install the driver on this system.

 

step 2:

 

install the web driver. If you can't do it out of the box, you'll need to use pacifist to open the pkg and install the driver from within pacifist. There's also an option (right click) to install them to the designated target. (I used this option first)

 

step 3:

 

reboot and enter clover to activate the nvidia driver (nvda_drv=1) 

 

step 4:

 

install the web driver a 2nd time.

 

 

Don't activate the nvidia graphics injection. This is not necessary anymore since the web driver will result in a proper shutdown.

  • Like 1
Link to comment
Share on other sites
Retsckor
Retsckor
Posted
Posted

Makes sense. Indeed it looks like something went wrong with the native nvidia drivers.

 

If you install the nvidia web drivers, you need to tell clover that you use them. (That has nothing to do with the nvidia pref pane where you can also select the native driver or web driver! In any case you need nvda_drv=1). So my boot options start like this:

<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>darkwake=no nvda_drv=1 kext-dev-mode=1</string>

step 1:

 

disable the nvda driver by adding nv_disable=1.

 

This will result in a non accelerated graphics system, so don't expect this to run smoothly and shiny. It's only to get around the error message from nvidia that you can't install the driver on this system.

 

step 2:

 

install the web driver. If you can't do it out of the box, you'll need to use pacifist to open the pkg and install the driver from within pacifist. There's also an option (right click) to install them to the designated target. (I used this option first)

 

step 3:

 

reboot and enter clover to activate the nvidia driver (nvda_drv=1) 

 

step 4:

 

install the web driver a 2nd time.

 

 

Don't activate the nvidia graphics injection. This is not necessary anymore since the web driver will result in a proper shutdown.

Thank you so much for the instructions!

 

Can you post a link to the Gt 640 drivers? I'm using the one BNZfive posted... are there more up to date drivers than this? also, how can i tell if QE/CI are working?

Link to comment
Share on other sites
BNZfive
BNZfive
Posted
Posted

Thank you so much for the instructions!

 

Can you post a link to the Gt 640 drivers? I'm using the one BNZfive posted... are there more up to date drivers than this? also, how can i tell if QE/CI are working?

 

Are you still having problems with shutdown? What are your system specs and do you have a dsdt for your board? I'll send you my clover config screenshots in a bit.

 

I am using legacy boot as I don't have UEFI on my H61N. I am also using a DSDT for my board (placed in /EFI/CLOVER/ACPI/patched/)

 

Attached are the screenshots of my clover configuration.

 

This config is for:

 

GA-H61N-USB3

2500k

GT640

 

Sleep, wake, shutdown, restart all working. Also have HDMI audio using HDMIAudio.kext

 

CloverConfig.zip

Link to comment
Share on other sites
sailor25462
sailor25462
Posted
  • Author
Posted

Thank you so much for the instructions!

 

Can you post a link to the Gt 640 drivers? I'm using the one BNZfive posted... are there more up to date drivers than this? also, how can i tell if QE/CI are working?

 

http://www.nvidia.com/download/driverResults.aspx/78853/en-us

 

thats for the english version, others are as well available. it's under the beta drivers section at nvidia. search for 600 series and use gtx680 to get the result. its all the same driver. One for all....

The drivers are built for a certain build number! so these are for Yosemite (full release, no beta!) 

Are you still having problems with shutdown? What are your system specs and do you have a dsdt for your board? I'll send you my clover config screenshots in a bit.

 

I am using legacy boot as I don't have UEFI on my H61N. I am also using a DSDT for my board (placed in /EFI/CLOVER/ACPI/patched/)

 

Attached are the screenshots of my clover configuration.

 

This config is for:

 

GA-H61N-USB3

2500k

GT640

 

Sleep, wake, shutdown, restart all working. Also have HDMI audio using HDMIAudio.kext

seems like the legacy boot version of clover doesn't have this specific problem... didn't try though.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...