Hervé

It's required after any kext addition, removal or modification, whether in /S/L/E or in /L/E. To repair permissions, type the following Terminal commands: sudo chmod -Rf 755 /S*/L*/E* sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo chown -Rf 0:0 /L*/E* ` To rebuild kextcache and prelinked kernel, type the following Terminal command: sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / ` Sometimes, the system returns an error message about not being able to modify/rebuild the cache and/or the prelinked kernel. In this case, the existing cache and prelinked kernel can be deleted using the following Terminal commands: sudo rm -Rf /S*/L*/PrelinkedKernels sudo rm -Rf /S*/L*/Caches/com.apple.kext.caches The cache and prelinked kernel can then be rebuilt using the above touch and kextcache commands.

Don't set DropOEM. Just select Generate P-States and Generate C-States. Then, I strongly recommend you tune FakeSMC to the keys of MBP6,1/6,2 and, of course, select that has your SMBIOS. https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ https://osxlatitude.com/index.php?/topic/7283-apple-mac-smc-keys/ https://osxlatitude.com/index.php?/topic/7807-nvidia-gpu-performance-tuning-with-agpm/

'haven't seen this model mentioned before, so it'll be same as usual for a 1st timer: 1) identify your other hardware elements (LAN, wifi, bluetooth, SD card reader, etc) 2) built your USB installer (with Clover or Enoch as boot loader) 3) install Sierra 4) look for the kexts/drivers suitable for your identified hardware elements and add support for them

After inquiring about his E6230 in an E6320 thread, walterwolf was specifically pointed to this guide... Makes me wonder if it's a E6220 or a E6230 he's got. There sure appears to be some confusion.

It does not look like you repaired permissions as instructed by JakeLo. Don't use Kext Wizard, do it manually.

They are 2 separate things with no relation between them. Whether you proceed or not is entirely up to you.

Revert to your original settings then.

The right patch maybe? http://www.insanelymac.com/forum/files/file/563-sierra-mbr-patch/

Look again! Use the built-in help if you can't see the obvious.

Only the webcam and the security chip are seen in IOReg. If it's a DW1550 you have, it may need to go into a WWAN/combo PCIe-USB slot for Bluetooth to be available (if WLAN slot is PCIe only).

Vey common mistake. Broadcom 5880 is a security chip fitted as standard on models that may receive the optional fingerprint reader. But, as stated by JakeLo, it's no Bluetooth module and none are listed on this M4800.

Ideally, /L/E rather than /S/L/E (not /S/L). You can cache kexts from there are opposed to inject them with Clover.

You cannot tell if SD card reader is USB-internal or PCIe by looking at the slot. You have to check whether it appears under the USB section of your SysProfiler or in the list of PCI devices in DPCIManager app (or Terminal command lspci -nn if you've installed the package). USB card readers normally work OOB or not all all. VoodooSDHC or Apple's own kext operate on compatible PCIe readers. If it's a PCIe model, you can try and declare it compatible with Apple's own device in DSDT. If it turns out compatible, it'll then work OOB.

The iGPU will consume less battery, yes. You can swap keys through the Keyboard PrefPane...

Seems Ok to me. Make sure to repair permissions and rebuilt your cache after you modify the FakeSMC kext.

Moving to Support section since posted in Guides section which clearly states "no support here"...

No, the FakeSMC patch of the D630 pack does include the PCI id of the GPU. You just missed it. NVS 135m carries device id 042b, so it's clearly different from the NVS 160M which you state to carry id 06eb. Read the thread with more attention...

Dell had a tendency to fit different webcams to those laptops. What's the model? Its PCI ids? The E6320 was a typical example with some laptops fitted with a Sunplus webcam and some with a Sonix. Only the former is supported under OS X, not the latter. Same thing with the E6230: some laptops are fitted with a Sonix webcam carrying device id 0x648b (supported) and some with a different Sonix model carrying device id 0x6449.

Grab your entry from your current version's AGPM kext, though there should be little of not no difference to what's posted in the original thread. D630 and E6500 don't have the same GPU. If you grab the D630 FakeSMC that includes the patch for NVS 135M, remember to change the GPU id or the patch will not be effective. That's clearly stated in the thread.

If you've had trouble with every Dell/Lenovo/HP laptop you convert to Hackintosh, I can only assume it's linked to the manner in which you install or tune your systems because I've had no trouble using Chrome on my Hacks and I've had a few... I don't know which system you're on right now but you can start with the CPU & AGPM tuning threads & articles posted on the forum and web site. http://www.osxlatitude.com/tuning-performance-with-fakesmc-smbios-plist/ https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ https://osxlatitude.com/index.php?/topic/7807-nvidia-gpu-performance-tuning-with-agpm/

It's not an Info.plist patch, it's a binary file one! Hence the Find/Replace for Clover...

If you don't know of any other reason already, the answer is probably no.

Well, now you've modified your initial post to explain things a little better... Anyway, I don't think you can do what you seek to do. What system do you experience such issue with? Did you tune your graphics for GPU throttling (AGPM)?

You can verify full graphics acceleration in the usual manner: translucent Finder's bar, clicking in & out of LaunchPad, DVDPlayer Supported Features, etc.

Sounds like 2nd/final stage boot glitch. Fixed with the following IOGraphicsFamily kext patch: Find: 0100007525 Replace by: 010000EB25