Karakino Posted August 5, 2009 Author Share Posted August 5, 2009 EVGA GTX 295 Co op Edition works! Go to the following URL. I provided the instructions. Begin reading post #235. http://forums.macrumors.com/showthread.php...020#post8199020 Thank you folks for this site. uuuuuuuuuuuuuoooooohhhhhhhh man!!!...... i'll try this when i'll finish downloading the newest ideneb 10.5.7 dvd... then i'll report immediately back to you... i only hope that the system will see both gpus of my asus gtx 295... Link to comment Share on other sites More sharing options...
meroy Posted September 8, 2009 Share Posted September 8, 2009 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: <?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)/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>NVCAP</key> <data> BQAAAAAAAwAMAAAAAAAACwAAAAA= </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>NVIDIA GeForce GTX 295 OpenGL Engine [EFI]</string> </dict> <key>PciRoot(0x1)/Pci(0x1,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>NVCAP</key> <data> BQAAAAAAAwAMAAAAAAAACwAAAAA= </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>NVIDIA GeForce GTX 295 OpenGL Engine [EFI]</string> </dict> </dict> </plist> 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. Link to comment Share on other sites More sharing options...
MastaG Posted September 9, 2009 Share Posted September 9, 2009 Ok here my setup Asus Rampage Extreme socket 775 Asus ENGTX295 (dual gpu) 1792MB , Both gpu's have the same id: 10de:05e0 (I dont have to insert the "0x05eb10de&0xfff8ffff" for this card) intel4x:~ ginobadouri$ gfxutil -f Display DevicePath = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) I'm currently running OSX 10.5.8 with the EVGA GT200 drivers and ATY_Init.kext. My bootloader is Chameleon 2 rc3 Here's my /Extra/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">'>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>920400000100000002000000430200000c00000002010c00d041030a000000000101060000010 101060000000101060000020101060000007fff040022000000400031002c00640065007600690063 0065005f00740079007000650000000b000000646973706c6179220000005600520041004d002c007 4006f00740061006c00730069007a0065000000080000000000003820000000400031002c0063006f 006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163140000004000300 02c006e0061006d0065000000120000004e5644412c446973706c61792d411e00000072006f006d00 2d007200650076006900730069006f006e0000002e0000004e5649444941204765466f72636520475 45820323935204f70656e474c20456e67696e65205b4546495d1c0000006400650076006900630065 005f0074007900700065000000100000004e5644412c4765466f72636514000000400031002c006e0 061006d0065000000120000004e5644412c446973706c61792d420e0000006e0061006d0065000000 0f0000004e5644412c506172656e7420000000400030002c0063006f006d007000610074006900620 06c00650000000e0000004e5644412c4e564d6163100000004e005600430041005000000018000000 05000000000003000c0000000000000b0000000022000000400030002c00640065007600690063006 5005f00740079007000650000000b000000646973706c6179100000006d006f00640065006c000000 1a0000004e5649444941204765466f7263652047545820323935430200000c00000002010c00d0410 30a000000000101060000010101060000000101060000000101060000007fff040022000000400031 002c006400650076006900630065005f00740079007000650000000b000000646973706c617922000 0005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000003820 000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4 e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706c6179 2d411e00000072006f006d002d007200650076006900730069006f006e0000002e0000004e5649444 941204765466f7263652047545820323935204f70656e474c20456e67696e65205b4546495d1c0000 006400650076006900630065005f0074007900700065000000100000004e5644412c4765466f72636 514000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d420e00 00006e0061006d00650000000f0000004e5644412c506172656e7420000000400030002c0063006f0 06d00700061007400690062006c00650000000e0000004e5644412c4e564d6163100000004e005600 43004100500000001800000005000000000003000c0000000000000b0000000022000000400030002 c006400650076006900630065005f00740079007000650000000b000000646973706c617910000000 6d006f00640065006c0000001a0000004e5649444941204765466f7263652047545820323935</string> </dict> </plist> The device string was generated from your example gfx.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>PciRoot(0x0)/Pci(0x1,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>NVCAP</key> <data> BQAAAAAAAwAMAAAAAAAACwAAAAA= </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>NVIDIA GeForce GTX 295 OpenGL Engine [EFI]</string> </dict> <key>PciRoot(0x0)/Pci(0x1,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>NVCAP</key> <data> BQAAAAAAAwAMAAAAAAAACwAAAAA= </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>NVIDIA GeForce GTX 295 OpenGL Engine [EFI]</string> </dict> </dict> </plist> The first PCIRoot key is what gfxutil -f Display shows.. The second is almost the same only I changed the last part from 0x2 to 0x0. I don't know if this is right.. cant gfxutil give me both PCI keys? I'm not using any smbios.plist or dsdt.aml files. I've cloned the Snow Leopard final disc into a seperate partition and only added fakesmc.kext (for SL) into /S/L/E Then recreated the kextcache. When SL boots I can see fakesmc and NVDANV50Hal being loaded but when the screen inits it only gives a black screen and hangs. The same happens for 10.5.8 when I try to boot it without ATY_Init.kext. So there must be something wrong with my gfx.plist? Link to comment Share on other sites More sharing options...
meroy Posted September 9, 2009 Share Posted September 9, 2009 Ok here my setup Asus Rampage Extreme socket 775 Asus ENGTX295 (dual gpu) 1792MB , Both gpu's have the same id: 10de:05e0 (I dont have to insert the "0x05eb10de&0xfff8ffff" for this card) intel4x:~ ginobadouri$ gfxutil -f Display DevicePath = PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) I'm currently running OSX 10.5.8 with the EVGA GT200 drivers and ATY_Init.kext. My bootloader is Chameleon 2 rc3 gfxutil -f display reported this for your first PciRoot entry. Okay, this one is correct. PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0) Acquire IORegistryExplorer. Remove the GFX EFI string from your boot plist file. Put back the ATY_Init Netkas extension. Refresh the Extension.mkext file: (assuming you installed ATY_Init under /S/L/E) sudo kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions. Boot using -x32. Run IORegistryExplorer. Select IODeviceTree from the first pull-down menu. Type display in the search field. Click on each display@0 or GFX@0 entries. Look for NVCAP and write those values somewhere. Also pay close attention to the IODeviceTree value for both displays (just below the search field). This will help determine the correct setting for the 2nd PciRoot entry in your gfx.plist file. The NVCAP value is what ATY_Init injected. You want to use and convert this for your gfx.plist NVCAP entry. This is what I did to get my single pcb edition working. Both PciRoot and NVCAP entries must be correct. See if both NVCAP entries are the same for both GPUs. If not, you will need to adjust accordingly inside your gfx.plist file. Good luck. Link to comment Share on other sites More sharing options...
MastaG Posted September 9, 2009 Share Posted September 9, 2009 Thanks bro it worked:) You're the man! I've found another gfx.plist from a french site which was closer to my system. I used PlistEdit Pro to edit in the NVCAP and NVPM values which I got from IORegistryExplorer and ATY_Init.kext IORegistryExplorer is a great app since it shows the correct PciRoot keys for both adapters. <?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)/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>VRAM,totalsize</key> <data> AAAAIA== </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.01</string> </dict> <key>PciRoot(0x0)/Pci(0x1,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> BAAAAAAAAwAMAAAAAAAABwAAAAA= </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.02</string> </dict> </dict> </plist> IORegistryExplorer shows NVCAP for both adapters but the NVPM value only shows up on the second adapter, so I removed it from the first one in my gfx.plist All works great now and both dvi ports work. It only reports the VideoRAM wrong. The first cards shows up with both connected displays and 896MB and the second adapter only shows 512MB without any connected displays but that's ok. Thanks for everything! Link to comment Share on other sites More sharing options...
meroy Posted September 9, 2009 Share Posted September 9, 2009 It only reports the VideoRAM wrong. The first cards shows up with both connected displays and 896MB and the second adapter only shows 512MB without any connected displays but that's ok. You're almost there. You can fix your ram setting. Change the value for the first VRAM,totalsize setting from AAAAIA== to AAAAOA==. Both need to be set to AAAAOA== for your GTX 295 card (each GPU having 896 MB of ram). Congratulations. Link to comment Share on other sites More sharing options...
Zerix Posted September 10, 2009 Share Posted September 10, 2009 You're almost there. You can fix your ram setting. Change the value for the first VRAM,totalsize setting from AAAAIA== to AAAAOA==. Both need to be set to AAAAOA== for your GTX 295 card (each GPU having 896 MB of ram). Congratulations. I am in exactly this same position *scratching head* I have made the changes and added AAAAOA== for both VRAM,totalsize yet SnowLeopard is reporting the second GPU as 512Mb still. Strange. I wonder if OpenCL sees them .. Im gonna go check -Z Link to comment Share on other sites More sharing options...
meroy Posted September 10, 2009 Share Posted September 10, 2009 I am in exactly this same position *scratching head* I have made the changes and added AAAAOA== for both VRAM,totalsize yet SnowLeopard is reporting the second GPU as 512Mb still. Did you remember to remove ATY_Init.kext from /S/L/E and refresh your Extensions.mkext. The presence of ATY_Init.kext will override GFX entries configured in the boot plist EFI string. If you want to keep ATY_Init.kext in place, change VRAM,totalsize inside ATY_Init.kext/Contents/Info.plist to AAAAOA== and refresh your Extensions.mkext. sudo kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions Link to comment Share on other sites More sharing options...
meroy Posted September 10, 2009 Share Posted September 10, 2009 Run this command to refresh the system kext cache files under Snow Leopard: sudo kextcache -system-caches This will refresh the following files: /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Caches/com.apple.kext.caches/Directories/System/Library/Extensions/* IOKitPersonalities_i386.ioplist.gz IOKitPersonalities_x86_64.ioplist.gz KextIdentifiers.plist.gz KextPropertyValues_OSBundleHelper_i386.plist.gz KextPropertyValues_OSBundleHelper_x86_64.plist.gz Link to comment Share on other sites More sharing options...
Zerix Posted September 10, 2009 Share Posted September 10, 2009 Did you remember to remove ATY_Init.kext from /S/L/E and refresh your Extensions.mkext. The presence of ATY_Init.kext will override GFX entries configured in the boot plist EFI string. If you want to keep ATY_Init.kext in place, change VRAM,totalsize inside ATY_Init.kext/Contents/Info.plist to AAAAOA== and refresh your Extensions.mkext. sudo kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions Ok, headed home from work now. Going to try this right away! I was under the impression that I needed ATY_init.kext to be able to operate at all but I've been reading a bit and I guess all it really does is allows the dual monitor stuff to work. I think I have that right ... right? -Z Link to comment Share on other sites More sharing options...
meroy Posted September 11, 2009 Share Posted September 11, 2009 Ok, headed home from work now. Going to try this right away! I was under the impression that I needed ATY_init.kext to be able to operate at all but I've been reading a bit and I guess all it really does is allows the dual monitor stuff to work. I think I have that right ... right? -Z Both displays works on my system without the Netkas ATY_Init kext. The EFI string in my boot plist is all I have configured for my graphics card. In any event, that explains why you're still seeing 512 MB. The ATY_Init defaults to 512 MB. Folks are able to change the VRAM,totalsize in ATY_Init plist to match their setup. Refresh Extensions.mkext afterwards. You should see 896 MB for both GPUs on your GTX 295 card. Link to comment Share on other sites More sharing options...
Raph4 Posted September 11, 2009 Share Posted September 11, 2009 for GTX295 Dual-PCB new version only rev.62.00.6C.00.01/02 and ID:05eb see my post here: http://www.darwinx86.org/guides/installer-...280#comment-284 Link to comment Share on other sites More sharing options...
meroy Posted September 12, 2009 Share Posted September 12, 2009 for GTX295 Dual-PCB new revision only (62.00.6C.00.01/02)see my post here: http://www.darwinx86.org/guides/installer-...280#comment-284 Thank you for the kext. I no longer need to add the 05eb entry to the NVDANV50Hal.kext plist file. Your kext works from /Extra/Extensions.mkext too. Awesome. Link to comment Share on other sites More sharing options...
Aliased Teen Posted September 24, 2009 Share Posted September 24, 2009 I'm having a few issues getting my Gigabyte GTX 295 (single PCB) recognised properly under SL. I have PC EFI 10.3, which apparently has a "graphics injector" option that I'm using, as the Enabler package does not seem to want to install. Likewise with the EVGA drivers, they refused to install, but I manually installed the three packages inside the single master package. I've also added my dev-id (05eb10de) to the Info.plist in NVDANV50.kext. System Profiler recognises two video cards, one named "Display" and one named "Unknown". The unknown one correctly reports 896MB of VRAM, the display reports nothing at all. The OpenGL extension viewer only offers the Apple software renderer, making me think that drivers aren't loading correctly. Here is my kernel boot up log (I've snipped the timestamps and "localhost kernel[0]:" for brevity) that backs up this thought: *snip* Any ideas? EDIT: Solved my dilemma, explained below. Link to comment Share on other sites More sharing options...
ANARCHiNTOSH Posted September 25, 2009 Share Posted September 25, 2009 can any one explain step by step how to install an EVGA GTX 295 Coop in snow leopard? im quite new to all this and i cant quite get my head around meroys instructions! im not sure where id get hold of the NVDANV50Hal.kext .... im running a retail snow install on a GA-EX58-UD5 using Digital dreamers script, it currently shows up in system profiler as having only 32MB of VRAM, and i know that isnt right! snow leopard with a GTX295 would be wicked Link to comment Share on other sites More sharing options...
Aliased Teen Posted September 28, 2009 Share Posted September 28, 2009 can any one explain step by step how to install an EVGA GTX 295 Coop in snow leopard? im quite new to all this and i cant quite get my head around meroys instructions! im not sure where id get hold of the NVDANV50Hal.kext .... im running a retail snow install on a GA-EX58-UD5 using Digital dreamers script, it currently shows up in system profiler as having only 32MB of VRAM, and i know that isnt right! snow leopard with a GTX295 would be wicked It is indeed wicked. I too used d_d's script, albeit with a Gigabyte GTX 295 (rev 2.0) and a GA-EX58-UD4P. The first time around, I made the (apparently quite silly) mistake of force-installing the EVGA drivers for OS X 10.5 and trying (but failing) to install netkas' graphics enabler. It turns out that netkas' enabler is already built into his PC-EFI tool. What I did was choose Chameleon 2.0 RC3 bootloader from d_d's script (this requires a DSDT file in your /Extra directory) and replaced the /boot file with PC EFI v 10.3. I then turned on the option in the /Extra/com.apple.boot.plist for GraphicsEnabler = yes. This caused boot-up to hang as it recognised a video card, but could not find drivers for it. To solve this, I edited the Info.plist in NVDANV50.kext (in /System/Library/Extensions) and added my device id 0x05eb10d0. The system now booted successfully, but showed "Display" and "Unknown" as the graphics adaptors. I finally turned off the graphics enabler and instead opted for the EFI string as meroy explained, which gave me great joy as it provided the correct information in System Profiler. Just a short while ago I updated to 10.6.1 and my computer would hang at boot up. I confirmed my suspicion (using my Macbook) that the update had modified the NVDANV50.kext file. I then switched to the alternative of using Rph4's NVGTX295.Fix.kext in my /Extra folder. This allows for a nice vanilla Snow Leopard with complete GTX 295 support. (Sorry if this was long-winded, but you might find this account of what I tried and how it went wrong useful!) Link to comment Share on other sites More sharing options...
ANARCHiNTOSH Posted September 30, 2009 Share Posted September 30, 2009 It is indeed wicked. I too used d_d's script, albeit with a Gigabyte GTX 295 (rev 2.0) and a GA-EX58-UD4P. The first time around, I made the (apparently quite silly) mistake of force-installing the EVGA drivers for OS X 10.5 and trying (but failing) to install netkas' graphics enabler. It turns out that netkas' enabler is already built into his PC-EFI tool. What I did was choose Chameleon 2.0 RC3 bootloader from d_d's script (this requires a DSDT file in your /Extra directory) and replaced the /boot file with PC EFI v 10.3. I then turned on the option in the /Extra/com.apple.boot.plist for GraphicsEnabler = yes. This caused boot-up to hang as it recognised a video card, but could not find drivers for it. To solve this, I edited the Info.plist in NVDANV50.kext (in /System/Library/Extensions) and added my device id 0x05eb10d0. The system now booted successfully, but showed "Display" and "Unknown" as the graphics adaptors. I finally turned off the graphics enabler and instead opted for the EFI string as meroy explained, which gave me great joy as it provided the correct information in System Profiler. Just a short while ago I updated to 10.6.1 and my computer would hang at boot up. I confirmed my suspicion (using my Macbook) that the update had modified the NVDANV50.kext file. I then switched to the alternative of using Rph4's NVGTX295.Fix.kext in my /Extra folder. This allows for a nice vanilla Snow Leopard with complete GTX 295 support. (Sorry if this was long-winded, but you might find this account of what I tried and how it went wrong useful!) Thanks pal, any help is appreciated! So at the moment my progress is stalled as i wait for replacement DDR3 to arrive (my ocz goldies were buggin out), but i think i understand how to get it working now. From my understanding i would need to: 1.convert meroy's gfx.plist to hex using gfxutil not quite sure what "Run gfxutil -f display and change the PciRoot key" means 2.insert the newly created efi string into the boot plist 3.insert 0x05eb10de&0xfff8ffff into NVDANV50Hal.kext/Contents/Info.plist 4.run as root --does this mean opening terminal with administrator privileges?: kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions When my memory arrives ill give it a try. Link to comment Share on other sites More sharing options...
hackdan Posted November 9, 2009 Share Posted November 9, 2009 for GTX295 Dual-PCB new version only rev.62.00.6C.00.01/02 and ID:05ebsee my post here: http://www.darwinx86.org/guides/installer-...280#comment-284 Hi Rph4 I have 2 dual PCB in QUAD SLI PNY GTX 295 cards in 10.6.1 Retail installation over ASUS WS P6T7 SuperComputer motherboard, I follow your steps but no luck, the mode VESA was better but I can't enable OpenCL / QE / CI, .I m desperate so please please please let me a anti-idiot guide step by step , I m very frustated with me computer. i was saving for a long time by buy it.... Link to comment Share on other sites More sharing options...
hackdan Posted November 14, 2009 Share Posted November 14, 2009 +1 I appreciate all that you guys are doing, but this isn't very noob-friendly at all. First I see appending the NV50 file with those strings, then another saying don't worry about it because a kext fixes it. Could someone graciously write a step-by-step? Hell, I'll paypal somebody a few bucks if they wanted. haha http://aquamac.proboards.com/index.cgi?boa...&thread=959 Hey check this is very long but i have a advance .... I think.... wherever maybe in short time we have the anti-idiot guide of ours dreams! Link to comment Share on other sites More sharing options...
meroy Posted November 16, 2009 Share Posted November 16, 2009 hackdan, go here for more noob friendly post. I'm not able to monitor these posts. I hope this will help you. You have a dual-pcb gtx 295. My plist will not work with your card as I have the single pcb edition. My plist doesn't have the @2 entires that may be needed by your card(s). http://www.insanelymac.com/forum/index.php?showtopic=184318 Link to comment Share on other sites More sharing options...
flint_MAC_ru Posted November 20, 2009 Share Posted November 20, 2009 2 merroy: good seeing you keeping up with GTX295 help - thanks a lot. I've translated your guides to Russian mac-forrums for those how have 295, however 10.6.2 changed the situation - strings are no longer working in boot.plist and only way to boot back after the update is to remove strings, so the result is - basic mode with efianabler. I want to belive that you fix it somehow (at least for single pcb you have), so could you make a guide for 10.6.2 users? Link to comment Share on other sites More sharing options...
meroy Posted November 20, 2009 Share Posted November 20, 2009 2 merroy: good seeing you keeping up with GTX295 help - thanks a lot. I've translated your guides to Russian mac-forrums for those how have 295, however 10.6.2 changed the situation - strings are no longer working in boot.plist and only way to boot back after the update is to remove strings, so the result is - basic mode with efianabler. I want to belive that you fix it somehow (at least for single pcb you have), so could you make a guide for 10.6.2 users? The strings continues to work for me under 10.6.2. Go here: http://www.insanelymac.com/forum/index.php?showtopic=184318. My current plist is posted there. Did you remember to add the pci id to NVDANV50HAL? Not sure which card you have single or dual PCB design. There is no need to add the PCI ID if you install NVGTX295.zip from this post: http://www.darwinx86.org/guides/installer-...280#comment-284 This zip file contains a kext: NVGTX295.Fix.zip. Add this to your /Extra/Extensions/. Link to comment Share on other sites More sharing options...
flint_MAC_ru Posted November 21, 2009 Share Posted November 21, 2009 The strings continues to work for me under 10.6.2. Go here: http://www.insanelymac.com/forum/index.php?showtopic=184318. My current plist is posted there. Did you remember to add the pci id to NVDANV50HAL? Not sure which card you have single or dual PCB design. There is no need to add the PCI ID if you install NVGTX295.zip from this post: http://www.darwinx86.org/guides/installer-...280#comment-284 This zip file contains a kext: NVGTX295.Fix.zip. Add this to your /Extra/Extensions/. thanks a lot meroy - it woks!!! i completely forget about device id (i have single pcb). I'll let guys from http://www.applelife.ru know as well. I tried both ways - add id to NVDANV50Hal.kext & NVDANV50Hal.kext and by adding NVGTX295.Fix.zip to Extra. Both OK!!! Link to comment Share on other sites More sharing options...
ANARCHiNTOSH Posted November 21, 2009 Share Posted November 21, 2009 hey everyone, ive written a complete noob friendly guide explaining meroys method and created a pack containing everything you need to get it working i also translated Raph4s kext instructions, which is attached to my guide. mmm noob friendly guide meroy, whats the lowdown on dual monitor mode? its not working on my installation but ive heard other people have had success. i just get two black screens when i plug in my second monitor. hmm. Link to comment Share on other sites More sharing options...
meroy Posted November 22, 2009 Share Posted November 22, 2009 meroy, whats the lowdown on dual monitor mode? its not working on my installation but ive heard other people have had success. i just get two black screens when i plug in my second monitor. hmm. Try the following for the NVCAP value: Look for NVCAP in your plist file and replace the value with this one for both PciRoot entries in your plist file. This will enable both displays for your setup. BQAAAAAAAwAMAAAAAAAACwAAAAA= I don't think it's possible to come up with one plist template to accommodate both the dual and single PCB designs. Congrats on making your GTX 295 card work under SL. The value above will complete your setup and allow you to use 2 displays. Remember to breath when you see both displays enabled under SL. Link to comment Share on other sites More sharing options...
Recommended Posts