Hervé

Disable the on-board BT in BIOS.

VENdor id & DEVice id: official identifiers of computer hardware... Will be listed under SysProfiler->Bluetooth section and/or SysProfiler->USB section. Example:

Here, you'll find an up-to-date list of the most compatible laptops that run macOS perfectly. As Jake answered in post #2, "we don't have a section" for your initial query. The closest thing we have to that is the list of compatible systems available off the EDP (Beta) menu at the top of your screen. Answers to your latest questions about instructions, bootpacks and so on are already available in the forum Guides section. And those evolve day by day, week by week, month by month. You could use that section to make a list of Hackintosheable laptops and assess level of compatibility. Most of the guides clearly state what works and what does not. I know... chores and homework...

You should consider that guide obsolete, that's why it's in the archived section. If you're using Clover, you're probably injecting kexts, in which case make sure you've copied the same kexts on your HDD (and it's Clover EFI partition if applicable) as found on your USB key. There are better guides these days: https://osxlatitude.com/index.php?/topic/7478-dell-latitude-e6xxxe7xxx-yosemite-install-guide/ https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-clover-guide/ this one is for the E6220 but the genral principles remain (just adapt the bootpack to E6240 DSDT and screen res if applicable) )https://osxlatitude.com/index.php?/topic/7914-dell-latitude-e6220-with-i5-2520m-hd3000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/

There are many threads about dual booting in the related multiple boot/bootloader sections. Have a browse through. Obviously, no need for a Win partition to install OS X/macOS or create their associated partition(s). Let's close this thread.

If we could stick to the topic "ssd m..2 not showing" in this thread...

That'll depend on what you're trying to do...

Chameleon/Enoch boot options & flags can be listed through the historical "?" command if you enter it at the bootlaoder prompt. Boot option Wait=Yes will stop the boot processbefore loading the kernel. You will see a summary listing tables that loaded. By default, Chameleon/Enoch loads SSDT.aml (or ssdt.aml) from /Extra folder if present. It's just the same as for the DSDT. Pike R Alpha's ssdt generartor script creates a file carrying that file name, so it can be used "as is". If you use a different file name, you'll have to manually specify that at the bootprompt or in the o.c.B.plist. In other words, it's the same old way it's always been for the last 8 or 9 years, if not more. Google is your friend, you can use it to learn about Chameleon flags and options... http://chameleon.osx86.hu/

Seems issues are linked to: 1) EFI BIOS settings (point to USB key + internal SSD whilst OP boots off a USB HDD) 2) NVRAM plist files placed in EFI folder The NVRAM file seems to be the main cause as it clearly overwrote SMC keys + SMBIOS parameters defined in the Clover config file.

Once again... Read the FAQ section. https://osxlatitude.com/index.php?/forum/161-faqs-tutorials/

FakePCIID_Intel_HD_Graphics.kext useless without Fake_PCIID.kext... Just like VoodooHDA without AppleHDADisabler.

You can build a USB installer on a key formatted with an MBR partition scheme, yes.

https://sourceforge.net/projects/hwsensors/files/

There must be some rogue trace of an older VoodooPS2Controller v1.8.21 somewhere. Remove DrHurt's VoodooPS2controller v4.0.0 from Clover EFI folder and put it in /L/E. Then repair permissions and rebuild your cache. I'm not aware of anything the sort but you wouldn't have anything linked to an older VoodooPS2Controller in your PrefPanes, would you? If you can't get rid of the KP, all I can suggest is a fresh re-installation...

So you're still getting KPs on VoodooPS2Controller? Give the attached version a try (uploaded from my E6230 on which it works perfectly). It's Dr Hurt's R4. VoodooPS2Controller.kext.zip

You've kept KernelBooter_kexts set to Yes, consequently you can only boot without cache (i.e; with -f flag) and with add-on kexts in /E/E. Copy (not move) your add-on kexts to /L/E, repair permissions, rebuild your cache, set KernelBooter_kexts to No and you'll be able to boot normally. You're using MBP7,1 SMBIOS which is Ok but it seems you simply copied the plist from some place and did not update it to remove/replace the CPU and RAM speeds manually set there. Remove these or adjust according to your M6400.

The USB device renaming applies to USB2.0 ports. In case you ignored this, please note that: UHCI refers to USB1.x controllers EHCI refers to USB2.0 controllers XHCI refers to USB3.0 controllers https://en.wikipedia.org/wiki/Host_controller_interface_(USB,_Firewire)

Afaik, there is no ready-made bootpack here for this machine, so do as usual: list your hardware specs and look for eventual support & drivers. You have a 2nd gen Sandy Bridge system so you'll have to apply the AppleIntelCPUManagement kext patch to avoid KP. Graphics will depend on HD3000 iGPU or discrete GPU. If HD3000 iGPU, graphics acceleration will be obtained by simple injection of the SNB laptop layout. These are the 2 x priority items. For the rest (audio, LAN, wifi, etc), we'll see as you post your specs.

Difficult to say with so little info. Try it.

55C to 60C-ish is perfectly normal if CPU runs at Turbo boost speeds. Expect it to idle around/just under 50C. Don't expect 45C or even lower...

OP should go for latest Sierra version, regardless...

You need to activate AICPUPM aka AsusAICPUPM aka AppleIntelCPUPowerManagement patch on Sandy Bridge and Ivy Bridge platforms. User Clover Configurator app to tune your Clover config.

https://osxlatitude.com/index.php?/topic/9961-how-do-i-repair-permissions-and-rebuild-the-cache-yosemite-and-later/

Or it could simply be a duff physical connection at one cable end...