v3ct0r

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 :$

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

 

Edited Nvidia Kexts.zip

 

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

When booting 'normally' I can get the audio/mic to work using VoodooHDA, but specifically with the version I have posted below, I can get more out of it.

 

I am not sure which version it is (I forgot; I used it in Lion though) but it gives you some level of volume control (the sound completely turns off after about 6 'squares' in the volume control popup to the left of the maximum volume 'square') and a working microphone, whereas the one that came with the ML4300 pack remained at the same volume, whether turned all the way down or up.

 

VoodooHDA.kext.zip

 

Place in System/Library/Extensions (Note: you may have to replace the one currently there if you used Darvinko's install method) and repair permissions using anything you'd like (Disk Utility, MyHack, etc.)

I can confirm that the NVDAResman.kext is the culprit of us having to use the -x boot flag and the [iOBluetoothHCIController][start] -- completed error.

Perez4Prez - try reinstalling the NVidia kexts back in, one at a time, trying to reboot without the -x flag after each to see if we can isolate the kext causing the boot to hang. There are three that end in hal, try those first as I don't think it is the NVDAResman.kext.

 

Will do; I am not with my laptop right now but I will try this as soon as I am.

Hello again!

 

I come bringing good news! I managed to boot WITHOUT SAFE MODE and fix the [iOBluetoothHCIController][start] -- completed error!

 

All I did was delete the NVD*.kexts/move them to a different location (ex. the desktop in a folder called NVDIA Kexts Backup, etc.).

 

Then I rebooted in verbose mode to see what (if any) errors showed up and it took me to the login screen and I was able to login!

 

Now that those kexts are gone, however, there are sure to be new problems, one of which I found where if you don't touch the computer for a few minutes, and it goes/tries to go to the screensaver, the entire screen goes white and there is a grey rectangle where your cursor should be.

 

One step down a few to go (I hope)!

I have tried booting up with the wireless switch off and it has no effect on where the boot hangs...

 

@tengokuu I can confirm that the voodoobattery.kext in extra\extensions and repairing disk permissions works.

 

Also, to repair permissions, install other kexts, etc., multifail from tonycrapx86 makes things a lot easier

Hey guys,

 

First I'd like to give Darvinko a huge thank you; I've been trying to get ML to work since DP3 and couldn't. His method worked the first try!

 

Now, getting the rest of the system to work:

 

I have installed multifail 4.6.1 from tonycrapx86.com/downloads (have to register)

I replaced the AppleACPIPlatform.kext from 10.6.7 and Netkas's IOPCIFamily.kext (basically the same ones Darvinko was talking about)

I cleaned up the org.chameleon.boot.plist by removing everything except EthernetBuiltIn=yes, Kernel=mach_kernel, and (for my convenience) Timeout=n

 

After all that, I rebooted, but this time normally, in verbose mode (-v only; no -x)

 

It hangs at the following:

[iOBluetoothHCIController][start] -- completed

 

The line right before the one above is:

DSMOS has arrived

 

Once again, thank you Darvinko and everyone else who is involved in getting ML on the E6XXX

 

 

P.S.

I have an E6400 with a Core 2 Duo (2.8 GHz) and NVIDIA Quadro NVS 160M Graphics. I also have a 30GB SSD and 4GB of ram, if it helps. Previously, this machine ran Snow Leopard and Lion.