netkas.org forum
November 20, 2017, 08:07:56 PM *
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 ... 12 13 [14] 15
  Print  
Author Topic: GFX-Strings  (Read 227583 times)
sfera
Newbie

Offline Offline

Posts: 1


« Reply #195 on: January 08, 2008, 09:44:51 AM »

Dump for ATI 1900XT.

Wink

* ATI1900XT.txt (6.79 KB - downloaded 139 times.)
Logged
MoDs
Newbie

Offline Offline

Posts: 42


« Reply #196 on: January 09, 2008, 09:43:49 AM »

How do i make my own gfx string? Do i have to have a real macpro? Is there anyway i can create my string without having a real mac (trial and error, guessing, ...)?

Please someone answer my question, cause i'm definitely lost here Huh

Thanks in advance.
Logged
B666
Newbie

Offline Offline

Posts: 16


closer to g0d


« Reply #197 on: January 12, 2008, 08:09:15 AM »

I have this same question here in my mind, cause i've used a 7600GT string from a iMac, and get a black screen, i compare my string (the same from here, from the Gxxxx package), and they're different.
Sorry for this noobish question, but, i'm little lost about it.
Thanx!
Logged
time ed
Jr. Member
**
Offline Offline

Posts: 98



« Reply #198 on: January 12, 2008, 03:20:59 PM »

How do i make my own gfx string?

I have this same question here

REV2/1.13.08
A. Synopsis:
1. dump your ioreg
2. find your device properties
3. find your device path
4. edit your device path and properties into a reference doc - either string or plist
5. edit com.apple.Boot.plist

B. Detail:
1. grab mcmatrixs' gfxutil here and give a *thorough* read to this thread:
http://forum.netkas.org/index.php/topic,64.msg519.html#msg519

2. dump your device tree. In Terminal type: ioreg -w0 -l IODeviceTree > regdump.txt

3. Find a reference hex string/plist for your device (or one that's close) one of two ways: A) comb the forums here as there are many posted; B) use one of the supplied strings in netkas' efi package.

4. if using a hex string, convert to xml: ./gfxutil -i hex -o xml in.hex out.plist.
(if you want a nice decoded list of all the strings and data in the plist: ./gfxutil -s -n -v -i hex -o xml in.hex out.plist).

5. find PCI0@0 in your regdump. Note the acpi-path and _UID.

6. follow the device tree from PCI0@0 to display@0. When you find display@0, note the parent device. This will be your path, i.e.:
+-o PCI0@0  <class IOACPIPlatformDevice, registered, matched, active, busy 0, retain 67>
      | {
      ...
      |   "acpi-path" = "IOACPIPlane:/_SB/PCI0@0"
      |   "_UID" = "1"
      ...       
      | }
      |
      +-o pci-bridge@1  <class IOPCIDevice, registered, matched, active, busy 0, retain 9>
         | {
         ...
         |
         +-o display@0  <class IOPCIDevice, registered, matched, active, busy 0, retain 16>

Path in this example is: _SB/PCI0@0_UID=1/pci-bridge@1/display@0
Shorthand is: pciroot(0x1)/pci(0x1,0x0)/pci(0x0,0x0)

7. following mcmatrixs' guide, convert your device path to shorthand notation, then edit <key> for device path in your plist, i.e.:
...
<key>PciRoot(0x1)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
   <dict>
        ...

8. add or change in the plist all properties for your device found in syslog:
a) open Console in Applications >Utilities
b) click "Show Log List" and highlight system.log
c) in the Filter field (top right) type NVinject or ATIinject or whatever you use to get your card working.
d) you should see something like this for NVInject:
NVinject: Probing.
NVinject: Setting NVPM=<data not shown>
NVinject: Setting @0,device_type=display
NVinject: Setting NVCAP=<data not shown>
NVinject: Setting @0,compatible=NVDA,NVMac
NVinject: Setting model=Graphics by NVIDIA
NVinject: Setting @1,name=NVDA,Display-B
NVinject: Setting device_type=NVDA,Parent
NVinject: Setting name=display
NVinject: Setting rom-revision=NVinject 0.1.7
NVinject: Setting @0,name=NVDA,Display-A
NVinject: Setting @1,compatible=NVDA,NVMac
NVinject: Setting @1,device_type=display

..or something like this with ATIinject:
ATIinject: Setting @0,display-link-component-bits=0x00000006
ATIinject: Setting DFP1,EDID=<data not shown>
ATIinject: Setting ATY,Copyright=Copyright ATI Technologies Inc. 2005
ATIinject: Setting @0,display-connect-flags=0000000000
ATIinject: Setting @0,display-dual-link=0x00000002
ATIinject: Setting @0,ATY,EFIDisplay=LVDS
ATIinject: Setting model=ATY,RadeonX1600
ATIinject: Setting AAPL00,DualLink=0x00000001
ATIinject: Setting @0,device_type=display
ATIinject: Setting LVDS,EDID=<data not shown>
ATIinject: Setting @1,display-connect-flags=0000000000
ATIinject: Setting AAPL,backlight-control=0x00000001
ATIinject: Setting ATY,DeviceID=<data not shown>
ATIinject: Setting name=ATY,WormyParent
ATIinject: Setting AAPL00,Coherency=0x00000002
ATIinject: Setting @1,connector-type=0x00000004
ATIinject: Setting @0,compatible=ATY,Wormy
ATIinject: Setting @1,name=ATY,Wormy
ATIinject: Setting @0,AAPL,boot-display=0x00000001
ATIinject: Setting @0,name=ATY,Wormy
ATIinject: Setting @1,compatible=ATY,Wormy
ATIinject: Setting @0,display-dither-support=0000000000
ATIinject: Setting @0,connector-type=0x00000002
ATIinject: Setting @0,inverter-current=0000000000
ATIinject: Setting @1,device_type=display
ATIinject: Setting @0,display-link-type=0000000000
ATIinject: Setting device-id=<data not shown>
ATIinject: Setting ATY,EFIVersion=01.00.068
ATIinject: Setting device_type=ATY,WormyParent
ATIinject: Setting AAPL00,LinkType=0000000000
ATIinject: Setting ATY,VendorID=0x00001002

[CAUTION: Observation] I have no idea which properties to include in a string. When I built the .plist for my card (XFX7600GT), I included the device path, and the minimum information found in my syslog. For me, that worked. YMMV. You should carefully match device properties in your ioreg with those in an "already working" string.

9. convert plist to hex: ./gfxutil -i xml -o hex in.plist out.hex

10. insert new hex string into com.apple.Boot.plist.

11. Remove 3rd party kexts, clear cache, and reboot.

Comments, suggestions, revisions welcomed! Please PM or email me.

[String Editing Note]: try not use TextEdit when working with the hex string or xml plist. Its been my experience that using TextEdit will add application metadata to the file and corrupt your hex. Plist Editor (an X-Code add-on tool) works well for editing the plist, but vi or nano is necessary when working with the hex string. vi and nano are Terminal applications and very simple to use. Docs are available for the googling, or can be found in Terminal by typing: man vi; or man nano.
« Last Edit: January 14, 2008, 04:39:18 PM by time ed » Logged
MoDs
Newbie

Offline Offline

Posts: 42


« Reply #199 on: January 12, 2008, 09:36:36 PM »

@time ed: Thanks a ton  Grin
Logged
macgirl
Newbie

Offline Offline

Posts: 22



« Reply #200 on: January 12, 2008, 10:04:28 PM »

Yeah, thnaks, I succeeded.
Logged
macgirl
Newbie

Offline Offline

Posts: 22



« Reply #201 on: January 12, 2008, 10:45:48 PM »

What so different in a Geforce 6600?

I cant create a working gxf string    Cry
Logged
B666
Newbie

Offline Offline

Posts: 16


closer to g0d


« Reply #202 on: January 12, 2008, 11:17:54 PM »

time ed, thanx a lot dude!
Logged
time ed
Jr. Member
**
Offline Offline

Posts: 98



« Reply #203 on: January 13, 2008, 02:33:14 PM »


"Making a GFX String" tutorial amended:
http://forum.netkas.org/index.php/topic,9.msg1028.html#msg1028

Added section for finding device properties.
Logged
SticMAN
Newbie

Offline Offline

Posts: 1


« Reply #204 on: January 14, 2008, 12:02:52 AM »

i have for a ASUS en7300gs on PCI1@1000 display0

<string>7c0200000100000001000000700200000e00000002010c00d041030a040000000101060000010101060000007fff04000e0000004e00560050004d000000200000000100000000000000000000000000000000000000000000000000000024000000400030002c005600520041004d002c006d0065006d00730069007a00650000000c00000000000004000000081c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f7263650e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c617922000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c000000150000004153555320454e3733303047532045464920000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d4114000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d61631e00000072006f006d002d007200650076006900730069006f006e0000000800000033313735100000004e00560043004100500000001800000004000000000003000c000000000000070000000024000000400031002c005600520041004d002c006d0065006d00730069007a00650000000c0000000000000400000008</string>
Logged
f41qu3
Global Moderator
Newbie

Offline Offline

Posts: 23

Freedom IRC


« Reply #205 on: January 17, 2008, 05:22:26 PM »

i make 4 and no one can...(666)

someone have a string to gma950 to i can test here?

gr8tz
Logged

Venimus, Vidimus, Vicimus: Welcome to ToH Style

For support and more infos go to irc.osx86.hu
Your happy hackint0sh IRC Network.

Current Mac: MacBook MB403LL/A
Current Hack: MSI M660
Current OS: Mac OS X 10.6 Snow Leopard Build 10A96
indraganzo
Newbie

Offline Offline

Posts: 24


« Reply #206 on: January 17, 2008, 05:35:24 PM »

i make 4 and no one can...(666)

someone have a string to gma950 to i can test here?

gr8tz
why dont you look at gma + EFI subject
http://forum.netkas.org/index.php/topic,58.0.html
Logged

Mobo: MSI 975x Platinum PU edition CPU: Intel® Core™2 Quad 6600 @ 2.89 Ghz GFX Card: Sparkle NVidia 7600 GS 256mb Memory: 4 x 1gb DDR2 667mhz HD: Seagate Baracuda 7200 80GB Os: Leopard 10.5.5 vanilla Kexts ,Sleep and Shutdown ok
f41qu3
Global Moderator
Newbie

Offline Offline

Posts: 23

Freedom IRC


« Reply #207 on: January 17, 2008, 05:56:39 PM »

right thanx =)

but i dump and apply...and ... nothing change...

accepting ideas

----added----

all works =) thx all
« Last Edit: January 18, 2008, 11:49:07 AM by f41qu3 » Logged

Venimus, Vidimus, Vicimus: Welcome to ToH Style

For support and more infos go to irc.osx86.hu
Your happy hackint0sh IRC Network.

Current Mac: MacBook MB403LL/A
Current Hack: MSI M660
Current OS: Mac OS X 10.6 Snow Leopard Build 10A96
spanakorizo
Newbie

Offline Offline

Posts: 2


« Reply #208 on: January 18, 2008, 11:02:39 PM »

8800gt?
Logged
SMF
Newbie

Offline Offline

Posts: 16


« Reply #209 on: January 19, 2008, 05:10:33 PM »

I'm trying to get a deeper understanding of strings and I've noticed some strange behaviour.  I"m working now on graphics strings to enable my 7600 GT.  If I use thawnhex's string moded for my p35 it works fine.  If I use the tutorial and nvinject data from console I can get the resulting plist and string to work but my display shows up differently.  With nvinject and thawnhex's string it shows up as the first display.  When I use a string based on my plist the display shows up as the second display.

Anyone see what I've done wrong or understand what might be going on here?

Thanks,
SMF

* 7600gtp35Strings.plist (0.94 KB - downloaded 136 times.)
Logged
Pages: 1 ... 12 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!