netkas.org forum
September 23, 2017, 08:23:51 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Information for registering users http://forum.netkas.org/index.php/topic,2246.0.html
 
   Home   Help Search Login Register  
Pages: 1 ... 13 14 [15]
  Print  
Author Topic: GFX-Strings  (Read 221198 times)
scrizz
Newbie

Offline Offline

Posts: 5



« Reply #210 on: February 23, 2008, 11:59:58 PM »

omfg  ATI x1800xl(7109) pls?
Logged
law
Newbie

Offline Offline

Posts: 1


« Reply #211 on: February 26, 2008, 08:32:24 AM »

This is the string I have working for my 7900GS

 
Code:
a603000001000000010000009a0300001400000002010c00d041030a000000000101060000010101060000007fff040014000000400032002c006e0061006d00650000001100000073656e736f722d706172656e7436000000400032002c00680077006300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e00000008000000000000021c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c0000001e0000004e5649444941204765466f72636520373930302047532045464922000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617912000000400032002c007200650067000000080000000000000222000000400032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770752d64696f646520000000400032002c0063006f006d00700061007400690062006c0065000000160000004e5644412c73656e736f722d706172656e7422000000400032002c002300730069007a0065002d00630065006c006c0073000000080000000000000020000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d413a000000400032002c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065007200730069006f006e000000080000000000000226000000400032002c0023006100640072006500730073002d00630065006c006c0073000000080000000000000114000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d007200650076006900730069006f006e0000000800000033303232100000004e00560043004100500000001800000004000000000003000c00000000000007000000000e0000004e00560050004d0000002000000001000000000000000000000000000000000000000000000000000000

Thanks, this worked with my 7600 GS also. In SystemProfiler under Display now writes NVIDIA 7900 GS EFI Smiley
Logged
websrvr
Newbie

Offline Offline

Posts: 7


« Reply #212 on: June 03, 2008, 10:59:25 PM »

Can someone post a non-encoded gfx string for an ATI video card.

While it seems to be the norm to post the encoded string the issue is building a more elaborate string to include other features and while I have heard lots of talk about ATI gfx strings I have yet to see a single one.
Logged
inside
Newbie

Offline Offline

Posts: 11


« Reply #213 on: June 04, 2008, 08:56:45 AM »

ATI X1900XTX

Code:
<?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>----->your device path<------</key>
<dict>
<key>@0,AAPL,boot-display</key>
<string>0x00000001</string>
<key>@0,ATY,EFIDisplay</key>
<string>0x42414756</string>
<key>@0,compatible</key>
<string>ATY,Alopias</string>
<key>@0,connector-type</key>
<string>0x00000200</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>ATY,Alopias</string>
<key>@1,compatible</key>
<string>ATY,Alopias</string>
<key>@1,connector-type</key>
<string>0x00000004</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>ATY,Alopias</string>
<key>AAPL,aux-power-connected</key>
<string>0x00000001</string>
<key>AAPL,backlight-control</key>
<string>0x00000000</string>
<key>ATY,Card#</key>
<string>109-A52027-00</string>
<key>ATY,Copyright</key>
<string>Copyright ATI Technologies Inc. 2005-2006</string>
<key>ATY,DeviceID</key>
<string>0x7249</string>
<key>ATY,EFICompileDate</key>
<string>Aug 18 2006</string>
<key>ATY,EFIHWInitStatus</key>
<string>0x00000000</string>
<key>ATY,EFIOrientation</key>
<string>0x08</string>
<key>ATY,EFIPostRBBM</key>
<string>0x0000444f</string>
<key>ATY,EFIPreRBBM</key>
<string>0x0000000f</string>
<key>ATY,EFIRestored</key>
<string>0x00000008</string>
<key>ATY,EFIVersion</key>
<data>
MDEuMDAuMTQwAA==
</data>
<key>ATY,FrameBufferOffset</key>
<string>0x000000e0</string>
<key>ATY,HWGPIO</key>
<string>0x0003daa3</string>
<key>ATY,IOSpaceOffset</key>
<string>0x00100000</string>
<key>ATY,MCLK</key>
<string>0x0009eb10</string>
<key>ATY,MRT</key>
<data>
cAAAAAAAfwBoAACAAAEAAGkAAIAAAQAA/////wIAAABgAACA/i8PAv////8C
AAAAYAAAgP4vDxL/////AgAAAGgAAICAAQAAaQAAgIABAABoAACAgAAAAGkA
AICAAAAAaAAAgAAAAABpAACAAAAAAHAAAAAAAH8AaAAAgAABAABpAACAAAEA
AP////8CAAAAYAAAgP4vDwL/////AgAAAGAAAID+Lw8S/////wIAAABoAACA
gAEAAGkAAICAAQAAaAAAgIAAAABpAACAgAAAAGgAAIAAAAAAaQAAgAAAAABw
AAAAAAB/AAgAAIASRAADdgAAgAAAAgB2AACAqEABAHYAAIAzBxEA/////xQA
AAB2AACAMwYBAHYAAIAzBgMAdgAAgDMGAwB2AACAMwYDAHYAAIAzBhMACAAA
gBJEAIMKAACAIiIHAGAAAIDuPw8S4AAAgDMGAAA=
</data>
<key>ATY,MemVendorID</key>
<string>0x0002</string>
<key>ATY,MemVendorIDFull</key>
<string>0xffff80ff</string>
<key>ATY,PCIConfigSpace</key>
<data>
AhBJcgcAEAAAAAADQAAAAAgAAOABEAAAAACy8AAAAAAAAAAAAAAAAAAAAAAC
EElyAACw8FAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAIQSXIBWAIGAAAAABCA
EQCgDwAAEAgAAAENAARAAAERAAAAAAAAAAAAAAAAAAAAAAAAAAAFAIAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>ATY,PlatformInfo</key>
<data>
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
</data>
<key>ATY,RefCLK</key>
<string>0x00000a8c</string>
<key>ATY,RegisterSpaceOffset</key>
<string>0x0000b2f0</string>
<key>ATY,Rom#</key>
<string>113-A52027-140</string>
<key>ATY,SCLK</key>
<string>0x000927c0</string>
<key>ATY,VendorID</key>
<string>0x1002</string>
<key>MVAD</key>
<data>
JwSCABcHALcnBIIAFwcAk0g/QAZwCEAAwACwBOIEAQADALAEQAYAA0g/QAZw
CEAAwACwBOIEAQADALAEQAYAAw==
</data>
<key>device_type</key>
<string>ATY,AlopiasParent</string>
<key>model</key>
<string>ATY,RadeonX1900</string>
<key>name</key>
<string>ATY,AlopiasParent</string>
<key>saved-config</key>
<data>
JwSCABcHALcnBIIAFwcAk0g/QAZwCEAAwACwBOIEAQADALAEQAYAA0g/QAZw
CEAAwACwBOIEAQADALAEQAYAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AADYt2ZIZxAAABAAAAhoAQAAAQAAAAYAAAC4nEICGAAAANi3ZkhonEICIG95
ByBveQfot2ZIGAAAAAAAAAAGAgAA+LdmSAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAABYOX9HgiAAABAAAAhoAQAAAQAAAAYAAAACAAEAAQABAETJRAbE
7TsAAQAAAEDJRAZEyUQGze47AAMAAgACAAIApGjnBQ==</data>
</dict>
</dict>
</plist>
Logged
websrvr
Newbie

Offline Offline

Posts: 7


« Reply #214 on: June 04, 2008, 01:56:13 PM »

ATI X1900XTX

Code:
<?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>----->your device path<------</key>
<dict>
<key>@0,AAPL,boot-display</key>
<string>0x00000001</string>
<key>@0,ATY,EFIDisplay</key>
<string>0x42414756</string>
<key>@0,compatible</key>
<string>ATY,Alopias</string>
<key>@0,connector-type</key>
<string>0x00000200</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,name</key>
<string>ATY,Alopias</string>
<key>@1,compatible</key>
<string>ATY,Alopias</string>
<key>@1,connector-type</key>
<string>0x00000004</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,name</key>
<string>ATY,Alopias</string>
<key>AAPL,aux-power-connected</key>
<string>0x00000001</string>
<key>AAPL,backlight-control</key>
<string>0x00000000</string>
<key>ATY,Card#</key>
<string>109-A52027-00</string>
<key>ATY,Copyright</key>
<string>Copyright ATI Technologies Inc. 2005-2006</string>
<key>ATY,DeviceID</key>
<string>0x7249</string>
<key>ATY,EFICompileDate</key>
<string>Aug 18 2006</string>
<key>ATY,EFIHWInitStatus</key>
<string>0x00000000</string>
<key>ATY,EFIOrientation</key>
<string>0x08</string>
<key>ATY,EFIPostRBBM</key>
<string>0x0000444f</string>
<key>ATY,EFIPreRBBM</key>
<string>0x0000000f</string>
<key>ATY,EFIRestored</key>
<string>0x00000008</string>
<key>ATY,EFIVersion</key>
<data>
MDEuMDAuMTQwAA==
</data>
<key>ATY,FrameBufferOffset</key>
<string>0x000000e0</string>
<key>ATY,HWGPIO</key>
<string>0x0003daa3</string>
<key>ATY,IOSpaceOffset</key>
<string>0x00100000</string>
<key>ATY,MCLK</key>
<string>0x0009eb10</string>
<key>ATY,MRT</key>
<data>
cAAAAAAAfwBoAACAAAEAAGkAAIAAAQAA/////wIAAABgAACA/i8PAv////8C
AAAAYAAAgP4vDxL/////AgAAAGgAAICAAQAAaQAAgIABAABoAACAgAAAAGkA
AICAAAAAaAAAgAAAAABpAACAAAAAAHAAAAAAAH8AaAAAgAABAABpAACAAAEA
AP////8CAAAAYAAAgP4vDwL/////AgAAAGAAAID+Lw8S/////wIAAABoAACA
gAEAAGkAAICAAQAAaAAAgIAAAABpAACAgAAAAGgAAIAAAAAAaQAAgAAAAABw
AAAAAAB/AAgAAIASRAADdgAAgAAAAgB2AACAqEABAHYAAIAzBxEA/////xQA
AAB2AACAMwYBAHYAAIAzBgMAdgAAgDMGAwB2AACAMwYDAHYAAIAzBhMACAAA
gBJEAIMKAACAIiIHAGAAAIDuPw8S4AAAgDMGAAA=
</data>
<key>ATY,MemVendorID</key>
<string>0x0002</string>
<key>ATY,MemVendorIDFull</key>
<string>0xffff80ff</string>
<key>ATY,PCIConfigSpace</key>
<data>
AhBJcgcAEAAAAAADQAAAAAgAAOABEAAAAACy8AAAAAAAAAAAAAAAAAAAAAAC
EElyAACw8FAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAIQSXIBWAIGAAAAABCA
EQCgDwAAEAgAAAENAARAAAERAAAAAAAAAAAAAAAAAAAAAAAAAAAFAIAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>ATY,PlatformInfo</key>
<data>
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
</data>
<key>ATY,RefCLK</key>
<string>0x00000a8c</string>
<key>ATY,RegisterSpaceOffset</key>
<string>0x0000b2f0</string>
<key>ATY,Rom#</key>
<string>113-A52027-140</string>
<key>ATY,SCLK</key>
<string>0x000927c0</string>
<key>ATY,VendorID</key>
<string>0x1002</string>
<key>MVAD</key>
<data>
JwSCABcHALcnBIIAFwcAk0g/QAZwCEAAwACwBOIEAQADALAEQAYAA0g/QAZw
CEAAwACwBOIEAQADALAEQAYAAw==
</data>
<key>device_type</key>
<string>ATY,AlopiasParent</string>
<key>model</key>
<string>ATY,RadeonX1900</string>
<key>name</key>
<string>ATY,AlopiasParent</string>
<key>saved-config</key>
<data>
JwSCABcHALcnBIIAFwcAk0g/QAZwCEAAwACwBOIEAQADALAEQAYAA0g/QAZw
CEAAwACwBOIEAQADALAEQAYAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AADYt2ZIZxAAABAAAAhoAQAAAQAAAAYAAAC4nEICGAAAANi3ZkhonEICIG95
ByBveQfot2ZIGAAAAAAAAAAGAgAA+LdmSAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAABYOX9HgiAAABAAAAhoAQAAAQAAAAYAAAACAAEAAQABAETJRAbE
7TsAAQAAAEDJRAZEyUQGze47AAMAAgACAAIApGjnBQ==</data>
</dict>
</dict>
</plist>
Thank you for posting the data.

Is it safe to assume that the encoded data will be the same regardless of ATI card in question or will there be different data for X1300, X1550, X1600, X1650... ?

What I have found is that some of the video cards (those with DVI and VGA ports) the VGA port is the primary port and the DVI port displays no video and I believe it is a detection issue due to the lack of driver compatibility.

If the table can be used for other ATI video cards with minor changes I believe that a gfx string might just allow both ports to be active resolving the no-DVI issue.

Other ATI cards that the DVI port is the primary port suffer the reverse problem where the VGA port does not display video so the same should be true.

Of course the proper solution would be to have an injector do this work but since the source for natit.kext is not publicly available, solving it in the injector is impossible and only leaves one to look for an alternate solution.
Does this allow both video ports to be active?
If this is true then I think we can make a generic
Logged
DrDeelay
Newbie

Offline Offline

Posts: 3


« Reply #215 on: June 04, 2008, 02:02:46 PM »

Well, I guess no, since some Cards just are not supported, eg the X1650....
My 7400Go didn't work after 10.5.3 anymore, even with the correct EFI-String.
Or would a modified EFI-String work then.

I'm not quite clear about that....

regards,
DrDeelay!
Logged
Darkvine
Newbie

Offline Offline

Posts: 2


« Reply #216 on: June 20, 2008, 12:40:13 AM »

Guys i have a serious( ) problem.I recently updated to 10.5.3 and all went fine except for the qe/ci thing.so after trying everything(NVKush,NVInject,blah blah blah )i came across the EFI String solution.So my plist is the following:



<?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>PciRoot(0x1)/Pci(0x2,0x0)/Pci(0x0,0x0)</key>
   <dict>
      <key>@0,compatible</key>
      <string>NVDA,NVMac</string>
      <key>@0,device_type</key>
      <string>display</string>
      <key>@0,name</key>
      <string>NVDA,Display-A</string>
      <key>@1,compatible</key>
      <string>NVDA,NVMac</string>
      <key>@1,device_type</key>
      <string>display</string>
      <key>@1,name</key>
      <string>NVDA,Display-B</string>
      <key>@2,#adress-cells</key>
      <string>0x01000000</string>
      <key>@2,#size-cells</key>
      <string>0x00000000</string>
      <key>@2,compatible</key>
      <string>NVDA,sensor-parent</string>
      <key>@2,device_type</key>
      <string>NVDA,gpu-diode</string>
      <key>@2,hwctrl-params-version</key>
      <string>0x02000000</string>
      <key>@2,hwsensor-params-version</key>
      <string>0x02000000</string>
      <key>@2,name</key>
      <string>sensor-parent</string>
      <key>@2,reg</key>
      <string>0x02000000</string>
      <key>NVCAP</key>
      <data>
      BAAAAAAAAwAMAAAAAAAABwAAAAA=
      </data>
      <key>NVPM</key>
      <data>
      AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
      </data>
      <key>device_type</key>
      <string>NVDA,GeForce</string>
      <key>model</key>
      <string>NVIDIA GeForce 7300GS</string>
      <key>name</key>
      <string>NVDA,Parent</string>
      <key>rom-revision</key>
      <string>0xa1000000</string>
   </dict>
</dict>
</plist>
 

Everything is ok(and the pci root ,checked it through gfxutil) but the qe/ci thing,COuld someone tell me what is the problem with this plist?My card is a 7300gs 265MB ,motherboard MSI k9 vgm-v.Thanx in advance gyus!!!
Logged
sWORDs
Newbie

Offline Offline

Posts: 37


« Reply #217 on: June 21, 2008, 10:54:10 AM »

Guys i have a serious( ) problem.I recently updated to 10.5.3 and all went fine except for the qe/ci thing.so after trying everything(NVKush,NVInject,blah blah blah )i came across the EFI String solution.So my plist is the following:



...
 

Everything is ok(and the pci root ,checked it through gfxutil) but the qe/ci thing,COuld someone tell me what is the problem with this plist?My card is a 7300gs 265MB ,motherboard MSI k9 vgm-v.Thanx in advance gyus!!!
Use this: http://www.mediafire.com/?xl19omzld9j
Logged

Gigabyte DS3, Q6600 3GHz (1333MHz bus), 4x 1GB Kingston DDR2 800, Asus 8500GT 512MB, OptiArc 7200S, 3x Samsung 500GB (dual bootable RAID0), CM Stacker 830, Tagan TG530-U22.
Leo4Allv3 + Kalyway 10.5.3 + 10.5.4 9E6 + Chameleon + GFX/ETH devicestrings + Intel ICH9 ACPI kexts + Taruga 889a HDAenabler.
thor486
Newbie

Offline Offline

Posts: 1


« Reply #218 on: June 23, 2008, 07:04:51 PM »

I created an EFI string for ASUS Geforce 8800GT 512MB, I tried to use the default EFI string for 8800 but I got the card recognized as XFX 8800GTS 640MB so I decided to create my own string Cheesy

Here it is Cheesy

* Geforce8800.hex.zip (0.46 KB - downloaded 109 times.)
Logged
djmastera2000
Newbie

Offline Offline

Posts: 26


« Reply #219 on: July 07, 2008, 10:33:01 PM »

Hello guys,

what happened after updateting to 10.5.4???

Installed string(7600go.hst) for 7600Go from Nvidia+EFI, applied 10.5.4 Combo, but after this no CI/QE Sad

Can anybody tell me what changed, or what to do to get back acceleration please?

Big THX! Smiley
« Last Edit: July 07, 2008, 10:35:07 PM by djmastera2000 » Logged
kdawg
Newbie

Offline Offline

Posts: 1


« Reply #220 on: July 01, 2009, 08:10:58 PM »

So I've extracted the ROMs for both my 512 8800GT and 256 8500GT. Then ran them through the NVCAP Utility found at NVinject.free.fr forums. I get these values.

04000000000003000c0000000000000700000000
0400000000000300040000000000000700000000

Problem is I need to convert them to a format similar to this,
BAAAAAAAAwAMAAAAAAAABwAAAAA=
…so I can insert them into my apple.com.boot.plist EFI strings.

Can anyone out there help me out?

Thanks.
Logged
Pages: 1 ... 13 14 [15]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines
SMFAds for Free Forums
Valid XHTML 1.0! Valid CSS!