Hervé

© 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.

Revert/swap the disks boot order. Clover is obviously on your OS X disk, not on the Windows disk. So make sure that the boot order 1st points towards the disk that has OS X on it. Ain't that logical?

OS X supports VGA but it depends on GPU model or OS X version, sometimes a mix of both. For instance, VGA is unsupported with mobile Haswell HD4600 whereas I've seen it work OOB on HD4400-based laptops. IvyBridge HD4000 supported VGA output in ML but not since Mavericks. On my old Latitude D630, the nVidia NVS Quadro 135M supports VGA output all the way from SL to Sierra. With your discrete ATI board, it should depend entirely on the framebuffer settings, i.e. the ATI Config personality you'll go for. The personality may also require binary patching.

Re: BIOS settings, I recommend: 1) Ethernet = Enabled (rather than enabled w/PXE - you're not going to boot via a LAN image, are you?) 2) display: I would statically define iGPU (Intel HD) or dGPU (ATI Radeon HD) but not set the primary display to auto. Hackintoshes do not support GPU switching.

Mmm, never went that high With Chameleon; always had issues with versions above 2500... Can you downgrade Chame to r2468 for instance, otherwise try the latest Enoch?

I give up.

'never ever seen such a KP before. I have absolutely no idea! You should be using MacBookPro6,1 SMBIOS (Arrandale) though, not MBP8,1 (SandyBridge...). What version of Chameleon did you install on that USB installer?

If you copy the file to the EFI partition, it's the right place. If you copy the file to the OS X partition, it's wrong. Upload a zipped copy of your entire EFI folder.

I'm trying to help, but it's difficult... I don't think you're saving or copying your config.plist to the right place. Maybe you'll enlighten us on that.

You didn't save the config.plist in French, did you?

He's killing me! If you really want to, you can try the following commands: cd / sudo rm -Rf *