ProjectOSX

Welcome Guest!

Returning User? Login here.

Want membership privileges? Register here.

2 Pages V   1 2 >  
 Start a new topic Add Reply
> Guide For All Nvidia Boards, Manual installation
Krazubu
post Feb 17 2009, 01:16 AM
Post #1
This topics gives the basic installation process for nVidia cards/chips. It also contains extended infos for people who are willing to test things or enhance driver support.
The given way is manual in the sense you'll need to do yourself several steps through terminal and plist editor, instead of just clicking a few buttons from an installer.
You can use any injector or NVEnabler that needs no special tweaking thanks to automatic detection.

Pros :
- You now what you do
- You now what files you're using.
- The chances of success are almost 100% if you follow the guide correctly.
- You can tweak the driver for your hardware
- You learn

Cons :
- Requires 2% of a brain


Supported :
QUOTE
-Almost all models (whatever the brand is) from 4800 (not MX) to current ones are supported, including resolution change + QE/CI. Only some specific kinds of chips are not supported, see the list below.
-Support of older cards decreases as OSX versions go. Infos about OSX compatibility for each card range are detailed below.


Unsupported :
QUOTE
- Graphic controllers integrated to the chipset, with shared memory. Those models usually have a number below 300 (eg : 7150, 8200).
- Some Quadro NVS 140 (120 & 130 are the same model) & NVS 570. After investigations, it seems the problem is because of a non-standard BIOS that can't be accessed by the kext. Possible solutions are to patch the kext to point it to the right place, or make a kind of bridge to it, or hotload a BIOS image that would be used, as it's currently done for some ATIs. However, trials have been done on this side without success.
- VAIO displays. The graphic card is not responsible by itself, the problem comes from an internal display controller. Only external output can be used.


*********************************************************************


Installation guide :


Before proceeding ensure you have the right stock kexts from the right OSX version (see below the guide relevant to your card generation to know about required kexts).
If you don't and need to recover them check this thread (on the bottom).

The installation process is the same for any model, only the NVDANV kext number varies, depending on the generation.
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.

Device ID must look like this :
<key>IOPCIPrimaryMatch</key>
<string>0x01d010de 0x01d010de&0xfff0ffff 0x039010de&0xfff0ffff 0x029010de&0xfff0ffff</string>


Add your ID like the sample in red, don't bother about the ones that are already there, you can ignore or delete them.


Manually define memory size (Optionnal) :
QUOTE
If your injecter is unable to detect memory size (fixed, not including shared) you can define it yourself in the plist. String and keys are as follows :

"VRAM,totalsize" :
<00000008> - 128Mb
<00000010> - 256Mb
<00000014> - 320Mb
<00000020> - 512Mb
<00000028> - 640Mb
<00000030> - 768Mb
<00000038> - 896Mb
<00000040> - 1024Mb
<00000060> - 1,5Gb
<00000080> - 2Gb



geForce GTX 200 series (Require Leopard 10.5.7 or above):
Add your device ID in /system/library/extensions/NVDAResman.kext/contents/info.plist
Add your device ID in /system/library/extensions/NVDANV50Hal.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.

launch terminal and type
sudo chown -R root:wheel /system/library/extensions
sudo chmod -R 755 /system/library/extensions
sudo rm /system/library/extensions.mkext
reboot




geForce 8000 & 9000 & GT100 series (cards with G94 or G95 GPU require Leopard 10.5.5 build 9F2114 or above, you can also find the kexts in the 1st Macbook software update 1.2 , those with G84 or G86 need 10.5.2 with graphic update or above, or 10.4.11):
Add your device ID in /system/library/extensions/NVDAResman.kext/contents/info.plist
Add your device ID in /system/library/extensions/NVDANV50Hal.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.

launch terminal and type
sudo chown -R root:wheel /system/library/extensions
sudo chmod -R 755 /system/library/extensions
sudo rm /system/library/extensions.mkext
reboot




geForce 6000 & 7000 series (6100 and 6150 not supported) (only work in 32bit mode after 10.6.2. With Lion you must use NVDAResmanG7xxx & NVDAResmanG7xxx.kext instead) :
Add your device ID in /system/library/extensions/NVDAResman.kext/contents/info.plist
Add your device ID in /system/library/extensions/NVDANV40Hal.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.

launch terminal and type
sudo chown -R root:wheel /system/library/extensions
sudo chmod -R 755 /system/library/extensions
sudo rm /system/library/extensions.mkext
reboot




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.

launch terminal and type
sudo chown -R root:wheel /system/library/extensions
sudo chmod -R 755 /system/library/extensions
sudo rm /system/library/extensions.mkext
reboot




geForce 3000 & 4000 series (not MX models) :
Add your device ID in /system/library/extensions/NVDAResman.kext/contents/info.plist
Add your device ID in /system/library/extensions/NVDANV20Hal.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.

launch terminal and type
sudo chown -R root:wheel /system/library/extensions
sudo chmod -R 755 /system/library/extensions
sudo rm /system/library/extensions.mkext
reboot


TV out support :
TV out usually works nice with Tiger but not with Leopar. NVEnabler contains built-in TV fix, however you might still need to manually set @X,display-cfg string to get good results.



*********************************************************************


Optional infos for people who want to go further :

Here is a sample of a plist that works fine with 7600GS :
QUOTE
<key>@0,AAPL,boot-display</key>
<data></data>
<key>@0,compatible</key>
<string>NVDA,NVMac</string>
<key>@0,device_type</key>
<string>display</string>
<key>@0,display-cfg</key>
<data>//82AA==</data>
<key>@0,name</key>
<string>NVDA,Display-A</string>
<key>@1,NVMT</key>
<data>CgD/IAAAAAAgA1gCAARAA5ADAABuAlkCXAIAAEAhRwIAAAAAAAAA/wAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAD//wAAAAAAAAAAAAABAAAAAAAAAA==</data>
<key>@1,can-hot-plug</key>
<data></data>
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<string>display</string>
<key>@1,display-cfg</key>
<data>AP8+AQ==</data>
<key>@1,fboffset</key>
<data>AAACAA==</data>
<key>@1,name</key>
<string>NVDA,Display-B</string>
<key>AAPL,aux-power-connected</key>
<data>AQAAAA==</data>
<key>AAPL,backlight-control</key>
<data>AAAAAA==</data>
<key>NVCAP</key>
<data>BAEBAAAACAAHAAAAAAAACgAAAAA=</data>
<key>NVDA,Features</key>
<data>7wIABA==</data>
<key>device_type</key>
<string>NVDA,Parent</string>
<key>model</key>
<string>NVIDIA GeForce 7600 GS</string>
<key>rom-revision</key>
<string>3011</string>
<key>saved-config</key>
<data>CgguAgAEAABBAAAAAAAAAAIGIANYAiAEKACoAHQCAQAFAAAAoA8AAAAAAAAAAAAAAAAAAAAAAAAAA
AAAP8CgAAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAA==</data>
<key>subsystem-id</key>
<data>AAQAAA==</data>

Those values give full support with that card : dual screen + mirror mode working fine + TV out
There is 1 cons, it needs a plug/unplug of the DVI to VGA adapter at GUI so that it redetects the displays, otherwise the screen stays black. I'm still working on this problem and will update ASAP.

The keys in red are those that need particular attention because they are highly related to proper display support and vary from one model to an other.
Here is a suggestion of alternative values for the cards that are closer to the 8600GT
QUOTE
<key>@0,NVMT</key>
<data>CwN/ICLwzyaAB7AEIAiwB9AHAADTBLMEuQQAAIDaLQkAAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAD//wAAAAAAAECz1QkBAAAAAAAAAAAIAAAAAAAA</data>
<key>@0,compatible</key>
<data>TlZEQSxOVk1hYw==</data>
<key>@0,device_type</key>
<data>ZGlzcGxheQ==</data>
<key>@0,display-cfg</key>
<data>AwEAAA==</data>
<key>@0,fboffset</key>
<data>AAAGAA==</data>
<key>@0,name</key>
<string>NVDA,Display-A</string>
<key>@1,compatible</key>
<string>NVDA,NVMac</string>
<key>@1,device_type</key>
<data>ZGlzcGxheQ==</data>
<key>@1,display-cfg</key>
<data>//8AAQ==</data>
<key>@1,name</key>
<data>TlZEQSxEaXNwbGF5LUI=</data>
<key>AAPL,aux-power-connected</key>
<data>AQAAAA==</data>
<key>AAPL,backlight-control</key>
<data>AAAAAA==</data>
<key>NVCAP</key>
<data>BQAAAAAADAADAAAAAAAACwAAAAA=</data>
<key>NVDA,Features</key>
<data>/wJPBQ==</data>
<key>device_type</key>
<data>TlZEQSxQYXJlbnQ=</data>
<key>model</key>
<data>TlZJRElBIEdlRm9yY2UgODgwMCBHVA==</data>
<key>rom-revision</key>
<data>MzIzMw==</data>
<key>subsystem-id</key>
<data>TwUAAA==</data>


You'll want to insert those strings inside the plist of your injecter, using the standard text editor, in the section called <key>entriesToAdd</key> between the 2 <dict> and </dict> markups.
Those strings are encoded in base64.


Here is an attempt to detail the various strings that may be used. It may and probably does contain errors, feel free to experiment and submit your findings.
QUOTE
Mandatory data :
  • @0 is hardware channel 0
  • @1 is hardware channel 1
  • AAPL belongs to generic display data like board or screen info.
  • AAPL00 is related to internal primary display
  • AAPL01 is related to internal secondary display (not seen here, used with GMA)
@0,can-hot-plug = <>
self explanatory // enabled if key is present, no value
@0,compatible = NVDA,NVMac
fixed
@0,device_type = display
fixed
@0,display-cfg = <ffff3600>
needs to be set for mirror mode good working, meaning unkown, known to play a role in outputs definition, must be used along with @1,display-cfg
@0,name = NVDA,Display-A
tells display on hardware channel @0 is node "Display-A"
@1,AAPL,boot-display = <>
display on channel @1 is used for boot screen // enabled if key is present, no value
@1,can-hot-plug = <>
self explanatory // enabled if key is present, no value
@1,compatible = NVDA,NVMac
fixed
@1,device_type = display
fixed
@1,display-cfg = <00ff3e01>
needs to be set for mirror mode good working
@1,name = NVDA,Display-B
tells display on hardware channel @1 is node "Display-B"
@1,fboffset = <00000200>
must be set for the logical primary display, is 200 for 7300/7600
AAPL,aux-power-connected = <01000000>
must be set to 1 otherwise the OS will warn about unplugged GFX power cord
AAPL,backlight-control = <01000000>
backlight control enabled if set to 1 (so should be 0 for PCI cards)



Internal screen specific (values taken from iMac 24" with 7600GT)

@0,EDID = <insert EDID here>
EDID in hex
@0,backlight-control = <01000000>
hardware channel 0 uses backlight control // Back light control must be enabled with AAPL,backlight-control
@0,built-in = <>
self explanatory // enabled if key is present, no value
@0,panelinfo = <00641500>
unknown
@0,use-backlight-blanking = <>
self explanatory // enabled if key is present, no value
AAPL00,DataJustify = <01000000>
unknown
AAPL00,Dither = <00000000>
enables dithering for displays that don't support 24bit colours
AAPL00,DualLink = <01000000>
enables dual link
AAPL00,Inverter = <01000000>
unknown
AAPL00,InverterCurrent = <00000000>
unknown
AAPL00,InverterFrequency = <08520000>
inverter frequency, unkown format
AAPL00,LinkFormat = <01000000>
unknown, might be the signal format
AAPL00,LinkType = <00000000>
unkown, might be the connector type
AAPL00,PixelFormat = <01000000>
unkown
AAPL00,T1 = <00000000>
AAPL00,T2 = <01000000>
AAPL00,T3 = <c8000000>
AAPL00,T4 = <c8000000>
AAPL00,T5 = <01000000>
AAPL00,T6 = <00000000>
AAPL00,T7 = <90010000>
Unkown


Last updated on 26/12/11
DVSoftware
post Aug 14 2009, 05:37 PM
Post #2
Hello,
I own a Toshiba X200-23g notebook computer with 2 nVidia 8600M GT cards in SLI mode. I tried every possible injector (including NVEnabler) and i just can't get it working... The best results I got is with NVinject 0.2.1 which enabled full QE/CI but i could never get 2 monitors to work (My notebook has VGA output), other injectors and efi strings cause a kernel panic. I'm not sure what information I need to provide, for the beginning, here is a copy from system profiler:

CODE
Nvidia GeForce 8600m GT:

  Chipset Model:    Nvidia GeForce 8600m GT
  Type:    Display
  Bus:    PCIe
  PCIe Lane Width:    x16
  Vendor:    NVIDIA (0x10de)
  Device ID:    0x0407
  Revision ID:    0x00a1
  ROM Revision:    NVinject 0.2.1
  Displays:
Display Connector:

Nvidia GeForce 8600m GT:

  Chipset Model:    Nvidia GeForce 8600m GT
  Type:    Display
  Bus:    PCIe
  PCIe Lane Width:    x16
  VRAM (Total):    256 MB
  Vendor:    NVIDIA (0x10de)
  Device ID:    0x0407
  Revision ID:    0x00a1
  ROM Revision:    NVinject 0.2.1
  Displays:
Display:
  Resolution:    1680 x 1050
  Depth:    32-bit Color
  Built-In:    Yes
  Core Image:    Hardware Accelerated
  Main Display:    Yes
  Mirror:    Off
  Online:    Yes
  Quartz Extreme:    Supported


Here are logs of NVEnabler:

CODE
Aug 14 01:03:05 localhost kernel[0]: NVEnabler: DEBUG  Setting property @0,compatibleNVEnabler: False ROM signature: 0x0000
Aug 14 01:03:05 localhost kernel[0]: NVEnabler: DEBUG  Setting property @1,display-cfg
Aug 14 01:03:05 localhost kernel[0]: NVEnabler: DEBUG  Setting property @1,name
Aug 14 01:03:05 localhost kernel[0]: NVEnabler: DEBUG  Setting property device_type
Aug 14 01:03:05 localhost kernel[0]: NVEnabler: DEBUG  Setting property @0,name
Aug 14 01:03:06 localhost kernel[0]: NVEnabler: DEBUG  Setting property @1,compatible
Aug 14 01:03:06 localhost kernel[0]: NVEnabler: DEBUG  Setting property @0,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe fails
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: init : begin
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe(display)
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: probe : probe
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG Model found: GeForce 8600M GTNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG  Setting property @0,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,nameNVEnabler: False ROM signature: 0x0000
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,name
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe fails
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: init : begin
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe(VGA1)
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: probe : probe
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: False ROM signature: 0x0000
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG Model found: GeForce 8600M GTNVEnabler: DEBUG VRAM: 0NVEnabler: DEBUG  Setting property @0,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,name
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,name
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe fails
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG Model found: GeForce 8600M GTNVEnabler: DEBUG VRAM: 256NVEnabler: DEBUG  Setting property @0,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,name
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,name
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,compatible
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @0,display-cfg
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler: DEBUG  Setting property @1,device_type
Aug 14 01:03:06 Macintosh kernel[0]: NVEnabler::probe fails


And roms from both cards are attached here:
Attached File  roms.zip ( 78.78K ) Number of downloads: 197


Let me know if you need any more information. Thank You

Edit: Ioreg dump attached
Attached File  NVEnabler_ioreg_dump_dvsoftware.txt ( 960.08K ) Number of downloads: 141


This post has been edited by DVSoftware: Aug 14 2009, 08:11 PM
Krazubu
post Aug 14 2009, 08:18 PM
Post #3
You gotta disable SLI mode it's not supported by OSX. About dual cards, it's not supported yet by NVE (I updated the 1st post to add that). Actually it's supported, but not "automatically", you have to add the necessary strings in the plist, then it should work fine.
You have to add the string "rm_multiboard_capable" and set its boolean value to 00000001.
DVSoftware
post Aug 14 2009, 08:26 PM
Post #4
There is no way to disable SLI on this laptop, can't it just treat it as 2 separate cards? sad.gif
To clarify, I don't need SLI to work, just dual monitors...
Krazubu
post Aug 14 2009, 08:35 PM
Post #5
Enabled SLI will make OSX panic, but if you say you could get QE before it means it wasn't the case for you, weird but let's try...
As for others with problems, try 1st to remove the 2 display-cfg strings.
If it doesn't help, set string "skipvbios_disabled" to 1
DVSoftware
post Aug 14 2009, 09:18 PM
Post #6
Same situation... I don't know if you noticed but it detects wrong ram amount for the first card... it detected 0MB before, now it detects 4096MB...
Krazubu
post Aug 15 2009, 10:10 AM
Post #7
After looking at your ROMs I notice that rom0 has only support for LVDS, and that rom1 has LVDS + DVI/VGA + TV. Dunno what you named your roms after, but take in account that it's the card with rom1 you have to use. About the other one, just let it die, ignore it. Also try something like NVInject for dual cards, tho I'm not optimistic it might have a plist that works better for this case.
DVSoftware
post Aug 15 2009, 11:17 AM
Post #8
card0.rom is the first card, and card1.rom is the second. Laptop display is apparently attached to the second card on boot, and i think it reattaches it to the first one when second monitor is plugged in (in other operating systems, i lose SLI with 2 monitors). Can I ignore the card by it's PCI address? NVinject Dual causes KP, and with NVinject 0.2.1 i get laptop display fully working with accelleration, and the most i could do with the second monitor is to stop it from going to standby, but then i lost laptop display, and haven't got picture on the second)
Krazubu
post Aug 15 2009, 01:56 PM
Post #9
Look in your IOReg, there's a subdevice called SL01@1, this is the secondary card. Usually OSX better likes to use the primary one but this is kind of random especially in your case where anything can happen depending on how they implemented all that stuff. So it looks NVInject could use your primary card, but it seems you'll need to use the secondary one to get VGA out, and probably not at the same time unless you manage to enable dual card support, which is maybe not possible with this hardware. There's no easy way, you're gonna have to do many trials. I'd better suggest you to use a device property string for that. You could convert the data of the working plist of NVinject to string, if it works for the primary it should work for secondary as well, and "aim" the secondary card with the device path. Not everybody is comfortable with that but I can't explain everything from scratch you'll have to do some research if you don't get everything.
DVSoftware
post Aug 16 2009, 07:17 PM
Post #10
THANK YOU, I finally managed to get dual monitors and QE/CI just by following Your suggestion to disable second card, I just made a plist with PCI ID of the second card, created a hex, and added it to com.apple.Boot.plist, and it finally works smile.gif
Harshy
post Oct 13 2009, 05:23 AM
Post #11
Hello,
I have an older 6800GT 256MB AGP card. Do the drivers disable QE and Core when put on a TV-Out? Currently I have NVEnabler working to the point that it shows a Television connected and allows resolution changes. I do not have a VGA or DVI monitor hooked up at this time. I havn't looked into re-installing the stock OGL files (since I had to do it for the NVDA* ones), and wonder if that is the next step in the process.

Thanks for the comments!
uncommah
post Nov 8 2009, 02:21 PM
Post #12
i wonder what the NVDA,Features property is for? do i need it?
Asus V1Sn ~ MacBookPro4,1
Intel® Core 2 Duo T9300 (2.5GHz) / DDR2 667 MHz / NVIDIA GeForce 9500M GS 512MB / Mobile Intel® PM965 Express + ICH8 / ALC660 / Intel® Wireless WiFi Link 4965AGN Apple Atheros AR5008 / eSATA (JMicron JMB360) / Intel® 82566MM Gigabit Ethernet
Musiquence
post Mar 23 2010, 11:46 AM
Post #13
Works like a charm! Thank you so much!!!

(HP Pavilion dv9000 laptop with NVIDIA GeForce GO 7600 256MB... 1440x900 and QE/CI enabled)
dckirba
post Aug 12 2010, 10:13 AM
Post #14
Hi Krazubu,

Thank you for an excellent guide. I've followed it and I have my Nvidia Quadro FX 3000 working with hardware acceleration and resolution change. (iPC 10.5.6, Voodoo kernel, NVDarwin 256).

Unfortunately, none of the available resolutions (800x600, 1024x768, 1280x1024) matches the native resolution (1440x900) of my monitor (Fujitsu Siemens Scaloview W19-1).

I've tried using SwitchResX, manually editing the windowserver plists and starting the computer with the monitor off, but I'm still unable to get native resolution.

I exported the monitor's EDID file using SwitchResX and strangely, it does list 1440x900 as one of the monitor's resolutions, but not under available resolutions. Here is the relevant section:
QUOTE
Established Timings:
--------------------
720 x 400 @ 70Hz
720 x 400 @ 88Hz
640 x 480 @ 72Hz
640 x 480 @ 75Hz
800 x 600 @ 75Hz
1024 x 768 @ 60Hz
1024 x 768 @ 70Hz
1024 x 768 @ 75Hz
1280 x 1024 @ 75Hz

Manufacturer Reserved Timings:
------------------------------
1152 x 870 @ 75Hz

Standard Timing Identification:
-------------------------------
#0: 1152 x 864 @ 75Hz (714F)
#1: 1280 x 720 @ 60Hz (81C0)
#2: 1280 x 720 @ 75Hz (81CF)
#3: 1280 x 1024 @ 60Hz (8180)
#4: 1440 x 900 @ 60Hz (9500)
#5: 248 x 155 @ 61Hz (0001)


I'm searched the web for the past couple of days and the only solutions I can find are the ones I've already tried.

After some thought, I realised that it's only 4:3 standard resolutions that are available and not widescreen resolutions. I have no idea if that is relevant at all.

Do you have any idea how to fix this issue? I would appreciate your help greatly.

Thank you,

David K
Krazubu
post Aug 12 2010, 03:04 PM
Post #15
You can force any resolution you want with SwitchresX, you probably didn't search enough.
Also check that you don't have forced resolution as boot parameter (something like Graphics Mode=1024x768x32 in com.apple.boot.plist).
dckirba
post Aug 12 2010, 07:02 PM
Post #16
Thanks for the quick reply smile.gif

I have tried several methods using SwitchResX and I don't have a forced resolution on the boot plist. In fact, I even tried forcing the native resolution of the monitor on the boot.plist . However, I will follow your suggestion and search some more for SwitchResX help.

Cheers,
David K
hectorox
post Apr 10 2011, 08:56 PM
Post #17
does someone know what fboffset should be for a geforce 9300M G, 256 MB ?
crizl
post Dec 25 2011, 04:28 PM
Post #18
I did everything by the book (by the post) in 10.6.1 with a geforce 6200 tc 256 mb pcie and now I'm stuck at "AirPort: Link Up in en1 "

I used NVEnabler64 as Injecter and followed all of the steps with NVDANV40 and NVDAResman...
Krazubu
post Dec 26 2011, 09:53 AM
Post #19
With Lion you must use NVDAResmanG7xxx and NVDANV40HalG7xxx kexts instead of usual ones. You also have to boot in 32bit. I updated the guide accordingly.
khorght
post Dec 31 2011, 06:36 PM
Post #20
Can't get QE/CI with nvidia 9300M GS 256mb. added generated hex to boot.plist but nothing changed - same non working QE/CI was with NVEnabler, NVEnabler64 and enabler from chameleon v2.1. tried this solution but no result again. my device id is 06e910de and i've added it to NVHal50 and nvresman and to enabler but i don't see this kexts as loaded in my system in SystemInfo.app. am i missing something or just screwed up with this bip-bip video-card?
 

2 Pages V   1 2 >
Add Reply Start a new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Powered By IP.Board © 2013  IPS, Inc.