Hervé

Ok, so your BT module is not detected and recognised by the OS then. Device labelled 5880 is not the Bluetooth module (its a built-in Broadcom Secure Applications Processor chip for optional fingerprint scanners). Ever tried to remove, even temporarily, the HPET kext to compare behaviour with/without it?

When I mentioned SysProfiler, I was more after something along the following lines but never mind:

BT devices are usually reported as USB hardware, so never listed in DPCIManager or lspci output... Check your SysProfiler.

Ok, there are several potential shutdown fixes to try. Let's try the 1st one: DSDT01.aml.zip Place the file in /Extra and reboot with Chameleon option DSDT=/Extra/DSDT01.aml. Let us know how it goes.

The Yosemite Bluetooth kexts needing patching with the PCI ids of your card maybe?

You can grab the AppleACPIPlatform kext v1.3.5 or v1.3.6 from most bootpacks provided in the EDP->Compatibility/Bootpacks pages. Place it in /E/E (aka /Extra/Extensions), then run myHack->myFix (quick). AppleACPIPlatform v1.3.5 and v1.3.6 come respectively from SL 10.6.7/10.6.8 and are generally mandatory for all Lion and Mountain Lion installations. Not required for Mavericks and Yosemite, the vanilla kexts do perfectly.

Correct, Chameleon Wizard does not provide profiles for all Mac models. However, you can easily create your own target profiles with a tool called Champlist. It provides you with a full list of Mac models and you can create and save the corresponding SMBIOS plist to use on your own Hack. Before you do that, stick to MBP8,1 and generate the SSDT for your i3 CPU in order to gain Turbo boost (if the CPU has it or course) and better speedstepping. Place the SSDT file in /Extra, then make sure that your Chameleon boot plist has "DropSSDT" option selected but "Generate P-States" + "Generate C-States" options unselected. http://www.hackintoshosx.com/topic/21475-guide-aio-guides-for-hackintosh/?do=findComment&comment=106897 If it's not already been done (but I expect it's included in Jake's packs), you probably need to patch the Apple CPU Power Management kext. I also suggest you grab the tuned-up FakeSMC kext from my E6320 Mavericks guide. Edit: bad luck, no Turbo boost on the i3-2330M, so it'll be 2.2GHz max for you.

As you might have gathered by now, Optimus technology is not supported on Hackintosh platforms; that's because Apple use a different technology on their own Macs and that's based on a dedicated little piece of hardware (vmux chip). Generally speaking, you cannot disable the integrated graphics chip of a Sandy/Ivy/Haswell/etc.-based laptop as the discrete GPU outputs video through it. It's a kind of rare thing to have a laptop with each GPU having its own private bus to the video output. That's the Apple hardware way whereas Optimus is a software solution. As such, you can only try and disable the nVidia chip through DSDT patching in order to rely solely on the integrated Intel HD 4400. The alternative is to delete the nVidia kexts so that they do not load. You'll have less powerful graphics support (though perfectly acceptable IMO) and increased battery life. You can look up for nVidia-disabling DSDT patches on the Net.

The thing with i8k is that you cannot automate its startup so you may want to forget about it. I do. If you cannot boot without -f flag, i.e. you need to boot without cache, your cache is obviously screwed and may not build because of the kext. On sure way to find out is to manually rebuild you cache and keep an eye on any possible error message indicating that cache cannot be build. In Terminal: sudo touch /System/Library/Extensions sudo kextcache -system-prelinked-kernel This being said, EDP was kind of screwing up all Latitude D series these last few months so you may want to skip it. I've posted a full Mavericks /Extra some time ago for the D630n. I can't remember in which thread exactly but look it up. Install it with myHack and no further need of EDP.

Not that many 2nd generation 2.2GHz Core i3; I'd say it's one of those 3. @okaenrique: Apple have not made many Mac models with Core i3 CPU, let alone 2nd gen SandyBridge ones. Maybe a couple of iMacs. As such, you should try various SandyBridge SMBIOS profiles before you find the one that works the best for you. Target MacBookAir4,1/4,2 or MacBookPro8,1, i.e. a model using integrated Intel HD 3000 GPU only.

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.