I have a GeForce GT 130m on my laptop. NVEnabler is the closest I've gotten so far to getting this card to work. I get a blue screen on boot.
Here's the output from ioreg. I ran it in safe mode (-x) if that matters.
Click to view attachment
Full Version: Nvenabler Testing And Discussion
Hi guys,
Any idea how to get Nvidia G105 M working with this? I tried installing it with the last 10.5.7 but only managed to get a blue screen. I tried other options like netkas injector, natit, nvkush etc. but nothing seemed to work.
Please suggest what to do (may be a display-cfg issue as noted in the first post).
Note: I don't currently have OSX86 installed, will do that over the next week and send an IOreg dump.
//Thanks
Any idea how to get Nvidia G105 M working with this? I tried installing it with the last 10.5.7 but only managed to get a blue screen. I tried other options like netkas injector, natit, nvkush etc. but nothing seemed to work.
Please suggest what to do (may be a display-cfg issue as noted in the first post).
Note: I don't currently have OSX86 installed, will do that over the next week and send an IOreg dump.
//Thanks
First of all thanks for your injector, it's really amazing . I arrived here later to try a lot of injectors before, the closest to yours was the nvinjectgo with the nvcap modified with some advice in nvinject forum, but with nvenabler I don't have to do anything. Both show me in the properties of graphics the 2 displays connected full hardware. The main problem here is the Laptop Display until now still no working (the DVI out with an VGA adaptor works really well). When I enter in the system later to load all the kernel and the kext, the display goes to black with the back light on (in verbose mode) and in normal mode I can see the grey apple until turns black. I tried to do a lot of things (putting the resolution of the screen in the com.apple.boot.plist it was the last) and putting the edid of my screen in the added entries of your injector.
All the proves it was made without the DVI connection first, and plugin later system loads, but nothing seems to work. Other thing, in safety mode both screens works without any artifact in mirror mode.
So I think I'm really close. I give it to you all what I have including the bios rom and the EDID specs.
Probably is a stupid thing I have to change in some place. Ah, I tried to use all the strings you put in the post and the only working one is the Mac Pro default. Thanks in advance.
Click to view attachmentClick to view attachmentClick to view attachment
All the proves it was made without the DVI connection first, and plugin later system loads, but nothing seems to work. Other thing, in safety mode both screens works without any artifact in mirror mode.
So I think I'm really close. I give it to you all what I have including the bios rom and the EDID specs.
Probably is a stupid thing I have to change in some place. Ah, I tried to use all the strings you put in the post and the only working one is the Mac Pro default. Thanks in advance.
Click to view attachmentClick to view attachmentClick to view attachment
is this works with FX5500 also.....???
I don't see why not, try it and see.
Don't forget you need 10.5.5 (or older) nVidia kexts for the FX5xxx series plus you will probably have to insert your device ID in all the relevant info.plists.
This post should put you on the right track, scroll down to where it says "geForce 5000 series".
http://www.projectosx.com/forum/index.php?showtopic=4
Don't forget you need 10.5.5 (or older) nVidia kexts for the FX5xxx series plus you will probably have to insert your device ID in all the relevant info.plists.
This post should put you on the right track, scroll down to where it says "geForce 5000 series".
http://www.projectosx.com/forum/index.php?showtopic=4
ALRIGHT!!! I FINALLY GOT IT WORKING!!! I managed to do some edits i thought would take and they did fine, I added my devID's in the NV kexts and added/removed the following from NVEnabler Info.plist
REMOVED:
@0,Display-cfg - I figured since this was causing problems, i'd remove it, and waddya know it worked for me
ADDED:
NVCAP
VRAM,totalsize
@0,built-in <00>
built-in <0> --these two keys apparently have something to do with gradient banding in internal notebook displays, i added these to ATY_Init and it fixed the banding
Using ATY_Init i managed to get all QE/CI working but even with VRAM,totalsize string it only showed 64mb of my vram (i have 256mb discrete)
Did the NVEnabler changes (removing displaycfg and addign the other values) and it now shows my full 256mb, QE/CI, etc. Dont know about external monitor or s-video out, but honestly i dont care as i dont use them
hardware:
nVidia Geforce GO 7200 256mb discrete memory, PCI express bus (built-in to notebook mobo but shows on PCI bus not integrated)
devID 01d610de
and as it will most likely help you all, a proper ioreg dump
Click to view attachment
thanks for the kext, and hope this helps ya
REMOVED:
@0,Display-cfg - I figured since this was causing problems, i'd remove it, and waddya know it worked for me
ADDED:
NVCAP
VRAM,totalsize
@0,built-in <00>
built-in <0> --these two keys apparently have something to do with gradient banding in internal notebook displays, i added these to ATY_Init and it fixed the banding
Using ATY_Init i managed to get all QE/CI working but even with VRAM,totalsize string it only showed 64mb of my vram (i have 256mb discrete)
Did the NVEnabler changes (removing displaycfg and addign the other values) and it now shows my full 256mb, QE/CI, etc. Dont know about external monitor or s-video out, but honestly i dont care as i dont use them
hardware:
nVidia Geforce GO 7200 256mb discrete memory, PCI express bus (built-in to notebook mobo but shows on PCI bus not integrated)
devID 01d610de
and as it will most likely help you all, a proper ioreg dump
Click to view attachment
thanks for the kext, and hope this helps ya
I doubt any of those values you added are involved, it's most likely display-cfg removal that helped.
If it's the NVCAP overriding that fixes the problem, it might mean that NVE has a problem dertermining it, that would be to dig.
About built-in string, yes it allows to have 24bit color depth on LCD.
If it's the NVCAP overriding that fixes the problem, it might mean that NVE has a problem dertermining it, that would be to dig.
About built-in string, yes it allows to have 24bit color depth on LCD.
QUOTE (Krazubu @ Aug 11 2009, 11:46 AM) 
I doubt any of those values you added are involved, it's most likely display-cfg removal that helped.
If it's the NVCAP overriding that fixes the problem, it might mean that NVE has a problem dertermining it, that would be to dig.
About built-in string, yes it allows to have 24bit color depth on LCD.
If it's the NVCAP overriding that fixes the problem, it might mean that NVE has a problem dertermining it, that would be to dig.
About built-in string, yes it allows to have 24bit color depth on LCD.
yeah i'm not sure if the nvcap matters or the vram string, but the built-in i know is what gives me the 24bit color and removing teh display-cfg got it turned on boot instead of black (no backlight) screen. i put the nvcap/vram,totalsize strings in just for good measure and everythign is gravy
My Second DVI port doesn't seem to work with BFG gtx 260 896MB..
the log displays this:
It seems to show 2 channels in ioreg though?
| | | +-o NVDA,Display-A@0 <class IONDRVDevice, registered, matched, active, busy 0, retain 10>
| | | | +-o NVDA <class NVDA, registered, matched, active, busy 0, retain 13>
| | | +-o NVDA,Display-B@1 <class IONDRVDevice, registered, matched, active, busy 0, retain 9>
| | | | +-o NVDA <class NVDA, registered, matched, active, busy 0, retain 10>
Any ideas?
the log displays this:
QUOTE
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: init : begin
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe(display)
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: probe : probe
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce GTX 260NVEnabler: DEBUG VRAM: 896NVEnabler: DEBUG Setting property @0,device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe fails
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: init : begin
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe(display)
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: probe : probe
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce GTX 260NVEnabler: DEBUG VRAM: 896NVEnabler: DEBUG Setting property @0,device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler::probe fails
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe(display)
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: probe : probe
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce GTX 260NVEnabler: DEBUG VRAM: 896NVEnabler: DEBUG Setting property @0,device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe fails
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: init : begin
Aug 11 22:42:16 localhost kernel[0]: NVEnabler::probe(display)
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: probe : probe
Aug 11 22:42:16 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce GTX 260NVEnabler: DEBUG VRAM: 896NVEnabler: DEBUG Setting property @0,device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Aug 11 22:42:17 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Aug 11 22:42:17 localhost kernel[0]: NVEnabler::probe fails
It seems to show 2 channels in ioreg though?
| | | +-o NVDA,Display-A@0 <class IONDRVDevice, registered, matched, active, busy 0, retain 10>
| | | | +-o NVDA <class NVDA, registered, matched, active, busy 0, retain 13>
| | | +-o NVDA,Display-B@1 <class IONDRVDevice, registered, matched, active, busy 0, retain 9>
| | | | +-o NVDA <class NVDA, registered, matched, active, busy 0, retain 10>
Any ideas?
Please provide the infos as written in post #1.
Here is my ioreg from Quadro NVS 320m (dev 0x040b). With NVEnabler I just got black screen (backlight is on but no picture ...). Same after I remove display-cfg. Secondary display is also black ...
Clubber_77 tested with 7200Go with foolowing results
1. With NVInjectGo two monitor are working: internal LCD laptop display and external monitor.
2. With NVEnabler only external monitor works.
NVInjectGo.info.plist
This NVCAP = <04000000 00000200 0d000000 00000007 00000000>
and VRAM = 128Mb
Report in russian here post #5.
1. With NVInjectGo two monitor are working: internal LCD laptop display and external monitor.
2. With NVEnabler only external monitor works.
NVInjectGo.info.plist
CODE
<key>entriesToAdd</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,display-type</key>
<string>LCD</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAgANAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<data>
AAAACA==
</data>
<key>device_type</key>
<string>NVDA,GeForce</string>
<key>model</key>
<string>NVidia GeForce Go 7200</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>NVinjectGo 0.2.0</string>
</dict>
<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,display-type</key>
<string>LCD</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAgANAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<data>
AAAACA==
</data>
<key>device_type</key>
<string>NVDA,GeForce</string>
<key>model</key>
<string>NVidia GeForce Go 7200</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>NVinjectGo 0.2.0</string>
</dict>
This NVCAP = <04000000 00000200 0d000000 00000007 00000000>
and VRAM = 128Mb
Report in russian here post #5.
QUOTE (apocolipse269 @ Aug 12 2009, 11:28 PM)
Slice i have the same hardware workign w/ NVEnabler (it gives QE/CI unlike nvinject), mine is 256mb but to get NVEnabler working you must remove display-cfg (mainly for @0) and add @0,built-in <00> and built-in <0> to info.plist. i can post my info.plist if you like
CODE
<key>IOPCIMatch</key>
<string>0x01d610de 0x000010de&0x0000ffff</string>
<key>IOProbeScore</key>
<string>8000</string>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>addProperties</key>
<dict>
<key>@0,built-in</key>
<data></data>
<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,display-cfg</key>
<data>//8AAQ==</data>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>VRAM,totalsize</key>
<data>AAAAEA==</data>
<key>NVCAP</key>
<data>BAABAAAAAwAMAAAAAAAACgAAAAA=</data>
<key>built-in</key>
<data>AA==</data>
</dict>
<key>skipvbios_disabled</key>
<false/>
<string>0x01d610de 0x000010de&0x0000ffff</string>
<key>IOProbeScore</key>
<string>8000</string>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>addProperties</key>
<dict>
<key>@0,built-in</key>
<data></data>
<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,display-cfg</key>
<data>//8AAQ==</data>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>VRAM,totalsize</key>
<data>AAAAEA==</data>
<key>NVCAP</key>
<data>BAABAAAAAwAMAAAAAAAACgAAAAA=</data>
<key>built-in</key>
<data>AA==</data>
</dict>
<key>skipvbios_disabled</key>
<false/>
the display-cfg prevents the monitor from coming on unless external is plugged in, the internal can then be turned on with "detect displays". removign @0,display-cfg solves this. adding @0,built-in and built-in solves 16bit color banding issues. I added my own NVCAP that was working with ATY_Init (dont know if necessary) and VRAM,totalsize (dont know if necessary). My card is go 7200 with 256mb discrete, though i think some of these cards had shared memory
QUOTE (apocolipse269 @ Aug 13 2009, 03:34 AM)
NVEnabler (it gives QE/CI unlike nvinject)
No, NVInject gives QE/CI fine.
QUOTE
the display-cfg prevents the monitor from coming on unless external is plugged in, the internal can then be turned on with "detect displays". removign @0,display-cfg solves this. adding @0,built-in and built-in solves 16bit color banding issues. I added my own NVCAP that was working with ATY_Init (dont know if necessary) and VRAM,totalsize (dont know if necessary). My card is go 7200 with 256mb discrete, though i think some of these cards had shared memory
If you add NVCAP manually then what is the advantage of the NVEnabler? I thought it is automatic detect.
My 7300LE had 128Mb discrete memory and 384Mb shared memory that can't be used by Mac OSX yet. Only 128.
Has he tried removing @X,display-cfg from NVEnablers plist? It could be those values broke it.
QUOTE (Slice @ Aug 12 2009, 08:06 PM)
Clubber_77 tested with 7200Go with foolowing results
1. With NVInjectGo two monitor are working: internal LCD laptop display and external monitor.
2. With NVEnabler only external monitor works.
NVInjectGo.info.plist
This NVCAP = <04000000 00000200 0d000000 00000007 00000000>
and VRAM = 128Mb
Report in russian here post #5.
1. With NVInjectGo two monitor are working: internal LCD laptop display and external monitor.
2. With NVEnabler only external monitor works.
NVInjectGo.info.plist
CODE
<key>entriesToAdd</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,display-type</key>
<string>LCD</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAgANAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<data>
AAAACA==
</data>
<key>device_type</key>
<string>NVDA,GeForce</string>
<key>model</key>
<string>NVidia GeForce Go 7200</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>NVinjectGo 0.2.0</string>
</dict>
<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,display-type</key>
<string>LCD</string>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>NVCAP</key>
<data>
BAAAAAAAAgANAAAAAAAABwAAAAA=
</data>
<key>VRAM,totalsize</key>
<data>
AAAACA==
</data>
<key>device_type</key>
<string>NVDA,GeForce</string>
<key>model</key>
<string>NVidia GeForce Go 7200</string>
<key>name</key>
<string>NVDA,Parent</string>
<key>rom-revision</key>
<string>NVinjectGo 0.2.0</string>
</dict>
This NVCAP = <04000000 00000200 0d000000 00000007 00000000>
and VRAM = 128Mb
Report in russian here post #5.
QUOTE (Slice @ Aug 13 2009, 03:07 PM)
No, NVInject gives QE/CI fine.
If you add NVCAP manually then what is the advantage of the NVEnabler? I thought it is automatic detect.
My 7300LE had 128Mb discrete memory and 384Mb shared memory that can't be used by Mac OSX yet. Only 128.
If you add NVCAP manually then what is the advantage of the NVEnabler? I thought it is automatic detect.
My 7300LE had 128Mb discrete memory and 384Mb shared memory that can't be used by Mac OSX yet. Only 128.
I'm not sure that the NVCAP even matters, i can remove it to be sure, but the reason i use NVEnabler over NVInject is b/c as i said NVInject never worked for me aside from getting better resolution (never got QE/CI with it). ATY_Init gives me QE/CI which is what i tried after i found out about nvenabler (which gave me black screen untill i edited plist properly). ATY_Init though only saw 64mb of my 256mb even with the VRAM,totalsize string added. NVEnabler gives me full QE/CI and 256mb VRAM. Plus, the advantage of NVEnabler is on-the-fly rom patching (not quite sure what its doing but w/e they say it makes the card act more native in OS X so i'll go with the flow for now
)
I was wondering if someone would enlighten me a bit about this problem I'm having. I'm sorry if this is the wrong place to post this, but I feel that this is the closest topic and the developers here are most knowledgeable about the display issues.
Previously, bcc9 tried the NVEnabler with his laptop (XPS1340) with the integrated 9400m. He said that QE/CI works on his system, which I am assuming the internal LCD worked for him. But he proceeded to continue on with mastering the NVCAP for the XPS 1340 since external displays doesn't seem to work with NVEnabler, which he has gotten it perfectly for his system now and modified a Natit.kext to include it.
Now, my laptop is a Dell Studio 1440, also with the integrated 9400m. The thing is, it comes in two types of displays, a 720p (1366x768) and 900p (1600x900). I have the 720p internal LCD. Someone else has the 900p. This other person with the 900p screen used bcc9's modified Natit.kext (with the working NVCAP), and the screen worked for him. However, I tried both NVEnabler and the modified Natit.kext but my LCD just goes blank, nothing shows, no LCD brightness. We both did the boot132+retail disk+Chameleonv2 method.
To me, this clearly seems like an issue with detecting the LCD display, but I'm not sure what to do. It doesn't seem like NVCAP values would play a large part in detecting the LCD. I know that by shuffling the bits in the NVCAP, you can control the display channels, for which in laptop internal LCDs, channel 1's hex value should always be 01. While researching more into it, I found that laptop owners 1-2 years ago had problems with internal LCDs because of the display EDID values for OSX to detect the screens. I don't think EDID values would be the problem since that would mean OSX should not even be able to show anything on screen via software emulation right?
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
I would much appreciate it if someone can point me out to the right direction, thank you very much!
Previously, bcc9 tried the NVEnabler with his laptop (XPS1340) with the integrated 9400m. He said that QE/CI works on his system, which I am assuming the internal LCD worked for him. But he proceeded to continue on with mastering the NVCAP for the XPS 1340 since external displays doesn't seem to work with NVEnabler, which he has gotten it perfectly for his system now and modified a Natit.kext to include it.
Now, my laptop is a Dell Studio 1440, also with the integrated 9400m. The thing is, it comes in two types of displays, a 720p (1366x768) and 900p (1600x900). I have the 720p internal LCD. Someone else has the 900p. This other person with the 900p screen used bcc9's modified Natit.kext (with the working NVCAP), and the screen worked for him. However, I tried both NVEnabler and the modified Natit.kext but my LCD just goes blank, nothing shows, no LCD brightness. We both did the boot132+retail disk+Chameleonv2 method.
To me, this clearly seems like an issue with detecting the LCD display, but I'm not sure what to do. It doesn't seem like NVCAP values would play a large part in detecting the LCD. I know that by shuffling the bits in the NVCAP, you can control the display channels, for which in laptop internal LCDs, channel 1's hex value should always be 01. While researching more into it, I found that laptop owners 1-2 years ago had problems with internal LCDs because of the display EDID values for OSX to detect the screens. I don't think EDID values would be the problem since that would mean OSX should not even be able to show anything on screen via software emulation right?
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
I would much appreciate it if someone can point me out to the right direction, thank you very much!
QUOTE (bcc9 @ Jul 20 2009, 10:20 PM)
Hi, I have a notebook with integrated 9400m. (The dell studio xps 1340). I just tried your enabler and it works for allowing qe/ci on this system, however the generated NVCAP does not work with an external DVI/HDMI monitor.
Previously I hand built an EFI string that enabled QE/CI for this system, and my hand built solution has an NVCAP that works with external DVI/HDMI, VGA, and displayport.
I would like to compare what your solution is doing with my current EFI string solution, is source code available? I notice that NVEnabler logs errors about being unable to ID the vga rom and card properly, I should be able to fix such problems with source. Contributing back of course.
Also, 9500m users (9400m+9200m) have been unable to get the 9200m part working via EFI string changes; should nvenabler work with dual integrated cards such as this?
FYI, here's what nvenabler logs as it's loading on this system; relevant ioreg info attached as well.
Click to view attachment
Previously I hand built an EFI string that enabled QE/CI for this system, and my hand built solution has an NVCAP that works with external DVI/HDMI, VGA, and displayport.
I would like to compare what your solution is doing with my current EFI string solution, is source code available? I notice that NVEnabler logs errors about being unable to ID the vga rom and card properly, I should be able to fix such problems with source. Contributing back of course.
Also, 9500m users (9400m+9200m) have been unable to get the 9200m part working via EFI string changes; should nvenabler work with dual integrated cards such as this?
FYI, here's what nvenabler logs as it's loading on this system; relevant ioreg info attached as well.
CODE
NVEnabler: init : begin
NVEnabler::probe(IGPU)
NVEnabler: probe : probe
NVEnabler: False ROM signature: 0xc10a
NVEnabler: False ROM signature: 0x991d
NVEnabler: DEBUG Model found: Unknown nVidia cardNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG Setting property @0,device_type
NVEnabler: DEBUG Setting property @0,compatible
NVEnabler: DEBUG Setting property @1,display-cfg
NVEnabler: DEBUG Setting property @1,name
NVEnabler: DEBUG Setting property device_type
NVEnabler: DEBUG Setting property @0,name
NVEnabler: DEBUG Setting property @1,compatible
NVEnabler: DEBUG Setting property @0,display-cfg
NVEnabler: DEBUG Setting property @1,device_type
NVEnabler::probe fails
NVEnabler::probe(IGPU)
NVEnabler: probe : probe
NVEnabler: False ROM signature: 0xc10a
NVEnabler: False ROM signature: 0x991d
NVEnabler: DEBUG Model found: Unknown nVidia cardNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG Setting property @0,device_type
NVEnabler: DEBUG Setting property @0,compatible
NVEnabler: DEBUG Setting property @1,display-cfg
NVEnabler: DEBUG Setting property @1,name
NVEnabler: DEBUG Setting property device_type
NVEnabler: DEBUG Setting property @0,name
NVEnabler: DEBUG Setting property @1,compatible
NVEnabler: DEBUG Setting property @0,display-cfg
NVEnabler: DEBUG Setting property @1,device_type
NVEnabler::probe fails
Click to view attachment
QUOTE (GAOO @ Aug 14 2009, 04:37 AM)
I was wondering if someone would enlighten me a bit about this problem I'm having. I'm sorry if this is the wrong place to post this, but I feel that this is the closest topic and the developers here are most knowledgeable about the display issues.
Previously, bcc9 tried the NVEnabler with his laptop (XPS1340) with the integrated 9400m. He said that QE/CI works on his system, which I am assuming the internal LCD worked for him. But he proceeded to continue on with mastering the NVCAP for the XPS 1340 since external displays doesn't seem to work with NVEnabler, which he has gotten it perfectly for his system now and modified a Natit.kext to include it.
Now, my laptop is a Dell Studio 1440, also with the integrated 9400m. The thing is, it comes in two types of displays, a 720p (1366x768) and 900p (1600x900). I have the 720p internal LCD. Someone else has the 900p. This other person with the 900p screen used bcc9's modified Natit.kext (with the working NVCAP), and the screen worked for him. However, I tried both NVEnabler and the modified Natit.kext but my LCD just goes blank, nothing shows, no LCD brightness. We both did the boot132+retail disk+Chameleonv2 method.
To me, this clearly seems like an issue with detecting the LCD display, but I'm not sure what to do. It doesn't seem like NVCAP values would play a large part in detecting the LCD. I know that by shuffling the bits in the NVCAP, you can control the display channels, for which in laptop internal LCDs, channel 1's hex value should always be 01. While researching more into it, I found that laptop owners 1-2 years ago had problems with internal LCDs because of the display EDID values for OSX to detect the screens. I don't think EDID values would be the problem since that would mean OSX should not even be able to show anything on screen via software emulation right?
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
I would much appreciate it if someone can point me out to the right direction, thank you very much!
Previously, bcc9 tried the NVEnabler with his laptop (XPS1340) with the integrated 9400m. He said that QE/CI works on his system, which I am assuming the internal LCD worked for him. But he proceeded to continue on with mastering the NVCAP for the XPS 1340 since external displays doesn't seem to work with NVEnabler, which he has gotten it perfectly for his system now and modified a Natit.kext to include it.
Now, my laptop is a Dell Studio 1440, also with the integrated 9400m. The thing is, it comes in two types of displays, a 720p (1366x768) and 900p (1600x900). I have the 720p internal LCD. Someone else has the 900p. This other person with the 900p screen used bcc9's modified Natit.kext (with the working NVCAP), and the screen worked for him. However, I tried both NVEnabler and the modified Natit.kext but my LCD just goes blank, nothing shows, no LCD brightness. We both did the boot132+retail disk+Chameleonv2 method.
To me, this clearly seems like an issue with detecting the LCD display, but I'm not sure what to do. It doesn't seem like NVCAP values would play a large part in detecting the LCD. I know that by shuffling the bits in the NVCAP, you can control the display channels, for which in laptop internal LCDs, channel 1's hex value should always be 01. While researching more into it, I found that laptop owners 1-2 years ago had problems with internal LCDs because of the display EDID values for OSX to detect the screens. I don't think EDID values would be the problem since that would mean OSX should not even be able to show anything on screen via software emulation right?
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
I would much appreciate it if someone can point me out to the right direction, thank you very much!
I tried REMOVING the @0,display-cfg (you can do both @0 and @1 if you want) and it solved the blank screen issue. NVEnabler auto detects proper NVCAP (though i added mine, which it uses the same so pretty sure it doesnt matter) so you shouldnt need to deal with that. one thing to add is to put the following
@0,built-in
built-in
both set to 0 data types in info.plist, this will fix LCD 16-bit color banding issues. give these a go
About the @0,built-in, I'm a bit confused.
Do you mean to add:
@0,built-in <Data type> Value: 0 (1 byte)
built-in <Data type> Value: 0 (1 byte)
or leave the values as blank:
@0,built-in <Data type> Value: (0 bytes)
built-in <Data type> Value: (0 bytes)
Thanks a lot for your help.
Do you mean to add:
@0,built-in <Data type> Value: 0 (1 byte)
built-in <Data type> Value: 0 (1 byte)
or leave the values as blank:
@0,built-in <Data type> Value: (0 bytes)
built-in <Data type> Value: (0 bytes)
Thanks a lot for your help.
QUOTE (apocolipse269 @ Aug 14 2009, 10:06 AM)
I tried REMOVING the @0,display-cfg (you can do both @0 and @1 if you want) and it solved the blank screen issue. NVEnabler auto detects proper NVCAP (though i added mine, which it uses the same so pretty sure it doesnt matter) so you shouldnt need to deal with that. one thing to add is to put the following
@0,built-in
built-in
both set to 0 data types in info.plist, this will fix LCD 16-bit color banding issues. give these a go
@0,built-in
built-in
both set to 0 data types in info.plist, this will fix LCD 16-bit color banding issues. give these a go
QUOTE (apocolipse269 @ Aug 14 2009, 03:50 AM)
Plus, the advantage of NVEnabler is on-the-fly rom patching (not quite sure what its doing but w/e they say it makes the card act more native in OS X so i'll go with the flow for now )
)What is mean "more native"? Do I really need it?
QUOTE (GAOO @ Aug 14 2009, 08:37 AM)
, I found that laptop owners 1-2 years ago had problems with internal LCDs because of the display EDID values for OSX to detect the screens. I don't think EDID values would be the problem since that would mean OSX should not even be able to show anything on screen via software emulation right?
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
BTW, I tried changing the display-cfg of NVEnabler to the macbook and macbook pro, but still no display output..
Yes, EDID string for a display must be for the display to work. EDID can be obtain from BIOS (if present in it), from I2C/DDC (if your hardware works with the same protocol as Apple's one), or from infoPlist of an injector. What about NVEnabler?
For laptop display there is one other property "Native Screen Resolution". Does NVEnabler know it?
QUOTE (apocolipse269 @ Aug 14 2009, 10:06 AM)
I tried REMOVING the @0,display-cfg (you can do both @0 and @1 if you want) and it solved the blank screen issue. NVEnabler auto detects proper NVCAP (though i added mine, which it uses the same so pretty sure it doesnt matter) so you shouldnt need to deal with that. one thing to add is to put the following
@0,built-in
built-in
both set to 0 data types in info.plist, this will fix LCD 16-bit color banding issues. give these a go
@0,built-in
built-in
both set to 0 data types in info.plist, this will fix LCD 16-bit color banding issues. give these a go
Its are old advices but not explanations what I want to hear. NVEnabler must be better then any injector else I don't see reasons for it.
@DVSoftware
Posts have been moved here where it better belongs as it's not really related to NVE
Posts have been moved here where it better belongs as it's not really related to NVE
About the @0,display-cfg, here's something that I noticed for my laptop Dell Studio 14z's internal LCD/GPU.
With @0,display-cfg key in NVEnabler's Info.plist, a blue screen shows up. First a dark color for 1 sec, then a light color after. Nothing else shows up.
By changing the value for the @0,display-cfg, NVEnabler detects different ROM signatures.
For example, with the original value of 03010000, this is my NVEnabler output (3 times in a row):
NVEnabler: init : begin
NVEnabler::probe(IGPU)
NVEnabler: probe : probe
NVEnabler: False ROM signature: 0x0000
NVEnabler: False ROM signature: 0x1500
NVEnabler: DEBUG Model found: Unknown nVidia cardNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG Setting property @0,compatible
NVEnabler: DEBUG Setting property @0,device_type
NVEnabler: DEBUG Setting property @0,display-cfg
NVEnabler: DEBUG Setting property @0,name
NVEnabler: DEBUG Setting property @1,compatible
NVEnabler: DEBUG Setting property @1,device_type
NVEnabler: DEBUG Setting property @1,display-cfg
NVEnabler: DEBUG Setting property @1,name
NVEnabler: DEBUG Setting property device_type
NVEnabler::probe fails
Using a value of 00000000, the False Rom Signature was 0xffff then 0x1500. Using 01000000 and other values gave different ROM signatures as well.
If I remove the @0,display-cfg key, then the display comes out black/empty/no output.
I am unsure whether this is helpful to you guys in debugging. I am curious what ROM signature refers to, and why NVEnabler needs it for its Algorithm (or how it is calculated based on @0,display-cfg?). It seems apparent that @0,display-cfg is pretty important to getting my LCD work, though I guess we're still at a loss as to the meaning of the values for @0,display-cfg..
With @0,display-cfg key in NVEnabler's Info.plist, a blue screen shows up. First a dark color for 1 sec, then a light color after. Nothing else shows up.
By changing the value for the @0,display-cfg, NVEnabler detects different ROM signatures.
For example, with the original value of 03010000, this is my NVEnabler output (3 times in a row):
NVEnabler: init : begin
NVEnabler::probe(IGPU)
NVEnabler: probe : probe
NVEnabler: False ROM signature: 0x0000
NVEnabler: False ROM signature: 0x1500
NVEnabler: DEBUG Model found: Unknown nVidia cardNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG Setting property @0,compatible
NVEnabler: DEBUG Setting property @0,device_type
NVEnabler: DEBUG Setting property @0,display-cfg
NVEnabler: DEBUG Setting property @0,name
NVEnabler: DEBUG Setting property @1,compatible
NVEnabler: DEBUG Setting property @1,device_type
NVEnabler: DEBUG Setting property @1,display-cfg
NVEnabler: DEBUG Setting property @1,name
NVEnabler: DEBUG Setting property device_type
NVEnabler::probe fails
Using a value of 00000000, the False Rom Signature was 0xffff then 0x1500. Using 01000000 and other values gave different ROM signatures as well.
If I remove the @0,display-cfg key, then the display comes out black/empty/no output.
I am unsure whether this is helpful to you guys in debugging. I am curious what ROM signature refers to, and why NVEnabler needs it for its Algorithm (or how it is calculated based on @0,display-cfg?). It seems apparent that @0,display-cfg is pretty important to getting my LCD work, though I guess we're still at a loss as to the meaning of the values for @0,display-cfg..
Still trying to get my GT 130M working. All I've been able to find out is that it's the same thing as a 9600M GT, just printed more finely for laptops. There doesn't seem to be proper drivers for it for linux yet either. My dump is a couple posts up.
Hello,
I would first like to say THANK YOU big time to the ones who made the nvenabler kext.
This is one hell of a kext! i've been trying out NVCAP values in other nvidia kexts for months (since I can not read my cards ROM there was nothing else I could do) and I never got to work multiple displays on my 8600M GS laptop card. Until i decided to give this a go. Everything worked INSTANTLY.
THANK YOU SO MUCH!!!!
You are doing a hell of a job.
I do have one question though. Is it in any way possible to read out the NVCAP value that nvenabler calculates for the card it is installed for? Since i must have tried about a hundred different strings, I'd be very interested in knowing which one actually does the job.
Thanks again,
grtz
HeH
my system is a HP dv9660 with geforce 8600M GS 256mb (internal+VGA+HDMI+compositeTVout)
I would first like to say THANK YOU big time to the ones who made the nvenabler kext.
This is one hell of a kext! i've been trying out NVCAP values in other nvidia kexts for months (since I can not read my cards ROM there was nothing else I could do) and I never got to work multiple displays on my 8600M GS laptop card. Until i decided to give this a go. Everything worked INSTANTLY.
THANK YOU SO MUCH!!!!
You are doing a hell of a job.
I do have one question though. Is it in any way possible to read out the NVCAP value that nvenabler calculates for the card it is installed for? Since i must have tried about a hundred different strings, I'd be very interested in knowing which one actually does the job.
Thanks again,
grtz
HeH
my system is a HP dv9660 with geforce 8600M GS 256mb (internal+VGA+HDMI+compositeTVout)
You can read out the NVCAP using gfxutil.
Look up how to use gfxutil on the netkas.org forums.
There's more to NVenabler than just the NVCAP string though.
Look up how to use gfxutil on the netkas.org forums.
There's more to NVenabler than just the NVCAP string though.
also works like a charm with snow leo.
but is there still a need for a 64-bit version of this?
but is there still a need for a 64-bit version of this?
QUOTE (Gringo Vermelho @ Aug 23 2009, 07:19 AM)
You can read out the NVCAP using gfxutil.
Look up how to use gfxutil on the netkas.org forums.
Look up how to use gfxutil on the netkas.org forums.
Great! Thanks!
cheers
Actually, could you help me with a small instruction how to do this with gfxutil?
I can't seem to find how...
Thank you very much
HeH
I can't seem to find how...
Thank you very much
HeH
Just type in terminal
ioreg -lw0 | grep NVCAP
when NVEnabler installed and works
ioreg -lw0 | grep NVCAP
when NVEnabler installed and works
Hi All, I don't know if you can help me, but I'm using NVEnabler and it's fully working (CI/QE, Change reolutions, sleep) But I'm getting Kernel Panics after display wake up.
To detail the situation:
I set up not to sleep computer neither HHD, only dislplay.
I'm using DVI to HDMI on an LG TV LCD and I set it up to go off when there's no signal. So when my display (pc) goes to sleep, after 5 minutes the tv goes of. When I turn on back the tv I get a kernel panic, even with or without moving the mouse to wake it up.
What would you suggest?
Thanks in advance
To detail the situation:
I set up not to sleep computer neither HHD, only dislplay.
I'm using DVI to HDMI on an LG TV LCD and I set it up to go off when there's no signal. So when my display (pc) goes to sleep, after 5 minutes the tv goes of. When I turn on back the tv I get a kernel panic, even with or without moving the mouse to wake it up.
What would you suggest?
Thanks in advance
This extension works well for my 9800GTX, DVI + TVout.
It works perfect on snow leopard 32 bits.
But not compatible with 64 bits.
Help please.
Thank you.
*edit by realityiswhere* - New topic merged into relevant developer discussion.
It works perfect on snow leopard 32 bits.
But not compatible with 64 bits.
Help please.
Thank you.
*edit by realityiswhere* - New topic merged into relevant developer discussion.
>Silaisa
I don't think we can do much for the moment, it's probably a problem with BIOS.
>Reinstaller
NVE is not compiled for 64bit, and won't be for the moment.
I don't think we can do much for the moment, it's probably a problem with BIOS.
>Reinstaller
NVE is not compiled for 64bit, and won't be for the moment.
is there a way to inject the Chipset Model?
add in the plist :
<key>model</key>
<string>Your Model here</string>
<key>model</key>
<string>Your Model here</string>
Click to view attachment
IT WORKS TERRIFIC IN LEOPARD 10.5.8!!!!
I have an Acer Aspire laptop with a GeForce Go 7900 GS 512MB (not flashed, and VGA rom bios is integrated into System BIOS)
At first, I kept getting a black screen until I read Krazubu's post about changing @0, display-cfg to <00>. In addition, I've done:
in IOPCIMatch I entered my device id: 0x029810de&0x0000ffff and added:
@0,built-in Data <>
built-in Data <00>
I also entered my device id in Geforce, NVDANV40Hal and NVDAResman. I put NVEnabler in S/L/E
I didn't do anything else and surprisingly everything comes up perfect: QE/CI, the graphic card name Go 7900 GS, the memory amount 512MB.
Developers, excellent work!
With NVinject, I also get QE/CI, but I have to manually specify everything in the plist: the memory amount, the model name, NVCAP, NVPM etc...With NVEnabler, I don't have to specify any of that. Amazing!
EDIT: It works just as fine in Retail Snow Leopard 32-bit
Click to view attachment
EDIT: It keeps getting better and better. With NVinject, I could only hotplug an external monitor to the laptop. When cold-booting with the monitor plugged in, I would get black screens on both the laptop and the monitor. With NVEnabler, I can cold-boot no problem with the monitor plugged in.
IT WORKS TERRIFIC IN LEOPARD 10.5.8!!!!
I have an Acer Aspire laptop with a GeForce Go 7900 GS 512MB (not flashed, and VGA rom bios is integrated into System BIOS)
At first, I kept getting a black screen until I read Krazubu's post about changing @0, display-cfg to <00>. In addition, I've done:
in IOPCIMatch I entered my device id: 0x029810de&0x0000ffff and added:
@0,built-in Data <>
built-in Data <00>
I also entered my device id in Geforce, NVDANV40Hal and NVDAResman. I put NVEnabler in S/L/E
I didn't do anything else and surprisingly everything comes up perfect: QE/CI, the graphic card name Go 7900 GS, the memory amount 512MB.
Developers, excellent work!
With NVinject, I also get QE/CI, but I have to manually specify everything in the plist: the memory amount, the model name, NVCAP, NVPM etc...With NVEnabler, I don't have to specify any of that. Amazing!
EDIT: It works just as fine in Retail Snow Leopard 32-bit
Click to view attachment
EDIT: It keeps getting better and better. With NVinject, I could only hotplug an external monitor to the laptop. When cold-booting with the monitor plugged in, I would get black screens on both the laptop and the monitor. With NVEnabler, I can cold-boot no problem with the monitor plugged in.
QUOTE (Krazubu @ Sep 11 2009, 10:41 PM)
add in the plist :
<key>model</key>
<string>Your Model here</string>
<key>model</key>
<string>Your Model here</string>
still "Unknown nVidia card". did i do it right?
Yes, it has to be in the "AddProperties" section.
QUOTE (Krazubu @ Sep 14 2009, 02:22 PM)
Yes, it has to be in the "AddProperties" section.
oh ok. so it should be a "child" of "addProperties" Dictionary. will report back the soonest possible. tnx.
Hello,
Thanks for great Enabler!
It gives me a working Palit 9800 GT Super+ with Samsung SyncMaster and Display-cfg set to 03010300. Seems working well on boot and after monitor sleep. QE/CI ok.
My problem is that I have AverMedia external DVI TV tuner. So the DVI output from video card first goes to tuner then from tuner to monitor.
I guess that there is some chip in tuner that mac drivers can't handle without proper Display-cfg.
I have a color noise on screen (like tv with disconnected antenna). This noise replaced a normal mac desktop picture for a second then return to noise and starts over again.
I have no problem with same config on Windows.
I understand that my problem is mostly related with tuner chip but it would be nice if I can get a proper Display-cfg value. Can I do it in Windows somehow?
BTW do you think that this is Display-cfg related issue?
Regards,
Ruslan
Thanks for great Enabler!
It gives me a working Palit 9800 GT Super+ with Samsung SyncMaster and Display-cfg set to 03010300. Seems working well on boot and after monitor sleep. QE/CI ok.
My problem is that I have AverMedia external DVI TV tuner. So the DVI output from video card first goes to tuner then from tuner to monitor.
I guess that there is some chip in tuner that mac drivers can't handle without proper Display-cfg.
I have a color noise on screen (like tv with disconnected antenna). This noise replaced a normal mac desktop picture for a second then return to noise and starts over again.
I have no problem with same config on Windows.
I understand that my problem is mostly related with tuner chip but it would be nice if I can get a proper Display-cfg value. Can I do it in Windows somehow?
BTW do you think that this is Display-cfg related issue?
Regards,
Ruslan
kewl!
tnx a lot for the help Krazubu and to your whole team for the kext.
more power to you guys!
tnx a lot for the help Krazubu and to your whole team for the kext.
more power to you guys!
Cool Macinized
Arbuz > I'm afraid there's nothing we can do, not on the GFX side at least. As far as I understand your tuner is using passthrough mode, and "catches" the output when it's working. If it makes a distortion on the picture, it has to be tuned on the tuner card itself. To ensure that GFX is giving output fine, directly plug the display to check that picture is OK.
I guess the tuner has to be initialized properly to let the display signal go through without altering it, or on the opposite, maybe OSX partly inits it whereas it should better let it fully off.
Arbuz > I'm afraid there's nothing we can do, not on the GFX side at least. As far as I understand your tuner is using passthrough mode, and "catches" the output when it's working. If it makes a distortion on the picture, it has to be tuned on the tuner card itself. To ensure that GFX is giving output fine, directly plug the display to check that picture is OK.
I guess the tuner has to be initialized properly to let the display signal go through without altering it, or on the opposite, maybe OSX partly inits it whereas it should better let it fully off.
Thanks Krazubu.
GFX works fine with display directly connected. I think the problem is that OSX partly inits the tuner chip or detects it wrongly.
I just don't know if there any way to fix it. Could it be connected with NVMT or Display-cfg values?
I think it would be helpful for people who using external tuner like me. I wasted a lot of time playing with injectors before I get that problem was in tuner.
GFX works fine with display directly connected. I think the problem is that OSX partly inits the tuner chip or detects it wrongly.
I just don't know if there any way to fix it. Could it be connected with NVMT or Display-cfg values?
I think it would be helpful for people who using external tuner like me. I wasted a lot of time playing with injectors before I get that problem was in tuner.
QUOTE (Krazubu @ Sep 14 2009, 05:20 PM)
Arbuz >
One more question. I found the value display-type in some info.plist. For example:
Does it affect the display detection?
CODE
<key>@1,display-type</key>
<string>LCD</string>
<string>LCD</string>
Does it affect the display detection?
and more )
I found that in the nvenabler plist IOProbeScore value set to 8000. This value is regulating the drivers priority right?
Should it be set to 0 then? Or am I wrong?
Regarding the priority could I set the fboffset value in the nvenabler plist?
Thanks.
I found that in the nvenabler plist IOProbeScore value set to 8000. This value is regulating the drivers priority right?
Should it be set to 0 then? Or am I wrong?
Regarding the priority could I set the fboffset value in the nvenabler plist?
Thanks.
Arbuz, NVE contains all the NECESSARY (only) stuff. All the rest is optional and generally smoke and mirrors. The more you add stuff, the more you take the risk to put wrong data. Experience shows that in 4/5 of the times, if you don't add a string, the driver will just figure it out automatically. Putting FB offset is just useless. Anyway feel free to experiment whatever you want, however please do this in my general nvidia thread, all that stuff is not really specific to NVE.
QUOTE (Krazubu @ Sep 16 2009, 02:36 PM)
Arbuz, NVE contains all the NECESSARY (only) stuff.
Hi tnx for your hard work!
But I have some problems...
I'm under snow
I insert my ID (0x040910de) in NVDAResman.kext and NVDANV50hal.kext
at boot NVE three times find my card nVidia 8700M GT but fails probe (False ROM signature: 0x0000)
I try every display-cfg (ffffffff, ffff3600, 03035000, 00ff3e01, 03010000, 03010300, 01ff0000, 00ff3e01, 0000000, 00) and removing display-cfg but nothing.
Better value allow loading background image and dock but pc hangs, others black or blue screen.
I attached ioreg from root loading and ioreg when i load my card with EFI string (in this case all is allowed but i can't see video in vlc or play dvd).
Thanks
root ioreg dump
EFI ioreg export
Working perfectly (2 DVI. S-video) on my Zotac 8600 GTS 256 Mb
Thanks!
Thanks!
What do you do exactly?
Please can you repeat step by step your actions?
Thanks
Please can you repeat step by step your actions?
Thanks
QUOTE (Alex79 @ Sep 18 2009, 04:30 PM)
What do you do exactly?
Please can you repeat step by step your actions?
Thanks
Please can you repeat step by step your actions?
Thanks
1. remove video from DSDT
2. install NVenabler
3. reboot with key -f
thats all
no need detect dysplay for me. s-video working after reboot
Version for Snow in progress? (x64)
(x64)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.