Jump to content

Snow Leopard And Evga Gtx 295


Wyzco
 Share

160 posts in this topic

Recommended Posts

hey i have a EX58-UD5, EVGA GTX295 and snow install too, seems quite popular.

 

havnt got it working yet... im waiting for my dvi monitor to arrive so i can try using meroys efi method

(had a vga monitor which i could only get working with my 295 by hacking ATY_Init, but the card would have all sorts of horrible problems playing video)

 

just read through your posts on aquamac, did you conclude that the card has to be in slot 1 on the ud5? ive installed mine in the slot thats two card slots down on my case from the audio jacks, i cant remember which slot that is though.

 

hope you solve your problem, if i knew more about this stuff i would try to help

 

if only EVGA would just write some 295 coop snowleopard drivers!

Link to comment
Share on other sites

MacWynn, monsterj:

 

MacWynn reported his PciRoot entry. I'm able to determine the 2nd based off his post above.

 

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) -- this is for the 2nd GPU

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) -- reported by MacWynn

 

For folks wanting to do this, just change the PciRoot (2 of them). This will work with a Single PCB 295 card. I think it will also work with a dual-pcb (old 295 card) as I included the @2 entries.

 

Also, there's no need for the ATY_Init extension with this plist. Remember to refresh your cache.

Use the attached NVGTX295.Fix.kext.zip file. Add it to your /Extra/Extensions or /S/L/E. This kext is for the single-pcb card and not required for the old dual-pcb 295 card. There is no need to add the PCI ID to NVDANV50Hal.kext when you have NVGTX295.Fix.kext installed.

 

Obtain gfxutil (I think you guys have this, but for those that don't, search on the web) and run the following:

gfxutil -i xml -o hex in.plist out.hex

 

## in.plist -- content below

## out.hex -- this is what goes into com.apple.Boot.plist

 

<key>device-properties</key>

<string>[out.hex content goes here without the brackets]</string>

 

## One liner tip on refreshing the system caches under Snow Leopard -- this is for /S/L/E

 

sudo kextcache -system-caches

 

 

<?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(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,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>
	BQAAAAAAAwAMAAAAAAAACwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAOA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce GTX 295</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>62.00.6C.00.05</string>
</dict>
<key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/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>
	BQAAAAAAAwAMAAAAAAAACwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAOA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce GTX 295</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>62.00.6C.00.04</string>
</dict>
</dict>
</plist>

NVGTX295.Fix.zip

Link to comment
Share on other sites

thanks a lot meroy, ill give it a try

is it generally thought better to use the fix.kext rather than adding id to NVDAN50HAL?

 

to macwynn, what pci slot are you using on the ud5, and does the card work fully from both?

 

Yes, it's generally better to use the fix.kext. But, it's also harmless to update NVDAN50HAL too. However, you'll need to remember to do this each time during a SL OS update. The fix.kext injects the pci id and contains no binary. If you want to switch slots for your graphics card, you'll need 4 entries configured in the plist file above. The only difference between the 4 of them is the PciRoot value. That's it.

 

To determine the 2nd slot, shut down your system, move the card to slot 2 and boot into single user mode. Then, run gfxutil -f display. This output is what is needed. From that, one can create the 4 entries for the plist file assuming we have the value for your 1st slot above in your previous post. Then, your plist file will work for either slot and even if you're using just one card and later decide to move to the 2nd slot.

Link to comment
Share on other sites

hey, i think the kext you attached to the post had no info.plist inside of it

 

EDIT: i used raph4's kext with your xml and it truly works like a dream. 1080p video at 2048x1152 resolution in snow leopard is awesome.

many thanks, it restores my faith in osx86 to know people like you exist

 

now that its working i think ill do a step-by-step write up for the wiki to try and help people like me who have absolutely no clue what their doing.

 

i just thought id mention that the string does provide vga support, and for any other EX58-UD5 owners the pciroots for the top video card slot are

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)

as meroy reported

 

i wasnt able to get dual monitor mode working, is this solved by updating to 10.6.1 (next hurdle =wifi!) as jfbell mentions?

Link to comment
Share on other sites

Special thanks to meroy. You rock.

 

After a very long night i managed to install Snow Leopard on the following configuration:

 

CPU: i7 920 Rev. D0

Mobo: EVGA X58 SLI Micro (P/N: 121-BL-E756-TR)

RAM: 3x1GB A-Data 1600MHz

HDD: 1x160GB WD

Video: EVGA 295GTX CO-OP (P/N: 017-P3-1295-ER)

 

First and foremost i downloaded the following files:

 

1. Mac OSX Snow Leopard 10.6 (since in Romania i can't buy the Retail DVD)

2. Empire EFI for Intel Core i7 and Intel X58 Chipset 1.02 (link)

3. Empire EFI 1.08 All in one (link)

4. OSX86Tools 1.0.150 (link)

5. NVGTX295.Fix.kext (link)

 

After that i unpacked the zip files and burned the ISO files. You might ask why did i download two different Empire EFI images. The answer is pretty simple. I found out that at least on my configuration is impossbile to start the install process if i use the 1.08 version. I inserted the 1.08 version, which booted up well, Darth Vader appeared on screen, after that i replaced the CD with the Snow Leopard install DVD which was detected well, the install started, but it hangs after ACPI. So i figured out that maybe on 1.08 version there are some experimental thing used so i donwloaded the 1.02 version which works fine for my config. After install the 1.02 CD was in drive so i did a reboot and selected the fresh install hdd from the menu, and SURPRISE it wasn't able to enter in X. So what i did was switching back to 1.08 and it worked well. I was able to complete the install and run the myHack Installer located in the /Extra/Post-Installation dir.

 

long things short.

 

insert Empire-EFI 1.02 -> boot -> switch to Snow Leopard Retail DVD -> Install -> Reboot -> Switch to Empire-EFI 1.08 -> Select your HDD and boot from it -> Finish Install -> Open Extra/Post-Installation from Empire-EFI 1.08 CD and install myHack Installer.

 

 

Now you have a running Snow Leopard system.

 

I the following post i will explain how did i installed the GTX295 board. Since i'm a noob in mac osx please tell me how can i make some screenshots for you guys regarding the steps for GTX295 installation.

 

Best regards,

Valentin

Link to comment
Share on other sites

How to get your GTX 295 working with

 Snow Leopard Step-by-Step

 

This is a post that the osx86 wiki can link to for an easy-to-install pack for snow leopard and nVidia GTX295.

Thanks to meroy for the efi string and general guidance and raph4 for the fix.kext.

If anyone sees anything that could be clarified, just pm me.

 

For card owners that would rather follow raph4's method,

heres a kext/efi string pack with his instructions translated from french.

I also included a pciroot detecting script, so you dont have to boot into Window$.

Raph4s_GTX295_Method.zip

 

The pack is intended for hackintoshes and works with 10.6.0 to 10.6.5 and software update

 

You can generate the efistring from leopard, but it will only provide graphics support for snowleopard.

 

It should hypothetically work for MacPro, if you can get it to boot into desktop with the card

installed (its possible this may work for you ).

You may also need to update your EFI firmware.

 

 

Overview

To get your card working you need to:

Find your card's pciroots using gfxutil (handled by the script)

Add your pciroots to the correct plist (handled by the script)

Convert the plist to an efi string using gfxutil (handled by the script)

If you have a single pcb card install the fix.kext (included in pack, just drag n drop onto kext utility)

Refresh kext cache and fix permissions (done by running kext utility)

Add the string to your com.apple.boot.plist (you do this manually)

 

The script currently only automates steps that can easily be automated,

and therefore isn't a full driver installer.

 

FAQ

What is the fix.kext and do i need it?

Only SinglePCB card owners need it. It allows system updating via Software Update without losing

graphics on next boot. It does this by injecting device-id 0x05eb10de&0xfff8ffff

into NVDANV50Hal.kext/Contents/Info.plist file.

 

Should I install any additional nVidia drivers for my card?

No. No other drivers are needed to make the card work with Snow Leopard.

 

Does this work for 10.5 Leopard?

No. The leopard method, also discovered/created by meroy can be found here:

http://forums.macrumors.com/showthread.php...020#post8199020

 

What features are working?

32-bit/64-bit support

DVI

VGA (via included DVI->VGA adaptor)

HDMI (via included DVI->HDMI adaptor, but no HDMI sound)

Dual monitors

QE/CI/OpenCL

Correct System Profiler Information

All sleep modes (its a little slow to wake sometimes)

 

What GTX295 cards does this work with?

This pack should work for most single and dual pcb 295s. Crazy ones with

modified designs (like the asus quad sli 295) will probably require a custom plist,

and if anyone writes one, pm me and i'll include it in the pack.

It is confirmed and tested working with:

EVGA Coop (singlepcb.plist)

Point of View GTX295 2xDVI (singlepcb.plist)

ZOTAC ZT-295E3MB-FSP (singlepcb.plist)

 

I'm building a hackintosh, whose GTX 295 should i buy? or What is SinglePCB and DualPCB?

There are two fundamental types of 295, older dual pcb cards and newer single pcb cards.

Older does not mean worse.

The first 295s (DualPCB) sold at a higher price point, so arguably they were of better build quality.

SinglePCB 295s cram all the parts onto a double sided pcb as they were created to be cheaper to manufacture,

but nevertheless included a design revision that nVidia promoted as 'better'.

In reality, the difference is negligible.

Beware not to make the hdmi socket a deciding factor when buying a GTX295 as it has not been tested

with this efi string and possibly requires hacked drivers.

 

If you really need a recommendation i would say go for the EVGA Coop if possible.

 

Preparation

You must have the GTX295 in the target computer you

aim to set it up for, and you'll need a bootable osx desktop.

There are two ways to do this:

1) Boot with these flags (type at chameleon boot screen): -x GraphicsEnabler=No

2) Use pcwiz's trick, which involves moving some kexts. Also use the boot flags from 1).

 

Instructions

1. Download the dmg below (with Safari), mount it and open the folder that appears on your desktop.

GTX295.EFiPack_v1.2.dmg [Mirror 1] [Mirror 2] [Mirror 3]

2. Generate your efi string

Double click on either "EFIString for SinglePCB" or "EFIString for DualPCB" according to your type of card.

3. If you have a single pcb card

Open the folder "NVGTX295.Fix.kext for SinglePCB cards" and follow the instructions to install your NVGTX295.fix.kext.

You can now use software update without losing graphics support.

 

4.Add a new graphics card entry to your com.apple.boot.plist

Your com.apple.boot.plist should be in the /Extra directory

Use Textwrangler.app to open your com.apple.boot.plist

Copy the coloured text below, and paste it into the plist underneath the other similiar entries.

<key>device-properties</key>

<string>paste my_single_pcb_efi_string.hex or my_dual_pcb_efi_string.hex content here</string>

Note: You should permanently have the words "device-properties" in your boot.plist.

 

Use Textwrangler or TextEdit to open the newly created my_single_pcb_efi_string.hex or my_dual_pcb_efi_string.hex

according to your type of card. It will be in the main folder of the disk image.

Once you've opened it, in the menu bar go Edit>Select All, Edit>Copy.

Paste the long number in between the <string></string> entry.

 

It should now look something similiar to this (dont worry about indentation):

 

<?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>-v</string>

<key>Timeout</key>

<string>5</string>

<key>device-properties</key>

<string>(very long number)</string>

</dict>

</plist>

 

When you've added the efistring, save it and exit.

 

Finishing This step is still important!

Get pfix and run it.

This will repair permissions and rebuild the cache if you had to trash your ATY_Init and any other injectors.

Reboot and enjoy B)

 

To test if it is fully working, try playing some HD trailers from apple.

Provided your internet is fast enough, if it does not play perfectly, something is wrong.

 

If you have success, it would be great to hear what card you own and to what extent it is working.

If you dont have success, feel free to post on this thread explaining your problem,

just please dont post long efi strings or quote this whole guide as you'll clutter it up.

 

Troubleshooting

Make sure you have uninstalled ATY_Init.kext -- To uninstall a kext just delete it and then run kext utility or pfix.

Make sure you read the Preparation section.

The pack is provided as a read/write .dmg for easy string generation,

if by accident you delete a required component, redownload the pack.

Try installing and running pfix and reboot.

Try using Raph4s GTX295 method by following his instructions.

This thread and this thread have a lot of useful info to peruse if your card isnt working with either method.

They might have an alternative plist that works for you.

 

Legacy (Old) Files

These are files that work, but i no longer recommend or provide support for them.

GTX295.EFiPack_v1.1.dmg [Mirror 1] [Mirror 2] [Mirror 3]

ATY.295.Fix.zip

 

Changelog

major update 18/10/10

pack updated to v1.2 (only changes are removal of kext utility and cosmetic fixs)

updated pfix link, edited some guide text, removed ATY_Init kext from general guide as its stupid

removed all references to KextUtility in guide

files are now interspersed throughout guide rather than attached at the end

Link to comment
Share on other sites

MacWynn, monsterj:

 

MacWynn reported his PciRoot entry. I'm able to determine the 2nd based off his post above.

 

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) -- this is for the 2nd GPU

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) -- reported by MacWynn

 

For folks wanting to do this, just change the PciRoot (2 of them). This will work with a Single PCB 295 card. I think it will also work with a dual-pcb (old 295 card) as I included the @2 entries.

 

Also, there's no need for the ATY_Init extension with this plist. Remember to refresh your cache.

Use the attached NVGTX295.Fix.kext.zip file. Add it to your /Extra/Extensions or /S/L/E. This kext is for the single-pcb card and not required for the old dual-pcb 295 card. There is no need to add the PCI ID to NVDANV50Hal.kext when you have NVGTX295.Fix.kext installed.

 

Obtain gfxutil (I think you guys have this, but for those that don't, search on the web) and run the following:

gfxutil -i xml -o hex in.plist out.hex

 

## in.plist -- content below

## out.hex -- this is what goes into com.apple.Boot.plist

 

<key>device-properties</key>

<string>[out.hex content goes here without the brackets]</string>

 

## One liner tip on refreshing the system caches under Snow Leopard -- this is for /S/L/E

 

sudo kextcache -system-caches

 

 

<?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(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,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>
	BQAAAAAAAwAMAAAAAAAACwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAOA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce GTX 295</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>62.00.6C.00.05</string>
</dict>
<key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/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>
	BQAAAAAAAwAMAAAAAAAACwAAAAA=
	</data>
	<key>NVPM</key>
	<data>
	AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
	</data>
	<key>VRAM,totalsize</key>
	<data>
	AAAAOA==
	</data>
	<key>device_type</key>
	<string>NVDA,GeForce</string>
	<key>model</key>
	<string>NVIDIA GeForce GTX 295</string>
	<key>name</key>
	<string>NVDA,Parent</string>
	<key>rom-revision</key>
	<string>62.00.6C.00.04</string>
</dict>
</dict>
</plist>

 

 

Niiiiiiice - finally after 3 days - working!!! Thank you!

 

Here's a test - I also have a GTX 260 - any Ideas how to get this working along side the GTX 295?

 

;)

Link to comment
Share on other sites

  • 2 weeks later...

double post :D

 

From your guide, i presume you already have osx installed and working inside osx to the get the graphics working?

Unfortunatley i havent been able to get that far.

i had this problem when i was setting up my card. it becomes a chicken/egg situation as without the card set up for osx you cant get into osx to set up the card.

 

the easiest thing to do would be reinstall your retail snow and install netkas' ATY_Init.kext when you install the kexts for your motherboard/sound etc. this should get you to a desktop where your computer is using the vesa card drivers (i hope). from here you should be able to follow the guide. ATY_Init will only work in 32-bit, so set the flag at the boot prompt

 

I have modified the dualpcb plist with the correct pci numbers (found them in the windows setup)

But is it just a case of then taking that script and putting it into the com.apple.boot.plist file under the text hat is already there?

 

no, once youve edited the dualpcb plist with the correct pci numbers you need to convert it to hex using a program called gfxutil by following the guides step 5 (you'll need to put the folder at root now i changed the guide). This will give you a very long number that you then paste into your boot.plist under the heading specified in the guide.

 

good luck,

im going to be improving my guide for people who dont already have an os x desktop to set up their card from, updating the files and attaching a better (no laggy windows) ATY_Init.kext to the post. for the time being, heres an ATY_Init that should work.

ATY_Init.kext.zip

Link to comment
Share on other sites

AH one other thing. Should i download drivers from nvidia?? and how do i know if im running in 64 or 32 bit??

Thanks

Alexdbad

 

definitely dont download the nvidia drivers. to find out whether you're in 32 or 64 go to system profiler/software there should be an entry under system software overview that says - 64-bit kernel and Extensions: No or Yes.

good luck! it should all fall into place if you follow the guide to the word. im in the process of updating my guide now, adding my slightly fixed ATY_Init to the post.

Link to comment
Share on other sites

Hi!

I have finally installed 10.6.2 on my GA-EX58-UD3R, i7-920 + Point of view GTX 295, 1792MB DD3,2xDVi.... with EFI 1,08 bootloader..........everything works great, except:

 

sleep function and VIDEO card still in VESA mode with one resolution mode. Os x boots fine and in system profiler in Graphics/Displays It Shows:

 

Type: GPU

Bus: PCIe

PCIe Lane Width: x16

VRAM (Total): 32MB

Vendor: NVIDIA (0x10de)

Device ID: 0x05eb

Revision ID: 0x00a1

 

I tried meroy guide (GTX295SnowLeo) and with gfxutil I get:

 

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

 

so If I undersand correctly to get hex valu I need to modify singlepcb.plist and enter

 

there <key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)</key>

but there are two places? how to get correct second string without guess????

In Your manual you type:

 

"Determine you're second gpu's pciroot

If this is your first set of values, your second set will be:

PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)"

 

So I tried to put those values (<key>PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0))

in bottom part of singlepcb.plist file save it and then run:

 

/Users/Snow/Desktop/GTX295SnowLeo/gfxutil -i xml -o hex /Users/Snow/Desktop/GTX295SnowLeo/singlepcb.plist /Users/Snow/Desktop/GTX295SnowLeo/efistring.hex

 

I got following hex values in efistring file:

"b80700000100000002000000d60300001500000002010c00d041030a0100000001010600000

30101060000000101060000020101060000007fff04003a000000400032002c00680077007300650

0

6e0073006f0072002d0070006100720061006d0073002d00760065007200730069006f006e000000

0

80000000000000222000000400032002c006400650076006900630065005f0074007900700065000

0

00120000004e5644412c6770752d64696f64650e0000004e00560050004d00000020000000010000

0

00000000000000000000000000000000000000000000000001e00000072006f006d002d007200650

0

76006900730069006f006e0000001200000036322e30302e36432e30302e3035100000004e005600

4

3004100500000001800000005000000000003000c0000000000000b0000000022000000400032002

c

002300730069007a0065002d00630065006c006c0073000000080000000000000022000000400030

0

02c006400650076006900630065005f00740079007000650000000b000000646973706c617910000

0

006d006f00640065006c0000001a0000004e5649444941204765466f726365204754582032393514

0

00000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d412000000

0

400032002c0063006f006d00700061007400690062006c0065000000160000004e5644412c73656e

7

36f722d706172656e7414000000400031002c006e0061006d0065000000120000004e5644412c446

9

73706c61792d4212000000400032002c00720065006700000008000000000000021c000000640065

0

076006900630065005f0074007900700065000000100000004e5644412c4765466f7263652000000

0

400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d

6

16326000000400032002c0023006100640072006500730073002d00630065006c006c00730000000

8

000000000000010e0000006e0061006d00650000000f0000004e5644412c506172656e7422000000

4

00031002c006400650076006900630065005f00740079007000650000000b000000646973706c617

9

20000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e564441

2

c4e564d6163220000005600520041004d002c0074006f00740061006c00730069007a00650000000

8

0000000000003836000000400032002c00680077006300740072006c002d0070006100720061006d

0

073002d00760065007200730069006f006e000000080000000000000214000000400032002c006e0

0

61006d00650000001100000073656e736f722d706172656e74d60300001500000002010c00d04103

0

a010000000101060000030101060000000101060000000101060000007fff04003a0000004000320

0

2c0068007700730065006e0073006f0072002d0070006100720061006d0073002d00760065007200

7

30069006f006e000000080000000000000222000000400032002c006400650076006900630065005

f

0074007900700065000000120000004e5644412c6770752d64696f64650e0000004e00560050004d

0

0000020000000010000000000000000000000000000000000000000000000000000001e000000720

0

6f006d002d007200650076006900730069006f006e0000001200000036322e30302e36432e30302e

3

034100000004e00560043004100500000001800000005000000000003000c0000000000000b00000

0

0022000000400032002c002300730069007a0065002d00630065006c006c00730000000800000000

0

0000022000000400030002c006400650076006900630065005f00740079007000650000000b00000

0

646973706c6179100000006d006f00640065006c0000001a0000004e5649444941204765466f7263

6

5204754582032393514000000400030002c006e0061006d0065000000120000004e5644412c44697

3

706c61792d4120000000400032002c0063006f006d00700061007400690062006c00650000001600

0

0004e5644412c73656e736f722d706172656e7414000000400031002c006e0061006d00650000001

2

0000004e5644412c446973706c61792d4212000000400032002c0072006500670000000800000000

0

000021c0000006400650076006900630065005f0074007900700065000000100000004e5644412c4

7

65466f72636520000000400031002c0063006f006d00700061007400690062006c00650000000e00

0

0004e5644412c4e564d616326000000400032002c0023006100640072006500730073002d0063006

5

006c006c007300000008000000000000010e0000006e0061006d00650000000f0000004e5644412c

5

06172656e7422000000400031002c006400650076006900630065005f00740079007000650000000

b

000000646973706c617920000000400030002c0063006f006d00700061007400690062006c006500

0

0000e0000004e5644412c4e564d6163220000005600520041004d002c0074006f00740061006c007

3

0069007a0065000000080000000000003836000000400032002c00680077006300740072006c002d

0

070006100720061006d0073002d00760065007200730069006f006e0000000800000000000002140

0

0000400032002c006e0061006d00650000001100000073656e736f722d706172656e74"

 

so next step is to open EXTRA\com.apple.Boot.plist and Add a new entry to your com.apple.boot.plist

To do it only way was copy it to other place and then after change overwrite original.

<key>device-properties</key>

<string>paste out.hex content here</string>

 

1 . So what I should write in place of device-properties?

2. I pasted hex value content between <string> my hex values - see above </string>

then save this file and overwrite original

 

When this is done next is to Install your fix.kext - so wich one it is????

I tried to use NVGTX295.Fix.kext and then use Kehtutulity it runs fine

and NVGTX295.Fix.kext pack after that is located in Extra\Extensions folder

but with no results after restart everything is the same....video resolution and display information.

 

So what I'm doing wrong or incorrectly?

 

Thank You!

Martins

 

I was like that before too, did you try run sudo kextcache -system-caches

after I run that command, I got my gtx295 working. the only thing is I am not sure if this is 100% hardware enabled or just a fix for now, because I still couldn't run Final Cut Studio 3, anyone knows?

 

edit: NVM, sorry about before, the card has nothing to do with FCS3 not working, I just forgot to turn the onboard lan on, and setup at en1 and got the FCS3 fully working, man this card is great, thanks to you all who help me making this card to work.

Link to comment
Share on other sites

I tried to type that command but after rebooting nothing has changed...

 

Can you post Your com.apple.boot.plist

 

Maybe I wrote innnnncoretly PCI nummbers?!

 

 

PROBLEM SOLVED!!!!!

 

The solution was very simple:

 

put com.apple.Boot.plist file to Library\Preferences\SystemConfiguration folder!!!!

 

run Kext utility and restart!

 

I attached my com.apple.Boot.plist file for (Point of View GTX295 2xDVI - both work even second dindt show that monitor is connected)

 

 

good luck!

 

 

 

Martins

 

update 2010.01.26 : for Video editing all CS4 programms works without trouble! with full hardware acel.

Library.zip

Link to comment
Share on other sites

PROBLEM SOLVED!!!!!

The solution was very simple:

put com.apple.Boot.plist file to Library\Preferences\SystemConfiguration folder!!!!

run Kext utility and restart!

I attached my com.apple.Boot.plist file for (Point of View GTX295 2xDVI - both work even second dindt show that monitor is connected)

good luck!

So how to test is it working corectly and with full support? - some test software?

Martins

 

great to hear it worked, the way i test it is to try playing 720p or 1080p videos. the apple trailers page has some free to download: http://www.apple.com/trailers/#section=justhd

another good way is to try installing logic or final cut pro, which would stall for me before i started using the efi string.

you wont ever be able to acheive 'full support' without evga or nvidia writing some snow leopard drivers with sli support (which isnt going to happen), but in reality this card is more than fast enough even without this.

 

is there anything that you think could have been clarified in my guide apart from the device properties thing?

Link to comment
Share on other sites

  • 2 weeks later...
Yes.

 

The EVGA GTX 295 Co-op Edition works under Snow Leopard. It's awesome. Both 32-bit/64-bit works. Also sleeps works. This is on a Gigabyte GA-EP45-UD3P motherboard. I created an EFI string and inserted that into the boot plist file. In addition to this, I had to insert 0x05eb10de&0xfff8ffff into the NVDANV50Hal.kext/Contents/Info.plist file.

 

Run as root afterwards:

kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions

 

## My gfx.plist file:

.....................

 

Use gfxutil to convert to hex and add to the boot plist file. Run gfxutil -f display and change the PciRoot key.

 

Good luck. I did this today to try to make this work so that I could run SL in 64-bit mode. The Netkas ATY_Init kext is currently only 32-bit. (this works for 32-bit if the EFI string doesn't work for you).

 

I'm attaching a picture which shows both GPUs being seen by OpenCL.

 

so if I understood something, if I'll use the EFI method I shouldn't install any additional driver? Right?

(does this works on Leopard? I've both on two different HDs)

 

One last newbie question, given that I'm going to change my working video card, do I have to modify the boot plist file and AFTER change the video card? or change it before, boot in safe mode and proceed with meroy's instrunctions?

 

Thanks a lot

Link to comment
Share on other sites

so if I understood something, if I'll use the EFI method I shouldn't install any additional driver? Right?

(does this works on Leopard? I've both on two different HDs)

One last newbie question, given that I'm going to change my working video card, do I have to modify the boot plist file and AFTER change the video card? or change it before, boot in safe mode and proceed with meroy's instrunctions?

Thanks a lot

 

the guide on post 33 of this topic explains everything for installing on snow leopard, and has a download pack with everything you need, despite being long and boring it is very newbie friendly and now (04/01/2010) contains a scripted efi string generater.

ive added some of your questions to the FAQ of the guide

(direct link to sl guide)

http://www.insanelymac.com/forum/index.php...t&p=1338125

 

for your installation specificly:

in order to get into your snow leopard desktop, before you swap in the gtx295, uninstall any previous graphics stuff (efi strings, kexts you might have needed for your other card) and install the hacked kext contained in the ATY.295.Fix.zip attached to the guide.

run through the guide after you swap in the gtx295, as you have to find the pciroots of the two gpus which can only be done with the gtx295 in the computer.

 

leopard, however, uses an entirely different method i am not familiar with which involves installing some drivers amongst other things. this post is by meroy and has directions for how to install on leopard.

http://www.insanelymac.com/forum/index.php...t&p=1214421

 

let me know if it works for you! if anythings still unclear, dont hesitate to ask

incidently, what gtx295 do you have?

Link to comment
Share on other sites

the guide on post 33 of this topic explains everything for installing on snow leopard, and has a download pack with everything you need, despite being long and boring it is very newbie friendly.

ive added some of your questions to the FAQ of the guide

(direct link to sl guide)

http://www.insanelymac.com/forum/index.php...t&p=1338125

 

for your installation specificly:

in order to get into your snow leopard desktop, before you swap in the gtx295, uninstall any previous graphics stuff (efi strings, kexts you might have needed for your other card) and install the hacked kext contained in the ATY.295.Fix.zip attached to the guide.

run through the guide after you swap in the gtx295, as you have to find the pciroots of the two gpus which can only be done with the gtx295 in the computer.

 

leopard, however, uses an entirely different method i am not familiar with which involves installing some drivers amongst other things. this post is by meroy and has directions for how to install on leopard.

http://www.insanelymac.com/forum/index.php...t&p=1214421

 

let me know if it works for you! if anythings still unclear, dont hesitate to ask

incidently, what gtx295 do you have?

 

Thanks a lot!

It seem's I've quite some work to do since I need to install both in Leopard and SL! I even don't remember how I installed the 8400 video card (maybe I used OSX86Tools, I'll search for the guide I followed).

My new video card is an EVGA GTX 295 Co-op Edition (Xmas gift....GREAT one!)

Link to comment
Share on other sites

  • 2 weeks later...

Hey there guys.

 

After much sweat, tears, and even a little bit of blood (nicked my knuckle on inner casing), I have come to a very frustrated dead end. Sadly, I am more noobish than experienced on these things, so have not been able to sort my configuration out, although some of the info on here goes over my head, so anyone helping out would be great.

 

I have a 4,1, 2009 mac pro. I also bought an EVGA GTX295. I thought I had all the info needed to install it but I was wrong. I attempted mroy's setup (http://forums.macrumors.com/showthread.php?t=707745&page=10) which hasn't worked due to me using Snow Leopard (6.2) rather than Leopard.

 

When I install using the GT120 as my helper in slot 3, I have no boot whatsoever. Black screen. I actually presumed that even though it might not boot into OSX, Windows would work under Boot Camp. So very wrong.

 

I have also attempted the Hackintosh method of installation on this thread involving what seems to amount to me as getting a HEX device name for the GTX295 to put into the boot.plist. Sadly, unlike the Hackintosh, I cannot even get into OSX to work this. I have attempted booting from the GT120 with the GTX295 also in place to get the hardware code as it were. This also didn't work.

 

My apologies if this has been figured out and posted, I've read the whole of this post and many others! I think I just don't have the technical knowledge to extrapolate the info I need.

 

So:

 

Mac Pro 2009, Quad Core Nehelam.

EVGA GTX295 Co-op.

Snow Leopard 10.6.1

 

If anyone could help me I would be so happy cos I'm ready to hang up my spurs after having spent a massive chunk of my life attempting this!

 

Cheers guys.

Link to comment
Share on other sites

yo keluchi,

theoretically it should be able to work 100% with macpro, but im afraid it might take some trial and error,

and most probably command line.

 

ive decided the best thing to do would be to make a small script pack that can be executed from single user mode.

(the commandline interface you get to by pressing command + s at boot)

it will take a while to source all the bash commands anyway so i might

as well put them all in a script rather than post them as a guide

EDIT: cant be done see post 52

im afraid you'll be acting as my alpha tester :D

 

you can boot into osx using a gt120 + gtx295 + ATY.295.Fix.zip graphics injector

but i think that would create more problems than it would solve,

plus im sure there are other people with mac pros and gtx 295s who would appreciate a pack!

 

ill let you know when its done. for now, you can chill :)

J

Link to comment
Share on other sites

darn, it seems that it is not possible to find card pciroots from single user mode.

this is down to gfxutil relying on a process that only runs on fully booted snow leopard. (IOService)

 

it is therefore impossible to make a script that can do it all from s u mode. :)

 

however, its possible that by removing the nvidia kexts included with snow leopard your mac pro will be made bootable. :(

it certainly works for GTX260 and snow leopard:

http://www.infinitemac.com/f19/guide-gefor.../post34607.html

 

HOW TO MOVE THE KEXTS:

so, put only your GTX295 in the mac without the GT120 and boot into single user mode (press and hold

Command S at boot) and type this at boot, pressing enter at the end of each line:

/sbin/mount -uw /

mkdir /kext_backup

mv /System/Library/Extensions/NV* /kext_backup

rm -rf /System/Library/Caches/com.apple.kext.caches

reboot

 

IF IT WORKS:

it will boot up into a horrificly low resolution vesa desktop

from there you should be able to follow my hackintosh guide:

http://www.insanelymac.com/forum/index.php...p;#entry1338125

remember to revert the nvidia kext moving after following the guide.

 

IF IT DOESNT WORK:

you can rescue your poor mac by reverting the kext moving

 

TO REVERT THE NVIDIA KEXT MOVING:

boot into single user mode again and type these commands:

/sbin/mount -uw /

mv /kext_backup/* /System/Library/Extensions/

chown -R 755 /System/Library/Extensions/NV*

chown -R root:wheel /System/Library/Extensions/NV*

rm -rf /System/Library/Caches/com.apple.kext.caches

rm -rf /kext_backup

reboot

 

good luck! let me know if you have any success or if anythings unclear,

its only fair that real mac users get to use awesome graphics cards

as well as us semi-legal folks.

 

J

Link to comment
Share on other sites

Cheers for your help Monsterj, however, when I boot with my 295 installed in PCI-E slot 1, whether the GT120 is in a different slot or not, the screen is blank. By this I mean that there is nothing. Even the power led on my monitor doesn't change from red to blue to indicate that it is receiving a signal...

Link to comment
Share on other sites

i suppose you could try moving the kexts in single user mode, with the gt120 installed?

however this may make it unbootable even with the gt120...

 

im not sure if i am able to help if it the display wont even turn on, but if you can somehow get evga

support to help you install it in bootcamp, you can then get the pciroots from windows and that will

be enough to write the efi string and install it in os x.

 

ill look into alternatives

Link to comment
Share on other sites

apologies for the delay, been doing real life stuff

 

do the fans and stuff turn on when you try to boot? or is it just completely dead?

what exactly does it do when you try to boot with only the 295 installed?

 

 

what i meant in the previous post was that you could try:

 

1 moving the kexts (see post 52) without the gtx 295 but with the gt120 installed,

2 shutdown,

3 remove the gt120,

4 install the gtx295

...and see if that will let you boot into snow.

 

what about your macpro power supply, is it strong enough to power the 295?

its a real hog, and evga recommend at least a 680W with 46A on a single 12V rail

(they normally over exaggerate, so you could maybe get away with 650W)

 

i expect you've tried the different compatible power connecters on the macpro motherboard....?

 

i know that people have successfully used the card in macpro before, so its not impossible,

just very frustrating :)

Link to comment
Share on other sites

 Share

×
×
  • Create New...