Jump to content

10.6.2 doesn't work with 8800GT EFI Strings

Bidule200

By Bidule200,
in OSx86 10.6 (Snow Leopard)

 Share
140 posts in this topic

Recommended Posts

Bidule200
Bidule200
Posted
Posted

Hello everyone,

 

my 8800GT works perfectly with 10.6.1,

but on 10.6.2 I get a black screen on boot.

 

But when I erase the HEX string from com.apple.boot.plist

I can boot in VESA mode (800x600 with no acceleration at all, and of course no QE/CI).

 

I already tried to get the 8800GT working by injecting the code directly to the DSDT.aml,

it works for 10.6.1 as expected but on 10.6.2 I get a black screen again.

 

 

Any help will be very appreciated,

because I begin to get mad on this ;)

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted
Hello everyone,

 

my 8800GT works perfectly with 10.6.1,

but on 10.6.2 I get a black screen on boot.

 

But when I erase the HEX string from com.apple.boot.plist

I can boot in VESA mode (800x600 with no acceleration at all, and of course no QE/CI).

 

I already tried to get the 8800GT working by injecting the code directly to the DSDT.aml,

it works for 10.6.1 as expected but on 10.6.2 I get a black screen again.

 

 

Any help will be very appreciated,

because I begin to get mad on this :)

Hi there.

Have you tried swapping your ports from DVI to VGA?

Sometimes this is needed to make screen works again.

 

Cheers.

bb.

Link to comment
Share on other sites
Rillipiru
Rillipiru
Posted
Posted
I'm sorry for you and it seems some others have that problem; but 8800GT can work on EFI string in 10.6.2

Mine is only EFI string, no injector, and it worked straight away.

 

Good luck with yours...

 

Again, same here. No injectors, just EFI studio and 8000 GT is still working. I really didnt trust the newer methods and i was right.

 

I have a DSDT, without any GPU strings.

Link to comment
Share on other sites
breakingbad
breakingbad
Posted
Posted
Again, same here. No injectors, just EFI studio and 8000 GT is still working. I really didnt trust the newer methods and i was right.

 

I have a DSDT, without any GPU strings.

 

Verdant once said:

It depends on which graphics card port the graphics driver is outputting the full signal to.......you may have to switch ports (typically to the port nearest the MOBO) to get on-the-fly resolution switching.....alternatively, you may have to sort out the correct NVCAP values in the Info.plist of your graphics injector kext, or as part of the graphics string.......

 

You must give it a try.

 

Cheers.

bb.

Link to comment
Share on other sites
hashmet
hashmet
Posted
Posted
Hello everyone,

 

my 8800GT works perfectly with 10.6.1,

but on 10.6.2 I get a black screen on boot.

 

But when I erase the HEX string from com.apple.boot.plist

I can boot in VESA mode (800x600 with no acceleration at all, and of course no QE/CI).

 

I already tried to get the 8800GT working by injecting the code directly to the DSDT.aml,

it works for 10.6.1 as expected but on 10.6.2 I get a black screen again.

 

 

Any help will be very appreciated,

because I begin to get mad on this :wacko:

 

Hey,

 

do you have two displays connected? If yes, try to plug out one of them. I have a similar problem. I cannot use two displays (one 24" monitor and 32" HD Ready TV).

 

hashmet

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

Yeah, I have two monitors (one Full HD monitor 24" and one Full HD TV 37")

 

They are both connected by a simple DVI-HDMI cable.

 

I'll try with VGA and with only one monitor.

Link to comment
Share on other sites
Krot
Krot
Posted
Posted
Hey,

 

do you have two displays connected? If yes, try to plug out one of them. I have a similar problem. I cannot use two displays (one 24" monitor and 32" HD Ready TV).

 

hashmet

 

It's working for me, just unplug second display and black screen has gone. Now need solution how to fix two displays issue :(

Link to comment
Share on other sites
Siobhan
Siobhan
Posted
Posted

People, it seems like a lot of us are having trouble with nvidia, post 10.6.2. In my topic nVidia 8600M freezing after 10.6.2 upgrade if HDMI monitor plugged in but not DVI I have the issue on my laptop with an 8600M GS where the built-in screen works fine, and some monitors work but others will cause a black screen on boot up, where as two (Acer AL2216W via DVI/HDMI cable and LG L204WT via same) cause no problems at all.

 

If I hook in my Acer P244w HDMI monitor or my Sony 60" KDS-60A2000 TV (both of which worked fine in 10.6.1) the screen will freeze, but I can still SSH into the laptop, and WindowServer is pegged at 99.9% CPU usage. Also, I cannot killall -HUP WindowServer; it will not reload and the only option is to hard power-off (reboot by power switch) the laptop.

 

Black screen occurs for me if these monitors are plugged in at startup as well.

 

Could i have more confirmation about his issue. I'm about to update and have a 8800GT. Thanks.
Anyone have any issues with a 8800GTS 320MB card and 10.6.2? I have BFG 8800GTS 320MB card and would like to know if it's going to work with the latest update. Thanks. :D

Andrea, rocwiff, I would hold off if I knew what you know now as far as 10.6.2 with nVidia is concerned. Lots of people are having issues after the update with certain monitors causing a freeze of/failure to load WindowServer and it doesn't seem limited to one particular NV 8xxx/9xxx card...

 

Obviously this is a big issue being seen by all; many are affected... let's try to come up with a solution quickly! :(

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

So if I understand,

 

the issue with 10.6.2 is that :

- with some nVidia GPU

- and some displays (HDMI involved ?)

the display makes WindowsServer crash at boot. = black screen

 

 

Am I right ?

Link to comment
Share on other sites
Siobhan
Siobhan
Posted
Posted
So if I understand,

 

the issue with 10.6.2 is that :

- with some nVidia GPU

- and some displays (HDMI involved ?)

the display makes WindowsServer crash at boot. = black screen

 

 

Am I right ?

Absolument, it seems you understand the issue completely. :)

Link to comment
Share on other sites
hashmet
hashmet
Posted
Posted
So if I understand,

 

the issue with 10.6.2 is that :

- with some nVidia GPU

- and some displays (HDMI involved ?)

the display makes WindowsServer crash at boot. = black screen

 

 

Am I right ?

 

I guess yes. Because of the fact that I've tried different methods (DSDT, GraphicsEnabler and NVkush) I would nearly say, that this could be a Apple problem. Has anyone experiences concerning a real Mac and dual monitors? If it works on a real mac maybe it's an Chameleon issue.

Link to comment
Share on other sites
mwkchan
mwkchan
Posted
Posted
People, it seems like a lot of us are having trouble with nvidia, post 10.6.2. In my topic nVidia 8600M freezing after 10.6.2 upgrade if HDMI monitor plugged in but not DVI I have the issue on my laptop with an 8600M GS where the built-in screen works fine, and some monitors work but others will cause a black screen on boot up, where as two (Acer AL2216W via DVI/HDMI cable and LG L204WT via same) cause no problems at all.

 

If I hook in my Acer P244w HDMI monitor or my Sony 60" KDS-60A2000 TV (both of which worked fine in 10.6.1) the screen will freeze, but I can still SSH into the laptop, and WindowServer is pegged at 99.9% CPU usage. Also, I cannot killall -HUP WindowServer; it will not reload and the only option is to hard power-off (reboot by power switch) the laptop.

 

Black screen occurs for me if these monitors are plugged in at startup as well.

 

 

Andrea, rocwiff, I would hold off if I knew what you know now as far as 10.6.2 with nVidia is concerned. Lots of people are having issues after the update with certain monitors causing a freeze of/failure to load WindowServer and it doesn't seem limited to one particular NV 8xxx/9xxx card...

 

Obviously this is a big issue being seen by all; many are affected... let's try to come up with a solution quickly! :(

 

I can confirm everything with the post! I was able to ssh my machine and found it stucks while loading up the WindowServer. I can't even issue a reboot or shutdown command. I got 2 monitors, the LG W2353V and the Philips 200WS, neither work.

Link to comment
Share on other sites
Siobhan
Siobhan
Posted
Posted
Well there is one thing I cannot believe! You have a 60" TV???!! RESPECT!
lol :(

 

Anyway, cross-post but important here too:

 

News flash:

 

I tried the VGA port with my Acer P244W (1920x1080 res) monitor over VGA -- NO FREEZE.

 

Runs perfectly at full res without any issue whatsoever. Freezes over HDMI-HDMI cable. Again, my DVI-D (DVI-HDMI cable) monitors do not cause the freeze, only HDMI-capable monitors with HDMI-HDMI cable cause the freeze (for me).

 

I can confirm everything with the post! I was able to ssh my machine and found it stucks while loading up the WindowServer. I can't even issue a reboot or shutdown command. I got 2 monitors, the LG W2353V and the Philips 200WS, neither work.
Well, technically you can issue a reboot or shutdown; they just don't happen because WindowServer absolutely refuses to quit in the hung state, so the reboot never occurs. If you even try killall -9 WindowServer (kill -9 <PID> same thing) you'll see it gets stuck in Es (WindowServer) state. I've tried looking at /var/log/windowserver.log, but it doesn't really tell me anything about why it is hanging - obviously the hang prevents any sort of logging of useful information.
Link to comment
Share on other sites
MacUser2525
MacUser2525
Posted
Posted
I tried the VGA port with my Acer P244W (1920x1080 res) monitor over VGA -- NO FREEZE.

 

Runs perfectly at full res without any issue whatsoever. Freezes over HDMI-HDMI cable. Again, my DVI-D (DVI-HDMI cable) monitors do not cause the freeze, only HDMI-capable monitors with HDMI-HDMI cable cause the freeze (for me).

 

To me that seems like it could be an issue with the AppleUpstreamUserClient.kext which controls access to protected content (HDCP) which those connections can support. I would see if deleting/renaming the .kext helps if so then get a Disabler.kext with the already mentioned .kext in its blacklist.

Link to comment
Share on other sites
mwkchan
mwkchan
Posted
Posted
lol :)

 

Anyway, cross-post but important here too:

 

News flash:

 

I tried the VGA port with my Acer P244W (1920x1080 res) monitor over VGA -- NO FREEZE.

 

Runs perfectly at full res without any issue whatsoever. Freezes over HDMI-HDMI cable. Again, my DVI-D (DVI-HDMI cable) monitors do not cause the freeze, only HDMI-capable monitors with HDMI-HDMI cable cause the freeze (for me).

 

I tried both DVI or DVI-HDMI, doesn't work. I used the NVDA Kexts from 10.6.1 and it works now. (as a workaround temporarily)

Link to comment
Share on other sites
Siobhan
Siobhan
Posted
Posted
To me that seems like it could be an issue with the AppleUpstreamUserClient.kext which controls access to protected content (HDCP) which those connections can support. I would see if deleting/renaming the .kext helps if so then get a Disabler.kext with the already mentioned .kext in its blacklist.
Whoa. That is an awesome, awesome recommendation! Trying that right now.

 

UPDATE: it didn't work - I removed the kext entirely from Extensions, rebuilt the mkext and rebooted - kextcache showed it wasn't running, but the screen hung the moment I plugged my HDMI monitor in. Thanks again for the suggestion!

 

I tried both DVI or DVI-HDMI, doesn't work. I used the NVDA Kexts from 10.6.1 and it works now. (as a workaround temporarily)

I backed up my 10.6.1 kexts; which ones did you replace in Extensions? NVDANV50hal.kext and NVDAResman.kext?

Link to comment
Share on other sites
mwkchan
mwkchan
Posted
Posted
Whoa. That is an awesome, awesome recommendation! Trying that right now.

 

UPDATE: it didn't work - I removed the kext entirely from Extensions, rebuilt the mkext and rebooted - kextcache showed it wasn't running, but the screen hung the moment I plugged my HDMI monitor in. Thanks again for the suggestion!

 

 

I backed up my 10.6.1 kexts; which ones did you replace in Extensions? NVDANV50hal.kext and NVDAResman.kext?

 

You will need to replace all 3 kexts starting with NVDA*. I suspect you could forget about 40Hal if you won't be using some old cards. Just replacing 50Hal will cause a KP. To be on the safe side, just replace all 3 kexts.

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

I can now identify clearly the incompatibility :

 

 

- If you boot 10.6.2 with a 1080p (1920x1080) HDMI 16:9 TV, plugged as main or secondary display,

you will get a black screen.

- If you plug it while the computer is running it will freeze.

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