Hervé

Please note that, starting with Yosemite, OS X kernels go to /System/Library/Kernels folder under the name of "kernel". As such, what you did by copying the kernel to HDD's root under the name of "mach_kernel" is an unnecessary step to me. Clover and recent versions of Chameleon/Enoch are fully capable to boot Yosemite and El Capitan with the kernel in vanilla name and at new default location. Your system KPs on EvoReboot so I'd remove that specific kext. What do you think? Personally, I've never needed it on my E6220 or the E6420 I briefly had between my hands. Since you're using Clover (I stick to Chameleon/Enoch), make sure to enable AsusAICPUPM option to cater for SandyBridge CPU power management and avoid related KP.

Once you've added kexts to /L/E, you must repair permissions and rebuild your cache: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / (or: sudo kextcache -system-prelinked-kernel) If you get error messages, re-type the last 2 commands.

? You either use VoodooHDA (and you have to disable AppleHDA) or you patch AppleHDA for your audio codec (and you'd probably have to patch your DSDT too). There is no "HDAEnabler" kext... Try an older VoodooHDA version such as v2.8.1 published in my D630 packs. You may also try to play with some settings in the VoodooHDA PrefPane.

No such issue on my D630 with v2.8.8, you may have something incorrectly configured in your Clover setup... Personally, I chose to stick to Enoch. CPU bus speed not set to anything above 200 000kHz in your Clover config for instance?

VoodooHDA only works provided you've also added AppleHDADisabler. The disabler kext usually comes with the VoodooHDA package. If you don't have it, install latest VoodooHDA v2.8.8. Google for it.

Ok, Intel i7-720QM is a quad-core Clarksfield CPU with DMI interface (or QPI) at 2.5GT/s. I guess that's what you're talking about when you mention FSB 2500MHz. DMI (QPI) was an evolution of the FSB and the latter no longer applies to Core generation CPUs. FSB applied to older CPU generation like CoreDuo, Core2Duo, Core2Quad, etc. The i7-720QM CPU has a nominal speed of 1.6GHz with Turbo boost to 1.73GHz (3 or 4 cores), 2.4GHz (2cores) or 2.8GHz (1 core). What I'm talking about by CPU bus speed is the actual base clock which, combined with CPU clock multiplier, provides the overall CPU speed/frequency. For instance, SandyBridge/IvyBridge/Haswell CPUs operate at frequency=multiplier x 100MHz (and all have a DMI of 5GT/s). This is what you typically see in HWMonitor app: In the case of the i7-720QM, LFM = 933MHz (the lowest frequency it runs at) and nominal multiplier = 12. As such, this CPU operates a 133MHz bus speed/base clock (1.6GHz / 12 = 133MHz). In HWMonitor, you'd see a multiplier of x7 at LFM speed, x12 at nominal speed, x13 at 3/4core Turbo boost (1.73GHz), x18 at 2cores Turbo boost (2.4GHz), x21 at 1core Turbo boost (2.8GHz). NB: I've read some people reporting inability to reach x21 multiplier with VT (Virtualisation Technology) enabled in BIOS... To have the expected "proper" CPU speeds reported, you'll need to configure Clover with a CPU bus speed of 133000 kHz. You should then see a CPU reported at 1.60GHz in "About this Mac" rather than 1.58GHz and same thing in HWMonitor.

Setting bus speed to 625000kHz sounds wrong to me. Arrandale (or 1st gen "i" core) CPUs typical use a 100MHz or 133MHz bus speed ('can't remember which). Which specific CPU model do you have?

In the case of Optimus, HDMI and DP may be wired to the nVidia GPU then.

Did you remove NullCPUPM and enable P States + C states in the Clover config? Regarding CPU speed, it's perfectly Ok to see 1.58GHz for a 1.6GHz nominal speed. Nothing to worry about, there's no bug here. Clover allows you to rectify this by specifying a nominal FSB bus speed in the CPU config menu/section. Lookup your exact CPU model and you'll find out the associated bus speed. Then, specify that (in KHz) in the Clover config. You do not need to modify AGPM kext in /S/L/E, the FakeSMC kext already contains the necessary patch.

Try this. FakeSMC_package_E6510_NVS-3100M.zip

Your SysProfiler shows that you're using MBP6,2 SMBIOS (which is Ok) and SMC version 1.58f17 (also Ok). I'm pretty sure your FakeSMC is therefore Ok but I'll check it out. I'll also inject an AGPM section to your FakeSMC to target your NVS 3100M GPU (ven/dev id 10de/0a6c). I'll reuse the same parameters as I did for nVidia NVS 135M of the D630/D830 series or NVS 160M of E6400/6500 series. It may turn out not fully optimum and may require further tuning but will nevertheless hopefully provide you with proper GPU throttling. Full explanations are available here. Edit: on checking your provided FakeSMC, no it's not tuned at all!

No sound but you can start and shutdown your laptop now? I'd call this progress. Audio we can fix easily in due course. It's totally secondary. Thanks for the IOReg. I can see your nVidia GPU as device VID under device PEG3@3. You probably already have full graphics acceleration for your NVS 3100M (i.e. it works OOB), but I can patch it for cosmetic reasons (like display "nVidia NVS Quadro 3100M" instead of "Dell NVS 3100M) and make the LCD screen internal. Your built-in screen appears as AppleDisplay, not AppleBacklightDisplay so I guess About thisMac->Displays tab shows an external screen picture instead of a laptop built-in LCD. Can you confirm? if you have an HDMI output, it should work OOB (2nd nVidia output port shows HDMI connector type). I'd be interested to hear if you see proper GPU throttling in HWMonitor app, especially after sleep. If you do not, AGPM tuning would probably fix that and provide you with much better GPU performance, better T° and better battery savings. I see your Broadcom wireless card as device PXSX under RP02@1C,1. Presumably a DW1510.

Yes, that's totally possible. Can you please post an IOReg (saved output from IORegistryExplorer app for instance) rather than your SysProfiler? It's not exactly the same thing... Thanks. A few 1st comments otherwise: You should avoid placing those add-on kexts to /S/L/E with Clover, unless they never load if placed elsewhere. You should inject them by placing them in EFI/CLOVER/kexts/10. (where xx is OS X release number). If you want them cached, place them in /L/E, repair permissions and rebuild your cache. Why do you use an older AppleACPIPlatform kext? It's not normally required since Mavericks (Lion and ML required roll-back to SL's kext). I would not be surprised if you USB issues came from that. I'd restore the vanilla kext. You have a E6510, i.e. an older laptop with an Arrandale CPU. You should not need NullCPUPM and should be able to enjoy native CPU SpeedStep/power management as long as you select P States and C States in Clover config. You do not need any patched AICPUPM kext nor any Clover power management patch (i.e. no kernelPm or AsusAICPUPM patch necessary). You have lspcidrv kext added but did you install the lspci package files (the exec + db files)? If you did not, then the kext does not serve any real purpose. myHack installed everything because Conti had included the full lspci package into his tool, Clover does not.

If you want HDMI and/or DP output off your HD4600 GPU, it's a "simple" matter of Azul FB patching. There are some guidance for that here. HD4600 GPU performance is not that poor... Fn-F3 reduces brightness, Fn-Insert increases it. DSDT patches may be applied to change that to expected Fn- combinations.

Apple menu -> System Information -> Hardware -> Graphics/Display Take a screenshot and post it. For a darwin report, you open up your Web browser, you type "google.com" in the URL field and once at the Google page (hopefully), you type "Darwin Dumper". You'll manage? Seriously guys, I really don't mean to be rude but please consider these books before even contemplating Hackintoshing your PCs!

Marto, can you please try and post pictures the right way? Adjust them before hand if required.

Ok. Which bootloader are you using? If Clover, can you please post your EFI folder? If Chameleon, post your /Extra and the kexts you've added.

Yes, could be a simple matter of injecting the correct ATY family. What does your SysProfiler show for Graphics? Does it say "no kext loaded" ?

I'm always wary of using (patched) DSDTs coming from different models. You said you were running Yosemite "without using DSDT.aml", i.e. without a patched table. As such, you can easily extract the original table from your BIOS. Patched DSDT tables always originate from there. Use any tool such as DSDTEditor, MaciASL or Chameleon Wizard to extract a file copy of your DSDT from the BIOS. You'll then have what we call a "raw DSDT". We can then look at patching it so that it fixes whatever needs to be tuned/fixed.

Ideally, yes, you should change your EHCI device (not the eventual _DSM category) to EHC1 or EHC2. However, you can normally still boot the USB installer off one of the USB ports. If you can boot without DSDT right now, do extract it off your BIOS and post it alongside a saved IOReg output from IORegistryExplorer.

And if you don't, repeat the touch + kextcache commands.

Locking this thread. It's a duplicate matter of other thread here.

Thanks Bronx; in fact it wasn't working for me earlier either but does now. So, R9 M370X has id 1002:6821. That's handled by AMD7000Controller. @ypdeveloper: check that kext for your M375 device id and, if need be, add it to the Info.plist file.

AMD appear to have R9 M370X for Mac, you have PC version R9 M375. http://www.amd.com/en-us/products/graphics/notebook/r9-m200# As indicated by Bronxteck, the Mac models fitted with such GPU are the MBP11,5. As such, use or create a MBP11,5 SMBIOS. http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.5-15-dual-graphics-mid-2015-retina-display-specs.html http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.8-15-dual-graphics-mid-2015-retina-display-specs.html You have to identify the Controller + FrameBuffer kexts that apply to the R9 M370X GPU and check what hardware ids they cover. You may then try to patch the kexts and add your own R9 M375 id. You may consider injecting some of your card details in DSDT if your card is not natively (properly) detected at hardware level. You would normally be able to obtain such graphics card details in IORegistryExplorer (or any similar app). However, please remember that dual GPU being often or usually unsupported in Hackintoshes, you may find yourself stuck with the integrated Iris GPU. You can't exclude that possible limitation.

Bronx meant the parameter in the Energy Savings PrefPane.