Contribute
Register

Recent content by PikeRAlpha

  1. PikeRAlpha

    Intel i219 Ethernet Drivers for Skylake / 100 Series Motherboards [TESTING]

    Note: The AppleIntelE1000e.kext need more love. More patching and I will upload mine when I am back home again.
  2. PikeRAlpha

    Testing Thread: Skylake Platform in OS X

    No problem. Works like a charm.
  3. PikeRAlpha

    Solving NVIDIA Driver Install & Loading Problems

    Solving NVIDIA driver install problems I'd like to ask you, kindly, to link to the original fix (2) for the black screen issues people here (1) were having, and to add appropriate credits for my work. Thank you! 1.)...
  4. PikeRAlpha

    Testing Thread: Skylake Platform in OS X

    You can drop specific SSDT tables in boot loaders, like the one I mentioned (SaSsdt.aml) and dropping this table can cause (boot) issues. In short. Only drop ACPI tables if you know what you are doing.
  5. PikeRAlpha

    USB 3.0 DSDT mods

    RehabMan is right. RefOf(AAPL) is not correct in my example, but it works in other cases (where it can be used) I just forgot to change it. And yes you can use something like this: Method(_DSM, 4, NotSerialized) { If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) } Return...
  6. PikeRAlpha

    Mavericks: Native CPU/IGPU Power Management

    Right. This shows me that the UEFI BIOS error you reported here, is not there. And yes please. Do fix the UEFI BIOS settings, until boot loaders start to do this for you, but remember what I said: set the first turbo ratio to clock frequency + 1 which in your case is 36 is it not? Also. Don't...
  7. PikeRAlpha

    Mavericks: Native CPU/IGPU Power Management

    User error. I said: "The first turbo ratio should be set to 36…" but you've set the fourth turbo ratio to 36. Basically limiting the turbo ratios. Look here: AICPUPMI: CPU Maximum Turbo Frequency........: 3600 MHz And you get fewer P-States now, which is correct, but the reason for it is that...
  8. PikeRAlpha

    Mavericks: Native CPU/IGPU Power Management

    You have a 3.5GHz processor and thus you should use that and nothing else. Also. The first turbo ratio should be set to 36, manually, because 'Auto' is still not functioning properly. Look here: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727 With that even a single core will run at 3.9 GHz...
  9. PikeRAlpha

    Mavericks: Native CPU/IGPU Power Management

    I looked at the MSR log from AppleIntelCPUPowerManagementInfo.kext and the only things that triggered my attention is the turbo ratio's. All of them being set to 39 is not optimal, because then any turbo request will result in 3.9 GHz. Not to mention that Apple's power management relies on some...
  10. PikeRAlpha

    SSDT generation script (Ivybridge PM)

    Correct!
  11. PikeRAlpha

    SSDT generation script (Ivybridge PM)

    I'm not even sure if that can be done with a non-K model. p.s. You want people here to guess how you fired up ssdtPRGen.sh (with what arguments) and what the output is?
  12. PikeRAlpha

    SSDT generation script (Ivybridge PM)

    Fixed in version 8.4 Thank you for reporting this! TIP: Whenever someone run into these two lines: Then your CPU model is not detected. Meaning that you have the use the script arguments until I fixed it.
  13. PikeRAlpha

    AppleIntelCPUPowerManagementInfo.kext (MSRDumper successor)

    I have an updated version of AppleIntelCPUPowerManagementInfo.kext available for download here: https://pikeralpha.wordpress.com/2013/12/29/appleintelcpupowermanagementinfo-kext/ Please use that version to see if it is working for you, and when it does/or not, then please report back to me...
  14. PikeRAlpha

    SSDT generation script (Ivybridge PM)

    I fixed a typo in the script and it should now work. p.s. Always provide the full output including the command used to fire up ssdtPRGen.sh
  15. PikeRAlpha

    RevoBoot: Frequently Asked Questions

    We have a RevoBoot UEFI version for some time already, but that won't become publicly available. There is no need for it. Clover appears to be working fine for most people, and I simply don't have time to support it so... I guess that makes it a definite no. @PJALM, I have patched UEFI BIOS...
Top