Hervé

You're confusing your Ivy Bridge E6330 model with its Sandy Bridge older brothers... Dell Latitude E6xx0 family models are as follows: Latitude E6x10 = 1st gen Core (Arrandale) laptops Latitude E6x20 = 2nd gen Core (Sandy Bridge) laptops Latitude E6x30 = 3rd gen Core (Ivy Bridge) laptops Latitude E6x40 = 4th gen Core (Haswell) laptops Each of those "i" Core CPU families integrate their own GPU: Arrandale = 1st gen Intel HD graphics Sandy Bridge = HD 3000 graphics (+ HD 2000) Ivy Bridge = HD 4000 graphics (+ HD 2500) Haswell = HD 4200/4400/4600/etc. graphics In your particular case, it appears you've confused the drivers used for Sandy Bridge HD3000 and those for Ivy Bridge HD4000. In the OS X world: AppleIntelSNBFB.kext = framebuffer for SaNdy Bridge HD3000 graphics AppleIntelFramebufferCapri = framebuffer for Ivy Bridge HD4000 graphics The E6330 being Ivy Bridge, the SNB/HD3000 framebuffer does not apply and, evidently, won't load. It's the Capri framebuffer that applies to your laptop. As such, patching the SNB framebuffer was useless. Regretfully, HD4000 VGA output is not supported under OS X since ML 10.8.2... You can only patch the Capri framebuffer for HDMI, DP and DVI output. You can refer to the dedicated HD4000 output thread JakeLo linked to (https://osxlatitude.com/index.php?/topic/2945-guide-for-enabling-vga-and-hdmi-in-intel-hd4000-gpu/). If you do not have any HDMI-capable display, I would suggest you invest in a mini-HDMI to VGA or mini-HDMI to DVI adapter to hook your external screen:

No need of a patched kernel on IvyBridge platforms; you only need the AICPUPM patch. If you use Clover, no particular reason why your E6530 would hang post-update. If you use Enoch, things are a little different since you need to re-patch the vanilla AICPUPM kext installed by the upgrade. Provided you kept NullCPUPM kext in /E/E and run a recent version of Enoch such as r2848, you should be able to boot with option & flag: -f KernelBooter_kexts=Yes. Add -v flag to boot in verbose mode and see where the laptop hangs.

I would suggest you install Sierra using a vanilla method, not a distro. We have guides in the EDP->Guides for supported models section.

Best possible cards, imo, are Apple's own Broadcom BCM4360 such as the BCM4360CD with mini-PICe adapter. If you need guidance on hardware elements replacement, download the owner's manual off Dell's web site!

A compatible card maybe? We cannot guess what's fitted to your computer so you'll have to tell us (as always...). We'll assume that: wireless is enabled in BIOS wireless on/off side switch is in ON position If necessary: https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/

What are the laptop specs? If it's dual GPU, you should be able to disable the discrete GPU (dGPU) through a SSDT patch. This assumes your integrated GPU (iGPU) is supported by OS X of course... You'll have to extract your raw ACPI BIOS tables and post them. With Clover, you can do that by pressing F4 at Clover main menu. All extracted tables will then be saved to Clover/ACPI/origin folder of your EFI partition or EFI main folder, depending on your Clover installation.

Seems like you're suffering from the well-known post-10.11.4 VoodooPS2Controller-related KP. Use one of Dr Hurt's revised versions.

Do as stated by JakeLo and manually set your board-id to same value as found in the SMBIOS posted in the bootpack. Or reuse his exact same SMBIOS but generate new serial number using the random buttons.

Build 16E195. Ok on my C2D D630, Sandy Bridge E6220, Ivy Bridge E6230 and Haswell E6440. Consider it safe to apply on all Hacks.

You should not need to add "Kernel=/System/Library/Kernels/kernel". That's the default path + kernel file and your syntax may be incorrect. Did you try any of the Lilu disabling or beta options to compare behaviour ? If you read the page Broxteck linked you to, it says:

installer is clearly complaining about file system format or partitioning size. Try and perform a low-level format from a Windows machine (you can use HDD Low Level Format tool from hddguru.com to that effect - a quick low-level format will suffice), then redo the SSD partitioning (GPT/GUID scheme) + partition formatting (OS X Extended (journaled)) from Disk Utility prior to actual OS installation.

These port replicators work Ok with all E6x20, E6x30 or E6x40 I've tested them with. You simply need to patch your Capri framebuffer kext as detailed in the dedicated Capri thread or in the thread Bronxteck linked above.

You can install Sierra on this workstation but the nVidia Quadro FX 1700 is probably not supported. It's very likely that you'll have to change it by a supported graphics card.

Then you have another copy, possibly in /L/E...

In Bluetooth settings, you normally see what is being broadcasted/advertised by the BT devices near you. You screenshot seems to show a BT Speaker of some sort which is using that name to advertise itself. It's not a result of anything on your Hack with the DW1380 (assuming what you've posted is a screenshot from your Hack running the DW1380 of course!) and if this info can be changed, that'll be only on the speaker itself. In OS X, this advertising info can be set in Sharing PrefPane->Bluetooth sharing section.

If you appear to lose audio on wake, whether speaker or headphones, put the laptop to sleep again and wake it. Audio should be fully functional again. From memory, VoodooHDA will work fine, just not support HDMI audio.

Re: ALC292, check my E6440 Sierra guide for dummy ALC kext & AppleHDA patching instructions.

Sleep & wake work perfectly as long as you disable hibernation and run native CPU SpeedStep. You will always run kernel 12.0 from DP1 in 32bit mode on a system with MLPF, there's no way around this...

Configure your TrackPad through the PrefPane.

sudo find / -name .kext -print 2>/dev/null

What exactly do you do when you "try to fix the ALC292 audio" ? ALC292 requires: 1) installation of dummy ALC292 kext in /L/E 2) patching of AppleHDA (2 x patches) in /S/L/E 3) cache rebuilding

You have the dual GPU model so I think HDMI is only supported through the nVidia GPU. You appear to run on the HD4000 iGPU. Bear in mind that Optimus technology is not supported on Hackintosh (because Apple use their own proprietary chip for dual GPU). On HD4000-only models, HDMI display output works OOB (but HDMI audio needs Capri framebuffer patching). If you can run on the nVidia GPU only, HDMI display output may work too. You can maybe run only on nVidia GPU if you enable Optimus in BIOS but then you might lose built-in LCD...

Why don't you try to boot your USB installer without cache?

Why did you opt for MacMini5,1 SMBIOS which is a Sandy Bridge platform (Core i5-2xxxM with HD3000 graphics) when you have a C2D platform with nVidia GeForce G210? I'd say that iMac10,1 SMBIOS would be much better (Core2Duo E7x00 with nVidia graphics). Give that a try. Could you post a zipped copy of your Clover EFI folder?

Having swapped motherboards, you effectively have a D430 that happens to be in a D420 casing... Since it's a tad misleading and only likely to cause confusion, claiming or stating to run MLPF'ed ML 10.8.5 on a D420 is best avoided; as such, the title of your thread was renamed and I would invite you to do the same for your video title. Indeed, it's because of the EDP gradual decay (lack of developers and interest oblige) that I started to post full packs that do not rely on the tool. It would seem the VoodooHDA kext you're using that's not fat binary (i.e. 32+64bit compiled) but 64bit-only. The version included in the pack I posted is v2.8.1 and that's fat binary. You can easily check the architecture of your kext with lipo Terminal command. For instance: lipo -info /Extra/Extensions/VoodooHDA.kext/Contents/MacOS/VoodooHDA If it's fat-binary, the command will return something like: Architectures in the fat file: <file name> are: x86_64 i386 If it's 64bit-only, the command will return something like: Non-fat file: <file name> is architecture: x86_64 ` As a test, I've just rebuilt my D430 ML cache and do not have those VoodooHDA-related error messages. Use the version included in the pack... NB: I don't know if it's just the poor quality of the video but you don't appear to run ML with graphics acceleration on that D430. Make sure you (re)configure 32bit kernel mode in the Chameleon o.c.B.plist. I'm not going to bother updating any of those old MLPF threads but the best way to run ML on those platforms with natively-unsupported GPUs is to start with a vanilla 64bit installation (w/o graphics acceleration of course), followed by all ML updates, including the security ones. Once all updates have been installed, proceed with MLPF conversion in order to run the systems in 32bit kernel mode with graphics acceleration.