Project OS X Forums > Nvenabler Testing And Discussion

mantu

Dec 19 2011, 11:45 PM

QUOTE (mantu @ Dec 19 2011, 12:35 PM)

just a simple question...
how can i know if my geforce fx 5200 pci is supported by nvenabler?
it's a week i'm trying to get it work on a lion retail install...
but now my suspect is that maybe it isn't supoprted...

many thank's in advice

attached is my ioreg:
Click to view attachment

and here is an extract of kernel.log

CODE

Dec 20 00:29:20 host518 kernel[0]: NVEnabler: init : begin
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : probe
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : ROM shadow enable
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : patch PRAMIN
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: dcb table at offset 0xae74
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: dcb numentries 0
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: numentries = 0 num_outputs = 0
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: Channel 1: 00
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: Channel 2: 00
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Model found: GeForce FX 5200
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG VRAM: 256
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @0,compatible
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @0,device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @0,name
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @1,compatible
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @1,device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property @1,name
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG  Setting property device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler::probe fails
Dec 20 00:29:20 host518 kernel[0]: NVDA,Display-B: Not usable

someone can please help me?

the graphic card seems to be correctly recognized but i can only use 1024x768 resolution...
many thank's in advice

kossak

Dec 21 2011, 04:34 PM

I'm sorry about this but my attachments are missing from the post above so please bear with me.

I'll attach here my ioreg dump and also my video BIOS which I extracted from DOS using nvflash.exe

I already tried about 10 or 20 different display-cfg combinations. I think the problem is that a certain instruction is needed to force detection on the output ports. In windows I press FN+F4 to do that. "detect displays" on OSX does absolutely nothing.

See 2 posts above for my original problem.

Maybe someone could patch my ROM or something? I attached it in base64 since I cant seem to upload binary files.

I've been trying to use chimera and its GraphicsEnabler also, injecting display-cfg strings via boot.plist.

Please help, I'll donate.

Click to view attachment
Click to view attachment

Gringo Vermelho

Dec 22 2011, 02:26 AM

QUOTE (mantu @ Dec 19 2011, 09:35 AM)

how can i know if my geforce fx 5200 pci is supported by nvenabler?

NVEnabler is not the problem here, the problem is that your video card is too old, it is not supported by the OS X Nvidia drivers.

Clubber_77

Dec 22 2011, 10:49 AM

how to disable debug mode in 64bit version?

Krazubu

Dec 22 2011, 12:06 PM

Clubber_77
No way

kossak
I'll look into your ROM
I need some more details on your output table. Your list seems to be quick n dirty.
You tell me you have 2 VGA, I only see one in the ROM, you tell you have 1 DVI, I see 4 DVI/HDMI capable outputs.
Please list exactly all the supported outputs, including those using some passive adapter (like DP to DVI).
I'll have to kill all the docking station outputs to make the built-in ones work.

EDIT : here's a trial, don't know what it's worth Click to view attachment
Use this NVCAP : 04000000 00000300 7c000000 0000000a 00000000
This display-cfg : for display A : ffff0100
for display B it will depend on the output you try, there are 3 DVI capable ones in the current BIOS, you'll have to try each : 00ff0901 or 00ff0601 or 00ff0001

kossak

Dec 23 2011, 12:26 AM

QUOTE (Krazubu @ Dec 22 2011, 12:06 PM)

kossak
I'll look into your ROM
I need some more details on your output table. Your list seems to be quick n dirty.
You tell me you have 2 VGA, I only see one in the ROM, you tell you have 1 DVI, I see 4 DVI/HDMI capable outputs.
Please list exactly all the supported outputs, including those using some passive adapter (like DP to DVI).
I'll have to kill all the docking station outputs to make the built-in ones work.

EDIT : here's a trial, don't know what it's worth Click to view attachment
Use this NVCAP : 04000000 00000300 7c000000 0000000a 00000000
This display-cfg : for display A : ffff0100
for display B it will depend on the output you try, there are 3 DVI capable ones in the current BIOS, you'll have to try each : 00ff0901 or 00ff0601 or 00ff0001

Thanks! I'm at home now, so I can't test DVI (I don't have a displayport adapter, so I'm using a standard vga analog).

I tested your rom with a simple analog VGA monitor and still no dice. used your NVCAP and ffff0100 for display-a and 00ff0001 for display b. No image on external monitor (primary is fine), and "detect displays" seems to be doing nothing.

I'll let you know tomorrow what happens with a DVI monitor connected to the docking station.

Just to be clear:

This laptop has:
- A primary monitor (doh

)
- A standard analog VGA port
- A DisplayPort

Then the docking station has:
- A standard DVI port
- A standard analog VGA port (might be converted from DVI, but I can't tell)
- A non standard DisplayPort connector (I believe its the standard for non mobile equipment).

Here are the specs for the docking station. you can see the full specs of it here:

http://h30094.www3.hp.com/product/sku/1021...2FNZ223AA%23ABA

I'll also attach the following extra information:

- My current DSDT.aml: this might be important because I extracted it from the laptop and had to comment out a specific portion that didn't compile. This portion is related to display detection routines, I believe. I'll also attach the original extracted DSDT so you can see what I did (I deleted all references to an externalint VGDD). What seems to happen is that the key combo to force detection (FN-F4) does nothing after I boot this DSDT. I usually can cycle through screens using that combo even on POST, but after the DSDT load I have to cold boot the PC to do that again.
- my bdmesg and dmesg.

Thanks again. Hope to hear from you soon and have a nice Chrismas btw

kossak

Dec 23 2011, 12:58 AM

Update: I GOT SIGNAL!

patched rom (krazubu)
NVCAP: 04000000000003007c0000000000000a00000000
DISPLAYA: FFFF0100
DISPLAYB: 00FF0601

I can use analog VGA out using this config on Chimera 1.7. It works great! detection doesn't work after boot (it has to be plugged in on boot).

I'll try tomorrow with DVI. This is progress! Thanks!

If DVI works I'll switch to NVEnabler. Chimera is great to test but I think they are missing a lot of injects. My card has the "chirping" sound and is not working at full performance, I think because its in the lowest mode of power saving.

EDIT: DVI works perfectly also with the above parameters. Looks like the Laptop's analog VGA port is passively converted from digital signal.

I'm a happy camper! Now I just need to:

- Patch AppleHDA (VoodooHDA gives me a lot of kernel panics on boot in 64 bit mode)
- Get sleep to work and remove a nagging delay on shutdown and reboot (probably need to clean my DSDT for this)
- Get Nvidia power states going (NVPM maybe, also probably related to sleep not working)
- Get my Broadcom 43224AG wifi card working (I might need to remove whitelist BIOS from my 8540p and modify the subvendor ID, not sure yet.)

Thanks krazubu for your help!

mantu

Dec 29 2011, 08:20 AM

QUOTE (Gringo Vermelho @ Dec 22 2011, 03:26 AM)

NVEnabler is not the problem here, the problem is that your video card is too old, it is not supported by the OS X Nvidia drivers.

so.... no way to use old kexts?

raultaboraz

Dec 29 2011, 07:14 PM

Click to view attachmentHi all,

I have 10.6.0 *working* perfect installation with 2 x DVI output with 9600 GSO card 512 Mb (QE / CI, perfect, all res, double DVI outputs).
When I update to 10.6.8 or even 10.7.0, it works BUT only with 1 DVI out. When I turn on second screen all is going to a a black screen...

Then:

Using 2 DVI Outputs (cinema Projector + Samsung LCD) = blackscreen
Using 1 DVI Output only (Samsung LCD only) = works! (QE / CI, perfect, all res, double DVI outputs)

I have read that this card works *native* ok when I can't get it working.

And also I extracted ROM (uploaded to Megaupload here) using a USB-portable Windows XP and nvflash --new and I get a lot of info about my 9600 GSO. With this NVCAP code I generated a hex string using OSXtools, but I am getting blackscreen again...

And also I have used NVenabler kext, it is detected well, but it does not work

Do you know what would be cause for this weird problem?? I really need to update my system (because some software requeriments) but I am not sure if I need to boy another GFX card

Thank you very much!

Gringo Vermelho

Dec 30 2011, 01:21 AM

QUOTE (mantu @ Dec 29 2011, 06:20 AM)

so.... no way to use old kexts?

No. Nvidia drivers and OpenGL framework from 10.5.5 will definitely not work on Lion.

mantu

Dec 30 2011, 08:33 AM

QUOTE (Gringo Vermelho @ Dec 30 2011, 02:21 AM)

No. Nvidia drivers and OpenGL framework from 10.5.5 will definitely not work on Lion.

so maybe i can try with snow leopard?

Gringo Vermelho

Dec 30 2011, 08:32 PM

You can try but I doubt it will work.
The only thing I can say for certain is that you need to stay in 32-bit mode, boot with arch=i386.

mantu

Dec 30 2011, 08:42 PM

QUOTE (Gringo Vermelho @ Dec 30 2011, 09:32 PM)

You can try but I doubt it will work.
The only thing I can say for certain is that you need to stay in 32-bit mode, boot with arch=i386.

If i want to try this way i have to use nvenabler also?! Or only the single kext like nvkush (that i was using in leopard)...

Many tnx

Gringo Vermelho

Dec 30 2011, 09:46 PM

NVKush should work fine in 32-bit Snow Leopard.

raultaboraz

Jan 3 2012, 11:01 AM

please anyone could point me with some help? I really appreciate your ideas... Thank you all

QUOTE (raultaboraz @ Dec 29 2011, 08:14 PM)

Click to view attachmentHi all,

I have 10.6.0 *working* perfect installation with 2 x DVI output with 9600 GSO card 512 Mb (QE / CI, perfect, all res, double DVI outputs).
When I update to 10.6.8 or even 10.7.0, it works BUT only with 1 DVI out. When I turn on second screen all is going to a a black screen...

Then:

Using 2 DVI Outputs (cinema Projector + Samsung LCD) = blackscreen
Using 1 DVI Output only (Samsung LCD only) = works! (QE / CI, perfect, all res, double DVI outputs)

I have read that this card works *native* ok when I can't get it working.

And also I extracted ROM (uploaded to Megaupload here) using a USB-portable Windows XP and nvflash --new and I get a lot of info about my 9600 GSO. With this NVCAP code I generated a hex string using OSXtools, but I am getting blackscreen again...

And also I have used NVenabler kext, it is detected well, but it does not work

Do you know what would be cause for this weird problem?? I really need to update my system (because some software requeriments) but I am not sure if I need to boy another GFX card

Thank you very much!

mantu

Jan 4 2012, 12:01 PM

QUOTE (Gringo Vermelho @ Dec 30 2011, 10:46 PM)

NVKush should work fine in 32-bit Snow Leopard.

i got it to work with lion booted in 32bit and this procedure (from another post in this forum):

geForce 5000 series (Support dropped with 10.5.6 you must use prior kexts):
Add your device ID in /system/library/extensions/NVDAResman.kext/contents/info.plist
Add your device ID in /system/library/extensions/NVDANV30Hal.kext/contents/info.plist
Find/download an injecter (any one will do, they're basically the same thing, only plists differ)
Add your device ID in (some_injecter.kext)/contents/info.plist
In the same plist, set the NVCAP string correctly (More informations here) and replace the IOProbeScore number by 0.

the card works ok now and monitor resolution it's ok... but animation are very slow (Seems that qe/ci not working...)

anyone has an idea for this problem?

many tnx!

khorght

Jan 5 2012, 04:25 PM

OS: Lion 10.7.2 (iAtkos L2)
Hardware: HP IQ512 (all-in-one pc with built-in 22" lcd, video - GeForce 9300M GS 256mb, only two outputs - built-in LCD and S-Video)
After installing eabler64 get black screen< tried to add display-cfg(03010000 and ffff0001) to info.plist, but no result. connected to device through the apple remote display - i can change resolution, but in "about tho mac" only graphic card an no displays found.
Enabler extracts this NVCAP: 0400000000000100fe0000000000000a00000000
NVCAPMaker give this: 04000000 00000100 02000000 00000007 00000000
in attached archive i've placed ioreg,dsdt (tried run nvenabler with and without it), rom extracted from video card and current nvenabler64.kext.

I Hope someone can help me.

Click to view attachment

gabriel2007

Jan 5 2012, 04:49 PM

QUOTE (khorght @ Jan 5 2012, 11:55 AM)

OS: Lion 10.7.2 (iAtkos L2)
Hardware: HP IQ512 (all-in-one pc with built-in 22" lcd, video - GeForce 9300M GS 256mb, only two outputs - built-in LCD and S-Video)
After installing eabler64 get black screen< tried to add display-cfg(03010000 and ffff0001) to info.plist, but no result. connected to device through the apple remote display - i can change resolution, but in "about tho mac" only graphic card an no displays found.
Enabler extracts this NVCAP: 0400000000000100fe0000000000000a00000000
NVCAPMaker give this: 04000000 00000100 02000000 00000007 00000000
in attached archive i've placed ioreg,dsdt (tried run nvenabler with and without it), rom extracted from video card and current nvenabler64.kext.

I Hope someone can help me.

I have the same touchsmart and I am right now trying to install snow leopard and it's the same , maybe we can help each other PM if you want to

khorght

Jan 5 2012, 08:59 PM

QUOTE (Krazubu @ Jan 5 2012, 09:44 PM)

Khorght there's no archive in your post.

i've clicked browse but forgot to click upload...

i've made some sniffing and find out my EDID:
00 FF FF FF FF FF FF 00 3A C4 00 00 00 00 00 00
2D 0C 01 03 80 20 14 00 EA A8 E0 99 57 4B 92 25
1C 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 7C 2E 90 A0 60 1A 1E 40 18 20
26 00 42 C9 10 00 00 18 00 00 00 FC 00 4E 76 69
64 69 61 20 44 65 66 61 75 6C 00 00 00 FC 00 74
20 46 6C 61 74 20 50 61 6E 65 6C 00 00 00 00 FD
00 00 3C 1D 41 0C 00 00 20 20 20 20 20 00 00 6E

tried to do some magic with AAPL but os even can't boot

Krazubu, if you interested a can dump something from my Macbook A1181 and maybe tomorrow a can get iMac MC814 and dump something again))

Click to view attachment

Krazubu

Jan 7 2012, 10:08 AM

Try this ROM with those display-cfg :

Click to view attachment
03010300 and ffff0001

Let it set the NVCAP.

khorght

Jan 7 2012, 06:41 PM

QUOTE (Krazubu @ Jan 7 2012, 11:08 AM)

Try this ROM with those display-cfg :

Click to view attachment
03010300 and ffff0001

Let it set the NVCAP.

Sorry, but nothing changed.What i've made - i've added two display-cfg sections to the plist of enabler64, removed skip_vbios section and added vbios <Data> patched bios copy pasted from HexFiend(free hex editor).i've uploaded current IOService and IODeviceTree plus kext with changes in plist according to the first post and your suggestions in previous post.i've found some dsdt injections for my card the only difference between out dsdts regarding graphics was - in my dsdt graphics card is VGA on p0p1 in dsdt i'fe found on some forum it's NVID on p0p1. it seems for me it's an dead end...one more thing - my device haven't EC in dsdt and i see no SBUS so if display-cfg have some offset in it i don't think it applyed somewhere or applied in wrong place.is it possible somehow to get those offsets by booting into vest mode?

Click to view attachment

Krazubu

Jan 8 2012, 10:26 AM

I suspected it wouldn't work because what I found was already rather ok.
IMO the problem is about the display being not detected for the same unknown reason that we find with VAIO and some NVS cards.

QUOTE

so if display-cfg have some offset in it

It doesn't.

Anyway, we don't care about DSDT at all. Simply erase everything related to the GFX branch from it, all that stuff can interfere wrongly.

khorght

Jan 8 2012, 02:06 PM

QUOTE (Krazubu @ Jan 8 2012, 11:26 AM)

I suspected it wouldn't work because what I found was already rather ok.
IMO the problem is about the display being not detected for the same unknown reason that we find with VAIO and some NVS cards.

It doesn't.

Anyway, we don't care about DSDT at all. Simply erase everything related to the GFX branch from it, all that stuff can interfere wrongly.

I think i've found the core of the problem - my motherboard have two lvds connectors plus unsoldered vga. If i disassemble 9300M GS and connect lcd panel to another connector i can boot using integrated(unsupported by osx) GMA3100, i think here is the problem and solution will never happen. May the luck be with you Krazubu and i think you can remove all my posts from this topic.

Gringo Vermelho

Jan 9 2012, 04:30 AM

QUOTE (khorght @ Jan 8 2012, 12:06 PM)

i think you can remove all my posts from this topic.

Your posts could prevent someone from wasting their time and energy with the same hardware.

Gringo Vermelho

Feb 17 2012, 10:00 PM

Krazubu;

Some dude posted the ROM from the PNY Nvidia Quadro 4000 for Mac over at VoodooProjects.
Here it is if you want to have a look.
Click to view attachment

Slyr

Feb 18 2012, 10:25 AM

I am the DUDE:)
I have read this topic again and again, but it is too much for me, I need yours help.
I have made new topics for my card, you can find here:
http://www.projectosx.com/forum/index.php?showtopic=2340
http://forum.voodooprojects.org/index.php/topic,2342.0.html

I can make everything, but I need help step by step...
I use hacintosh since 5 years, so I am not new in this world...
Thx.

Krazubu

Feb 21 2012, 08:46 PM

Can you please clearly state the problem ? what works and what doesn't ?

Anyway, things to try :

Install NVEnabler and use following data :

NVCAP : 05000000000003000c0000000000000a00000000

Your card has one DVI-I port (DVI +VGA), one DVI-D (only DVI) and one DP.
You can't use DP and DVI-D at the same time.
The display-cfg strings have to be fixed for the combination you intend to use :
- If you wish to use DVI-I & DP : 03010000 - ffff0d01
- If you wish to use DVI-I & DVI-D : 03010000 - ffff0601

Slyr

Feb 25 2012, 02:24 PM

Hi Krazubu!

I wasn't at home, but now I tried your method, and it is working!!!!!!!!
You are the best programmer, who I know...

I don't used NVEnabler, only EFI string with your NVCAP.
Click to view attachment

CODE

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Boot Graphics</key>
    <string>Yes</string>
    <key>EthernetBuiltIn</key>
    <string>Yes</string>
    <key>GraphicsEnabler</key>
    <string>no</string>
    <key>Kernel</key>
    <string>mach_kernel</string>
    <key>Kernel Flags</key>
    <string>npci=0x2000</string>
    <key>Theme</key>
    <string>Apple Default</string>
    <key>Timeout</key>
    <string>2</string>
    <key>device-properties</key>
<string>6802000001000000010000005c0200000d00000002010c00d041030a00000000010106000001
0101060000007fff04001e00000072006f006d002d007200650076006900730069006f006e000000
2
700000051756164726f2034303030204d4143204f70656e474c20456e67696e65205b4546495d220
0
0000400030002c006400650076006900630065005f00740079007000650000000b00000064697370
6
c6179100000004e005600430041005000000022000000d39d34d34d34d34d34d37d34d1cd34d34d3
4
d34d34d34d1ad34d34d34d340e0000006e0061006d00650000000b000000646973706c6179140000
0
0400030002c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d0
0
6f00640065006c0000001300000051756164726f2034303030204d41430e0000004e00560050004d
0
00000200000000100000000000000000000000000000000000000000000000000000014000000400
0
31002c006e0061006d0065000000120000004e5644412c446973706c61792d422000000040003100
2
c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616322000
0
005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000008020
0
00000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4
e
564d616322000000400031002c006400650076006900630065005f00740079007000650000000b00
0
000646973706c61791c0000006400650076006900630065005f00740079007000650000000f00000
0
4e5644412c506172656e74</string>
    <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
    <dict>
        <key>@0,compatible</key>
        <string>NVDA,NVMac</string>
        <key>@0,device_type</key>
        <string>display</string>
        <key>@0,name</key>
        <string>NVDA,Display-A</string>
        <key>@1,compatible</key>
        <string>NVDA,NVMac</string>
        <key>@1,device_type</key>
        <string>display</string>
        <key>@1,name</key>
        <string>NVDA,Display-B</string>
        <key>NVCAP</key>
        <data>
        05000000000003000c0000000000000a00000000
        </data>
        <key>NVPM</key>
        <data>
        AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
        </data>
        <key>VRAM,totalsize</key>
        <string>0x80000000</string>
        <key>device_type</key>
        <string>NVDA,Parent</string>
        <key>model</key>
        <string>Quadro 4000 MAC</string>
        <key>name</key>
        <string>display</string>
        <key>rom-revision</key>
        <string>Quadro 4000 MAC OpenGL Engine [EFI]</string>
    </dict>
</dict>
</plist>

Karl

Feb 25 2012, 08:23 PM

QUOTE (Krazubu @ Feb 21 2012, 02:46 PM)

Install NVEnabler and use following data :

NVCAP : 05000000000003000c0000000000000a00000000

Your card has one DVI-I port (DVI +VGA), one DVI-D (only DVI) and one DP.
You can't use DP and DVI-D at the same time.
The display-cfg strings have to be fixed for the combination you intend to use :
- If you wish to use DVI-I & DP : 03010000 - ffff0d01
- If you wish to use DVI-I & DVI-D : 03010000 - ffff0601

Great Stuff! I love this forum! I'm just soaking it in just now, reading all of this stuff. Mine's not working yet (Quadro 4000 PC version), but I think this thread is the right track for me!

One question: Is the NVCAP different for the PC version?
I assume so, at this point, because the Quadro 4000 for mac has different output configuration than the PC version.

Anyway, I'll keep studying this. Thanks to all!

Gringo Vermelho

Feb 25 2012, 09:34 PM

@Slyr

You can delete this (exactly this, no more, no less) from your boot.plist, it is useless:

QUOTE (Slyr @ Feb 25 2012, 12:24 PM)

CODE

    <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
    <dict>
        <key>@0,compatible</key>
        <string>NVDA,NVMac</string>
        <key>@0,device_type</key>
        <string>display</string>
        <key>@0,name</key>
        <string>NVDA,Display-A</string>
        <key>@1,compatible</key>
        <string>NVDA,NVMac</string>
        <key>@1,device_type</key>
        <string>display</string>
        <key>@1,name</key>
        <string>NVDA,Display-B</string>
        <key>NVCAP</key>
        <data>
        05000000000003000c0000000000000a00000000
        </data>
        <key>NVPM</key>
        <data>
        AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
        </data>
        <key>VRAM,totalsize</key>
        <string>0x80000000</string>
        <key>device_type</key>
        <string>NVDA,Parent</string>
        <key>model</key>
        <string>Quadro 4000 MAC</string>
        <key>name</key>
        <string>display</string>
        <key>rom-revision</key>
        <string>Quadro 4000 MAC OpenGL Engine [EFI]</string>
    </dict>

Only what's inside the display-properties string is used.
The other stuff up there does nothing, unless it's converted to hex and placed in the display-properties string.
But you've done that already.

QUOTE (Karl @ Feb 25 2012, 06:23 PM)

Is the NVCAP different for the PC version?

Which outputs does the card have?
Use GPU-z on Windows to extract the ROM, zip it and attach it here. Use the Full Editor to attach files.

Karl

Feb 25 2012, 09:57 PM

Click to view attachment

QUOTE (Gringo Vermelho @ Feb 25 2012, 03:34 PM)

Which outputs does the card have?
Use GPU-z on Windows to extract the ROM, zip it and attach it here. Use the Full Editor to attach files.

Product Specifications for PC Quadro 4000
DVI-I (1), DP (2), Stereo (1)

The configuration and connector types are a bit different
The PC has only 1 PCI slot: 2 DP and a DVI-I
http://ecx.images-amazon.com/images/I/71XV...0L._AA1500_.jpg
Where as the Mac has 2 PCI slots: DVI-I, DP and the optional stereo connector.
http://images.nvidia.com/products/quadro-4...kets-medium.png

Thanks for your response!

I've attached file from GPU-z

Krazubu

Feb 26 2012, 08:53 PM

Karl,
your card has 3 outputs but OSX can support 2, so we have to sacrifice one. Which one do you prefer we disable ?
The DVI one also supports VGA (with adapter)
The 2 DP ones also support DVI (with adapter)

Karl

Feb 26 2012, 10:44 PM

QUOTE (Krazubu @ Feb 26 2012, 02:53 PM)

Karl,
your card has 3 outputs but OSX can support 2, so we have to sacrifice one. Which one do you prefer we disable ?
The DVI one also supports VGA (with adapter)
The 2 DP ones also support DVI (with adapter)

Currently I only used the DVI input and if I wanted to use another input for a second preview monitor, I'd use a DP.

Later in my workflow, I'd like the ability to purchase a 3D monitor. I'm not sure if I would have to use the 2 DP inputs, more research is required on my part. When it all works, it's easier to try things out...but in my case here, due to the limitations, I think I would like to disable one of the DP inputs.

I knew...
video ram: 0x80000000
location: PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)

but I had no idea about the connectors/NVCAP

Thanks for your support on this!

Krazubu

Feb 27 2012, 09:41 AM

So here's the edits for DVI/VGA + DP/DVI, other DP/DVI disabled :

NVCAP : 05000000000003000c0000000000000a00000000

Display-cfg : 03010000 - ffff0f01

If that still doesn't work, your ROM might require patching, try and see.

Here is your connector data for info :

Group 03 :
VGA0 - 00
DVI0 - 00

Group 0c :
DP0 - 0f
DVI1 - 07

Group 30 :
DP1 - 0d
DVI2 - 06

Group names are to be used to complete the NVCAP.
hex value next to each connector is used to complete display-cfg, one for primary screen output, the other for secondary screen.

NVCAP : 050000000000XX00YY0000000000000a00000000

Display-cfg : 0301XX00 - ffffYY01

Karl

Feb 28 2012, 01:11 AM

QUOTE (Krazubu @ Feb 27 2012, 03:41 AM)

So here's the edits for DVI/VGA + DP/DVI, other DP/DVI disabled
If that still doesn't work, your ROM might require patching, try and see.

Thank you so much. I'll give it a whirl and report

UPDATE:
No luck with a proper setup just yet. Maybe I am using the wrong graphic utility to create the HEX device-properties.

Process followed:

plist file converted to HEX:

<?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)</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>
05000000000003000c0000000000000a00000000
</data>
<key>NVPM</key>
<data>
AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>VRAM,totalsize</key>
<string>0x80000000</string>
<key>device_type</key>
<string>NVDA,GeForce</string>
<key>model</key>
<string>NVIDIA Quadro 4000 2GB DDR5</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>KW Krazubu EFI String</string>
</dict>
</dict>
</plist>

Perhaps my Boot plist is not setup correctly as well?

<?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>EthernetBuiltIn</key>
<string>Yes</string>
<key>ForceHPET</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>
<key>GraphicsEnabler</key>
<string></string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-v npci=0x2000 darkwake=0 -force64</string>
<key>Legacy Logo</key>
<string>Yes</string>
<key>PciRoot</key>
<string>1</string>
<key>Timeout</key>
<string>2</string>
<key>UseKernelCache</key>
<string>Yes</string>
<key>device-properties</key>
<string>ec0300000100000001000000e00300...</string>
</dict>
</plist>

Chameleon/Chimera
GA-x58a-ud3r FE (using prepatched DSDT)
intel i7 970
Quadro 4000 PC Version.

All working but the video card....status 1024x768 only rez, not recognizing card.

The battle continues!!!!

Krazubu

Feb 28 2012, 10:27 AM

Have you checked that your Dev ID was present in the nvidia kexts ?
By the way, you haven't added the display-cfg strings.

Gringo Vermelho

Feb 28 2012, 07:56 PM

QUOTE (Karl @ Feb 27 2012, 10:11 PM)

<key>EthernetBuiltIn</key>
<string>Yes</string>

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

<key>PciRoot</key>
<string>1</string>

You might want to remove these to rule out any conflict with your device properties string. The correct PCIRoot is already injected by the device properties string (PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)) and since you'll be removing EthernetBuiltIn, you should also generate and append the string for built-in ethernet to it.

While troubleshooting it's better not to mix and match injection methods.

Karl

Feb 28 2012, 11:59 PM

QUOTE (Krazubu @ Feb 28 2012, 04:27 AM)

Have you checked that your Dev ID was present in the nvidia kexts ?
By the way, you haven't added the display-cfg strings.

I did not and am checking now. I think I got caught up in many methods and need to start over from the scratch.
I'm staring with page one of this thread and your "Guide for All Nvidia Boards"!

I'm using Lion 1.7 and there are 6 NVDA* kext files, including:
NVDANV40Hal and HVDAResman
Because my card [QUADRO 4000 PC ver] generation is not listed in the 2009 guide, I am curious about the other files.

Thank you very much for your help, it looks like you've been a pro at this for quite some time.

QUOTE (Gringo Vermelho @ Feb 28 2012, 01:56 PM)

You might want to remove these to rule out any conflict with your device properties string. The correct PCIRoot is already injected by the device properties string (PciRoot(0x1)/Pci(0x3,0x0)/Pci(0x0,0x0)) and since you'll be removing EthernetBuiltIn, you should also generate and append the string for built-in ethernet to it.

While troubleshooting it's better not to mix and match injection methods.

This is brilliant advice, thanks. It gets hairy and convoluted fast when you want your machine up and running.

I'm not exactly sure what you mean by generate and append the string for built-in ethernet to it. (maybe just clarify what "it" is in this sentence, sorry for ignorance if it is trivial) I am going to go ahead and remove those for troubleshooting. Thanks for the help!

Gringo Vermelho

Feb 29 2012, 01:23 AM

QUOTE (Karl @ Feb 28 2012, 08:59 PM)

I'm not exactly sure what you mean by generate and append the string for built-in ethernet to it. (maybe just clarify what "it" is in this sentence, sorry for ignorance if it is trivial)

"it" is the device-properties string. Use gfxutil (or whatever GUI - like EFI Studio/OSX86Tools - you're using for it) to generate the string for your ethernet, convert it to hex and simply paste it at the end, appending it to the existing device properties string.

http://forum.netkas.org/index.php/topic,64.0.html

The purpose of this string is to give your on-board ethernet the "built-in" property which is very important for compatibility with various OS X software. It's the exact same data that gets injected by using Chameleon's EthernetBuiltIn=y in org.chameleon.Boot.plist. You can also do this via DSDT if that's your thing.

Karl

Feb 29 2012, 04:41 AM

QUOTE (Gringo Vermelho @ Feb 28 2012, 07:23 PM)

"it" is the device-properties string. Use gfxutil (or whatever GUI - like EFI Studio/OSX86Tools - you're using for it) to generate the string for your ethernet, convert it to hex and simply paste it at the end, appending it to the existing device properties string.

http://forum.netkas.org/index.php/topic,64.0.html

The purpose of this string is to give your on-board ethernet the "built-in" property which is very important for compatibility with various OS X software. It's the exact same data that gets injected by using Chameleon's EthernetBuiltIn=y in org.chameleon.Boot.plist. You can also do this via DSDT if that's your thing.

Ok! Thanks.

QUOTE (Krazubu @ Feb 28 2012, 04:27 AM)

Have you checked that your Dev ID was present in the nvidia kexts ?

My Device ID via the GPU-z tool is 10DE - 06DD. Does this translate to the following?
<key>IOPCIPrimaryMatch</key>
<string>0x10de06dd</string>

For NVDANV40Hal...IOPCIPrimaryMatch is inside IOKitPersonalities>NVidiaRM
For NVDAResman...IOPCIPrimaryMatch does not exist, Is it correct to create it under the same Dictionary as that of NVDAANV40Hal?

Karl

Feb 29 2012, 07:48 AM

QUOTE (Krazubu @ Feb 27 2012, 03:41 AM)

So here's the edits for DVI/VGA + DP/DVI, other DP/DVI disabled :

NVCAP : 05000000000003000c0000000000000a00000000

Display-cfg : 03010000 - ffff0f01

If that still doesn't work, your ROM might require patching, try and see.

Here is your connector data for info :

Group 03 :
VGA0 - 00
DVI0 - 00

Group 0c :
DP0 - 0f
DVI1 - 07

Group 30 :
DP1 - 0d
DVI2 - 06

Group names are to be used to complete the NVCAP.
hex value next to each connector is used to complete display-cfg, one for primary screen output, the other for secondary screen.

NVCAP : 050000000000XX00YY0000000000000a00000000

Display-cfg : 0301XX00 - ffffYY01

I've been staring and looking at back threads...I really have no idea how to use this information.

1. I'm using PlistEdit Pro
2. We have all the information for my specific card
3. I have NVEnabler 64.kext
4. I know I have to modify some stock kexts with my Device ID

5. Currently I am looking inside the hood of info.plist of NVEnabler 64; specifically at the addProperties key.

Need to add display-cfg

Need to add NVCAP

Need to add VRAM, totalsize ( <00000080> 2GB )

I'm not sure about things to do with HEX. In the past I've made a Hex.out from the entire file, but I'm really shooting in the dark and not understanding what's going on.

"To edit a plist it's recommended that you use "property list editor" (available in dev tools) or "plist edit pro" (available on the web) especially for NVCAP editing otherwise it won't be displayed in hexa but in base64 which is unusable, else, the default textedit is ok." Krazubu's Installation Guide

Does this mean that if I put the values into the Outline or Text of a plist in PlistEdit Pro that it will convert to HEX without any other step?

Gringo Vermelho

Feb 29 2012, 04:22 PM

In the view menu of Apple's plist editor, click "show raw keys/values". When in this mode you can insert the NVCAP as it is (050000000000XX00YY0000000000000a00000000).

Karl

Feb 29 2012, 06:59 PM

Thanks! Awesome.

[Above is the wrong data for my NVCAP **see original NVCAP for my GPU above**]
[In PlistEdit Pro the function is under Definition>Show Raw Keys/Values]

Regardless, when I enter the NVCAP string (given to me by Krazubu via the GPU-z ROM) into the outline of PlistEditPro
05000000000003000c0000000000000a00000000 in the outline is converted to...
BQAAAAAAAwAMAAAAAAAKAAAAAA== in the text.

NICE!

Karl

Mar 3 2012, 06:02 PM

QUOTE (Karl @ Feb 29 2012, 12:59 PM)

Thanks! Awesome.

[Above is the wrong data for my NVCAP **see original NVCAP for my GPU above**]
[In PlistEdit Pro the function is under Definition>Show Raw Keys/Values]

Regardless, when I enter the NVCAP string (given to me by Krazubu via the GPU-z ROM) into the outline of PlistEditPro
05000000000003000c0000000000000a00000000 in the outline is converted to...
BQAAAAAAAwAMAAAAAAAKAAAAAA== in the text.

NICE!

Device ID is my next step. Anyone know the following?

My Device ID via the GPU-z tool is 10DE - 06DD. Does this translate to the following?
<key>IOPCIPrimaryMatch</key>
<string>0x10de06dd</string>

hotcorez

Mar 4 2012, 10:40 AM

Dear Krazubu,

I rely on HDMI for my monitor and have an 8600GT Desktop card which works on 10.6.5 with modified MBP3,1 rom, quadro drivers and 10.6.4 opencl. However, it will not work beyond 10.6.5, so to future-proof i bought a gt440 1.5gb oem card based on the GF106 GPU, also used in the GTS450 http://en.wikipedia.org/wiki/Comparison_of...orce_400_Series

Unfortunately i am having the same problem with this card on 10.6.8 (no hdmi) It has 3 outputs from top to bottom: DP, DVI and HDMI

I have tried GraphicsEnabler with no joy on chameleon 2.0 R760 - chameleon 2.1 R1827

However, the screen makes a popping noise when it goes to sleep and wakes, so its sending some kind of signal to my hdmi monitor

nvcap maker = 0400000000000300000000000000000700000000

I have attached the rom dumped using nvflash and would appreciate it if you could have a look to see if there is any hope for this card on osx !

Many Thanks,

Hotcorez

Click to view attachment

nitiz92

Mar 4 2012, 11:01 AM

Hello guys!
I just installed Lion 10.7.2 choosing the various kext based on my hardware configuration .. in a first installation, for my gtx 260 I used only the Graphic Enabler but I start a screen appeared with all dots (you can not see anything!) .. so I promptly made a second installation, but choose the NVEnabler, but the result was the same .. So I thought to add the id of my vga in the following kexts NVDAResman.kext NVDANV50HAL.kext NVEnabler.kext

Final report:
- Now I can see the desktop
- The vga is not recognized (system profiler in the phrase appears only GPU)
- QE / CI are not enabled (the transparent menus are not there)
- The resolution is fixed at 1024x768

What can I do?? Thanks in advance, I trust in you well more experience than me! (sorry for my bad english)

Krazubu

Mar 4 2012, 11:31 AM

Hotcorez,
Here's your output layout with details of hardware supported outputs for each :

DVI = DVI+VGA
HDMI = HDMI/DVI
DP = DP + DVI/HDMI

I disabled the 1st group due to driver limitation not supporting (for the moment) more than 2 channels.
Try loading the attached ROM and use this NVCAP :
0500000000000100060000000000000a00000000

Those display-cfgs
connector 1 : 03010600
connector 2 : ffff0f01 (for DP) or ffff0701 (for DVI/HDMI)

Click to view attachment

hotcorez

Mar 4 2012, 03:10 PM

Thanks Krazubu,

I tried several methods, a modified NVEnabler64.kext (0.1b) including data values for NVCAP, @0,display-cfg, @1,display-cfg and vbios and it just froze the machine after rebuilding caches, natit (even tried both display-cfg values for display-cfg @1 + NVCAP, @0,display-cfg and vbios) dsdt + GraphicsEnabler + UseNvidiaROM + VBIOS=Yes in /Extra but I still get a blank screen

Any thoughts?

Many Thanks,

Hotcorez

Krazubu

Mar 4 2012, 03:38 PM

Hotcorez,
Please try using a different output so we can know if the problem comes from there

hotcorez

Mar 4 2012, 03:44 PM

QUOTE (Krazubu @ Mar 4 2012, 03:38 PM)

Hotcorez,
Please try using a different output so we can know if the problem comes from there

Hi Krazubu,

I tried the 2 outputs i have cables for (dvi>hdmi and hdmi>hdmi) with every setup i tried, monitor is hdmi. I dont have a dp cable,

Cheers,

Hotcorez