Jump to content

9600M GT


PacmanMCE
 Share

107 posts in this topic

Recommended Posts

  • 3 months later...
  • 4 weeks later...

I have my 9600m GT up and running except via internal LCD which Im still working on...I used iPC 10.5.6 and selected ONLY NVDarwin 512mb for the graphic options, both my HDMI and VGA have full hw support etc...now just need to get my internal working

 

I run a Toshiba Qosmio G50

Link to comment
Share on other sites

ok.. it have been 2 weeks since I tried to do the same!

 

the results:

NON EFI:

drivers:

GEFORCE.

NVDANV50Hal.

NVDARESMAN.

(those drivers are good in 10.5.5 package or 10.5.6.. -> 1.5.34 or 1.5.36 versions)

you MUST override the PCImatch section with the number of the beast.. 0x0649010de

 

injector:

nvkush (KO)

nvdarwin (ok but no qe/ci )

nvinject (ok but no qe/ci 0.2.1 or 0.2.0)

nvresolv (ko)

nvinjectgo (0.2.0 OK with QE/CI but crash in system profiles in video section and cannot see lcd data..

you have at best 1280x800)

you can put nvcap with the ROM IN ATTACHED overriding the nvcap data in the injector.. but the result .. i'll test this evening.. if I have all the output working fine..

 

GFX EFI:

At today.. I haven't found any efi method to extrapolate from win/linux/mac the good efi of my card.. the only efi founded is the EFI of 9600GT 512mb.. which is QUITE different!!!

then.. with efi string the system start.. but no QE/CI

 

 

i tried also to replace IOGraphicsfamily.kext from 1.6.1 (10.5.5) to 1.7.1 (10.5.6) and a patched one 1.7.2..

 

i tried also to use drivers of Snow..

 

i tried also to use those drivers:

n9000 v1

n9000 v2

xdarwin 1.1

nvinstaller v 41

nvinstaller v52

nvinstaller v 1.2.1

nvinstaller v 1.2.3

nvinstaller v 1.2.5

acquamac

0-9f23 installer

 

without any real difference between native drivers and a good injector.. but most of them put injector that you must change inside!! if not.. you can see:

 

black screen..

strange screen

no screen (not black .. only text boot and no start of windowserver)

screen with thousand of crash and slow without the possibility of move.. ( nvdarwin with xdarwin .. .in ascade!)

 

bye

Link to comment
Share on other sites

@ugokind

 

Yours is running with your native LCD Resolution now? That's the only thing I want, my 1920x1080 resolution to use X-Code

 

I also have tested a lot of Drivers and Injectors, pretty much the same as ugokind and nothing help :angry:

Link to comment
Share on other sites

bah.. no! the maximun osx shows is the 1280.. nothing else. with a 9600gt efi it depends ONLY from the fLAG into the com.apple.boot.. ... if you write 1024 you see in 1024 and the pref display show only 1024.. etc..

 

but i'm using an injector.. and I never seen any 1900 ... how can you reached that??

Link to comment
Share on other sites

If only I can extract the 9600m Rom...then I could get the nvcap info sorted!, Ive tried to extract on a Sony AW17, AW25, AW27...cannot read the bios info

 

If you point me to how to do it maybe I can try on my AW11S though, also the very same card is used on the last MacBook Pros.

 

thanks for help

Link to comment
Share on other sites

here I am..

 

this is my

nvinjectgo.kext/contents/info.plist part with nvcap..

i've erased my hex data.. and put

 

<key>NVCAP</key>

<data>

0400000000000d00400000000000000700000000

</data>

Link to comment
Share on other sites

I Have an HP Pavillon DV5-1157ca with a NVIDIA 9600M GT card with 512 Mb memory. It works perfectly on a Leopard 10.5.6 installation with the vanilla kexts. No modification necessary. QE/CI, both laptop and external HDMI port working, rotate, mirror, etc. I haven't tested the VGA port but I suspect it would work also.

 

I used to use NVdarwin, but now I use an EFI GFX string made from the following in xml format:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

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

<dict>

<key>@0,AAPL,boot-display</key>

<data>

</data>

<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>@0,use-backlight-blanking</key>

<data>

</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,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>

BQEAAAAAAQAGAAAAAAABCwAAAAA=

</data>

<key>VRAM,totalsize</key>

<data>

AAAAIA==

</data>

<key>device_type</key>

<string>NVDA,parent</string>

<key>model</key>

<string>NVIDIA GeForce 9600M GT</string>

<key>rom-revision</key>

<string>test</string>

</dict>

</dict>

</plist>

 

Hope that helps.

 

(Of course you'll have to check to pciroot for your machine and adjust the VRAM,totalsize parameter to reflect your card. As for the rom-revision parameter, what you write there is irrelevant, but it is what's going to appear in system information)

Link to comment
Share on other sites

maybe I think it's caused by these typical situations:

 

-do you have other injector? if so--> remove it and leave only nvdarwin.. if you want to test it!

-in the 3 files.. geforce.. nvdanv50 and nvresolver did you check about correct id of the card?

 

 

PLEASE: could you give me the output of:

 

kextstat

 

?? It's a good start.

Link to comment
Share on other sites

I Have an HP Pavillon DV5-1157ca with a NVIDIA 9600M GT card with 512 Mb memory. It works perfectly on a Leopard 10.5.6 installation with the vanilla kexts. No modification necessary. QE/CI, both laptop and external HDMI port working, rotate, mirror, etc. I haven't tested the VGA port but I suspect it would work also.

 

I used to use NVdarwin, but now I use an EFI GFX string made from the following in xml format:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

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

<dict>

<key>@0,AAPL,boot-display</key>

<data>

</data>

<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>@0,use-backlight-blanking</key>

<data>

</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,name</key>

<string>NVDA,Display-B</string>

<key>NVCAP</key>

<data>

BQEAAAAAAQAGAAAAAAABCwAAAAA=

</data>

<key>VRAM,totalsize</key>

<data>

AAAAIA==

</data>

<key>device_type</key>

<string>NVDA,parent</string>

<key>model</key>

<string>NVIDIA GeForce 9600M GT</string>

<key>rom-revision</key>

<string>test</string>

</dict>

</dict>

</plist>

 

Hope that helps.

 

(Of course you'll have to check to pciroot for your machine and adjust the VRAM,totalsize parameter to reflect your card. As for the rom-revision parameter, what you write there is irrelevant, but it is what's going to appear in system information)

 

 

excuse me laqk.. but how can I use this xml?

i must remove my drivers.. but this file.. you use with osx86tools??

 

i don't know!!

 

thanks

Link to comment
Share on other sites

@tank6b:

I must point out that I'm using a vanilla leopard installation. I see that you're using iDeneb. Maybe this distro has some modified kexts or bundles that interfere with the display system. Maybe that has nothing at all to do with it, but maybe you could try to do a vanilla install and see how it goes.

 

@ugokind:

 

Yes, you can use OSX86Tools or EFIStudio to import the xml file, convert it to an hex string and inject it in your com.apple.Boot.plist file. Be sure to remove ALL injectors (NVinject, NVdarwin, etc) and use vanilla 10.5.6 kexts.

Link to comment
Share on other sites

thanks.. i just wrote to de osx86 team because the funcion to import doesn't work

 

i wrote and converted manually.. but it doesn't work

 

it give a black screen

 

i use the nvcap generated with the tool in vista..

thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...