[GUIDE] NEW Snow Leopard Retail on ASUS P6T Deluxe V1&V2

fc bayern · March 1, 2010

EDIT:
work!

Fabio

It works...just to know...

scott_donald · March 1, 2010

Ok, this is small guide how to use new DSDT from Fabio with EFI string.

Download new DSDT from Fabio's first page.

Download GFXUtil.

Create folder on your Desktop and name it "EFI"

Put inside the GFXUtil and the EFI.plist (from Fabio).

Change EFI.plist if you have other graphics card than nVidia GTX 260.

Open Terminal.

Write : cd Desktop/EFI/

Write : ./gfxutil -i xml -o hex ./EFI.plist ./EFI.hex

Quit Terminal.

Open EFI.hex (in EFI folder on Desktop) with TextEdit, select all and copy.

Open yours com.apple.Boot.plist

Add this before "</dict>" line

<key>device-properties</key>

<string> (paste here your EFI string (from EFI.hex) ) </string>

Save com.apple.Boot.plist.

And use new DSDT from Fabio.

ok i edited teh efi.plist form ifabio but all i did was change the 260 to 285... which is what i have...

then used terminal to make the hex...

now scared to edit the apple... file....

did i do it right???

ErmaC · March 1, 2010

ok i edited teh efi.plist form ifabio but all i did was change the 260 to 285... which is what i have...

then used terminal to make the hex...

now scared to edit the apple... file....

did i do it right???

hi scott donald

you have a little utility called IORegistryExplorer ? (you can find it in Xcode or Evo-DSDT)

If yes save your registry info and post here... we help you to extract the exact data you need to insert in the plist file.

Fabio

scott_donald · March 1, 2010

hi scott donald

you have a little utility called IORegistryExplorer ? (you can find it in Xcode or Evo-DSDT)

If yes save your registry info and post here... we help you to extract the exact data you need to insert in the plist file.

Fabio

here i think...

http://www.megaupload.com/?d=PE50VIQC

ErmaC · March 1, 2010

here i think...

http://www.megaupload.com/?d=PE50VIQC

Now I go to work...

tonight I try extract the data...

or... if someone do it too are welcome!

Fabio

dgobe · March 1, 2010

ok i edited teh efi.plist form ifabio but all i did was change the 260 to 285... which is what i have...

then used terminal to make the hex...

now scared to edit the apple... file....

did i do it right???

Don't forget that there is the config=<alternate config file> boot flag.

e.g. config=/Extra/com.apple.Scott_donald.plist

....and

DSDT=<alternate> .e.g. /Extra/fabioslatestandgreatest.aml

SMBIOS=<alternate> e.g. /Extra/smbiostest.plist

Always use those instead of replacing your working files, if something goes wrong, you can just reboot.

scott_donald · March 1, 2010

Now I go to work...
tonight I try extract the data...

or... if someone do it too are welcome!

Fabio

thanks ifabio appreciated...

Don't forget that there is the config=<alternate config file> boot flag.
e.g. config=/Extra/com.apple.Scott_donald.plist

....and

DSDT=<alternate> .e.g. /Extra/fabioslatestandgreatest.aml

SMBIOS=<alternate> e.g. /Extra/smbiostest.plist

Always use those instead of replacing your working files, if something goes wrong, you can just reboot.

hmm think i will just wait for ifabio to do... thanks thought... will look through and pay around...

kn6600 · March 1, 2010

Hello Fabio,

I have problem to get working Snow Leopard with two GTX 260 and EFI string.

Could you give me some advise please.

This is my working DSDT ( DSDT 3.1.2 with GFX injected) and my IOReg from that.

With this I have working system but graphics fan are spinning to the max after wake from sleep.

Thanks in advance,

Kristijan

dsdt.aml.zip

Kristijan_Mac_Pro_ioreg.zip

pOxbOx · March 1, 2010

What is the difference actually between GFX Injection and EFI Strings ?

I'm not totally sure about that stuff, right now I'm using the GraphicEnabler parameter in Chameleon and it's working fine.

It would be nice if anybody have any precisions on that, i'm kinda confused right now :S

Thanks guy, you're doing a great work !

Edit--

I currently have a GTX 275..

ErmaC · March 2, 2010

...

GeForce GTX 285 1Gb (0x10de 0x05e3)

I add the com.apple.Boot.plist for you GFX in the first page you can use it with the DSDT EFI Version

anyway

how said by dgobe is a good method to test the new DSDT+c.a.B.p

Don't forget that there is the config= boot flag.
e.g. config=/Extra/com.apple.Scott_donald.plist

....and

DSDT= .e.g. /Extra/fabioslatestandgreatest.aml

SMBIOS= e.g. /Extra/smbiostest.plist

Always use those instead of replacing your working files, if something goes wrong, you can just reboot.

Fabio

Hello Fabio,

I have problem to get working Snow Leopard with two GTX 260 and EFI string.

Could you give me some advise please.

This is my working DSDT ( DSDT 3.1.2 with GFX injected) and my IOReg from that.

With this I have working system but graphics fan are spinning to the max after wake from sleep.

Thanks in advance,

Kristijan

I add a c.a.B.p for your 2 GFX card.... tell me if work 2 GFX is new for me

If works pls post a screen shot of system profiler PCI card

Fabio

What is the difference actually between GFX Injection and EFI Strings ?
I'm not totally sure about that stuff, right now I'm using the GraphicEnabler parameter in Chameleon and it's working fine.

It would be nice if anybody have any precisions on that, i'm kinda confused right now :S

Thanks guy, you're doing a great work !

Edit--

I currently have a GTX 275..

there is 4 or more method for get work our GFX card

1) the GraphicsEnabler=y in the com.apple.Boot.plist (This is provided by the boot)

2) the DSDT injection works well too but need a "personal" DSDT

3) the EFI Strings in com.apple.Boot.plist (a long string)

4) the "driver" the injector like nvidia inject and ati inject (I use it the first time in leo 10.5.x)

Difference...?

Differences between the second and third there are not many, but as said before the strings are more manageable, and the DSDT via injection requires a custom DSDT for each "user" What I try to do is lighten the DSDT .... passing the work to the EFI strings, this is one of the reasons for which I prefer EFI strings, if you want to make your life simpler using the enabler of the boot

Fabio

dgobe · March 2, 2010

there is 4 method for get work our GFX card
1) the GraphicsEnabler=y in the com.apple.Boot.plist (This is provided by the boot)

2) the DSDT injection works well too but need a "personal" DSDT

3) the EFI Strings in com.apple.Boot.plist (a long string)

4) Injector kext :-)

Difference...?

Differences between the second and third there are not many, but as said before the strings are more manageable, and the DSDT via injection requires a custom DSDT for each "user" What I try to do is lighten the DSDT .... passing the work to the EFI strings, this is one of the reasons for which I prefer EFI strings, if you want to make your life simpler using the enabler of the boot

Fabio

Fabio is right, they are all different ways of injecting the right values into your ioregistry. It would be nice if the boot code was updated to look for a devprops.plist instead of having to convert to hex and put a device-properties key in c.a.B.p. That way you could just edit a plain old XML file with the Plist Editor or any other text editor and be done with it....I think that's one of the things that's harder than it needs to be.

EFI strings are an advantage when the code in "boot"(for GraphicsEnabler=y) doesn't do the right thing for your card, is unable to handle multiple cards or your card is unknown but still supported by one of the vanilla kexts. In looking at the source for Chameleon(and others) you can see the lists of known cards:

ATI cards
{ 0x10029589, "ATI Radeon 2600 Series"} ,
{ 0x10029588, "ATI Radeon 2600 Series"} ,
{ 0x100294C3, "ATI Radeon 2400 Series"} ,
{ 0x100294C4, "ATI Radeon 2400 Series"} ,
{ 0x100294C6, "ATI Radeon 2400 Series"} ,
{ 0x10029400, "ATI Radeon 2900 Series"} ,
{ 0x10029405, "ATI Radeon 2900GT Series"} ,
{ 0x10029581, "ATI Radeon 2600 Series"} ,
{ 0x10029583, "ATI Radeon 2600 Series"} ,
{ 0x10029586, "ATI Radeon 2600 Series"} ,
{ 0x10029587, "ATI Radeon 2600 Series"} ,
{ 0x100294C9, "ATI Radeon 2400 Series"} ,
{ 0x10029501, "ATI Radeon 3800 Series"} ,
{ 0x10029505, "ATI Radeon 3800 Series"} ,
{ 0x10029515, "ATI Radeon 3800 Series"} ,
{ 0x10029507, "ATI Radeon 3800 Series"} ,
{ 0x10029500, "ATI Radeon 3800 Series"} ,
{ 0x1002950F, "ATI Radeon 3800X2 Series"} ,
{ 0x100295C5, "ATI Radeon 3400 Series"} ,
{ 0x100295C7, "ATI Radeon 3400 Series"} ,
{ 0x100295C0, "ATI Radeon 3400 Series"} ,
{ 0x10029596, "ATI Radeon 3600 Series"} ,
{ 0x10029590, "ATI Radeon 3600 Series"} ,
{ 0x10029599, "ATI Radeon 3600 Series"} ,
{ 0x10029597, "ATI Radeon 3600 Series"} ,
{ 0x10029598, "ATI Radeon 3600 Series"} ,
{ 0x10029442, "ATI Radeon 4850 Series"} ,
{ 0x10029440, "ATI Radeon 4870 Series"} ,
{ 0x1002944C, "ATI Radeon 4830 Series"} ,
{ 0x10029460, "ATI Radeon 4890 Series"} ,
{ 0x10029462, "ATI Radeon 4890 Series"} ,
{ 0x10029441, "ATI Radeon 4870X2 Series"} ,
{ 0x10029443, "ATI Radeon 4850X2 Series"} ,
{ 0x10029444, "ATI Radeon 4800 Series"} ,
{ 0x10029446, "ATI Radeon 4800 Series"} ,
{ 0x1002944E, "ATI Radeon 4730 Series"} ,
{ 0x10029450, "ATI Radeon 4800 Series"} ,
{ 0x10029452, "ATI Radeon 4800 Series"} ,
{ 0x10029456, "ATI Radeon 4800 Series"} ,
{ 0x1002944A, "ATI Radeon 4800 Mobility Series"} ,
{ 0x1002945A, "ATI Radeon 4800 Mobility Series"} ,
{ 0x1002945B, "ATI Radeon 4800 Mobility Series"} ,
{ 0x1002944B, "ATI Radeon 4800 Mobility Series"} ,
{ 0x10029490, "ATI Radeon 4600 Series"} ,
{ 0x10029498, "ATI Radeon 4600 Series"} ,
{ 0x1002949E, "ATI Radeon 4600 Series"} ,
{ 0x10029480, "ATI Radeon 4600 Series"} ,
{ 0x10029488, "ATI Radeon 4600 Series"} ,
{ 0x10029540, "ATI Radeon 4500 Series"} ,
{ 0x10029541, "ATI Radeon 4500 Series"} ,
{ 0x1002954E, "ATI Radeon 4500 Series"} ,
{ 0x10029552, "ATI Radeon 4300 Mobility Series"} ,
{ 0x10029553, "ATI Radeon 4500 Mobility Series"} ,
{ 0x1002954F, "ATI Radeon 4300 Series"}
}

NVIDIA cards
{ 0x10DE0040, "GeForce 6800 Ultra" },
{ 0x10DE0041, "GeForce 6800" },
{ 0x10DE0042, "GeForce 6800 LE" },
{ 0x10DE0043, "GeForce 6800 XE" },
{ 0x10DE0044, "GeForce 6800 XT" },
{ 0x10DE0045, "GeForce 6800 GT" },
{ 0x10DE0046, "GeForce 6800 GT" },
{ 0x10DE0047, "GeForce 6800 GS" },
{ 0x10DE0048, "GeForce 6800 XT" },
{ 0x10DE004E, "Quadro FX 4000" },
{ 0x10DE0090, "GeForce 7800 GTX" },
{ 0x10DE0091, "GeForce 7800 GTX" },
{ 0x10DE0092, "GeForce 7800 GT" },
{ 0x10DE0093, "GeForce 7800 GS" },
{ 0x10DE0095, "GeForce 7800 SLI" },
{ 0x10DE0098, "GeForce Go 7800" },
{ 0x10DE0099, "GeForce Go 7800 GTX" },
{ 0x10DE009D, "Quadro FX 4500" },
{ 0x10DE00C0, "GeForce 6800 GS" },
{ 0x10DE00C1, "GeForce 6800" },
{ 0x10DE00C2, "GeForce 6800 LE" },
{ 0x10DE00C3, "GeForce 6800 XT" },
{ 0x10DE00C8, "GeForce Go 6800" },
{ 0x10DE00C9, "GeForce Go 6800 Ultra" },
{ 0x10DE00CC, "Quadro FX Go1400" },
{ 0x10DE00CD, "Quadro FX 3450/4000 SDI" },
{ 0x10DE00CE, "Quadro FX 1400" },
{ 0x10DE0140, "GeForce 6600 GT" },
{ 0x10DE0141, "GeForce 6600" },
{ 0x10DE0142, "GeForce 6600 LE" },
{ 0x10DE0143, "GeForce 6600 VE" },
{ 0x10DE0144, "GeForce Go 6600" },
{ 0x10DE0145, "GeForce 6610 XL" },
{ 0x10DE0146, "GeForce Go 6600 TE/6200 TE" },
{ 0x10DE0147, "GeForce 6700 XL" },
{ 0x10DE0148, "GeForce Go 6600" },
{ 0x10DE0149, "GeForce Go 6600 GT" },
{ 0x10DE014C, "Quadro FX 550" },
{ 0x10DE014D, "Quadro FX 550" },
{ 0x10DE014E, "Quadro FX 540" },
{ 0x10DE014F, "GeForce 6200" },
{ 0x10DE0160, "GeForce 6500" },
{ 0x10DE0161, "GeForce 6200 TurboCache(tm)" },
{ 0x10DE0162, "GeForce 6200SE TurboCache(tm)" },
{ 0x10DE0163, "GeForce 6200 LE" },
{ 0x10DE0164, "GeForce Go 6200" },
{ 0x10DE0165, "Quadro NVS 285" },
{ 0x10DE0166, "GeForce Go 6400" },
{ 0x10DE0167, "GeForce Go 6200" },
{ 0x10DE0168, "GeForce Go 6400" },
{ 0x10DE0169, "GeForce 6250" },
{ 0x10DE016A, "GeForce 7100 GS" },
{ 0x10DE0191, "GeForce 8800 GTX" },
{ 0x10DE0193, "GeForce 8800 GTS" },
{ 0x10DE0194, "GeForce 8800 Ultra" },
{ 0x10DE019D, "Quadro FX 5600" },
{ 0x10DE019E, "Quadro FX 4600" },
{ 0x10DE01D1, "GeForce 7300 LE" },
{ 0x10DE01D3, "GeForce 7300 SE" },
{ 0x10DE01D6, "GeForce Go 7200" },
{ 0x10DE01D7, "GeForce Go 7300" },
{ 0x10DE01D8, "GeForce Go 7400" },
{ 0x10DE01D9, "GeForce Go 7400 GS" },
{ 0x10DE01DA, "Quadro NVS 110M" },
{ 0x10DE01DB, "Quadro NVS 120M" },
{ 0x10DE01DC, "Quadro FX 350M" },
{ 0x10DE01DD, "GeForce 7500 LE" },
{ 0x10DE01DE, "Quadro FX 350" },
{ 0x10DE01DF, "GeForce 7300 GS" },
{ 0x10DE0211, "GeForce 6800" },
{ 0x10DE0212, "GeForce 6800 LE" },
{ 0x10DE0215, "GeForce 6800 GT" },
{ 0x10DE0218, "GeForce 6800 XT" },
{ 0x10DE0221, "GeForce 6200" },
{ 0x10DE0222, "GeForce 6200 A-LE" },
{ 0x10DE0240, "GeForce 6150" },
{ 0x10DE0241, "GeForce 6150 LE" },
{ 0x10DE0242, "GeForce 6100" },
{ 0x10DE0244, "GeForce Go 6150" },
{ 0x10DE0247, "GeForce Go 6100" },
{ 0x10DE0290, "GeForce 7900 GTX" },
{ 0x10DE0291, "GeForce 7900 GT" },
{ 0x10DE0292, "GeForce 7900 GS" },
{ 0x10DE0298, "GeForce Go 7900 GS" },
{ 0x10DE0299, "GeForce Go 7900 GTX" },
{ 0x10DE029A, "Quadro FX 2500M" },
{ 0x10DE029B, "Quadro FX 1500M" },
{ 0x10DE029C, "Quadro FX 5500" },
{ 0x10DE029D, "Quadro FX 3500" },
{ 0x10DE029E, "Quadro FX 1500" },
{ 0x10DE029F, "Quadro FX 4500 X2" },
{ 0x10DE0301, "GeForce FX 5800 Ultra" },
{ 0x10DE0302, "GeForce FX 5800" },
{ 0x10DE0308, "Quadro FX 2000" },
{ 0x10DE0309, "Quadro FX 1000" },
{ 0x10DE0311, "GeForce FX 5600 Ultra" },
{ 0x10DE0312, "GeForce FX 5600" },
{ 0x10DE0314, "GeForce FX 5600XT" },
{ 0x10DE031A, "GeForce FX Go5600" },
{ 0x10DE031B, "GeForce FX Go5650" },
{ 0x10DE031C, "Quadro FX Go700" },
{ 0x10DE0324, "GeForce FX Go5200" },
{ 0x10DE0325, "GeForce FX Go5250" },
{ 0x10DE0326, "GeForce FX 5500" },
{ 0x10DE0328, "GeForce FX Go5200 32M/64M" },
{ 0x10DE032A, "Quadro NVS 55/280 PCI" },
{ 0x10DE032B, "Quadro FX 500/600 PCI" },
{ 0x10DE032C, "GeForce FX Go53xx Series" },
{ 0x10DE032D, "GeForce FX Go5100" },
{ 0x10DE0330, "GeForce FX 5900 Ultra" },
{ 0x10DE0331, "GeForce FX 5900" },
{ 0x10DE0332, "GeForce FX 5900XT" },
{ 0x10DE0333, "GeForce FX 5950 Ultra" },
{ 0x10DE0334, "GeForce FX 5900ZT" },
{ 0x10DE0338, "Quadro FX 3000" },
{ 0x10DE033F, "Quadro FX 700" },
{ 0x10DE0341, "GeForce FX 5700 Ultra" },
{ 0x10DE0342, "GeForce FX 5700" },
{ 0x10DE0343, "GeForce FX 5700LE" },
{ 0x10DE0344, "GeForce FX 5700VE" },
{ 0x10DE0347, "GeForce FX Go5700" },
{ 0x10DE0348, "GeForce FX Go5700" },
{ 0x10DE034C, "Quadro FX Go1000" },
{ 0x10DE034E, "Quadro FX 1100" },
{ 0x10DE0391, "GeForce 7600 GT" },
{ 0x10DE0392, "GeForce 7600 GS" },
{ 0x10DE0393, "GeForce 7300 GT" },
{ 0x10DE0394, "GeForce 7600 LE" },
{ 0x10DE0395, "GeForce 7300 GT" },
{ 0x10DE0397, "GeForce Go 7700" },
{ 0x10DE0398, "GeForce Go 7600" },
{ 0x10DE0399, "GeForce Go 7600 GT"},
{ 0x10DE039A, "Quadro NVS 300M" },
{ 0x10DE039B, "GeForce Go 7900 SE" },
{ 0x10DE039C, "Quadro FX 550M" },
{ 0x10DE039E, "Quadro FX 560" },
{ 0x10DE0400, "GeForce 8600 GTS" },
{ 0x10DE0401, "GeForce 8600 GT" },
{ 0x10DE0402, "GeForce 8600 GT" },
{ 0x10DE0403, "GeForce 8600 GS" },
{ 0x10DE0404, "GeForce 8400 GS" },
{ 0x10DE0405, "GeForce 9500M GS" },
{ 0x10DE0407, "GeForce 8600M GT" },
{ 0x10DE0408, "GeForce 9650M GS" },
{ 0x10DE0409, "GeForce 8700M GT" },
{ 0x10DE040A, "Quadro FX 370" },
{ 0x10DE040B, "Quadro NVS 320M" },
{ 0x10DE040C, "Quadro FX 570M" },
{ 0x10DE040D, "Quadro FX 1600M" },
{ 0x10DE040E, "Quadro FX 570" },
{ 0x10DE040F, "Quadro FX 1700" },
{ 0x10DE0420, "GeForce 8400 SE" },
{ 0x10DE0421, "GeForce 8500 GT" },
{ 0x10DE0422, "GeForce 8400 GS" },
{ 0x10DE0423, "GeForce 8300 GS" },
{ 0x10DE0424, "GeForce 8400 GS" },
{ 0x10DE0425, "GeForce 8600M GS" },
{ 0x10DE0426, "GeForce 8400M GT" },
{ 0x10DE0427, "GeForce 8400M GS" },
{ 0x10DE0428, "GeForce 8400M G" },
{ 0x10DE0429, "Quadro NVS 140M" },
{ 0x10DE042A, "Quadro NVS 130M" },
{ 0x10DE042B, "Quadro NVS 135M" },
{ 0x10DE042C, "GeForce 9400 GT" },
{ 0x10DE042D, "Quadro FX 360M" },
{ 0x10DE042E, "GeForce 9300M G" },
{ 0x10DE042F, "Quadro NVS 290" },
{ 0x10DE05E0, "GeForce GTX 295" },
{ 0x10DE05E1, "GeForce GTX 280" },
{ 0x10DE05E2, "GeForce GTX 260" },
{ 0x10DE05E3, "GeForce GTX 285" },
{ 0x10DE05E6, "GeForce GTX 275" },
{ 0x10DE0600, "GeForce 8800 GTS 512" },
{ 0x10DE0602, "GeForce 8800 GT" },
{ 0x10DE0604, "GeForce 9800 GX2" },
{ 0x10DE0605, "GeForce 9800 GT" },
{ 0x10DE0606, "GeForce 8800 GS" },
{ 0x10DE0609, "GeForce 8800M GTS" },
{ 0x10DE060C, "GeForce 8800M GTX" },
{ 0x10DE060D, "GeForce 8800 GS" },
{ 0x10DE0610, "GeForce 9600 GSO" },
{ 0x10DE0611, "GeForce 8800 GT" },
{ 0x10DE0612, "GeForce 9800 GTX" },
{ 0x10DE0613, "GeForce 9800 GTX+" },
{ 0x10DE0614, "GeForce 9800 GT" },
{ 0x10DE061A, "Quadro FX 3700" },
{ 0x10DE061C, "Quadro FX 3600M" },
{ 0x10DE0622, "GeForce 9600 GT" },
{ 0x10DE0623, "GeForce 9600 GS" },
{ 0x10DE0626, "GeForce GT 130" },
{ 0x10DE0627, "GeForce GT 140" },
{ 0x10DE0628, "GeForce 9800M GTS" },
{ 0x10DE062A, "GeForce 9700M GTS" },
{ 0x10DE062C, "GeForce 9800M GTS" },
{ 0x10DE0640, "GeForce 9500 GT" },
{ 0x10DE0641, "GeForce 9400 GT" },
{ 0x10DE0642, "GeForce 8400 GS" },
{ 0x10DE0643, "GeForce 9500 GT" },
{ 0x10DE0644, "GeForce 9500 GS" },
{ 0x10DE0645, "GeForce 9500 GS" },
{ 0x10DE0646, "GeForce GT 120" },
{ 0x10DE0647, "GeForce 9600M GT" },
{ 0x10DE0648, "GeForce 9600M GS" },
{ 0x10DE0649, "GeForce 9600M GT" },
{ 0x10DE064B, "GeForce 9500M G" },
{ 0x10DE065B, "GeForce 9400 GT" },
{ 0x10DE06E1, "GeForce 9300 GS" },
{ 0x10DE06E4, "GeForce 8400 GS" },
{ 0x10DE06E5, "GeForce 9300M GS" },
{ 0x10DE06E8, "GeForce 9200M GS" },
{ 0x10DE06E9, "GeForce 9300M GS" },
{ 0x10DE06EA, "Quadro NVS 150M" },
{ 0x10DE06EB, "Quadro NVS 160M" },
{ 0x10DE087D, "ION 9400M" },
{ 0x10DE087E, "ION LE" },
{ 0x10DE0A20, "GeForce GT220" },
{ 0x10DE0A60, "GeForce G210" },
{ 0x10DE0A65, "GeForce 210" },
{ 0x10DE0CA3, "GeForce GT240" }

derail82 · March 2, 2010

My GPU is a 4870HD, so I'm assuming one of the following strings will work.

{ 0x10029440, "ATI Radeon 4870 Series"} ,
{ 0x10029444, "ATI Radeon 4800 Series"} ,

{ 0x10029446, "ATI Radeon 4800 Series"} ,

{ 0x10029450, "ATI Radeon 4800 Series"} ,

{ 0x10029452, "ATI Radeon 4800 Series"} ,

{ 0x10029456, "ATI Radeon 4800 Series"} ,

The question I would like to ask is... what exactly do I change in the efi.plist available on the front page? There is a large chunk of strings inbetween <dict> and </dict> towards the end of the file. Several of the lines have nVidia-sounding values such as "NVDA, NVMac", "NVDA,Display-A", "NVDA,Display-B", "NVDA,Parent", "NVCAP", and "NVPM" in addition to the obvious "Nvidia GeForce GTX 260" string.

What exactly do I change? I've tried googling various combinations of keywords such as "4870", "efi", "device information" but was unable to find what I was looking for. If anyone could point me in the right direction I would greatly appreciate it.

dgobe · March 2, 2010

Just remove the entire <dict>.....</dict> dictionary entry for the graphics and use GraphicsEnabler=y. Use kn6600's instructions above.....or post your ioreg dump.

derail82 · March 2, 2010

Just remove the entire <dict>.....</dict> dictionary entry for the graphics and use GraphicsEnabler=y. Use kn6600's instructions above.....or post your ioreg dump.

I tried removing the entire <dict>...</dict> dictionary entry and used the Config=/Extra/com.apple.Joe.plist and DSDT=/Extra/DSDTjoe.aml" GraphicsEnabler=y boot flags, however no luck.

Here is my registry information saved from IORegistryExplorer. Thanks

Joe___s_Mac_Pro.zip

kn6600 · March 2, 2010

I add a c.a.B.p for your 2 GFX card.... tell me if work 2 GFX is new for me
If works pls post a screen shot of system profiler PCI card

Fabio

Hi Fabio,

With your c.a.B.p for 2 x GTX260 system hang up just before boot graphics mode (with -v switch).

This was first try in the morning. I am at work now , after work I will convert it to plist and will try only to inject GFX part thru EFI.plist.

Thank you,

Kristijan

scott_donald · March 2, 2010

thanks ifabio...

rebooted and now works with the efi string for graphics... thanks for making the effort to do it...

dgobe · March 3, 2010

Asus put up 0901 BIOS with a release date of 2/25, ya right!

ErmaC · March 3, 2010

Asus put up 0901 BIOS with a release date of 2/25, ya right!

Yep 2101 fo the P6T deluxe v1... (the note say... stability????) anyone have more info about this more stability??

I download and we see

thank's for the news

Fabio

dgobe · March 3, 2010

(the note say... stability????) anyone have more info about this more stability??

I'm guessing that just means they fixed whatever they broke in 0804. I've never seen them remove a BIOS revision before but I'm sure it happens on occasion.

@karineko

I finally had some time to do the MSRTools testing this weekend. I had to use the M2.3 DSDT(with SS info for 920) and booted into 32bit mode. It always showed SS: on TM1: on and TM2: off for all tests. It also only shows 2 cpus: CPU0 and CPU1.

Using iMac11_1 smbios.plist(has StepDataDict for platform) and smc-piketon fakesmc.kext:

CPU0 was constantly bouncing between 2.67 and 2.90 in small steps: 2.67, 2.69, 2.78, 2.79, 2.81, 2.90

CPU1 was always showing as in turbo mode 2.81

Using MacPro4_1 smbios.plist(no StepDataDict) and smc-thurley fakesmc.kext:

CPU0 was constantly bouncing between 2.67 and 2.90 in small steps: 2.67, 2.69, 2.78, 2.79, 2.81, 2.90

CPU1 was always showing as in turbo mode 2.81

Using MacPro3_1 smbios.plist(has StepDataDict for platform) and smc-napa fakesmc.kext:

CPU0 idled properly at 1.6 and boosted into turbo mode 2.81

CPU1 was mostly showing as in turbo mode 2.81 but after a very long idle period would drop to 1.6

Seems like MacPro3_1 is the way to go if we can trust what MSRTools is telling us. I did not try to copy the StepDataDict and PLimit values from MacPro3_1 into either MacPro4_1 or iMac11_1 platform plists. I'm mostly away from my main computer this week so I might try that when I get time. Can we just inject data from MacPro3_1 with EFI string so we don't have to touch vanilla kext? Never thought I'd be anxious for Apple to release new hardware but where is the MacPro5_1!

ErmaC · March 3, 2010

I post in the first page the DSDT v3.1.3

Fixed compatibility problem with AppleVIAATA.kext

enjoy!

note tomorrow I post the EFI version...

Fabio

dgobe · March 3, 2010

[/i]solved compatibility with AppleVIAATA.kext
I found the problem that causes the non-functioning of Sleep with that kext is a injected (cosmetics) data inside the DSDT...

with this DSDT you can use this kext for the PATA support w/o corrupt the sleep .

DSDT v3.1.3 (Full)

So are you saying that when you inject the "Marvell 88SE6121" cosmetic strings with the DSDT it breaks sleep, but not when using EFI string? Or do they both cause the sleep problem? I'm not at my main computer so I have to ask silly questions!

acano · March 3, 2010

Thanks for this guide.

I've tried several guides but none of them worked for me due to my hardware.

My specs are: i7 920, 12 GB, P6T-D V2 0901 BIOS AND this graphics:

8400 GS for display (pci-e 1x)

285 GTX 2GB (pci-e 16x)

285 GTX 2GB (pci-e 16x) both for CUDA purposes

I got iDeneb 10.5.8 working ONLY if I install with only 2 GB Mem stick

I cant get SL working no way!

I've tried installing from iDeneb to another HDD but when booting it goes to black screen (seems graphics configuration)

I've tried installing from this post ISO, but it stops loading at IOAPIC vectors 20x stuff

I've tried installing from lastest empire EFI ISO but hangs at black screen (i got it only once, my best) or KP (if 12 GB ram) if I boot "normal" it only detects the 8400 GS, if I boot with "GraphicsEnabler=Y PciRoot=0" the boot reports all graphics cards detected correctly with their full names and ports.

I've tried from OS X Universal 3.6 but it reboots just after F8 flags no matter which flags I type.

So my best is to install SL from 10.5 but it hags on black screen. And SURPRISE, SL boots OK if I only use ONE graphic and, but it results on black screen if I have the 3 connected.

What can I do about that?, I need the 3 gpus permanently connected

Thank you very much.

ErmaC · March 3, 2010

@ dgobe

yep the EFI strigns have this problem too looks like th model" and "name" or AAPL,code" make the problem...

so for now I simply delete this part... when I have more time I do more test ...

Fabio

pablogad · March 3, 2010

Hi All

Many thanks for this helpful thread:

System:

MB: Asus P6T Deluxe Ver 2

CPU: i7 920 @2.66

Mem: Corsair 6gb

Gfx: Zotac GTS 250 (VGA, DVI, HDMI)

Monitor: Phillips 230c (x 2)

System: 10.6.2

I'm a total newbie to this scene so please bear with me.

I used the provided boot 123 and retail 10.6.2 disk to install system. I'm having difficulty getting my gfx card dual display to work on VGA and DVI. VGA shows at full resolution 1920 x 1080; when i try DVI I get a black screen

I noticed in system profiler that my gfx card is shown as unknown and I've tried the following fixes without any degree of certainty or success:

1. AquaMac's GFX - generated GFX string (in snow leopard as I don't have leopard) and pasted into apple....plist file in "Extras" folder

2. Installed following Kexts: NVEnabler 64.kext, NVDANV50Hal.kext NVDAResman.kext using Kext Utility.

I've been messing around with this for the past 2+ weeks and would appreciate any advice/assistance.

qbe · March 3, 2010

reporting Installer v1.13 working

- boot without any problem

- speedstep working according to hardware meter (idle = 148W consumption vs 161W = speedstep disabled in bios / stock vcore 1.25, 2671Mhz)

- sleep working when manualy selected (menu/keyboard), not working automaticaly through energy saver timout setting

-firewire not working

-------------

without OpenHaltRestart.kext shutdown doesnt work

[GUIDE] *NEW* Snow Leopard Retail on ASUS P6T Deluxe V1&V2

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

[GUIDE] NEW Snow Leopard Retail on ASUS P6T Deluxe V1&V2