Hervé

Apple removed the built-in facility to have a Display icon on the Finder's bar (that's what the "menu line" is called) when Mountain Lion was introduced back in 2012. If you wish such a tool, you can refer to this old thread on the matter (I personally still recommend (and use) Display Menu app today)… Do think of using the forum Search facility. Re: HDMI audio, make sure to use: patched AppleHDA patched SNB framebuffer Everything is already available here.

You've not bothered to apply any of the changes suggested in post #7.

"I can not activate the the Monitor icon on home screen"... Sorry, I don't understand; what do you mean?

Seems Ok. You say you're booting off an external USB disk. Did you try to boot with the internal HDD removed?

Well, those offending kexts sure aren't in the cache or list of kexts to cache; otherwise, they would be listed in the warning about invalid signature. On that basis, we have to conclude that they are injected by Clover through the EFI/Clover/kexts/10.12 or EFI/Clover/kexts/Other folder. There can be no other explanation. 'might be a good idea to post a zipped copy of your full EFI folder...

From Terminal, type the following commands. 1) to remove prelinked kernel (it should auto re-generate): sudo rm -f /System/Library/PrelinkedKernels/prelinkedkernel 2) to remove kext cache: sudo rm -Rf /System/Library/Caches/com.apple.kext.caches/* 2) to rebuild cache + prelinked kernel: sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / (or: sudo kextcache -system-prelinked-kernel) If you get an error message "... 77", re-type the touch + kextcache commands. Ignore any message "... 17".

Then the offending kexts are still cached. Try and manually delete cache folders + prelinked kernel, then rebuild the cache.

If you've rebuilt your cache and there are still traces of the offending kexts, try and locate them on the disk. From Terminal, type: sudo find / -name NullCPUPowerManagement.kext -print 2>/dev/null and repeat this for the VoodooPS2Controller kext. One question: this EFI folder you're looking at, is at at the root of your Sierra partition or in the mounted EFI partition? Make sure to look in the right place...

@OliverZ: Apple has no native support for mobile Haswell iGPU; that's why all laptops based on mobile HD4200/HD4400/HD4600 iGPU must fake desktop HD4600 model (id 8086:0412). Of course, you could try MBP11,1 or MBP11,2 SMBIOS, but I had no graphics issue using MBA6,2 on my mobile HD4600-based E6440.

...and the AGPM settings you used would be?

When you fake desktop HD4600, I believe it's 0x80860412, not 0x04128086... Use latest CloverConfigurator and there'll be no doubts.

No, you also need to rebuild your cache, otherwise it's as if the kexts were still present. Open up Terminal and use the following commands once kexts have been deleted: sudo touch -f /L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / If you use Clover, make sure the kexts are not in the EFI/Clover/kexts/10.12 or Other folder.

Great! Would be useful for other users if you could provide the settings you used (Mac model, PCI ids, thresholds) and the various GPU core/Memory frequency steps you noticed... 162/???? MHz 202/1620 MHz 405/???? MHz 666/3010 MHz

Confirmed to work on Precision M4400 with nVidia FX 770M and Precision M4800 with nVidia K2100M.

Re: Bluetooth, disable the search in the BT PrefPane.

There is no support whatsoever for cards based on that Broadcom chip (e.g.: DW1530, DW1540). https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/ myHack v3.3.1 fully supports Mavericks installation but the buck stops there. The pack you've referred to comes off my myHack-based E6220 guide. If you've properly installed it at the onset on the myHack USB installer, myHack will install it automatically at the end of the Mavericks installation. It may not install the boot loader though, but that's easy to sort out: boot the finalised installation via the USB installer, then download and install a recent Chameleon (or Enoch) package.

Tried the double keypress to remove CAPS lock? That's necessary under Sierra.

Erm... obviously, the MacPro5,1 was the newer machine, not the MacPro4,1. The above statement was made with regards to CPU power management, as clearly stated. In that respect, MacPro4,1 is closer to the Z600 than the MacPro5,1. Given the known issues linked to MacPro4,1 SMBIOS, MacPro5,1's might be better suite and that's what was hinted... SMBIOS profiles are usually chosen on such criteria as CPU models or graphics cards/GPUs, hardly on memory speed.

I've noticed that, since 10.12.3 (can't say for earlier Sierra versions), the DVI patch no longer seems to work for DVI secondary output. My DVI connected screen remains undetected after startup (repeated behaviour off 2 x different types of docking station/port extender). I can only get DVI output by booting my laptop with lid closed, i.e. with single display output to DVI. Edit: 05 Sep2018 DVI output recovered in Sierra and High Sierra with AppleGraphicsDevicePolicy kext patch as described in post #5 below.

Added DW1830 combo Wifi ac/BT4.1 NGFF M.2 card. Supported OOB from Yosemite only. Earlier OS X versions will require DSDT or AirPortBrcm4360 kext patching.

Ok, so it is a DW1830... It may not work 100% OOB on the basis that it's not an Apple device. You'll have to tell us... Can you confirm the PCI ids (wireless AND bluetooth)? According to wikidevi, you should have: wireless = 14e4:43ba bluetooth = 0a5c:6410 Wireless device id 43ba is supported by AirPortBrcm4360 PlugIn of IO80211Family kext since Yosemite (it's present in the Info.plist file of the kext). As such, you can expect wifi to work OOB. If it did not, a simple DSDT patch to declare compatibility with Apple's own BCM94360 devices (id 43a0 for instance) should suffice. Faking Apple's BCM94360xx id through Clover may work too. For the Bluetooth, I expect you'll probably still require the Brcm firmware patches. Experiment by yourself, see how it goes and report back... NB: changed thread title to reflect the related hardware here...

Indeed, that sounds like the issue is your Windows USB media, not the HDD.

Won't any Windows installer allow to wipe off any disk partition and start afresh?

It doesn't. Z600 is based on Intel chipset 5520 and the integrated ICH9/ICH10 I/O Controller supports USB2.0 ports only.