Hervé

P & C States are for CPU power management, so won't be of any help in relation to a shutdown issue. This is more a DSDT problem. There are existing DSDT patches on offer for fixing such issue. I would suggest you extract your raw DSDT or make a backup of your existing one if applicable and use the tool called DSDTEditor to apply these shutdown patches to the raw/existing DSDT. You may try them one by one to verify the likely results. Start from your initial DSDT everytime and save the patched version to say DSDT01.aml, DSDT02.aml, etc. With Chameleon, you can place these DSDT files in /Extra and manually call them at boot time through option DSDT=/Extra/. This method is totally safe as you simply reboot as normal if the system hangs or go crazy with the patched DSDT. If you feel uncomfortable or unable to do this yourself, post your zipped raw/existing DSDT and we'll patch it for you.

It's up to you...

Do you have the kext AppleACPIPlatform v1.3.5 or v1.3.6 in /E/E? It's required for ML.

You can update directly through the AppStore or via the Combo update. It's a straight update with nothing further to do afterwards.

I've identified the SSDT-related problem and it appears the culprit that messes up behaviour of Fn-F1 (causing the key combination to shutdown the laptop rather than put it to sleep) is the following _DSM method at the very end of the \_PR.CPU0 scope: Method (_DSM, 4, NotSerialized) { Store ("Method CPU0._DSM Called", Debug) If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 // This appears to be the value causing trouble }) } Return (Package (0x02) { "plugin-type", One }) } I'd lie by pretending to know what this particular value equates to, but am investigating...

Ok, well it's not exactly what you indicated earlier. If you're following Jake's guide to the letter, you should have no problems at all.

Oh, you'll never get your installer to work that way; you need to read up a little and do that part properly. There are plenty of guides on the Net and on this site. I let you read about the differences between Mavericks and Yosemite too.

Mmm, I don't believe that's sufficient. I had to binmod the Azul framebuffer to change desktop id 0412 to mobile id 0416. You sure need to inject the layout-id, either through DSDT injection like you posted or through boot loader parameter. The device-id, on the other hand, is not necessary in the DSDT.

So you're not changing references of Desktop 0x80860412 to Mobile 0x80860416 In the Azul FrameBuffer?

I believe your Azul binary patch may be incorrect or meant for some specific systems. Personally, this is not how I binmodded my framebuffer when working on my mobile HD 4600-based Dell E6440. I presume you're looking at patching for Yosemite. You did not make that clear and that's pretty critical to avoid confusions and mistakes for/by other people.

To be very honest, Yosemite is not the easiest version of OS X to install, especially if you're an absolute beginner in Hackintoshing. I strongly suggest you fall back to Mavericks, it'll be a much easier version to install with myHack and the documented process you'll find in the EDP menu at the top of the OSXLatitude page.

Then no reason why HD300-based graphics would not work OOB like it does with Mavericks. I suggest you forget your previous installation method and rebuild your Yosemite USB installer manually, adding Chameleon (or Clover) afterwards. In fact, if I were you and if it really is Yosemite that you want, I would actually install Mavericks on a small partition, from which I would work out a larger Yosemite installation.

There are various suggestions made in existing M4600 threads in this very forum. Have a look and you may get some useful pointers. It'll help you learn a thing or two I'm sure.

Ha, time to bake the motherboard in the oven...

Sometimes, weird things happen. All of a sudden, DVD Player stopped working and returned the well known initialisation error: I installed the IOAHCISerialATAPI_injector kext and the DVD came back to life, though slightly differently and somehow improved this time. When looking at the Supported Features in the Help menu, HD is no longer reported Unsupported like it used to be: This applies to both Mavericks and Yosemite. I had been playing with DSDT/SSDT recently so the trouble may originates from that. 'need to see if I can suss out a way to get rid of that horrible little kext though. IOAHCISerialATAPI_Injector.kext.zip I'll add it to the next Yosemite boot pack.

Can you post your zipped /Extra folder? Did you configure the BIOS as per recommended settings? Run BIOS A17 if at all possible. Post the specs of your model so we know which one it is (Intel/nVidia GPU, screen res). A few recommendations: if you have an Intel wireless card, disable it in BIOS or remove it (it'll have to go anyway). disable Bluetooth initially too. when you run the USB installer, format your target HDD using GPT scheme and format your partition Mac OS X Extended (Journaled).

You may want to experiment with PciRoot + npci Chameleon options. Eg: PciRoot= npci=

Well, your SMBIOS + boot plists. The kexts you've added to /S/L/E, you know those files that you've used to build your system.

That's a very old FakeSMC kext you seem to be using there...

Means you probably don't have the same screen resolution as the one I had and you need a different DSDT. But you never specified what you have... The table from my guide can easily be updated. If you have a screen res like 1600x900, boot with Chameleon option EnableDualLink=Yes (if you use that bootloader of course).

D430 with Core2Duo CPU, right? No Intel wifi card? Try booting with flags -f -v in case the cache is screwed up.

I'm pretty sure that's my tuned pack but I've just noticed the Chameleon boot plist posted in the above pack did not contain the 32bit kernel option (arch=i386). Boot with that Chameleon manual option (enter it at boot loader prompt after you've pressed a key or F8 at sliding bar), then add it to the boot plist with Chameleon Wizard.

Just grab the patched/older Intel frame buffer kext from the boot pack, copy it to /E/E and run myFix (quick). This applies to all GMA950-based Latitude D Series. In EDP, it's called the Brightness Fix.

If there was a SSDT file in the E6220 pack, it may not suit your own CPU. This is a very CPU-specific item. Remove it. If you're still having issues, try installing the NullCPUPowerManagement kext. Read this guide for instance. Please follow common sense rule #1: post your specs or list them in your forum signature. PS: Please reduce your picture size in the future. There really is no point attaching a 5Mo 5248x3936 file in a post!

No NullCPUPowerManagement in /Extra/Extensions? P + C States generation selected in your Chameleon boot plist? SpeedStep enabled in BIOS? Tuned FakeSMC kext to match SMC keys of the MBP6,2? Ha, you're running 10.10.2... means no myHack installation... Please post the files you've used. Are you running Chameleon?