Jump to content
  1. Jeffrey.C

    Jeffrey.C

  2. Onixs

    Onixs

  3. shiecldk

    shiecldk

  4. styrian

    styrian

  5. StoneTemplePilots

    StoneTemplePilots

  6. SUN_sw1

    SUN_sw1

  7. bcc9

    bcc9

  8. Gringo Vermelho

    Gringo Vermelho

  9. qwerty12

    qwerty12

  10. tonydickinson

    tonydickinson

  11. VultUx

    VultUx

  12. aplee

    aplee

  13. Lkr

    Lkr

  14. Dr. Hurt

    Dr. Hurt

  15. Doublepranks

    Doublepranks

  16. xtraa

    xtraa

  17. tranduyquang

    tranduyquang

  18. Tyler Worth

    Tyler Worth

  19. sea_man

    sea_man

  20. 459below

    459below

  21. beta992

    beta992

  22. K0gen

    K0gen

  23. The Real Deal

    The Real Deal

  24. bdv

    bdv

  25. k3nny

    k3nny

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By IOIIIO
      It took some messing around, but I have made a kext patch which can be used as a superior alternative for NullCPUPowerManagement.kext.

      Since it still allows AICPM to load, we can now load X86PlatformPlugin and by extension AGPM on a system where CPU PM doesn't work. This is useful on for example AMD systems, where CPU PM cannot be enabled properly.

      So far tested on Catalina and High Sierra, but should also work on other versions, and is reported to give very decent performance improvements when paired with an appropriate SSDT-PLUG SSDT and AGPM injector kext.
       
      Does not work in combination with NullCPUPowerManagement.kext
       
      From: D0 05 00 00 84 C0 74 46 E8 To: D0 05 00 00 84 C0 EB 46 E8 On: com.apple.driver.AppleIntelCPUPowerManagement  
    • By Majed DH
      Hi everyone. 
      I have HP 15-da0xxx series laptop. i got macos mojave installed on it. but I was trying to get my intel graphics working but i couldn't change dmvt preallocation. 
      So I updated the bios (unfortunately). And since then i could not boot any version of clover. 
      I tried two versions that were working and even an installer that worked before is not working:
       
      I searched alot about the error and found nothing relared to macos or hackintosh..  would it be solved by patching the dsdt? 

      Any suggestions people ? 
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
×