netkas.org forum
August 17, 2019, 02:43:48 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 2 [3] 4 5 ... 8
  Print  
Author Topic: How To: EFI GFX+Audio Introduction & Tutorial  (Read 289826 times)
MoDs
Not Newbie
*
Offline Offline

Posts: 42


« Reply #30 on: January 24, 2008, 12:42:01 AM »

is this right:

./gfxutil -s -n -v -i hex -o xml 8800gts320.txt out.plist?

Yes, it should be.

MoDs
Logged
westwaerts
Not Newbie
*
Offline Offline

Posts: 17


« Reply #31 on: January 26, 2008, 08:34:43 PM »

apprechiating everyones work for this
but for my understanding 2 questions:

how to check the efi version ( i have one running, but simply dont know which)?

the theory of string appendices i got, but whats the effort ?
will the graphic errors, that appear randomly in preview be gone ( or is it a beta drivers fact)?




Logged
countercraft
Newbie

Offline Offline

Posts: 1


« Reply #32 on: January 31, 2008, 06:13:07 AM »

Hi guys, I've followed this guide, but when I reboot the PC, the system hangs up before start the GUI. I read somewhere this work only for mobo with Intel chipset. My chipset is VIA, but I'm running PC_EFI v8 perfectly. My processor is a Celeron 420.

So, it's true that only works with Intel mobos?

thanks
Logged
MacPaq
Not Newbie
*
Offline Offline

Posts: 22


« Reply #33 on: January 31, 2008, 02:10:32 PM »

Hi Mods,

I am so excited to learn about this. I have some questions tho. I have a ACER M5630 quad core, with  Kalyway installed, GUID and pc_efi_v80. I am dying to get the ATI HD2400pro to work. (tried Triakis' package without luck) So I follow the guide to the letter twice without success. I boot up the machine, it makes absolute no different. I am still getting only one resolution 1024x768. Is version 8 efi the right one to use or is there a newer one I don't know of?

Some other questions in general, where did these string come from in the first place? When I downloaded from the link for ATI, there are two files, one is R2400.hst and the other is R2400.bst, what is the .bst file for? I also need a string for the ALC888 ICH7 for the sound. And could this method be apply to WiFi cards as well.

Thank you so much.
« Last Edit: February 02, 2008, 06:24:39 PM by MacPaq » Logged
time ed
Jr. Member
**
Offline Offline

Posts: 98


« Reply #34 on: January 31, 2008, 07:09:15 PM »


I assume you verified your device path(s) and modified downloaded strings accordingly?
Logged
0xdeadbeef
Not Newbie
*
Offline Offline

Posts: 25


« Reply #35 on: January 31, 2008, 10:52:47 PM »

I am dying to get the ATI HD2400pro to work. (tried Triakis' package without luck) So

I don't think anyone has had success with the 2400. I would like to know what exactly was done to the power-management of Triakis to see if we can do the same with Iago, but since i don't have an original Triakis, I can't compare
Logged

Conquering the world - 8 hex digits at a time.
MacPaq
Not Newbie
*
Offline Offline

Posts: 22


« Reply #36 on: January 31, 2008, 11:15:01 PM »

Hum, that's very disappointing. I did get the ATI HD2400 Pro to response after I put the hex of the plist in com.apple.Boot.plist. It gets as far as the a blue screen then it hangs there. But I guess it's good that at least it was responding. Here is the plist I have, funny that the dev path is the same as in the tutorial. Does this look right? I wonder why the 2400 is such a PITA? Is there another card any of you gurus can recommend ? Does the 2600 have a great chance of success?

<?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(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
   <dict>
      <key>@0,compatible</key>
      <string>ATY,Iago</string>
      <key>@0,device_type</key>
      <string>display</string>
      <key>@0,display-connect-flags</key>
      <string>0x34323031</string>
      <key>@0,name</key>
      <string>ATY,Display-A</string>
      <key>@1,compatible</key>
      <string>ATY,Iago</string>
      <key>@1,device_type</key>
      <string>display</string>
      <key>@1,display-connect-flags</key>
      <string>0x34323031</string>
      <key>@1,name</key>
      <string>ATY,Display-B</string>
      <key>ATY,EFIVersion</key>
      <string>01.00.207</string>
      <key>ATY,EFIVersionBios</key>
      <string>113-B22501-X22B</string>
      <key>ATY,Rom#</key>
      <string>113-B2250F-207</string>
      <key>ATY,memsize</key>
      <string>268435456</string>
      <key>ATY_EFIEnabledMode</key>
      <string>0x32</string>
      <key>VRAM,totalsize</key>
      <string>268435456</string>
      <key>device_type</key>
      <string>ATY,IagoParent</string>
      <key>model</key>
      <string>ATI,RadeonHD2400</string>
      <key>name</key>
      <string>ATI Radeon HD 2400 EFI</string>
   </dict>
</dict>
</plist>

A dump question,

is this the whole thing I should put in the com.apple.Boot.plist? It's LONG!
3d0300000100000001000000310300001100000002010c00d041030a000000000101060000010101060000007fff04000e0000006e0061006d00650000001a00000041544920526164656f6e204844203234303020454649220000005600520041004d002c0074006f00740061006c00730069007a00650000000d0000003236383433353435361c0000006400650076006900630065005f0074007900700065000000120000004154592c4961676f506172656e742a0000004100540059005f0045004600490045006e00610062006c00650064004d006f0064006500000005000000322a0000004100540059002c00450046004900560065007200730069006f006e00420069006f0073000000130000003131332d4232323530312d58323242220000004100540059002c00450046004900560065007200730069006f006e0000000d00000030312e30302e32303736000000400031002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000003130323422000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c000000140000004154492c526164656f6e48443234303022000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c61791c0000004100540059002c006d0065006d00730069007a00650000000d00000032363834333534353620000000400031002c0063006f006d00700061007400690062006c00650000000c0000004154592c4961676f14000000400030002c006e0061006d0065000000110000004154592c446973706c61792d41160000004100540059002c0052006f006d0023000000120000003131332d4232323530462d32303736000000400030002c0064006900730070006c00610079002d0063006f006e006e006500630074002d0066006c006100670073000000080000003130323414000000400031002c006e0061006d0065000000110000004154592c446973706c61792d4220000000400030002c0063006f006d00700061007400690062006c00650000000c0000004154592c4961676f

Sorry for the long post. I am just learning. Thanks again for the tutorial, I learn a lot. Roll Eyes
« Last Edit: February 01, 2008, 12:20:39 AM by MacPaq » Logged
brywalker
Not Newbie
*
Offline Offline

Posts: 7


« Reply #37 on: February 02, 2008, 03:39:00 AM »

I don't understand why I am having so much trouble here. I really really don't. I am very technically inclined, but this just never ever works.

When I try to convert my hex:

Code:
6c0200000100000001000000600200000d00000002010c00d041030a010000000101060000010101060000007fff04001e0000004100540059002c00560065006e0064006f0072004900440000000600000002101c0000006400650076006900630065005f00740079007000650000000f0000004154592c416c6f70696173220000004100540059002c00450046004900560065007200730069006f006e0000000e00000030312e30302e323139001e0000004100540059002c004400650076006900630065004900440000000600000080720e0000006e0061006d0065000000150000004154592c416c6f70696173506172656e7422000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c617922000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c000000130000004154492c526164656f6e583139353020000000400031002c0063006f006d00700061007400690062006c00650000000f0000004154592c416c6f7069617314000000400030002c006e0061006d00650000000f0000004154592c416c6f7069617314000000400031002c006e0061006d00650000000f0000004154592c416c6f70696173200000004100540059002c0043006f007000790072006900670068007400000035000000436f7079726967687420414d4420496e632e20416c6c205269676874732052657365727665642e20323030352d3230303820000000400030002c0063006f006d00700061007400690062006c00650000000f0000004154592c416c6f70696173

To plist via:

Code:
./gfxutil -s -n -v -i hex -o xml in.hex out.plist

I get:

Code:
./gfxutil: cannot convert from hex to bin, invalid hex inputfile 'in.hex'!

Fantastic.

Well I have another plist that I can convert back to test (taken directly from this forum)...

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>PciRoot(0x1)/Pci(0x1,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 7600 GS</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>0x32323033</string>
</dict>
</dict>
</plist>

I get:
Code:
./gfxutil: invalid property list xml inputfile 'in.plist.rtf'!

Bollocks.

What could be going wrong here?Huh?



Logged
MacPaq
Not Newbie
*
Offline Offline

Posts: 22


« Reply #38 on: February 02, 2008, 04:23:02 AM »

Did you type exactly as this:
./gfxutil -s -n -v -i hex -o xml in.hex out.plist

If so the in.hex sould be YourFileName.hex
Logged
time ed
Jr. Member
**
Offline Offline

Posts: 98


« Reply #39 on: February 02, 2008, 02:39:52 PM »

Did you type exactly as this:
./gfxutil -s -n -v -i hex -o xml in.hex out.plist

If so the in.hex sould be YourFileName.hex

You are correct, sir....
Logged
brywalker
Not Newbie
*
Offline Offline

Posts: 7


« Reply #40 on: February 02, 2008, 05:21:11 PM »

Did you type exactly as this:
./gfxutil -s -n -v -i hex -o xml in.hex out.plist

If so the in.hex sould be YourFileName.hex

Yes. In fact, I copied and pasted directly into terminal. I also renamed the file to in.hex (via mv) to insure that it wasn't something on my end.

I have no idea what could be going wrong unless textedit is playing tricks on me. Maybe I do it all on notepad on the PC and transfer it over.
Logged
mtrr
Not Newbie
*
Offline Offline

Posts: 27


« Reply #41 on: February 02, 2008, 05:24:44 PM »

do a "file yourinfile" in terminal, I bet you're not using a plaintext file as input. textedit defaults to rtf (AFAIR).

cheers
Logged
MacPaq
Not Newbie
*
Offline Offline

Posts: 22


« Reply #42 on: February 02, 2008, 06:31:38 PM »

Hi,

Is there a vid card that works for sure with any of these strings or even the inject method? I don't care whether it's a nVidia or Radeon, as long as it's PCIe 16 and  works in dual head 1680x1050 and 1280x1024, I prefer to have one DVI and one VGA, two VGAs  is ok as well. Any recommendation? I don't understand why the ATIRadeon2400Pro is such a PITA as I have read so many posts and there are very few mention about this card

TIA
« Last Edit: February 02, 2008, 06:35:37 PM by MacPaq » Logged
MacPaq
Not Newbie
*
Offline Offline

Posts: 22


« Reply #43 on: February 02, 2008, 09:45:24 PM »

Yes. In fact, I copied and pasted directly into terminal. I also renamed the file to in.hex (via mv) to insure that it wasn't something on my end.

I have no idea what could be going wrong unless textedit is playing tricks on me. Maybe I do it all on notepad on the PC and transfer it over.

cheers

Just a thought, I don't know for sure since I didn't write the gfxutil, it may be using some frameworks from the library, if so then you will need to have xcode installed, d/l free from Appe. One way or the other, it you like to play with OS X, always nice to have xcode handy cause it contains lotta goodies. Smiley
Logged
0xdeadbeef
Not Newbie
*
Offline Offline

Posts: 25


« Reply #44 on: February 03, 2008, 12:33:18 AM »

I have no idea what could be going wrong unless textedit is playing tricks on me. Maybe I do it all on notepad on the PC and transfer it over.

Textedit is a complete fuckup. Use pico or vi in a terminal. Pico is easier.
Logged

Conquering the world - 8 hex digits at a time.
Pages: 1 2 [3] 4 5 ... 8
  Print  
 
Jump to:  

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