Jump to content

nForce OS X Snow Leopard (10.6) RETAIL INSTALL GUIDE on a Series 6 or 7 nForce chipset / Intel CPU MOBO

verdant

By verdant,
in OSx86 10.6 (Snow Leopard)

 Share

Snow Leopard on nForce + Intel CPU MOBO in Desktop  

213 members have voted

  1. 1. Have you successfully installed a working, bootable Snow Leopard system?

    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      34
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      50
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using the USB flash drive installer method
      18
    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      14
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      13
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using verdant's nForceSLBoot132DVD installer method
      6
    • Yes, on a Series 7 (750i, 780i, or 790i) nForce chipset Intel CPU MOBO using OSInstall.mpkg method from Leopard to another HDD/volume
      10
    • Yes, on a Series 6 (650i or 680i) nForce chipset Intel CPU MOBO, using OSInstall.mpkg method from Leopard to another HDD/volume
      9
    • Yes, on a Series 6 (610i or 630i) nForce chipset Intel CPU MOBO, using OSInstall.mpkg method from Leopard to another HDD/volume
      8
    • No, none of the above methods has worked for me
      35
    • I have sold or plan to sell my nForce chipset MOBO to go over to the "light" side....Intel chipset MOBO.....
      10
    • I have sold or plan to sell my nForce chipset MOBO to buy a "real" Mac
      6

  2. 2. Would you say that your Snow Leopard system is working to your satisfaction (e.g. compared to Leopard)

    • 100%
      60
    • 90%
      53
    • 80%
      20
    • 70%
      19
    • 60%
      4
    • 50%
      6
    • <50%
      18
    • Are you running 10.6.1 successfully , having auto-updated without any problems
      21
    • Are all the standard Apple applications running OK
      12

  3. 3. Is your Snow Leopard system working 100% on

    • SATA HDD
      173
    • SATA DVDRW including burning disks
      47
    • PATA (IDE) HDD
      42
    • PATA (IDE) DVDRW including burning disks
      51
    • Video
      146
    • Onboard LAN (Ethernet)
      131
    • USB devices (mounting/unmounting), plus USB keyboard and USB mouse
      161
    • Firewire
      54
    • PS/2 keyboard and mouse
      42
    • Audio including Front Panel headphones and microphone
      63
    • Audio except Front Panel headphones
      38
    • Audio except Front Panel microphone
      27
    • Sleep including waking from sleep
      24
    • PCI NIC
      24
    • eSATA
      20
    • Bluetooth
      41
    • WiFi
      38
    • Time Machine
      53
    • Overclocking
      35
    • Auto Software Update e.g. to 10.6.1
      90

2,142 posts in this topic

Recommended Posts

MasterTiiro
MasterTiiro
Posted
Posted

Ok, I got leopard to work by installing voodoo 9.5.0 kernel.

 

I notice from -v mode there are a lot of "firewire GUID ffffffffffffff is invalid". What is that

 

Well, back to leopard for a second. On LAN is working, sound is working, wireless is also working. The only thing that is not working is my video card. I guess it's time to search for that kext.

 

Should I have everything working before installing Snow Leopard or Do I just go straight to SL?

 

Glad to help......also see my Leopard distro install guides in my blog...... :P
Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Ok, I got leopard to work by installing voodoo 9.5.0 kernel.

 

I notice from -v mode there are a lot of "firewire GUID ffffffffffffff is invalid". What is that

 

Well, back to leopard for a second. On LAN is working, sound is working, wireless is also working. The only thing that is not working is my video card. I guess it's time to search for that kext.

 

Should I have everything working before installing Snow Leopard or Do I just go straight to SL?

 

Glad you got Leopard running with Voodoo 9.5.0........hope my blog install guides were of some help........ :P

 

The Firewire GUID invalid message could be a BIOS issue or a IOFirewire kext issue.......but if you do not need Firewire at present or in the future, just disable it in BIOS........

 

YES - get everything working 100% in Leopard because then you will fully understand what your system needs to run OS X in terms of non-Apple kexts plus video injector kext or graphics string etc......

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

Hit a bump again. I was trying to find a solution for my graphics card because I want a higher resolution than the default low res, so I tried the gfx strings method. But I'm sad to say that it freezes osx loading screen. I can't get back in osx anymore. I guess I will need to reinstall, again. Is the graphics string method for snow leopard only? If so, where can I get kext for Leopard?

 

I also got a black screen after the loading from installing gt200_drivers_pkg.pkg last time.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Hit a bump again. I was trying to find a solution for my graphics card because I want a higher resolution than the default low res, so I tried the gfx strings method. But I'm sad to say that it freezes osx loading screen. I can't get back in osx anymore. I guess I will need to reinstall, again. Is the graphics string method for snow leopard only? If so, where can I get kext for Leopard?

 

I also got a black screen after the loading from installing gt200_drivers_pkg.pkg last time.

 

Graphics strings work in both Leopard and Snow Leopard

 

Did you keep a backup of your original com.apple.Boot.plist without the graphics string entry under <key>device-properties</key>?

 

How much video RAM does your nvidia geforce gtx 260 have?

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

I couldn't boot into osx so I reinstalled.

 

I believe it's some odd number like 896mb. It's the evga gtx 260 216cores.

 

 

I have a question - can I do the graphic string method right after I finish installing or do I have to install some kext first? I've heard a lot about injector, modified driver from nvidia, and a lot more, so I'm confused. I don't know if I should have something else beside the graphic strings method or just do straight in. I saw a lot of different version of guides from different forums, but don't know which one to try.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
I couldn't boot into osx so I reinstalled.

 

I believe it's some odd number like 896mb. It's the evga gtx 260 216cores.

 

 

I have a question - can I do the graphic string method right after I finish installing or do I have to install some kext first? I've heard a lot about injector, modified driver from nvidia, and a lot more, so I'm confused. I don't know if I should have something else beside the graphic strings method or just do straight in. I saw a lot of different version of guides from different forums, but don't know which one to try.

 

The options for getting a graphics card working are as follows:

1. For nVidia graphics cards, the Chameleon Graphics Enabler option via com.apple.Boot.plist:

 

<key>GraphicsEnabler</key>
 <string>y</string>

 

2. Injector kext such as NVEnabler

 

3. Graphics string option via com.apple.Boot.plist:

 

<key>device-properties</key>

<string>"for example: 6c0200000100000001000000600200000d00000002010c </string>

 

where the graphics string is generated by EFIStudio v1.1 for example.....

 

For your EVGA GTX260 (896MB, cores 216) graphics card use EFI strings........

 

Try this string.......

GTX260.txt

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Do I follow this guide but paste the string you gave me?

 

http://www.infinitemac.com/f19/guide-geforce-gtx-260-in-snow-leopard-t4057/

 

No, simply paste the string between <string></string> under <key>device-properties</key> in your com.apple.Boot.plist......and see what happens.....if it works you may want to put in just above <key>device-properties</key>

 

<key>Graphics Mode</key>
<string>HxVx32</string> "Replace H and V with your display values"

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted
No, simply paste the string between <string></string> under <key>device-properties</key> in your com.apple.Boot.plist......and see what happens.....if it works you may want to put in just above <key>device-properties</key>

 

<key>Graphics Mode</key>
<string>HxVx32</string> "Replace H and V with your display values"

 

 

This is sad....It doesn't work, guess I got to find new ways to do it. This is my com.apple.boot.plist

 

 

 

<?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>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
<key>Timeout</key>
<string>5</string>
	<key>GraphicsEnabler</key>
	<string>y</string>

<key>device-properties</key>
<string>cd0300000100000001000000c10300001500000002010c00d041030a01000000010106000003
0101060000007fff04003a000000400032002c0068007700730065006e0073006f0072002d007000
6
100720061006d0073002d00760065007200730069006f006e0000000800000000000002220000004
0
0032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770
7
52d64696f64650e0000004e00560050004d000000200000000100000000000000000000000000000
0
0000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e00
0
000090000003331373261100000004e00560043004100500000001800000004000000000003000c0
0
0000000000070000000022000000400032002c002300730069007a0065002d00630065006c006c00
7
3000000080000000000000022000000400030002c006400650076006900630065005f00740079007
0
00650000000b000000646973706c6179100000006d006f00640065006c0000001a0000004e564944
4
941204765466f726365204754582032363014000000400030002c006e0061006d006500000012000
0
004e5644412c446973706c61792d4120000000400032002c0063006f006d00700061007400690062
0
06c0065000000160000004e5644412c73656e736f722d706172656e7414000000400031002c006e0
0
61006d0065000000120000004e5644412c446973706c61792d4212000000400032002c0072006500
6
700000008000000000000021c0000006400650076006900630065005f00740079007000650000001
0
0000004e5644412c4765466f72636520000000400031002c0063006f006d00700061007400690062
0
06c00650000000e0000004e5644412c4e564d616326000000400032002c002300610064007200650
0
730073002d00630065006c006c007300000008000000000000010e0000006e0061006d0065000000
0
f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740
0
79007000650000000b000000646973706c617920000000400030002c0063006f006d007000610074
0
0690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c00740
0
6f00740061006c00730069007a0065000000080000000000003836000000400032002c0068007700
6
300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000
8
0000000000000214000000400032002c006e0061006d00650000001100000073656e736f722d7061
7
2656e74</string>
</dict>
</plist>

 

 

I don't think my card is working on 10.5.6, so I'm just going to go ahead and install SL. However, I'll still need your help on the way to installing it....

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
This is sad....It doesn't work, guess I got to find new ways to do it. This is my com.apple.boot.plist

 

 

 

<?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>Kernel</key>
 <string>mach_kernel</string>
 <key>Kernel Flags</key>
 <string></string>
 <key>Timeout</key>
 <string>5</string>
	 <key>GraphicsEnabler</key>
	 <string>y</string>

<key>device-properties</key>
<string>cd0300000100000001000000c10300001500000002010c</string>
</dict>
</plist>

 

 

I don't think my card is working on 10.5.6, so I'm just going to go ahead and install SL. However, I'll still need your help on the way to installing it....

 

It does not work like that.............I am using the same graphics string I use with Leopard 10.5.6 in Snow Leopard BECAUSE the graphics card is the same......you problem is that in your Boot.plist you are using 2 methods simultaneously! I did not say to use 

<key>GraphicsEnabler</key>
<string>y</string>

with a graphics string........the 3 methods are mutually exclusive........so try with:

<key>GraphicsEnabler</key>
<string>n</string>

or remove these lines from your Boot.plist........also if you have tried any injector kexts, then remove them /S/L/E.....

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

OK that way worked! I got it to my native resolution, but I still only get 32mb of vram. It makes browsing through everything so slow. Every time I scroll up or down, the content would overlap each other. Did that happen to you?

So I guess making the taskbar/title bar translucent is out of the question, right?

It doesn't say my video card, but the device and vendor ID checked out, I googled. I just don't know why it's still 32MB VRAM.

 

Picture_3.jpg

 

 

============================

 

But what I'm really concerned about is the DSDT patching. I got up to 

nano Debug/dsdt.dsl

and this is what I'm seeing:

 

Picture_2_3.jpg

 

As you can see, this is nowhere close to your example. Did I grab the wrong file or something? I didn't see any link to that dsdt patching file in your tutorial, so I went to the original author's thread.

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
OK that way worked! I got it to my native resolution, but I still only get 32mb of vram. It makes browsing through everything so slow. Every time I scroll up or down, the content would overlap each other. Did that happen to you?

So I guess making the taskbar/title bar translucent is out of the question, right?

It doesn't say my video card, but the device and vendor ID checked out, I googled. I just don't know why it's still 32MB VRAM.

 

Picture_3.jpg

 

 

============================

 

But what I'm really concerned about is the DSDT patching. I got up to 

nano Debug/dsdt.dsl

and this is what I'm seeing:

 

Picture_2_3.jpg

 

As you can see, this is nowhere close to your example. Did I grab the wrong file or something? I didn't see any link to that dsdt patching file in your tutorial, so I went to the original author's thread.

 

Working on DSDT.dsl file first, it is a long file of 9000+ lines typically.......so in the nano editor, use the search function Ctrl-W with "Device (RTC)" but without quotes as the search term, then just use the arrow keys to move down to where you need to make the changes.......

 

Regarding your graphics issue, before trying the graphics string I posted, did you try any other methods involving kexts etc.?.....I assume that you have removed 

<key>GraphicsEnabler</key>
<string>y</string>

from your com.apple.Boot.plist file.....

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

I've only removed all the kexts that I've installed(nvinject, nv enabler 64). Do I need to remove all the "ati radeon bundles" or "geforce kexts" or "nvdan* and "nvdresman" Picture_4.jpg

 

And yes I've tried the graphics enabler also. That was the first thing I tried, same result so I decided to use the string instead.

 

Working on DSDT.dsl file first, it is a long file of 9000+ lines typically.......so in the nano editor, use the search function Ctrl-W with "Device (RTC)" but without quotes as the search term, then just use the arrow keys to move down to where you need to make the changes.......

 

Regarding your graphics issue, before trying the graphics string I posted, did you try any other methods involving kexts etc.?.....I assume that you have removed 

<key>GraphicsEnabler</key>
<string>y</string>

from your com.apple.Boot.plist file.....

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
I've only removed all the kexts that I've installed(nvinject, nv enabler 64). Do I need to remove all the "ati radeon bundles" or "geforce kexts" or "nvdan* and "nvdresman" Picture_4.jpg

 

And yes I've tried the graphics enabler also. That was the first thing I tried, same result so I decided to use the string instead.

 

No, AFAIK you do not need to remove any graphics related kexts installed from the Retail OS X DVD, only any non-Apple injector kexts like NVEnabler etc....

 

I have looked at the .plist file derived from the string and everything appears OK to be for the GTX260......so suggest you also put your com.apple.Boot.plist in Library/Preferences/SystemConfiguration, as well as in /Extra.........and see what happens......

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

Oh ok, then I've done that.

 

 

The Boot.plist is already in Library/Preferences/SystemConfiguration, isn't it? I mean, that where I first found it. I've put Boot.plist into the Extra folder. However, I don't see any changes to my system, still 32mb vram.

 

Just to be sure, can you take a look at my current Boot.plist?

 

 <?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>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
<key>Timeout</key>
<string>5</string>
<key>device-properties</key>
<string>cd0300000100000001000000c10300001500000002010c00d041030a01000000010106000003
0101060000007fff04003a000000400032002c0068007700730065006e0073006f0072002d007000
6
100720061006d0073002d00760065007200730069006f006e0000000800000000000002220000004
0
0032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770
7
52d64696f64650e0000004e00560050004d000000200000000100000000000000000000000000000
0
0000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e00
0
000090000003331373261100000004e00560043004100500000001800000004000000000003000c0
0
0000000000070000000022000000400032002c002300730069007a0065002d00630065006c006c00
7
3000000080000000000000022000000400030002c006400650076006900630065005f00740079007
0
00650000000b000000646973706c6179100000006d006f00640065006c0000001a0000004e564944
4
941204765466f726365204754582032363014000000400030002c006e0061006d006500000012000
0
004e5644412c446973706c61792d4120000000400032002c0063006f006d00700061007400690062
0
06c0065000000160000004e5644412c73656e736f722d706172656e7414000000400031002c006e0
0
61006d0065000000120000004e5644412c446973706c61792d4212000000400032002c0072006500
6
700000008000000000000021c0000006400650076006900630065005f00740079007000650000001
0
0000004e5644412c4765466f72636520000000400031002c0063006f006d00700061007400690062
0
06c00650000000e0000004e5644412c4e564d616326000000400032002c002300610064007200650
0
730073002d00630065006c006c007300000008000000000000010e0000006e0061006d0065000000
0
f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740
0
79007000650000000b000000646973706c617920000000400030002c0063006f006d007000610074
0
0690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c00740
0
6f00740061006c00730069007a0065000000080000000000003836000000400032002c0068007700
6
300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000
8
0000000000000214000000400032002c006e0061006d00650000001100000073656e736f722d7061
7
2656e74</string>


</dict>
</plist>

 

No, AFAIK you do not need to remove any graphics related kexts installed from the Retail OS X DVD, only any non-Apple injector kexts like NVEnabler etc....

 

I have looked at the .plist file derived from the string and everything appears OK to be for the GTX260......so suggest you also put your com.apple.Boot.plist in Library/Preferences/SystemConfiguration, as well as in /Extra.........and see what happens......

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
Oh ok, then I've done that.

 

 

The Boot.plist is already in Library/Preferences/SystemConfiguration, isn't it? I mean, that where I first found it. I've put Boot.plist into the Extra folder. However, I don't see any changes to my system, still 32mb vram.

 

Just to be sure, can you take a look at my current Boot.plist?

 

 <?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>Kernel</key>
 <string>mach_kernel</string>
 <key>Kernel Flags</key>
 <string></string>
 <key>Timeout</key>
 <string>5</string>
<key>device-properties</key>
<string>cd0300000100000001000000c10300001500000002010c00d041030a01000000010106000003
0101060000007fff04003a000000400032002c0068007700730065006e0073006f0072002d007000
6
100720061006d0073002d00760065007200730069006f006e0000000800000000000002220000004
0
0032002c006400650076006900630065005f0074007900700065000000120000004e5644412c6770
7
52d64696f64650e0000004e00560050004d000000200000000100000000000000000000000000000
0
0000000000000000000000001e00000072006f006d002d007200650076006900730069006f006e00
0
000090000003331373261100000004e00560043004100500000001800000004000000000003000c0
0
0000000000070000000022000000400032002c002300730069007a0065002d00630065006c006c00
7
3000000080000000000000022000000400030002c006400650076006900630065005f00740079007
0
00650000000b000000646973706c6179100000006d006f00640065006c0000001a0000004e564944
4
941204765466f726365204754582032363014000000400030002c006e0061006d006500000012000
0
004e5644412c446973706c61792d4120000000400032002c0063006f006d00700061007400690062
0
06c0065000000160000004e5644412c73656e736f722d706172656e7414000000400031002c006e0
0
61006d0065000000120000004e5644412c446973706c61792d4212000000400032002c0072006500
6
700000008000000000000021c0000006400650076006900630065005f00740079007000650000001
0
0000004e5644412c4765466f72636520000000400031002c0063006f006d00700061007400690062
0
06c00650000000e0000004e5644412c4e564d616326000000400032002c002300610064007200650
0
730073002d00630065006c006c007300000008000000000000010e0000006e0061006d0065000000
0
f0000004e5644412c506172656e7422000000400031002c006400650076006900630065005f00740
0
79007000650000000b000000646973706c617920000000400030002c0063006f006d007000610074
0
0690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c00740
0
6f00740061006c00730069007a0065000000080000000000003836000000400032002c0068007700
6
300740072006c002d0070006100720061006d0073002d00760065007200730069006f006e0000000
8
0000000000000214000000400032002c006e0061006d00650000001100000073656e736f722d7061
7
2656e74</string>


</dict>
</plist>

 

The string should be continuous without any spaces/hidden formatting charcters etc..............paste the string into TextEdit and then copy from TextEdit into com.apple.Boot.plist.......or use OSx86Tools to add it to com.apple.Boot.plist.......

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

There are no spaces within the string I assure you. Those are only caused by the text formatting of the editor. If I maximized the editor's window, you wouldn't see any spaces.

 

A lot of people are reporting that that my graphics card works in Snow Leopard. Is there any reason why I can't try to install SL now?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
There are no spaces within the string I assure you. Those are only caused by the text formatting of the editor. If I maximized the editor's window, you wouldn't see any spaces.

 

A lot of people are reporting that that my graphics card works in Snow Leopard. Is there any reason why I can't try to install SL now?

 

Fine......I had to ask.....hope you understand...... :(

 

I have some thoughts:

 

Firstly, explicitly disable GraphicsEnabler by

<key>GraphicsEnabler</key>
  <string>n</string>

 

Second, try generating your own EFI graphics string via GFX Strings Creator option in OSx86Tools......or use Universal OSx86 Installer........

 

Third, insert your GFX card device ID in /System/Library/Extensions/NVDAResman.kext/Contents/Info.plist and

in /System/Library/Extensions/NVDANV50Hal.kext/Contents/Info.plist under

<key>IOPCIPrimaryMatch</key>

Open Info.plist file via Terminal using sudo nano etc., or right-click, choosing "Open With", and selecting your preferred Text Editor app; e.g.Text Edit, TextMate, TextWrangler, Property List Editor, or PlistEdit Pro etc.

 

Fourth, ensure that SLI mode is disabled in BIOS if that is an option......

 

Fifth, repair /S/L/E permissions:

sudo chown -R root:wheel /System/Library/Extensions
sudo chmod -R go=u-w /System/Library/Extensions
sudo touch /System/Library/Extensions

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
do I do them in order or pick 1? I did the os86x tool method and can't boot after that. Do I do all of them and then reboot?

 

Try them in order........and before using your custom EFI graphics string, compare it with the one I posted earlier, by converting each from hex format to xml format......

 

Unfortunately, it is not always easy to solve GFX card issues remotely......many posters in other threads have done a clean re-install out of desperation...... :unsure:

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

It's a no go. Tried everything you suggested, but then I can't boot into osx so I change com.apple.boot.plist back to the way it was.

 

It's interesting but the only way I can get high resolution is doing the "graphics mode=" like you suggested. How come it can't detect my graphics card, but it can be forced into 1920x1200? Weird...

 

Try them in order........and before using your custom EFI graphics string, compare it with the one I posted earlier, by converting each from hex format to xml format......

 

Unfortunately, it is not always easy to solve GFX card issues remotely......many posters in other threads have done a clean re-install out of desperation...... :unsure:

 

 

UPDATE: I cloned the BOOT volume to OSX_BACKUP volume with carbon copy, and update the BACKUP volume to 10.5.8. Would it make a difference if I change the com.apple.boot.plist in the BACKUP volume?

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
It's a no go. Tried everything you suggested, but then I can't boot into osx so I change com.apple.boot.plist back to the way it was.

 

It's interesting but the only way I can get high resolution is doing the "graphics mode=" like you suggested. How come it can't detect my graphics card, but it can be forced into 1920x1200? Weird...

 

 

 

 

UPDATE: I cloned the BOOT volume to OSX_BACKUP volume with carbon copy, and update the BACKUP volume to 10.5.8. Would it make a difference if I change the com.apple.boot.plist in the BACKUP volume?

 

No, each OS X volume is separately bootable and as long as you keep a separate folder somewhere with your different versions of com.apple.Boot.plist, knowing the details of each, you can keep one OS X system as a working one, while you try to sort out your graphics card on the other.......

 

You may have to modify the graphics card PCI path, so that your graphics card can be recognised.......

Link to comment
Share on other sites
MasterTiiro
MasterTiiro
Posted
Posted

No? Are you sure? How come the osx from OSX_BACK volume still retains the high resolution when its com.apple.boot.plist does not have the "Graphics Mode=1920x1200x32" that I put in the plist of OSX_BOOT volume? But when I take that string out of the plist from OSX_BOOT, leopard from both sides return to low resolution. I'm thinking it's connected somehow.

 

Modify PCI path? I didn't know we need to do that. I've search through a lot of info, but have never heard of that. How do I go about doing that?

 

I was hoping I could get video card to work in 10.5.8, since a lot of people said it's possible. I heard I need "nvenabler and gt200 2f16" to make it work. I think I got nvenabler, but I don't where to find gt200 2f16. If I could get that to work on the backup volume, I'll probably clone it to the boot volume. Does that sound right? Or should I just leave BOOT volume the way it is?

 

No, each OS X volume is separately bootable and as long as you keep a separate folder somewhere with your different versions of com.apple.Boot.plist, knowing the details of each, you can keep one OS X system as a working one, while you try to sort out your graphics card on the other.......

 

You may have to modify the graphics card PCI path, so that your graphics card can be recognised.......

Link to comment
Share on other sites
verdant
verdant
Posted
  • Author
Posted
No? Are you sure? How come the osx from OSX_BACK volume still retains the high resolution when its com.apple.boot.plist does not have the "Graphics Mode=1920x1200x32" that I put in the plist of OSX_BOOT volume? But when I take that string out of the plist from OSX_BOOT, leopard from both sides return to low resolution. I'm thinking it's connected somehow.

 

Modify PCI path? I didn't know we need to do that. I've search through a lot of info, but have never heard of that. How do I go about doing that?

 

I was hoping I could get video card to work in 10.5.8, since a lot of people said it's possible. I heard I need "nvenabler and gt200 2f16" to make it work. I think I got nvenabler, but I don't where to find gt200 2f16. If I could get that to work on the backup volume, I'll probably clone it to the boot volume. Does that sound right? Or should I just leave BOOT volume the way it is?

 

I think it is Chameleon bootloader related......on both OS X Leopard i.e. OSX_BACK and OSX_BOOT volumes, reinstall Chameleon RC3 or RC4 bootloader, and put the same com.apple.Boot.plist file in /Extra on each volume......and then try with and without "Graphics Mode=1920x1200x32".......

 

I mentioned the PCI path because your card does not seem to be recognised/picked up......it has the form

DevicePath = PciRoot(0x0)/Pci(0x1,0x0)Pci(0x0,0x0)

in the .plist version of your hex EFI graphiccs string........

 

Get the EVGA 2F16 driver here.....

 

You should get your video working properly on all your OS system volumes......

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...