Search results

  1. slead

    [solved] Boot error after upgrade to newest BIOS with AGESA v2

    upload your config.plist
  2. slead

    Big Sur Beta 3

    Worked for me by just clicking on update, from the Software Update menu in Settings. While updating, it hangs for a while (maybe 2 or 3 min) at Forcing CS_RUNTIME, but then it continues and restarts twice and boom, finished.
  3. slead

    Catalina 10.15.6

    The same here, just clicked on the update button. It downloads the update and restarts the computer, then you select macOS Installer from the OC boot menu and it starts the update. After that it restarts again and boom...all good. Took around 20 min.
  4. slead

    Big Sur - Opencore setup - need help please!

    last try from me...
  5. slead

    Big Sur - Opencore setup - need help please!

    I downloaded your GoodEfi.zip and went through it. I have made some modifications. This is what I have done: RebuildAppleMemoryMap = False SignalAppleOS = True SyncRuntimePermissions = False You have 2 kext files for your ethernet, I removed one. In Tools, I removed everything except...
  6. slead

    Big Sur - Opencore setup - need help please!

    Upload your latest EFI folder as a zip file.
  7. slead

    Big Sur - Opencore setup - need help please!

    Download the latest nightly build for your kexts from here. Download the latest nightly build for opencore and drivers from here. Then try it again with the following boot arguments: -lilubetaall vsmcgen=1 -disablegfxfirmware good luck
  8. slead

    Big Sur - Opencore setup - need help please!

    What kind of error message do you get?
  9. slead

    I might attempt to get the new mac os running on ryzen

    Here is my EFI folder. The only thing I have done is I removed the platform info (replaced it with sort of random stuff), just fill in your generated SMBios. good luck
  10. slead

    I might attempt to get the new mac os running on ryzen

    I have it running. It is the Beta 2. I used the latest builds (nightly builds) from OC, Lilu, VSMC and WEG. Also used these boot arguments: -lilubetaall vsmcgen=1 -disablegfxfirmware I have the SMBios of the Mac Pro 2019 and tried to use the MacProMemoryNotificationDisabler for the memory...
  11. slead

    macOS Big Sur is on AMD

    Already checked it out and tried all the combinations. I thought, maybe it is because of the USB stick (Kingston 32GB) but then I put the Catalina installer on it for a test, worked just fine. I am now testing another USB stick and I will also try to get everything from the latest builds...
  12. slead

    macOS Big Sur is on AMD

    I have the exact same error. Will try it later with latest builds of OC etc.
  13. slead

    Setting up after installation

    Your config file seems fine tbh. The only thing that did pop into my eye was in: Kernel > Add #4 USBPorts.kext here the ExecutablePath is missing And the same is true with #7 AGPMInjector.kext, here the ExecutablePath is also missing. Anyway, the only thing that I would suggest is to compile...
  14. slead

    Setting up after installation

    could you upload your config file again?
  15. slead

    Ryzen 9 3900x x570 - [EB|#LOG:EXITBS:START] - Please help

    I had the same error. Everything was working fine, but when I updated the BIOS yesterday I had that error. Quick google search revealed that I had to set RebuildAppleMemoryMap and SetupVirtualMap to NO. I changed that on my USB stick, booted and it worked. I then changed that also in the config...
  16. slead

    macOS Big Sur is on AMD

    The only thing that I can then think of is:. 1. compile and add your SSDT-EC.aml in the ACPI folder and the config file 2. Try adding npci=0x2000 to your boot-args good luck
  17. slead

    macOS Big Sur is on AMD

    In your config file, set the following: Booter > Quirks: RebuildAppleMemoryMap = False If that does not work, then do the following too: SetupVirtualMap = False good luck
  18. slead

    Setting up after installation

    I compiled it for you. I am confused by your question, do you use clover or OpenCore?
  19. slead

    Install freeze

    First try this: in boot-args add the following npci=0x2000 If no success, try this: In your EFi > OC > Tools folder, delete everything except OpenShell.efi If you have a nvme drive, add NVMeFix.kext to your kexts and also to your config file. good luck
  20. slead

    Stuck on this part for months.

    I downloaded your EFI folder and looked at it. I would suggest two things. 1. You indicated that your storage device is a m.2 NVME but you don't have the NVMeFix.kext in your Kexts folder an also not in your config file. 2. You don't have the SSDT-USBX.aml file in your ACPI folder and thus also...
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.