Jump to content

(Solved) 8800 GT on Mavericks? help please


3square
 Share

24 posts in this topic

Recommended Posts

hello all,

 

I have a 8800 GT and a 8500 GT. They both ran great, pumping out my quad monitors setup in lion and ML. This was done via injection code method in the boot plist.

 

I bit the bullet and upgraded to Mavericks, and what do you know... all mess up now =\ install went fine, boot back in everything else work (wifi, sounds, bluetooth, HD etc.) except for the graphic cards. Only one monitor, no QE/CI, choppy as hell. I also got the warning about nvidia web driver doesn't support Mavericks blah blah blah.

 

100 million dollar question... any one know how to get my cards to work? please?

 

tried using nvenabler, no go, try loading the old nvidia kext from ML, nada.

 

any suggestion would greatly appreciated.

 

dell XPS 420

newest chameleon 2266

graphic enabler: on

smbios: macpro 3,1

both cards recognized and identified in system report

custom DSDT, i found one that was made for my xps 420. work fine before all this.

retail Mavericks, installed over ML (i know... messy way)

Link to comment
Share on other sites

None, try rebuilding the kexts using kext wizard. Or boot with -f

Also delete the nvda next with tesla name

Do you mean delete all nvda kext with tesla in the name?

 

This is what I have been booting with:

 

<key>Graphics Mode</key>
<string>1024x768x32</string>
<key>GraphicsEnabler</key>
<string>No</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-f -v npci=0x2000</string>
<key>Timeout</key>

<string>5</string>

 

If I boot GraphicsEnabler Yes I get gray screen, if I remove npci flag, boot dies after DSMOS arrives.

Link to comment
Share on other sites

Yes try deleting all the nvda kext with tesla in the name. Reference the post I link. My setup is a dell xps 420, with dsdt... Not sure what else it'll take for your to work. Good luck

I did not need to boot with any flag, and graphic enabler is set to yes. I do have injection for the cards in the boot plist

Link to comment
Share on other sites

Try to boot with flag npci=0x3000.

 

Have fun.

I tested this... but no resolution change and also I lose my audio fix (I am using my patched AppleHDA from ML which works).

 

 

 

Yes try deleting all the nvda kext with tesla in the name. Reference the post I link. My setup is a dell xps 420, with dsdt... Not sure what else it'll take for your to work. Good luck

I did not need to boot with any flag, and graphic enabler is set to yes. I do have injection for the cards in the boot plist

I backed up and deleted all nvda & Gforce kext with "tesla" in their name... also changed my boot.plist to the following

 

<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-f -v</string>
<key>Timeout</key>
<string>5</string>
 
I still don't have my resolution but I think were getting somewhere as I could not boot GraphicsEnabler=Yes before. I was also able to boot without npci=0x2000.
 
Update: I just tried adding
 
<key>Graphics Mode</key>
<string>2048x1152x32</string> (this is my 23" Samsung's native resolution)
 
I also figured that since the issue is just "tesla" kext and it works with DP8's kext it should work with kext installed by 10.9 retail (minus the "tesla" kext), reverted to 10.9 installed kext and it dose work.

 

 

Now the system see's my card correctly but resolution is off. It boots into 1280x1024. And no graphics acceleration.

 

Screen%2520Shot%25202013-10-28%2520at%25

Link to comment
Share on other sites

I tested this... but no resolution change and also I lose my audio fix (I am using my patched AppleHDA from ML which works).

 

 

 

I backed up and deleted all nvda & Gforce kext with "tesla" in their name... also changed my boot.plist to the following

 

<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-f -v</string>
<key>Timeout</key>
<string>5</string>
 
I still don't have my resolution but I think were getting somewhere as I could not boot GraphicsEnabler=Yes before. I was also able to boot without npci=0x2000.
 
Update: I just tried adding
 
<key>Graphics Mode</key>
<string>2048x1152x32</string> (this is my 23" Samsung's native resolution)
 
I also figured that since the issue is just "tesla" kext and it works with DP8's kext it should work with kext installed by 10.9 retail (minus the "tesla" kext), reverted to 10.9 installed kext and it dose work.

 

 

Now the system see's my card correctly but resolution is off. It boots into 1280x1024. And no graphics acceleration.

 

Screen%2520Shot%25202013-10-28%2520at%25

 

that's where i was at in the beginning. it boots into mavericks, default resolution no acceleration.

 

From what it seem is with DP8, it did included the support for our GFX cards; with the NVDA's kext (no tesla). but with the retail 10.9, they drop the support hence our problem.  I even replace the NVDA kext from ML, it wouldn't work. but the DP8 does.

 

i'll check my setup again later and i'll post my kext for you.

 

hang tight!

 

are you using any injection code for your?

Link to comment
Share on other sites

that's where i was at in the beginning. it boots into mavericks, default resolution no acceleration.

 

From what it seem is with DP8, it did included the support for our GFX cards; with the NVDA's kext (no tesla). but with the retail 10.9, they drop the support hence our problem.  I even replace the NVDA kext from ML, it wouldn't work. but the DP8 does.

 

i'll check my setup again later and i'll post my kext for you.

 

hang tight!

 

are you using any injection code for your?

3square, thanks for all your help so far. Yes, I also tried ML kext at 1st.

 

Injection, I am still reading up a learning about… bit fuzzy to understand for me atm, but I think my dsdt.aml. I don't recall where I originally got it but it could have been from an old topic here on InsanelyMac for the Asus P5E (maybe 3-4 years old now).

Link to comment
Share on other sites

3square, thanks for all your help so far. Yes, I also tried ML kext at 1st.

 

Injection, I am still reading up a learning about… bit fuzzy to understand for me atm, but I think my dsdt.aml. I don't recall where I originally got it but it could have been from an old topic here on InsanelyMac for the Asus P5E (maybe 3-4 years old now).

my chameleon.boot.plist

<key>Boot Banner</key>
	<string>No</string>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1680x1050x32</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>Rescan</key>
	<string>Yes</string>
	<key>SystemType</key>
	<string>1</string>
	<key>Theme</key>
	<string>LoginToLion</string>
	<key>Timeout</key>
	<string>3</string>

i include my S/L/E portion of the NVDA* kext that i'm using. same one from DP8.

 

Use this to generate a EFI injection for your card.  from the drop down menu, it'll give you a list of cards. select your card, and it should add the efi string into your chameleon.boot.plist.

http://www.insanelymac.com/forum/topic/124911-osx86tools-final-release-is-here/

 

you can see my complete chameleon.boot.plist  which the included efi string.  i'm using the string to include both my cards.

 

as you can see from my graphic card description "Rom Revision"... it said EFI.

 

I'm including a zip of all the NVDA's related kext...include two that has TESLA. i guess i didn't have to delete all of the TESLA's kext.  Worth a shot dropping it in.

 

Sorry i can't be anymore specific. I've manage to "fumble" along and figure out how to get it to work on mine. It been working since Lion till now, so that's all i know.

hope any of this will help you.

post-841174-0-17591000-1383022674.png

post-841174-0-84425000-1383022685_thumb.png

post-841174-0-70895600-1383023292_thumb.png

NVDA_DP8.zip

Link to comment
Share on other sites

Thanks 3square, I will try it out this afternoon and report back….. 1 question though, did you remove any of your Geforce kext from S/L/E?

 

To get this far I had to remove (GeForceTesla.kext, GeForceTeslaGLDriver.bundle, GeForceTeslaVADriver.bundle). Anyway, I will experiment and see where I get.

Link to comment
Share on other sites

3square, I tried replacing all my NVD kext with yours and adding device string to my boot plist. However there was no change for me. Also it did not seem to matter that these included the tesla kext, however (at least for me) the Geforce tesla kext I listed above are a problem. If those are in my S/L/E folder, I get a gray screen at boot.

 

Anyway, I have to look deeper into my dsdt and see how that is set up. Thanks for your time.

Link to comment
Share on other sites

Thanks 3square, I will try it out this afternoon and report back….. 1 question though, did you remove any of your Geforce kext from S/L/E?

 

To get this far I had to remove (GeForceTesla.kext, GeForceTeslaGLDriver.bundle, GeForceTeslaVADriver.bundle). Anyway, I will experiment and see where I get.

i did not do anything to the Geforce Kext

Link to comment
Share on other sites

@jackbutler Did you have any luck with this?

 

@3square Which Nvidia kexts do you see loaded in System Information > Software > Extensions? And BTW, what model identifier are you using for your system?

No, I am still looking for a solution. I think some others have the same issue.

 

I did see someone posted to the OSx86 wiki regarding Asus P5E build working w/Mavericks, however they are running a Geforce 9800GT.  Also I would like to know a few other errors they may have solved, but it was not a detailed explanation.

Link to comment
Share on other sites

No, I am still looking for a solution. I think some others have the same issue.

 

I did see someone posted to the OSx86 wiki regarding Asus P5E build working w/Mavericks, however they are running a Geforce 9800GT.  Also I would like to know a few other errors they may have solved, but it was not a detailed explanation.

 

I recently scrapped my old rigged (Dell XPS 420) for a new Gigabyte board z77x-up5-th. I am using the HD4000 along with my 8800GT card. i was able to do so by injecting the efi string for both graphics; as mentioned above.

 

i'll get a screen grab of the loaded extension for you, once i get home later.

Link to comment
Share on other sites

@jackbutler Did you have any luck with this?

 

@3square Which Nvidia kexts do you see loaded in System Information > Software > Extensions? And BTW, what model identifier are you using for your system?

 

kext wizard showing those NVDA and geforce kext loaded.

post-841174-0-42606600-1383628945_thumb.png

Link to comment
Share on other sites

Hi JackButler, do you have successfully installed your video card?

I have the same problem with my Zotac 8800 gt.  I have correct resolution for my display (1680x1050), but nothing acceleration qe/ci!

No still looking for fix or what the issue is. My monitor is 23" Samsung with native 2048x1152... I only get 1280x1024 with no qe/ci.

Link to comment
Share on other sites

  • 6 months later...

Have not really spent time on this till today... try with fresh 10.9 + 10.9.3 Combo updater on external test HD. Inject via org.chamelion.boot.plist. Also must remove GeForce Tesla kext (otherwise will not boot).

 

So I now have MSI 8800GT showing up and correct screen resolution for my main monitor, however no acceleration.

 

 

<dict>


<key>GraphicsEnabler</key>
<string>Yes</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>-f -v nvda_drv=1</string>
<key>Timeout</key>
<string>5</string>
<key>Graphics Mode</key>
<string>2048x1152x32</ string> 
<key>device-properties</key>
<string>6c0200000100000001000000600200000d00000002010c00d041030a000000000101060000010101060000007fff04001e00000072006f006d002d007200650076006900730069006f006e0000002e0000006e5669646961204765466f7263652038383030204754204f70656e474c20456e67696e65205b4546495d22000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c6179100000004e00560043004100500000001800000004000000000003000c00000000000007000000000e0000006e0061006d00650000000b000000646973706c617914000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d006f00640065006c0000001a0000006e5669646961204765466f72636520383830302047540e0000004e00560050004d000000200000000100000000000000000000000000000000000000000000000000000014000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d4220000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163220000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000002020000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616322000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c61791c0000006400650076006900630065005f00740079007000650000000f0000004e5644412c506172656e74</string>
</dict>
Link to comment
Share on other sites

Today Downloaded new released drivers for 10.9.3 (WebDriver-334.01.01f01.pkg). Installed, rebooted and set to NVIDIA Web Driver then restarted again... I have acceleration however when I check system preferences it says OS X Default is running (in boot -v it says "NVDASartup: web"). Not sure why but maybe because I have to boot with -f all the time otherwise hangs on bluetooth thing. :unsure:

 

 

Screen%2520Shot%25202014-05-17%2520at%25

Link to comment
Share on other sites

  • 11 months later...
 Share

×
×
  • Create New...