Jump to content
14 posts in this topic

Recommended Posts

My desktop has a EVGA 8800GTX in it. I recently setup Snow Leopard on it with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]. Had no problems installing, and everything works except I can't change the resolution from 1024x768. I'm new with installing MAC os, but so far I've tried to find a kext for the 8800GTX, and used OSX86 Tools to add an EFI Graphics string, both without success.

 

I've updated to 10.6.6, which http://wiki.osx86project.org/wiki/index.ph...#Graphics_Cards says the 8800GTX is compatible with with the right EFI Graphics string. Am I doing the EFI string wrong? I did notice that OSX86 Tools is no longer being developed and is made for 10.5.

 

I would really appreciate some advice. Thanks

I used 8800GT before, EFI strings from OSX Tools are still valid, although Chamelon will do it automatically if you set GraphicsEnabler=ON. Use Lizard for Chameleon, which is basically GUI for chameleon.

 

NVenabler is slower than EFI.

 

Thanks,

an1r0n

8800GT and 8800GTX are COMPLETELY different cards. They have a different codenames (G92 vs G80) and are produced using different processes (65 vs 90). Therefore EFI string for 8800GTX doesn't work as good as it works with 8800GT. So if an EFI string works with 8800GT, it doesn't necessary mean that an EFI string will also work with 8800GTX (not with all hardware configurations at least).

Thank you for clarification, but if you have read what I wrote with much greater detail you would have noticed that I was confirming that strings from OSX tools still work, even custom ones. I did not say "use 8800GT string for 8800GTX".

 

Don't be smart ass, just read the full sentence.

...I did not say "use 8800GT string for 8800GTX"...
Neither did I. :)

 

My point is that cpirius was asking about his 8800GTX card (not 8800GT).

 

Also I've stated (that was not so clear from the sentence though) that in MY PC, with hardware I HAVE, an EFI string (from OSX86Tools; nor custom, neither build-in) and Chameleon buil-in graphics enabler DON'T work properly with 8800GTX/Ultra card (I have). Therefore in MY case only Nvenabler has worked, that's it. I don't say EFI string or Graphics enabler doesn't work with ALL 8800GTX cards (or with any other card for that matter), it just doesn't work in my configuration. So it is possible that cpirius might have the same situation.

 

Other cards may work perfectly (including 8800GT which is used in MacPro) with EFI string/Chameleon - I don't doubt that. On the contrary I know some cards do work. But no system is alike.

 

And on the subject...

OSX86Tools inserts EFI string to /Library/Preferences/SystemConfiguration/com.apple.Boot.plist while if you use Chameleon, com.apple.Boot.plist is loaded from /Extra folder (the one that is placed to /Extra is used to override the stock one in /Library/Preferences/SystemConfiguration (those you leave the stock one in peace)). Therefore if you use OSX86Tools to insert an EFI string, it will not work with Chameleon, 'cos the string should be inserted to com.apple.Boot.plist located in /Extra.

 

You can do it manually or using Lizard for Chameleon as an1r0n has suggested.

NVenabler is slower than EFI.

It is not possible for device property injection to affect graphics speed or quality. Some injection methods may make "more stuff" work, such as analog TV-out, dual displays or HDMI audio, but it is not technically possible for one injection method to be "faster" than another. GraphicsEnabler, device properties strings, NVEnabler and other injector.kexts are not drivers.

 

If the card is not performing well, you're looking at a video card driver or power management issue, or injection is not working at all.

Hey Gringo,

 

I actually had 8600GT and {censored}load of problems because vga port being primary and dvi being secondary. I found out that GUI is a lot faster on vga, because it's primary port (next to motherboard). I had to find a solution to make Mac OS think that DVI is primary and VGA is secondary so I will have much better picture (vga signal was lesser quality than dvi). And guess what, ony NVenabler helped me! With efi strings that couldn't be done.

 

But I did notice a 20% speed decrease in performance while using nvenabler kext instead of efi string. Drivers were same when I was using EFI strings and later NVenabler, so it mostly depends of configuration of the kext. After i just bought 8800GT which had dual dvi ports and solved all speed problems with efi string.

 

I must disagree with your statement that all these methods provide the same speed, maybe same result but definitely not the speed. The less kexts you have, the better, and EFI strings is the most natural way if you have supported graphics card. I really don't want this to become some argument, but you'll agree with me that in some cases NV enabler is faster than EFI strings and in other cases EFI is the one that's faster.

 

Cheers,

an1r0n

If you want to switch the order of your display ports, inject a custom NVCAP value that does that. All current injection methods can do it, even Chameleon's GraphicsEnabler with NVCAP= flag in com.apple.Boot.plist.

 

Whether you use injector.kext, GraphicsEnabler, DSDT gfx0 device or device properties string, the data that gets injected all ends up in the same place, the IORegistry. Once that is done, the injection method has done its job, it's not running all the time like a sound driver for example. This is one of the reasons why it doesn't matter if your injection method is via kernel extension or device properties string or whatever you like to use. If you look at it this way, one method is not superior to the other. Of course one method may benefit from more tweaking.

In the end you must make sure that the properties that get injected are adequate for your particular hardware. All reasonably modern injection methods can be tweaked to do that, NVEnabler via its info.plist (properties to add key) GraphicsEnabler via com.apple.Boot.plist and if using gfx0 DSDT device or device-properties string you can simply add any properties you want to inject to your heart's content.

Of course, depending on your hardware and skills and/or level of curiosity it might be easier just to try different injection methods rather than tweaking your existing one, until you end up with the results you want.

 

I maintain that as long as the appropriate properties are injected, difference in performance is not technically possible.

Hey, I just want to point out that currently the G80 cards (8800GTS 320/640, 8800GTX, and 8800 Ultra) have a bug in drivers in DP4. You need to remove the 2 kexts for older cards (NVDAResmanG7xxx.kext and GeForce7xxx.kext) and then these cards work great in Lion.

 

I read this in a post here and have since confirmed it.

 

If anyone is in a position to report DP4 bugs to Apple, please mention this.

 

Basically, DP4 tries to load both the G70 and G80 kexts and fails.

Hey, I just want to point out that currently the G80 cards (8800GTS 320/640, 8800GTX, and 8800 Ultra) have a bug in drivers in DP4. You need to remove the 2 kexts for older cards (NVDAResmanG7xxx.kext and GeForce7xxx.kext) and then these cards work great in Lion.

 

I read this in a post here and have since confirmed it.

 

If anyone is in a position to report DP4 bugs to Apple, please mention this.

 

Basically, DP4 tries to load both the G70 and G80 kexts and fails.

 

Wow, didn't know that! I was planning to return my old 8800GT when Lion comes, in case 460 GTX doesn't get working. Thanks!

×
×
  • Create New...