ATI and possibly nVIDIA resolution patch (based on prasys' 915resolution port)

[CEOS]

I just try it and it brings back the GUi .....at least somehow
my screens aspect is detected wrong
4/3 instead of 16/9
i just can see a really small area  of the GUI (a part of the upper left corner)
and chameleons graphic enabler is screwed.
just give me a really low resolution (something like 200x200)

will post the debug output tomorrow, it's very late now and i have school at 8:00 tomorrow....

[Azimutz]

@lebidou, no changes on GMA so, this is just testing with ATI.
Debug info working fine, only the duplicates remain.. i already have them commented out on "my" build.
Resolution change also works, but not without weirdness. I only tried with 1280x800x32; it changes the resolution but the menu gets like if we were on text mode, up & down arrows instead of left & right, "booting foreign OS" messages showing, that stuff. Using Tab to change to text mode, there's no get back to graphics mode. Otherwise booter works fine. At login native resolution kicks in.

About the theme stuff... as you already noticed i don't build with embedtheme and i always use the Theme key on Boot.plist. It's just a choice i made a while ago; the Themes folder is so small that i don't see a reason to make "boot" so big. Also, there were some reports of problems caused by embedding theme or not, when i was testing BootCDMaker, i think. Have to check.. me, i never had much problems or anything that pointed directly for Themes as cause of problems.

[lebidou]

Hum... Weird as you say, it seemed to be working for me, but I'll do some more testing, to see what I forgot.

At login, native resolution kick in because your graphics driver take over, that is normal and expected behaviour.

For the theme stuff, I think that it wasn't a problem with r684 because it required to be compiled with embedded theme to have themes. Now I compile without it also, but the problem is that if you don't have specified a theme, GUI won't load. That's why GUI wouldn't show up for CEOS (I hope so).

The duplicate thing will be gone in future releases.

EDIT: Just ran a few tests, and left & right arrows are ok for me, I don't have any booting foreign OS messages, the only thing I can confirm is that going from text to graphics mode is broken. Still looking

[Azimutz]

Hum.. nice info. I knew part of that Themes stuff but still had doubts, your answer just clarified them.

Yeah.. it's weird.. graphics mode still works but it seems that text mode behavior overlaps graphics.
Menu is still usable, just weird. And if i try to change resolution again also doesn't work... or type another stuff.
Will test more later if needed... still have a ton of stuff to clean from these past couple of weeks at least they've been educational!

[lebidou]

The Mode changing feature should be fixed. This is a general, not-vendor-dependent feature. It should bring no changes for any cards, apart from the fact that you can set your mode before booting.

Although, while playing a bit with it, I noticed that some modes are set in Chameleon but default 1024x768 is back when launching the kernel. Modes already supported by your monitor should be fine though (in my case 1280x800, 1024x640 and 800x500 are ok, but 1280x720 or 1152x720 won't).

@CEOS, I missed your post, just saw it, sorry. The Graphics enabler should not be screwed, because the patch doesn't concern GraphicsEnabler at all. You should check your plist maybe you mistyped something. I can't wait for the output.

[Azimutz]

@lebidou, latest news: "Graphics Mode" change fine, graphics mode->text mode fine, no changes on the rest. They weren't expected anyway.

[lebidou]

Update for NVIDIA only : I refined a bit CVT Timings (again), for the second table they almost fit perfectly with the original table, for the first one, values are closer. It takes in count the frequency of the mode we overwrite, so the pixel clock should be the same (as there is no pixel clock value in the second table, it's either calculated or fixed within the vbios.)
The first modes of the second table aren't patched anymore (the 320x200 ones.)

I'm wondering if, despite the patch, the actual mode it sets is the original one, and not the resized one. From CEOS' photos, the first mode of second table is patched with native mode (320x200 -> 1920x1080), and the mode it is about to set is this one (#271, ie 0x10F is standard 320x200x32@60Hz). CEOS reported that the set mode was 200x200 like (probably 320x200 actually.)
The one time it (almost) worked, the patched mode was 1920x1200, so it seemed good! Well... with a 120 pixels garbled band at the bottom, because buffer's height was 1080.
Eberts had a band too because it patched the mode from 1280x1024 to 1280x800. The buffer was 1280x800, but the actual mode was still 1280x1024!
I'm not sure I'm explaining it right...

So CEOS, I hope that the new one is working better, and I'm waiting for at least as much photos as the last time to posted. having so much info at a time really made my day. (I don't need much...)

@Azimutz, I don't think I can do much more about GMA, I went on Andy's Thread on InsanelyMac about is patch for 945GMA (wich includes 915resolution from prasys and gma graphicsEnabler from nawcom.) It apparently does not work for everyone. So I guess I'm stuck at the same point as he is.

[CEOS]

seems things get worse with the new version.
here is the debug output: http://rapidshare.com/files/368441485/Archiv.zip.html


no gui and i'm unable to boot OSX with it....

[lebidou]

Ok, I found a typo that made the 320 modes and below to be patched while it shouldn't. However, what I'm more concerned about is the resolution it got. Could you post your Boot.plist again?
It behaves as if there were no Graphics Mode key, and thus, try to set a 1024x768 mode because it detected the insane mode from your EDID. This shouldn't happen.

I have updated the files in first post with fixed typo, but since the resolution isn't detected right, I don't expect it to work ok.

[CEOS]

I don't expect it to work ok.

you was right.
it totally doesn't work.

just give me this screen, than my pc restarts: http://i40.tinypic.com/oid3lu.jpgi tried with and without theme.

this is the requested boot.plist:

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Default Partition</key>
<string>hd(2,2)</string>
<key>EthernetBuiltIn</key>
<string>yes</string>
<key>Graphics Mode</key>
<string>1920x1080x32</string>
<key>GraphicsEnabler</key>
<string>yes</string>
<key>Hide Partition</key>
<string>hd(3,1) [hd(4,1)]</string>
<key>PCIRootUID</key>
<string>1</string>
<key>Timeout</key>
<string>5</string>
<key>Theme</key>
<string>Default</string>
</dict>
</plist>


[THe KiNG]

   <key>Graphics Mode</key>
   <string>1920x1080x32</string>

That is wrong IMHO...what kind of display is that, is it a TV?
It should be 1920x1200x32 if is a normal PC display.

[Azimutz]

According to http://en.wikipedia.org/wiki/Display_resolution it's a 1080 Full HD resolution.

@lebidou, i have two annoyances, one small and the other not so:

- the normal booter version always waits for "Press any key.." before getting to GUI. Small annoyance...
- the debug version, still hangs like i explain on post #173. I can't boot with debug version! Big annoyance...

Edit: ok, the "big annoyance" has nothing to do with your code as i suspected. Booted without "USBBusFix=y" and problem gone. I reported this a while ago on the repo (Chameleon, issue #7)... it seems the usb bus were the wireless keyboard/mouse it's connected, gets disconnected at this point if the boot process pauses at that point?!.. will try to mess a bit with this...

About the GMA... as i already mentioned, i don't paid much attention to it before because of the comments i read and the fact that i don't use it much these days as the ATI is working fine; using it now to help test this patch. Now, i know i read some explanation on why this doesn't work for me, but i can't seem to find it now
What puzzles me is this desktop GMA950 is so easy to patch with dsdt.. the card is already supported by the system?! QE/CI works ootb. Will try to find more info on this...

Edit: i knew i'd read this some were So the reason why it's not so simple to make desktop GMA's to work with Graphics Enabler is explained here, at the end of the first post by Nawcom:
http://forum.voodooprojects.org/index.php/topic,1029.0.html
It's a fact, my dsdt has no entries for graphics.

[THe KiNG]

According to http://en.wikipedia.org/wiki/Display_resolution it's a 1080 Full HD resolution.

I know that, but dosen't mean is native monitor resolution.
On my 24" Samsung display native resolution is 1920*1200 and yes is full HD compliant.
But we are talking about diff thing here, and that boot.plist entry can explain the bad aspect ratio.
But i can be wrong, I'm not such a display expert...
Just my 2 cents.

[Azimutz]

Yeah, you can be right there, The King.. just read a bit more. I'm also not a display expert, in fact it confuses me a bit Thanks for your input.

[CEOS]

That is wrong IMHO...what kind of display is that, is it a TV?
It should be 1920x1200x32 if is a normal PC display.

you are right.
it's a TV.
i connect it to my pc using a DVI/HDMI swith.

btw, 1920x1080 is HDTV.
the HD logo on a PC monitor just says that the device is able to show HD content which was recorded in 1920x1080 through up or downscaling