Hervé

That'll work.

You can add the patch to FakeSMC Info.plist. It'll then be sustainable to macOS updates, as long as Apple does not change the kext name and the associated Info.plist entries syntax like they often do between releases. It's the same as for any such patches (AGPM, WWAN, Bluetooth) where you add an entry rather than modify existing ones.

Silly question probably but did you disable hibernation? Re: wifi USB dongle, it should not be a problem as long as you do not enable "USB wake" in BIOS". Make sure it's the same for LAN: no "Wake on LAN". Your kexts are Ok.

That's right; unsupported afaik.

Try the attached. * DSDT mods done: combined both _DSM methods of LPCB device into a single one _PWR methods of GLAN/HDEF/EHCx devices changed from returning (0x0D,0x04) to (0x0D,Zero) removed "If" tests in _PWR method of EHCx devices to keep a single "Return" statement NB: It would be interesting to know what mods you made to the _WAK method. revised_DSDT.aml.zip * Clover config mods done: removed all selected ACPI fixes removed USB FixOwnership option injected proper MBP6,2 SMBIOS revised_Clover_config.plist.zip

Check your add-on kexts then; there's clearly something wrong somewhere.

Patch details sure are Ok but it seems you somehow screwed the framebuffer kext. Maybe you made another binary mod by mistake somewhere... Why don't you update to 10.12.6 and use the patched kext I uploaded? Save yourself some time!

No, proceed as follows: place the FakePCIID kexts in /L/E place the Brcm kexts in /S/L/E manually repair permissions to both folders manually rebuild your cache remove those kexts from Clover kexts folder if present there reboot and check behaviour If you don't know how to manually repair permissions and rebuild the cache, check the FAQ forum section.

Any update will re-instate vanilla kexts in /S/L/E and overwrite any patched kexts, That's a general matter that should be known by all. Make a good note of that. Hence the explanations I just wrote above regarding patched SNB framebuffer kext (the kext versioning trick can be generalised too). It's a little silly to revert to a backed-up 10.12.3 installation when repatching the 10.12.5 vanilla framebuffer would have sorted you out. If you run Enoch, you know what to do now (and update to 10.12.6)... If you use Clover, you should configure the patch in the "on-the-fly" manner.

When you rebuild the cache, OS X/macOS includes kexts in /S/L/E and /L/E. Kexts in Clover EFI folder are injected, not cached. Obviously, don't duplicate kexts in both places (/S/L/E or /L/E and EFI/kexts/xxx).

'just verified VGA output on my E6220 under Sierra 10.12.6 and all is Ok. Personally, I patch the vanilla SNB framebuffer kext as described in post #5 of my E6220 guide, increase the patched kext's version by adding a leading 9 (e.g.: 910.2.37) and place it in /L/E. Once permissions are repaired, this patched kext always takes precedence over the vanilla version left untouched in /S/L/E and the cache is rebuilt using that patched version. It's sustainable to OS updates. Patched_10.12.6_AppleIntelSNBGraphicsFB.kext_v910.2.37.zip I invite you to do the same. Avoid mistakes such as using Yosemite 10.10.5 patched SNB Framebuffer kext in Sierra 10.12.6.

Did you patch the Capri framebuffer kext?

Post an IOReg output. DW1830 is supposed to work OOB with the vanilla kexts.

Re: Broadcom 5880 https://osxlatitude.com/index.php?/topic/1225-fingerprint-broadcom-ush-bcm5880/&do=findComment&comment=54164 https://osxlatitude.com/index.php?/topic/9301-dell-precision-m4800-macos-sierra/page-9&do=findComment&comment=71698 Guys, if in doubt, use Google!

'not heard of any signal drops or random disconnections with AR9285-based cards.

Recovery partitions are created by default when installing OS X/macOS for some years now. Useful on Clover-based installations but not on Chameleon-Enoch ones because these cannot boot recovery partitions. As such, it can be desirable to remove them to retrieve the (small) disk space they take and suppress them from the list of partitions. This is achieved with Terminal commands through the following method: verify volumes arrangement and identify main + recovery partition disk identifier. The recovery partition will directly follow the main volume to which it relates. diskutil list reformat recovery partition under HFS+ type and new name (no space) diskutil eraseVolume HFS+ <new name> <disk identifier> (eg: [...] Blank disk0s3) recover ex-recovery/Blank partition disk space by merging it with its associated main volume (listed right above it). diskutil mergePartitions HFS+ <main Volume> <main disk id> <blank disk id> (eg: [...] Sierra disk0s2 disk0s3) NB: Partitions have to be sequential to be merged. For help on the diskutil command, type man diskutil.

CoreStorage logical volume management was introduced by Apple in Lion. Since Yosemite, Apple has forced its utilisation by default. Whilst this is Ok with Clover-based installations, it is not with Chameleon/Enoch-based ones because these cannot boot CoreStorage volumes. As such, after fresh installations and, sometimes, updates (depending on how the installation was made), it's therefore necessary to revert CoreStorage volumes to legacy mode. This is achieved with Terminal commands through the following method: verify CoreStorage status and identify volume diskutil list if logical volume found/listed, revert to legacy volume mode diskutil CoreStorage revert <disk identifier> (eg: disk1) verify return to legacy mode diskutil list NB: For help on the diskutil command, type man diskutil.

Hibernation is enabled by default after any fresh installation of Apple's OS; sometimes, it's even re-enabled after an update. Although Clover has supported hibernation for some time, it can still cause issues on Hackintoshes and it's often desirable to disable hibernation in order to revert to plain old sleep. This is achieved through the following Terminal commands: sudo pmset -a hibernatemode 0 ` To delete the sleep file: sudo rm -f /var/vm/sleepimage ` To point the sleep file towards null device (though sleep file may still re-appear): sudo pmset -a hibernatefile /dev/null ` To verify hibernation setup: pmset -g

Graphics acceleration is one of the most important required feature to run OS X/macOS properly. Without it, OS performance is poor to extremely poor depending on the hardware specs of the computer, especially the CPU. Graphics acceleration can be verified through the following (non-exhaustive) actions: Translucent Finder's bar (most visible from Snow Leopard to Mavericks) LaunchPad through Dock icon (clicking in and out of LaunchPad should be quick and totally smooth) DVD player app -> Help Menu -> Show Supported Features (all should be enabled) Desktop switching through Ctrl-Up/Ctrl-Down/Ctrl-Left/Ctrl-Right (should be quick and smooth) Desktop and Screen Saver PrefPane (all desktop pictures and screen savers should show Ok) Without graphics acceleration, system will feel laggy and graphics glitches will occur.

macOS Sierra and later no longer allow all apps to run by default. Instead, GateKeeper protection was beefed up and it now limits execution to apps downloaded from AppStore or AppStore & identified developers. As such, some downloaded apps cannot be executed without triggering a warning and users may have to go to the Security & Privacy PrefPane to allow the app to run. To change his and allow execution of all downloaded apps by default, type the following Terminal command: sudo spctl --master-disable The restriction will then be lifted and all downloaded apps will be allowed to run. I believe this info was 1st reported by Netkas.

Since Yosemite 10.10.4, OS X/macOS supports trimming for non-Apple SSD. The facility can be enabled through the following Terminal command: sudo trimforce enable ` For earlier versions, the IOAHCIBlockStorage kext must be binary patched to suppress whitelisting for Apple-branded SSDs only: Find: 004150504c452053534400 (=> " APPLE SSD ") Replace by: 0000000000000000000000 (=> " ") NB: this patch can also be used for Yosemite 10.10.4 and later.in I believe the patch was 1st reported at InsanelyMac. It's one of the kext patches provided by default in Clover Configurator.

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 the cache, type the following Terminal command: sudo touch -f /S*/L*/E* sudo touch -f /L*/E* The cache should then automatically rebuild itself.

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