madmodmike

I understand, but I've no problem at all with GraphicsEnabler, my only issue at the moment is to get chameleon (and therefore, the OSX loading screen with the spinning wheel) displayed at full 1920x1080, just like Clover does with PatchVBiosBytes

In my case, I've no problem at all with GE=Yes (the card works perfectly under ML, including OpenCL/CUDA), it's just an issue about the Chameleon resolution, locked to the maximum available by my vesa tables, so I suppose doing the DSDT stuff won't improve my situation, am I right?

Alex009988, on 19 March 2013 - 02:07 PM, said:

Do you know how to do that, or can you point us to the right direction, maybe linking a tutorial or something that explains this?

I've already tried editing the table from vbios dump, but with no luck (the nvidia bios has the vesa tables encrypted), is the videoBios in the DSDT equivalent to the memory patch done by Clover?

bigpoppa206, on 14 February 2013 - 09:43 PM, said:

It's the card itself, but unfortunately trying the "hard" way (dumping the video bios, finding the vesa tables location, hex editing and re-flashing) gives no significant results, having still the same, unaltered, modes after the whole procedure. Tried a few times, then gave up, then tried out of curiosity Clover, with a tutorial full of encoded strings for the search and replace, and it worked

http://www.projectos...83&#entry22683.

Looks like on the new GeForce bioses they're encrypted or encoded somewhere, and the only way is the on-the-fly search and replace like Clover does with the PatchVBiosBytes option, as the guy said on his tutorial:

Quote

Quote

That's correct, probably it uses two or more different tables depending on the output interface.

This is for instance a picture I took moments ago, using the analog output (DVI-VGA adapter), more modes, and higher resolution than digital DVI (it goes up to 1600x1200, instead of the 1280x800 available in DVI)



Unfortunately I can't find my DisplayPort-DVI adapter at the moment, but I suspect it would give me the same modes I get from the DVI output.

Sorry man but you're probably misunderstanding me, or I'm not good enough to explain myself

My problem isn't related to GraphicsEnabler, GraphicsEnabler is just a parameter that instruct Chameleon to patch stuffs AFTER you select your OSX partition and press ENTER to boot it, not before, and its only purpose is to make OSX aware of your graphics card. Only OSX, not Chameleon itself

I can get rid of it at all, or pass it as a parameter before booting OSX (writing "GraphicsEnabler=Yes" or "No" as a boot parameter), this doesn't change the fact that the Chameleon screen where you select which partition to boot (and only this), is locked to a resolution that depends on which modes are available in your VESA Table (see the screenshot later).

What happens after doesn't matter, as I said before, my OSX is working straightforward in 1920x1080 and full GPU acceleration, the problem here is before the boot process, when Chameleon loads up (and is stuck to the maximum VESA mode available, cannot go further).

Here's why I used Clover as a reference, because using the snip I quoted some posts ago, it can patch on the fly the VideoBios, allowing VESA modes unavailable in the default vbios (like 1920x1080), thus having the Bootloader screen and the boot process (with the Apple logo and the spinning wheel) to run in 1920x1080 as well instead of being limited to the maximum VESA mode available.

The problem is in the VESA Tables, which anyone can see writing the "?video" parameter (without quotes) in the Chameleon bootmenu, I've tried to hexedit the video bios and reflash it, but so far looks like the VESA Tables are hidden or encrypted somewhere else.

For reference, this is a picture I've taken from my Chameleon, the maximum VESA mode available to me at the moment is the last one.





So that's why an "on the fly search&replace", like Clover does, would be imho definitely great for Chameleon