Darvinko

You cannot "add" it to an existing partition with Windows, you would have to create a separate partition on the drive to install OSx to. Unless you do this: http://www.macbreaker.com/2012/02/mac-os-x-on-mbr-partition.html. NOTE: This was for SL, not sure if it applies to Lion, ML

See if installing this kext helps (replace existing one - back up exiting one just in caseIO80211Family.kext.zip), I modified it to work with your adaptor.

It may be heavier than the MacBook Air, but performs nearly (or equally) as well, at about 20% - 25% of the cost, and there is the satisfaction of knowing you did it, and learned enough to do it again!

Put your USB stick back in the machine you created it on (the one with My Hack on it). Start up your machine and click on the my hack program (which should be in your application folder). After authenticating, choose to run "MY FIX" from the menu (the menu you use to choose to create the USB stick). When asked where to run my fix, choose the install stick (not / which is your hard drive). When asked if you want to run a Full or Quick MY FIX, choose full. This should make your USB Stick usable to install.

A quick note to anyone who may decide to do a dual boot with Windows. Update your windows partition to a point after the Service Pack(s) is/are installed prior to re-installing Chameleon bootloader on your OSx partition. The reason is that Windows Service Pack requires access to the bootloader, which it can't access if it is not an active partition, and the installation will fail. This will save you the time of having to make the Windows partition active again, going through the Download and Installation of the Service Pack again and re-installing Chameleon on your OSx partition again. All other updates will install without Windows needing to be active.

Try this: http://www.mediafire.com/?8zvpa722gqjdzdx

Patel4Prez, You bring up a very good point, which I didn't take into consideration when writing the guide or responding to members. Obviously, you want to be at the latest BIOS for your system and updating your BIOS has an impact on your DSDT.aml. All along, based on my thinking that, because of the almost identical specs, the E6400 and E6500 are pretty much the same. When you brought up the fact that you were at the lastest BIOS (A32), I remembered I was at A27. When I looked to find the lastest update for my E6500, I found out, Surprise, I was at the latest, A27. Because, of this, there are going to be some differences in the machines ability to utilize some of these kexts, something I didn't take into account when responding to questions about the E6400. Thank You.

I am not aware of a "true" sleep solution. For graphics, try going into launchpad, see if it enters smoothly, also try opening chess and see if you can make moves with the pieces. As for Chameleon, as the system runs, it will smooth out and should pick up as the install "settles" in.

Overheating has been noted by many, including true Mac users. It would appear to be an issue within Mountain Lion, something we anticipate Apple will address in an update.

It depends on your router. If you have an n speed router, both cards will work, but the 1397 is a g speed card, the 1510 is an n speed card (and works OOB), so you are better able to take advantage of the routers capability. Since routers are backward compatible, your 1397 will work, but at g speeds. You will need the IO80211Family.kext because other kexts have dependencies on it, namely the AppleAPCIPlatform.kext.

The only thing I can think of is trying to use the other two edited kexts as they likely have dependencies on each other. If not revert to the originals. I had a problem where a power adaptor I used (not sure where I got it from), had a bent pin (the center one where it goes into the laptop) and it was pressing against the side, not going where it should. On the laptop, it gave the indication that it was charging (actually wasn't) and caused KP's. Check contacts on docking station and connector on bottom of laptop for bent connections or foreign objects which might create a "grounding" affect.

Thanks for the help, had the opportunity to spend the day with a Grand-Niece. I can assume that the Bluetooth was working in windows prior to ML installation, so we can rule out card and connections? If so, try going into system preferences and see if the bluetooth card is being recognized, and if so check vendor and device id's to see if maybe Dell used some from another vendor.

Try adding -x boot flag to see if it will boot in safe mode, also trying using a different USB port when booting. I assume you have the hard drive set at AHCI and bluetooth shut off?

Try using the edited NVDAResman.kext from the Mountain Lion thread (Mountain Lion Anyone?). The first post contains kexts from ML that I edited to include support for the Nvidia Quadro NVS 160M. There are three kexts within the file, use the one, install with Kext Wizard and run My Fix (Full) from the My Hack utility.

I re-read the thread. When the other member had his black screen issue, it may have been because he placed his IOPCIFamily.kext in Extra/Extensions. Make sure you are placing it in System/Library/Extensions and then run a My Fix on the installer afterward. Use a full My Fix, not the Quick one. One other thing I didn't have in the guide (now added): Before installing, make sure your Hard Drive is in AHCI mode and shut down bluetooth as these impact your install. To put your hard drive in AHCI mode, you need to enter BIOS by tapping the f2 key repeatedly during startup. You will enter System Properties. Use the down arrow key to highlight the System Configuration section and hit enter. As it expands, use the down arrow to highlight SATA Operation and hit Enter. Using your cursor, click the AHCI button, click apply, then click exit. You will then boot normally. On the right side of the laptop, move the switch so the red is exposed. This shuts off wireless devices. Then continue with your install.

The processors (and graphics) are different (as you know), so there are some differences in the install. For example, the edited NVIDIA kexts support the Quadro 160M graphics card, I'm not sure if there is native support in ML for your graphics card or if they had to modify them. There is an excellent thread for the E6420/E6520 which I'm sure answers some (if not all) of these questions.

Also, try using with GraphicsEnabler=Yes -v -f. You indicated that would bring you so far before getting a KP. The verbose mode should tell you where it is KP'ing (what kext's might be causing the KP). Let us know so we can sort it out from there.

I'm not sure what is causing the Black Screen, one member had an issue with it and I believe a re-install worked for him. I, as well as others have used the M4300 bootpack successfully. It is the extra folder that you will use when you get toward the end of installation. Do you get far enough along in the installation to where you are asked if you want to use a generic extra or your own?

In the forums on this site, under E6XXX, there is a guide for Mountain Lion Installation, under Mountain Lion Anyone? We used the M4300 boot pack which worked well and the E6400/E6500 Lion bootpack which worked well for a member who removed the arch i386 Key and string from the org.chameleon.plist. The keys were the IOPCIFamily kext and editing the NVIDIA kexts to replace those currently installed in ML. Give it a shot, there are several members there who are able to provide assistance if needed.

I'm sorry, I've been away for a few days and just read your posts. When you created your installer, did you remember to 1. Click on backup replaced kexts when adding the IOPCIFamily.kext and 2. Run My fix (from the my hack utility) after installing, remembering to choose the installer as being where you are running the my fix on. Then aften installing the three Edited NVIDIA kexts, again choosing to back them up in Kext Wizard and running both Extra and S/L/E repair under the maintenance tab? Failure to run my fix (and making sure it is on the installer, not the hard drive) after IOPCIFamily.kext and running Maintenance after 3 Edited NVIDIA kexts (again, make sure it is on the installer) will cause issues with your installation. Also, make sure you are REPLACING the kexts, not adding additional kexts! Let us know how it works.

Not sure why, but EDP created issues with my install.

Sorry, I've had a few things to attend to. I have not had any issues with heat, nor with the trackpad. Conversely, I have not had the success with sleep that some of you have had, although I have not really tried to correct it other than going into terminal and adding Mariusz command to achieve sleep to RAM. I have not had the time to research the heating issues, but obviously you have taken the right steps. Occasionally, in bed, when the sheets or blankets impede air circulation, it will run hotter, but not to the point of shutting down (or even warning me), so best kept on a firm surface, if possible elevating the unit without blocking airflow. As always, let us know if you find a cause or solution. EDIT:It does appear to be an issue that might require a "fix" from Apple in the ML software.

Glad to hear it. Although you said E6410, which has different architecture, I'm visualizing E6400/E6500 and it doesn't need that fix.

I will be compiling (after I get all the fixes together) and re-editing my first post to post a comprehensive guide for installing ML on the E6400/E6500. I hope to have it done this evening. Thanks for your patience.