Hervé

Looking good, thanks. Please note that you should not use the VoodooSDHC kext as that's unnecessary and highly likely to cause wake issues. Instead, patch your DSDT to inject compatibility with Apple's default SD card reader. Details of the patch are available here and in original thread from Joe82. The patch works perfectly on all E6x20/6x30/6x40 models. Have you found ACPIPoller to be necessary? I've not needed it on my E6230... HDMI output and HDMI audio are also achievable through a combination of DSDT patches + Capri FB patches and AppleHDA patches.

If you run DCPIManager, it'll show you the exact audio codec fitted to your system.

Replace kextcache command by: sudo kextcache -system-prelinked-kernel

I guess there probably will not be proper support for mobile HD530 until Apple bring out a MacBook/MacBookPro based on that iGPU. Skylake MBPs have been awaited for some time and may be launched end of the year. At present, the only Skylake-based Apple Mac platforms are: MacBook9,1 which are fitted with HD515 graphics (no discrete GPU) iMac17,1 have 6th gen i5/i7 CPUs with integrated HD530 but I don't think it's being used in a switched mode with the AMD dGPU

If you can't patch AppleHDA, I'd recommend you use a much more recent VoodooHDA than v2.8.5. Slice recently published his own version v2.8.9 and that seems to work rather well on systems where it was deployed.

Here are BIOS settings that are known to work on the E6440 (Haswell CPU with Intel HD4600 graphics) under Mavericks, Yosemite, El Capitan, Sierra and High Sierra. These settings were tested and verified with BIOS A05, A08, A13, A14, A16, A17, A18 and A21. Boot Sequence: . Diskette drive = Off . Internal HDD = On . USB Storage Device = On . CD/DVD/CD-RW Drive = Off . Onboard NIC = Off . Boot List Otion = Legacy *** Set boot order according to own choice *** *** mini SSD option may also be offered if internal mSATA SSD is installed *** System Configuration . Integrated NIC = Enabled . Parallel Port = Disabled (you may opt for any other options if required) . Serial Port = COM1 . SATA Operation = AHCI . Drives: * SATA-0 = On * SATA-1 = On * SATA-2 = On * SATA-4 = On . SMART Reporting: * Enable SMART Reporting = On or Off . USB Configuration: * Enable Boot Support = On * Enable External USB Port = On * Enable USB3.0 Controller = On . USB PowerShare: * Enable USB PowerShare = On . Audio: * Enable Audio = On . Keyboard illumination = Level is 100% or any other settings. This applies only to models with backlit keyboards . Unobtrusive Mode: * Enable Unobtrusive Mode = Off . Miscellaneous Devices: * Enable Mobile Bay = On * Enable Microphone = On * Enable eSATA Ports = On * Enable Hard Drive Free Fall Protection = On * Enable ExpressCard = On * Enable Camera = On * Enable Media Card = On Video: . LCD Brightness = Max or whatever settings you prefer Security: . Admin Password = not set . System Password = not set . Internal HDD-0 PW = not set . Strong Password = Off . Password Configuration = default settings . Password Bypass = Disabled . Password Change: Allow Non-admin Password Changes = selected . Non-Admin Setup Changes = Off . TPM Security = Off . Computrace® = Deactivate . CPU XD Support = enabled . OROM Keyboard Access = Enable . Admin Setup Lockout = Off Secure Boot: . Secure Boot Enable = Disabled . Expert Key Management: * Enable Custom Mode = Off * Custom Mode Key Management = PK Performance: . Multi Core Support = All . Intel® SpeedStep = Enabled . C-States control = On . Intel® TurboBoost = Enabled . HyperThread Control = Enabled . Rapid Start Technology = Disabled Power Management: . AC Behavior: * Wake on AC = Off . Auto On Time = Disabled . USB Wake Support = Off . Wireless Radio Control: * Control WLAN radio = Off * Control WWAN radio = Off . Wake on LAN/WLAN = Disabled . Block Sleep = Off . Peak Shift = Off . Advanced Battery Charge Configuration = Off . Primary Battery Charge Configuration = Express Charge (or any other choice) . Battery Slice Charge Configuration = Standard (or any other choice) . Intel® Smart Connect Technology = Off POST Behavior: . Adapter Warnings = Enabled . Keypad (Embedded) = Fn Key Only . Mouse/TouchPad = Touchpad/PS-2 Mouse . Numlock Enable = Enabled . Fn Key Emulation = Enabled . MEBx Hotkey = Enabled . POST hotkeys = Enable F12 Boot Option Menu . Fast Boot = Minimal . Extend BIOS POST Time = 0 seconds (or any other choice) Virtualization Support: . Virtualization = Enabled . VT for Direct I/O = Off (otherwise use Chameleon/Clover option dart=0) . Trusted Execution = Off Wireless: . Wireless Switch: * WWAN = On * WLAN = On * WiGig = On * Bluetooth = On . Wireless Device Enable: * WWAN = On * WLAN/WiGig = On * Bluetooth = On

The guide I had initially posted clearly mentioned Chameleon. The above posts are for Enoch for which things differ.

Run GeekBench or something similar that triggers a high CPU load. The fan should then spin and at high speed as the CPU speed increases and reaches turbo boost mode. If the fan still doesn't spin, it's highly likely that you'd have an electrical fault with the fan (fan disconnect or gone faulty). Fan control is usually automatic and there's very little you can do in terms of control. Dell laptop BIOS does not usually allow you to do much on that front, if anything at all.

I've also revised your /Extra folder as it did not seem adequate/correct for its purposes: removed kexts NullCPUPM + Patched_10.7_AppleRTC (used for Lion) + AppleACPIPlatform v1.5 (from ML?) kexts that are not required imo configured kernel cache + built-in Eth + laptop computer type + P&C States generation (for native CPU speedstep) + GraphicsEnabler boot options added the kernel.plist used by Enoch, even if options are kept to no (may come useful if you move to EC or Sierra) added an updated Themes folder to get nice bootloader icons for Mav/Yos/EC/Sierra (that's totally optional) added boot option kext-dev-mode=1, which is necessary for Yosemite Try it and report accordingly. Herve_revised_E6410_Extra.zip

Enoch is a branch of Chameleon, so it still uses the /Extra folder, the o.c.B. plist and smbios plist and all the rest (subfolders Themes, modules, etc.). However, Enoch has adopted enhanced features compared to good old Chameleon: kexts placed in /Extra/Extensions (/E/E) will be injected at boot time if boot option KernelBooter_kexts=Yes is used; otherwise, they're ignored add-on kexts should be installed to /Library/Extensions (/L/E) or, if required, /System/Library/Extensions (/S/L/E) from where they can be cached Enoch now makes use a kernel.plist file where you can specify additional kernel patching parameters such as kernel power management (for Haswell CPUs and beyond, SIP disabling values, etc). The complete list and explanation are available in the Chameleon/Enoch thread at InsanelyMac. For El Capitan and beyond, SIP can be disabled through CsrActiveConfig parameter which need to be set to the desired value (3 for instance) When you copy kexts to /L/E or /S/L/E, you must repair permissions: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* then rebuild your cache: sudo touch -f /L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / If you get errors, repeat these last 3 commands. Obviously you can restrict permissions repair + touch commands to the folder you've updated. If you place your add-on kexts to /L/E (which you should) and attempt to boot without cache, then /L/E is ignored. You'll quickly understand that, in such a case, missing FakeSMC is going to lead to trouble so you must cater for this. This is why one should always keep a copy of all add-on kexts to /E/E (including the almighty NullCPUPowerManagement), from where they can be called through the following set of boot flags and parameters for instance: KernelBooter_kexts=Yes -f -v. Kexts placed in /E/E do not need any permissions repair, they will be used as is.

© Consomac.fr: [ 1] 0x191e0000 - Intel® HD Graphics 515..........(ULX GT2) [ 2] 0x19160000 - Intel® HD Graphics 520..........(ULT GT2) [ 3] 0x19260000 - Intel® Iris™ Graphics 540.......(ULT GT3) [ 4] 0x191b0000 - Intel® HD Graphics 530..........(Halo GT2) [ 5] 0x193b0000 - Intel® Iris™ Pro Graphics 580...(Halo GT4) [ 6] 0x19120000 - Intel® HD Graphics 530..........(Desktop GT2) [ 7] 0x19020001 - Intel® HD Graphics 510..........(Desktop GT1) [ 8] 0x19170001 - Skylake Desktop.................(GT1.5) [ 9] 0x19120001 - Intel® HD Graphics 530..........(Desktop GT2) [10] 0x19320001 - Skylake Desktop.................(GT4) [11] 0x19160002 - Intel® HD Graphics 520..........(ULT GT2) [12] 0x19260002 - Intel® Iris™ Graphics 540.......(ULT GT3) [13] 0x191e0003 - Intel® HD Graphics 515..........(ULX GT2) [14] 0x19260004 - Intel® Iris™ Graphics 540.......(ULT GT3) [15] 0x193b0005 - Intel® Iris™ Pro Graphics 580...(Halo GT4) [16] 0x193b0006 - Intel® Iris™ Pro Graphics 580...(Halo GT4) So only 2 x layout-id to try in theory: 0x19160000 or 0x19160002.

You're still trying to boot your USB installer, right? If so, your SMBIOS definition is in the /Extra folder. I suggest you install Enoch r2839 (latest at time of writing) and upload a zipped copy of your full /Extra folder. It looks like it needs a good review...

Sierra will work with the same set of add-on kexts and settings you currently use for El Capitan. Use the forum search facility for your backup needs. Disk cloning and/or backups have been quite intensively discussed in the past.

Oups, major copy/paste mistake on my part there. My apologies. I've adjusted the guide... VGA output is unsupported on HD4000 since Mavericks (and possibly late versions of ML). DVI output will work off docking station though, I tested that.

Seems you need to boot without cache and rebuild it afterwards.

Unlike the GPU state changes log entries, HWMonitor is not "real time": the counters/stats get refreshed at a pre-defined interval, typically anything from 2 to 5s. You may reduce this to 1s and see more GPU state changes but it'll never be as time-accurate as the log and, clearly, still some work to do on the thresholds. Cuda-Z may be more appropriate if it still works... Keep on trying, you're on the right path. Voltage will vary according to GPU load and throttling; it's not a fixed parameter and not something you can adjust. In that respect, it's like the CPU voltage re: CPU SpeedStep.

If you've registered for Beta testing, you can download Sierra GM off Apple's web site where you'll get a Redeem Code. Failing that, you're only 10days away from general public release...

Legacy mode not an option?

You had initially listed this: Can't you remove the useless entries through the "Delete Boot Option" button any more? Can't you reset BIOS to default settings?

I find it strange that you're unable to set boot order in BIOS; unless it's locked of course and you do not have the password... On my E6220/E6230/E6440 systems, I can set the disks boot order in BIOS. For instance, in my E6440, I have a regular 3.5" SATA HDD (with Windows) + an mSATA SSD (with multiple OS X Partitions + Enoch bootloader). In BIOS, I can set 1st boot device from the displayed list of media (SATA HDD, mSATA SSD, USB, CD/DVD, floppy). If I set 1st boot disk to 3.5" SATA HDD, I'll always boot Windows directly (because that's all the system sees) but if I set 1st boot disk to the mSATA SSD, then Enoch allows me to boot any of the installed OS X partitions or Windows from the SATA HDD, since it's listed too. Ok, this is all legacy mode, but... I can also manually overwrite this by pressing F12 at the BIOS POST logo to get a list of boot device to choose from. This is how people usually boot their USB installer (Press F12, select USB media). I'm surprised you cannot do the same with your E6430.

I'm quite confident you can achieve good results with the right settings. Reason for this is that both the NVS 3100M of the E6410 and the GT 330M of MBP6,1/6,2 are based on same architecture GT2xx. http://www.notebookcheck.net/NVIDIA-Quadro-NVS-3100M.24738.0.html http://www.notebookcheck.biz/NVIDIA-GeForce-GT-330M.27335.0.html Info.plist of AGPM kext shows the following nVidia ids for MBP6,1/6,2: Vendor 10de, Device 0029 -> GeForce GT 330M = chip GT216 Vendor 10de, Device 0a34 -> GeForce GT 240M = chip GT216 As far the Dell Latitude E6510 dGPU: Vendor 10de, Device 0a6c -> NVS 3100M = chip GT218 So, they are close cousins. Inject the section for Vendor10deDevice0029 of MacBookPro6,1 or 6,2 entries to your FakeSMC and adjust the thresholds to test: <key>Threshold_High</key><array> <integer>57</integer> <integer>70</integer> <integer>80</integer> <integer>100</integer> </array> <key>Threshold_High_v</key> <array> <integer>1</integer> <integer>3</integer> <integer>98</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>68</integer> <integer>75</integer> <integer>94</integer> </array> <key>Threshold_Low_v</key> <array> <integer>0</integer> <integer>2</integer> <integer>4</integer> <integer>99</integer> </array>

Ok, so you have throttling between 4 states (0, 1, 2, 3) -which is good news- but I guess the current threshold values are not adequate. You need to play with those until you find settings that are good in terms of performance on screen. For instance, you'll see in my guide that I adjusted the default MBP5,1 threshold values from: <key>Threshold_High</key> <array> <integer>57</integer> <integer>65</integer> <integer>82</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>68</integer> <integer>75</integer> <integer>95</integer> </array> to: <key>Threshold_High</key> <array> <integer>57</integer> <integer>65</integer> <integer>74</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>40</integer> <integer>60</integer> <integer>75</integer> </array> That was done over a period of time, setting values and testing/evaluating graphics performance of my NVS 135M until I felt satisfied, the aim being mostly of minimising the delays for throttling GPU core/RAM speeds up and down according to graphics demand/load. As I said, I've no direct and/or straight method to set those threshold values according to GPU model. It's purely a manual "set and test" method. In your case, you should start from the MBP6,1/6,2 default settings of one or the other nVidia entries (vendor 10de). You may also experiment with control-id value, i.e. 17 or 18. I would not refer to the threshold of the Intel 1st gen HD iGPU (8086:0046).

That's exactly it: instead of patching the AGPM kext in /S/L/E, something one would require re-doing after each OS X update, FakeSMC can instead be used to inject the same patch. FakeSMC never gets replaced or overwritten at OS X updates, so the patch remains effective throughout. Make sure you start from your original AGPM Info.plist code, do not copy the code I posted to illustrate my thread because it may not match the vanilla AGPM version.

The tuned FakeSMC is essentially targetting native CPU SpeedStep. For GPU throttling, you have to look at the AGPM tuning and experiment as mentioned in the guide. I've no straight answer for any given GPU model... The guide mentions how to log GPU throttling behaviour, so use that to verify actual GPU state changes and then experiment with threshold levels.

https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ https://osxlatitude.com/index.php?/topic/7807-nvidia-gpu-performance-tuning-with-agpm/ Afaik, NVS 3100M CPU clocks up to 600MHz and the RAM up to 800MHz.