Darvinko

Hold on - I'll send a link for an IO80211Family.kext. Drop it into Extra via kext wizard, then run a my fix full and viola! upon reboot.

Poldas, If you're still considering Mountain Lion on your E6500, join us on the Mountain Lion Anyone thread. We'd enjoy having someone else to compare notes with.

Yes, drop into S/L/E on your boot stick and run my fix (full) before booting with it.

I have been diverted recently, but it appears most things are working well. I haven't tried sleep yet, I've had to re-install a couple of times and want to avoid that if possible, so I want to do it when there are minmal distractions. I'm going to attempt iLife and iWork also to see if they cause any issues. If I can help you with anything, let me know.

Tengokuu, Did you resolve your Black Screen issue? I have resolved the Wi-Fi issue by dropping a IO80211Family.kext into Extra and running a full My Fix. Upon reboot you will see the familiar WiFi icon in the menu bar. You will need to go into network and reset it, but it's back working!

My previous attempts to install Truesuite have been met with the message that the software can't find the reader, thus it won't work. After we get ML up and running properly, I want to see if I can make it recognizable.

Tengokuu, After giving it some thought, I believe the WiFi problem is related to the bootloader Chameleon. Different versions have their own quirks. Patel4Prez used the M4300 bootpack with it's bootloader, exchanging only Mariusz' DSDT.aml to eliminate needing to add the GraphicsEnabler=Yes boot flag. You used the Lion version of the E6400/E6500 bootpack, which I later reverted to after seeing your success with it. Shortly after that, my WiFi broke and you had reported the same issue. Different versions of Chameleon play differently with kexts and bundles. I will try to re-create my bootstick, see what we get and maybe we can assemble a working ML bootpack for this model.

I'm having a problem restoring WiFi - what are you using?

Maybe Patel4Prez can, I'm on a mobile device. Or you should be able to extract them from the boot stick.

This is what you should have in S/L/E: Edited versions of: GeForce.kext NVDANV50hal.kext NVDAResman.kext Unedited versions of: NVDAGF100hal.kext NVDAGK100hal.kext

I think it will eliminate your need for the boot flag.

You are replacing the GeForce.kext and the other two. When I edited the two 100hal kexts, they didn't appear to have a beneficial effect. You can edit them, use kext wizard with the option to back up replaced kexts to a folder on your desktop and you can revert if you want to.

Restore both 100hals.

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.

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.

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.

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

I don't have an SSD, I was getting that same message. It was (when I had Wi-Fi), followed by another message showing the handshake for Airport, and I would have Wi-Fi, so I'm not sure if that's the problem. On the same hand, I didn't think the NVDAResman.kext was involved in the installation hang. I know Apple has made some moves in the past that have affected kexts and the bundles that utilize them, but that is an area beyond my abilities (at least for now - I hope to learn more from this). Unfortunately, my mother passed early this morning, and I will be away and busy for a little while. Hopefully, much headway will be made in the coming days.

Thanks for the heads up Syonagar, we appreciate it.

I'm not sure, my Wi-Fi broke also, but I have Ethernet. I tried putting the NVidia device id into the kext NVDANV100hal.kext and deleted the NVDANV50hal.kext and NVDSMU.kext, ran my fix, no good. I have done the same on the bootstick and I'm re-installing it now, I'll let you know if there's any difference. As far as Wi-Fi, I'm not sure what went awry, it recognized my rebranded card initially, but I lost it yesterday. Works fine in Lion.

ProjectOSx.com offers this definition of the NVDAResman.com.kext - One of three very important original Apple kexts required by OSx86 machines for nvidia graphics functionality. This kext is responsible for providing resolution changing capabilities with nvidia graphics cards. It names the GEforce.kext and NADANV50hal.kext among the three. That's not to say they haven't tampered with code. In Lion, they assumed control of a graphics issue by in essence overwriting the manufacturers control, causing a shutdown if the value exceeded a certain threshold. It is reasonable to assume that something is affecting graphics, but it may not be the kexts themselves.

Patel4Prez - 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.

Adding the device id into the info.plist of NVDANV50Hal.kext (Nvidia graphics) didn't have any effect on the graphics. In addition to repairing permissions, we can go into security, unlock, allow downloads from any source and install kext wizard, which will allow for cache & mkext rebuilding. I have reverted back to Mariusz 0EDP (LION) pack (removing the arch i386 string) and have the same results as Patel4Prez, getting to DSMOS has arrived and the Bluetooth complete line. It appears there may be an issue with the modified IOPCIFamily.kext loading. I will look into dependencies today to see if that impacts something else.

Yeah, to play it safe, I shut off anything wireless, shut down the performance components. I'm thinking it's graphics related - the card may not be supported. I'm going to try adding the device id to the info.plist of the appropriate Nvidia.kext(s), run it through a my fix, re-install and see what happens.

Unfortunately, I have not made any progress, nor Have I heard of any from members Tengokuu, dafob and Patel4Prez, whom have been contributing to getting ML up and running on the E6400/E6500 series. Anybody who might have suggestions or advice is welcome to offer and one of us will test ideas or theories. I have updated the installation guide to reflect the input of these forum members.