Jump to content

Mountain Lion anyone?


Darvinko

Recommended Posts

I tried editing NVDAGF100hal.kext and NVDAGK100.hal.kext with the device id's and no appreciable difference, no difference in graphics, etc.. I lost the audio and bluetooth icons from the menu bar, but was able the add them back via System Preference, clicking on each of the devices and clicking "show (device) in menu bar". Until we determine there is a useful reason to edit these, I would avoid editing them.

Link to comment
Share on other sites

I have figured out how to avoid using the -x boot flag while booting up our systems. It boots properly, restarts properly, audio, bluetooth, eject and time machine icons show in the menu bar and the system response is much snappier. All Nvidia kexts stay in S/L/E and the device id must be inserted into the following kexts: GeForce.kext, NVDANV50hal.kext, NVDAResman.kext. You must use TextEdit to accomplish this (if you are uncomfortable using it, maybe someone will be kind enough to post the edited kexts.

 

First, I suggest you go to System Preferences->Security->unlock security->allow applications downloaded from anywhere.

 

Then go to Safari and download kext wizard.

 

The device id you will be entering is for the Nvidia Quadro NVS160 graphics controller (if you don't have that graphics controller, this won't help.

 

The device id you will be entering is: 0x06eb10de&0xffe0ffff (these are all zeros, not the letter o)

 

Now, open Mountain Lion, go into S/L/E and go to the kexts mentioned above. I did these one kext at a time. For the GeForce.kext and the NVDAResman.kext, insertion will be in the form of IOPCIMatch followed by 0x06eb10de&0xffe0ffff. You need the drag the kext (we'll start with the GeForce.kext) to you desktop. After it's on your desktop, right click it and click on "Show Package Contents". A contents folder will show. Double click it and the contents will show. Drag the info.plist to your desktop. Right click and go to "open with", slide it to show your options and click "TextEdit". You will then click on open to see an expanded info.plist which you can edit. In the GeForce.kext, place these (The key and string lines from above) in between the other IOPCIMatch and the IOPProbeScore (in the second grouping, offset a little to the right of the first grouping). Start at the end of the end of that IOPCI's string line, hit enter (after hitting the space bar enough to start directly under the line above) and enter those two lines. Make sure these are two separate lines - follow the same format you see. MAKE SURE THESE LINES ARE EXACTLY AS SHOWN OR THEY WILL NOT WORK AND YOU WILL HAVE TO RE-EDIT THEM. After you have added the two lines, close the TextEdit box, drag the info.plist back to the contents, close the contents box. Leave the edited kext on your desktop. Follow the same procedure for the NVDAResman.kext, placing the two line again between the string line of the last IOPCIMatch and before the IOProbeScore (these lines are in the third grouping). For the NVDANV50hal.kext, you only need add the device id number I indicated above (no key or string). Open the kext the same way, go down to where you see a group of devices id's (similar format to your's -just different number and letters) add the device id between the one that starts with 0x06e010 and the one that starts with 0x086010. Close the same way, again, leave the kext on the desktop. Close all boxes and open kext wizard, click on the installation tab. Make sue you check the Backup kexts that will be replaced (they will be saved to a folder on your desktop - you can always drag them to the trask later). Make sure you click the System/Library/Extensions destination tab. Drag the three kexts to the "Select kexts to install" box. Click install. When that's done, click the maintenance tab, click on both Extra and System/Library/Extensions tab. Click Execute. When that's done reboot (shut down and startup may take longer than usual as ML "digests" the changes). If it takes longer than five minutes, hold the power button for a second, look for signs of hard drive activity, if hard drive light blinks wait another minute or two, and then shut down with power button.

 

Graphics still needs work, audio shows, but isn't working (kext installation likely), bluetooth (if you have it) shows, time machine shows (I didn't check either of them), keyboard and trackpad (which had stopped working for me) work again. Sorry I didn't check more out, I have to leave, but wanted to throw this out there.

 

Would someone please edit these kexts and make the edited versions available for those who don't know how to or are hesitant to edit them themselves? Thank You

 

Darvinko, you've done it again! IT WORKED! No more screen tear, stuttering, etc.!

 

Attached are the edited kexts as per your request. Also, after the restart, I had to boot with GraphicsEnabler=Yes at boot, otherwise I got a black screen; not sure if it will happen to you since Darvinko didn't mention it, but if it does, you know know how to get past it :D

 

Edited Nvidia Kexts.zip

 

I'm also very sorry to hear about your mother; my best condolences go out to you...

Link to comment
Share on other sites

Darvinko, you've done it again! IT WORKED! No more screen tear, stuttering, etc.!

 

Attached are the edited kexts as per your request.

 

Edited Nvidia Kexts.zip

 

I'm also very sorry to hear about your mother; my best condolences go out to you...

 

I'm about to have at your kexts, will report how it goes later on.

 

Darvinko, sorry about your loss... :(

Link to comment
Share on other sites

I'm about to have at your kexts, will report how it goes later on.

 

Darvinko, sorry about your loss... :(

 

Quick note: I had to boot with GraphicsEnabler=Yes after a restart; if I didn't, I got a black screen. I will modify my earlier post to reflect this....

 

Thanks for reminding me :$

Link to comment
Share on other sites

Quick note: I had to boot with GraphicsEnabler=Yes after a restart; if I didn't, I got a black screen. I will modify my earlier post to reflect this....

 

Thanks for reminding me :$

 

Weird thing, when I removed those kexts, I booted with GraphicsEnabler=Yes, and it had a native 1440x900 res already, turned it off, got back 1280x800. Just a weird thought. :rolleyes:

 

So graphics are really working? (I'm myHacking my ML partition right now.) Like, you can ACTUALLY open Launchpad without it flipping tables on you?

Link to comment
Share on other sites

Graphics seem to be working, VooDoobattery.kext got my battery icon back in the menu bar, VooDooHDA.kext 2.7.4 has got audio working (but volume isn't where it should be), am unable to check WiFi as I'm in a vehicle. It's starting to look promising. Graphics may need some work - launchpad takes a while to open and framebuffering seems slow.

Link to comment
Share on other sites

Quick though, Patel4Prez. Are you still using the M4300 bootpack? I reverted to the Lion bootpack for E6400/E6500, which may account for the GraphicsEnabler=Yes that I'm not needing. I believe Mariusz edited his DSDT.aml to eliminate the need for that.

Link to comment
Share on other sites

Ok, I'm confused. When I removed the NVD kexts, you guys said there was three of them to remove. I had to remove four.

 

NVDAGF100Hal.kext

NVDAGAK100Hal.kext

NVDANV50Hal.kext

...and NVDAResman.kext

 

At the moment, I have the three kexts I just got from Patel4Prez. What should I restore?

Link to comment
Share on other sites

×
×
  • Create New...