Hervé

What was the issue? And with which version of VoodooHDA?

If you used myHack3.2, there's an issue booting in 32bit mode. You can either make a new installer with myHack3.1.2 or try and boot the existing one with option: arch=x86_64. After installation is done, you'd have to do the same thing until you update to Chameleon v2248 or later. Please read Announcements&News + EDP Bugs section, the issue is well detailed there. It's obviously not visible enough since people keep asking this same thing on and on...

Is Kext Wizard actually compatible with Lion and ML in the way it actually handles cache? I've never used it since switching to myHack to avoid conflicts like Mario said.

Try to delete the cache and manually re-create it.

Apple changed IOBluetoothFamily kext in 10.8.5 again (made it very much like in Mavericks) so you'll probably need to patch the kext to recover Bluetooth. They've basically added a new PlugIn (whose name eludes me right now) that seems to overwrite individual manufacturer's kexts (eg: CSR) and that appears to kill off most Bluetooth adapters. However, if you patch the appropriate PlugIn kext with your hardware PCI ids, you should get BT services again. I helped Leon that way after he updated one of his laptops to ML 10.8.5 last week. For audio, try to switch to VoodooHDA if you have not already done so. Again, audio loss or trouble is being repeatedly reported by Hackintosh users after updating to 10.8.5.

I'm quite surprised you mention Extensions.mkext as that was last seen on Leopard or Snow Leopard as far as I know. Unless I'm massively mistaken, that is no longer used in Lion or ML. Your cache can be found in /System/Library/Cache/com.apple.kext.caches/Startup. You would normally see files of the following sort: pc20:Startup admin$ ls -l total 21464 -rw-r--r-- 1 root wheel 81911 Sep 19 22:46 IOKitPersonalities_i386.ioplist.gz -rw-r--r-- 1 root wheel 41 Sep 19 22:46 KextPropertyValues_OSBundleHelper_i386.plist.gz -rw-r--r-- 1 root wheel 10902476 Sep 19 22:46 kernel cache You can manually rebuild your cache with the kextcache CLI command. For instance: sudo touch /System/Libraries/Extensions sudo kextcache -system-prelinked-kernel

Hi, there's a couple of things you can check: 1) status of -f flag in the Chameleon boot plist; it should be off. 2) presence/absence of any rogue manual boot option at Chameleon bootstrap; press a key at Chameleon delay bar to check if any cache related option or boot flag has remained after the ?: prompt or not. If you find something, delete it, boot your system and once you're back into OS X, remove the NVRAM plist file that is in /Extra. Then reboot and evaluate how it goes...

No such BIOS option on those D620/D820 models, no. For the rest, look up EDP pages for compatibility table and bootpack, you'll have your answer... You could also browse the forum section dedicated to D8xx models.

With ML, ANV-Slice PS2 kexts are kind of a must... So, opt for that in EDP System Build if it's not the default setting.

After a surge of articles last Spring, September is looking busy again on the article front with very practical stuff published so far this month. There will be more to come of course... Keep tuned to the web site too.

And in case someone asks, to make it very simple... 802.11b (2.4GHz) -> 11Mbps 802.11a (5GHz) -> 54Mbps 802.11g (2.4GHz) -> 54Mbps 802.11n (2.4GHz or 5GHz) -> 150/300/450Mbps 802.11ac (5GHz) -> 500/1000+Mbps

I suggest you do the following: 1) in Win, check which partition is active using DISKPART tool (available from Command line) 2) make sure the Lion partition is active 3) once rebooted in Lion (by whatever method), re-install Chameleon. My wife's D620 nVidia is actually running on a 320Gb SATA HDD with Win7/Lion 10.7.5 on MBR partitions in that particular order (i.e Win7 1st, Lion 2nd - I installed Lion afterwards, having reduced the original Win7 partition through Windows disk management tool). I'll check out the arrangements through DISKPART tonight. For Chameleon, I'm running v2251 if memory serves me right. Installation was made with myHack 3.1.2 quite some time ago.

All MLPF guides have now been updated in that respect (KP on AppleEFIRunTime/EFINVRam when booting installations made with myHack 3.2 in 32bit mode). Hopefully that will close the matter.

What concept would that be? I mean, what's the purpose? I don't understand what you're trying to achieve here.

Ha! That is kind of obsolete, we should probably archive that guide by now. Just follow the process documented in EDP pages at top of screen and use the booptack provided for the D630 nVidia. That will get you through without a problem.

Did you do your install with myHack as per our recommended process?

Try to boot with -f boot flag and UseKernelCache=No option; if you do boot ML, re-run myFix (full) to repair permissions and rebuild cache.

You appear to have a cache issue. What kind of D630 is this? Intel or nVidia graphics?

Redownload and retry. Use our installation process documented in EDP pages.

Try with myHack v3.1.2 because I'm pretty sure myHack v3.2 does not support MBR partitions.

Guys, please, it's all over the place: install Chameleon v2248 or above to fix that issue. https://osxlatitude.com/index.php?/topic/2870-read-up-boot-issue-kp-with-sl-l-mlpf-sl-installation-issue-with-myhack-32-beta8/?p=21885

It's more a matter of kext needing patching, at least we know it's a certainty for Bluetooth. Apple changed the way they handle BT again in 10.8.5. It's very close to what they do in Mavericks.

You may get some form of load-balancing, but that's probably of little value for a home usage that would be primarily Internet oriented. You could try multiple IP traces to Internet addresses to verify.

That sounds Ok from a procedure point of view. What KP do you get? What does it say? Can you post a picture of it?

Not much to fear, EDP always makes a backup of the previous /Extra folder so that you can recover if need be.