Hervé

T6670 is indeed Penryn family, so Ok for Sierra. I posted a detailed step-by-step Sierra guide in the Installation Guides section of the forum; I suggest you refer to it and follow it. Bootpack available in the guide and in the dedicated thread of this very D6xx support section. You will not be able to install Sierra using a MB4,1 SMBIOS. My guide is very explicit on this SMBIOS matter...

My E6230 works 100% under HighSierra. I run it under Enoch but installed and update through a Clover USB key. I will post my EFI folder in a couple of days if you want (currently on business travel). I've not experienced any of those issues you've listed but if you skip some parts of the guides, not everything will work, obviously... Do you have the same webcam as listed in my guide (same vendor + device id)?

Yup, that would be a most excellent choice.

Files are ok but you're mistaken: your computer is not fitted with an AR5B97 card but with another Atheros card built on AR9485 chip (id 168c:0032). That's where somehow bad news come because AR9485-based cards don't have great support under OS X/macOS. See note 4 in the wireless inventory thread. Chunnan's latest drivers are available in post #408 of his thread. He did stipulate that AR9485's Tx rate will be limited to 11Mbps. No mention of Rx rate but I guess you can try it out and report accordingly. Other people reported very poor wireless performance in the thread. If your own results are dissapointing, you really should consider replacing your card with another model with better support.

Ok, so you've found out that AR5B97 carries PCI ids 168c:002e. A search on that id or "pci168c" In IORegistryExplorer will probably not lead you to it because the search is usually conducted on the IOReg elements/Tree items, not info they contain. You have to browse down your IOReg tree and, if the card is enabled, you'll find it listed under a specific device. In the right part of the app, the id should be listed under several parameters called "compatible", "name" or "IOName". For instance, it could under a device called PXSX, itself under a device called RP0x. This is what you would then look for in DSDT for patching. As requested by Jake, post a zipped copy of your DSDT + zipped copy of your saved IORegistryExplorer output. Here's an example of what you ought to look for in IOReg: Alternatively, you can patch the Atheros kext, even if temporarily. In /S/L/E, look for IO802.11Family kext. Inside it, there's a PlugIns folder containing several wireless manufacturer's kexts. You'll be looking for Atheros40 kext and inside this kext, you'll need to modify the Info.plist file to insert your AR5B87 PCI ids as follows: <key>IONameMatch</key><array> <string>pci168c,30</string> <string>pci168c,2a</string> <string>pci168c,2e</string> <-- patch to insert AR5B97's id <string>pci106b,0086</string> <string>pci168c,1c</string> <string>pci168c,23</string> <string>pci168c,24</string> </array>

No, we don't do that here. You can read the various guides posted in our Guides section and learn how to create the USB installer. It's not that difficult.

Check the FAQ section and you'll find your answer... You don't need any add-on kext! Tell us if it works once you've done the needful because we're lacking test results in EC/Sie/HiSie for that model.

myHack development stopped at Mavericks several years ago. Since then, you build your USB installer using a manual process detailed in the many guides posted in the Guides section of the forum or through Apple's createinstallmedia command (you can google for it). Stay away from distros, you'll only have trouble. On paper, your laptop's specs are fully compatible with all recent versions of OS X/macOS. But you have dual GPU so support for the nVidia 610M will have to be confirmed (somehow, I have doubts) and 1st gen Intel HD may be fully or only partially supported. You'll have to refer to the Bible on 1st gen Intel HD graphics to verify where you stand. If nVidia dGPU is not supported and your cannot gain full graphics acceleration with the Intel HD iGPU, forget OS X/macOS on this laptop.

The "sudo ..." line is a Terminal command you type to create your USB installer. By "Cap", he meant the name of the formatted USB key used to create the installer. In your case, you need to replace "Cap" by the name you'll have given to your key. For instance, say you use a 16GB key formatted with the name "16GB_USB", your Terminal line command will be: sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/16GB_USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --no interaction The command assumes you have OS X El Capitan's downloaded installation package in the "Applications" folder, which is its default location on download. The command is basically split as follows: sudo -> invokes superuser rights /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia -> the program inside the downloaded package that creates an installation media --volume /Volumes/ -> the target installation media you want to use, by its formatted name --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app -> the location of the source installation package --no interaction -> as its name implies, no interaction with the user during media creation You can read all about this Apple installation media creation command here.

I'm sure you've noticed it was an archive with various versions throughout the years... So, download the latest version and copy the 2 x downloaded kexts to /S/L/E. Then repair permissions and rebuild your cache according to the instructions posted here. The alternative is to identify your audio codec and try to patch AppleHDA kext. Once you have VoodooHDA running, look at your system with DPCIManager app.

Indeed you can with Clover.

Consider SL obsolete these days, though you could start with that to experiment but you should really go for High Sierra. Plenty of installation guides flying around. Look them up in the guides section. Obviously, you'll have to tune the installation to match your own specific hardware components in terms of LAN, wireless, audio, card reader, etc. You can use your MacBook to build your HighSierra USB installer.

You could try 2 x things: in your Keyboard PrefPane, set your keyboard to " PC" type install Logitech layout for your language (if it exists) in /Library/Keyboard Layouts, then choose it in your Keyboard PrefPane. Logitech layouts are available in Ukulele app (v1.8.4 or v2.2.8) as explained here. I guess you may also try other available layouts in the apps, even in v3.2.7. http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele

According to Dell's support web site, it's an Alps TouchPad alright but I guess too recent of a model to be supported by the installed driver... http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=NVCF6&lwp=rt -> under "Applies to"

I can't.

I highly recommend this. Got one in all my E6xxx Hackintoshes, including the E6230. Works OOB, no hassle, no setup required. All Airdrop/HandOff/BT features supported as in a real Mac.

The IOGraphicsFamily patch for High Sierra differs from El Capitan and Sierra. It is: Find: 0100007522 Replace by: 010000EB22 If you use the wrong patch, you risk a KP... Why do you enable "Load VBIOS" in Clover config? What VRAM problems does this solve?

@themarkwik, with regards to graphics, the term is acceleration, not accreditation.

Sorry but Darwin kernel 15.3.0 is NOT Sierra's kernel, it's El Capitan's... Either the OP got it wrong in his stated OS X/macOS version or, somehow, he's trying to install Sierra with the kernel from El Capitan 10.11.3. And that ain't gonna work!

Apple changed the way USB ports are managed when El Capitan was introduced and controller devices need to be renamed and a USB injector used. Your DSDT shows 2 x USB2.0 controllers: EHC1 (@1A) and EHC0 (@1D). Most computers have these numbered EHC1 and EHC2. Clover's on-the-fly facility includes patches to rename EHC1/EHC2 to EH01/EH02, nothing for EHC0. Your IOReg clearly shows device EH01 operational with attached built-in USB devices (webcam + card reader) but, quite naturally, nothing under EHC0. What you need to do is either: patch your DSDT to rename EHC0 to EH01 and EHC1 to EH02 so that your system falls within the usual numbering (don't know if EH00 would work, never tried it). apply the Clover on-ht-fly patches, knowing that you'll have to adjust the patch for EHC0. I attach a pre-patched DSDT, no other APCI tables of yours contained references to EHCx devices. Place that DSDT in Clover's ACPI/patched folder. DSDT.aml.zip You Clover config shows a few mistakes that need to be fixed (use Clover Configurator app to that effect): ACPI section: remove the P States and C States generation. These are not applicable to your Sandy Bridge platform Kernel & Kext Patches section: you have the correct AICPUPM patch enabled. As such, you can remove the NullCPUPowerManagement kext I saw in your Clover kexts folder. You'll need to generate your CPU-specific power management SSDT with Pike R Alpha's well-known generator in order to enjoy proper CPU SPeedStep (no Turbo boost on your i3-2310M). Remove the KernelPm (for Haswell and later) + DellSMBIOSPatch patches. In Graphics section: you're not injecting anything. Are you currently enjoying full graphics acceleration OOB with your nVidia GPU? If not, your might have to inject nVidia. This dGPU model certainly is supported under OS X/macOS.

Westmere CPUs are same generation as 1st gen Core "i" CPUs. As such, they don't require any AICPUPM patching so re-instate the vanilla kext. Just activate P States + C States generation in Clover. You might need VoodooTSCSync but I would not think so. This is a HP computer so you may also need to activate Kernel Lapic patch although that usually applies to HP laptops.

If you use Enoch, you have to manually add the kernel to /S/L/Kernels. Copies of Sierra kernels are available in the OS X/macOS section of the forum. You can refer to my Dell E6xxx or D630 Enoch guides for guidance on Enoch-based installation. There will be a few thing to do to be able to boot Sierra 10.12 with Enoch. All is explained in details in the guides. It should be a lot easier than with Clover which requires its own driving licence most of the time. But before anything else, please post your systems specs with full exact model of hardware: CPU, audio, LAN, LAN, wifi, etc. Also post a zipped copy of the Extra folder you used.

All sorted with the following adjustments: Clover Configurator tool + Clover updated to latest versions since some changes to the config.plist (eg: SSDT drops) were not kept on reload. Ok afterwards. Kext cache + Prelinked kernel would not rebuild due to the replacement of IOBluetoothFamily kext by a 2013 patched version that proved totally incompatible. The vanilla kext was restored and kextcache command then executed successfully without errors. All add-on kexts migrated from /S/L/E to /L/E and tagged in green for easy identification. Replaced patched AICPUPM of unknown origin in /S/L/E by vanilla kext since the Clover config applied the AICPUPM on the fly patch. Deleted nvram.plist from EFI volume and cleared nvram, especially to remove numerous SMC key entries that did not match MBP9,2 hardware. Replaced FakeSMC with a slightly older version from my own E6230 bootpack with all PlugIns inside and Info.plist already tuned to MBP9,2 SMC keys. Permissions repaired and cache rebuild. Full CPU SpeedStep + Turbo boost on reboot. It's tad better than running stuck @800MHz...

Try to add EPADFix or CodecCommander kext. Can't remember if they work from /L/E or if they have to be in /S/L/E like AppleHDA.

Re: wireless card, if the E7440 has space for a full size card, I highly recommend this: https://osxlatitude.com/index.php?/topic/7554-apple-broadcom-bcm4360cd-80211-ac-wifi-and-bluetooth-combo-card/