Jump to content

maddie

Just Joined
  • Content Count

    41
  • Joined

  • Last visited

About maddie

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

655 profile views
  1. maddie

    OpenCore Discussion

    Z370 you mean, I presume? If so, your Z370 machine is quite similar to mine (ASUS Z370-F). Here is my EFI folder, fill in your SMBIOS info and see it helps. You might need some minor changes to make everything work. My OC could be slightly older than yours, 0.5.1 still, but right before the "MinKernel/MaxKernel" commit. So if you're gonna test it out I would suggest you replace the whole thing, and upgrade later if you want. EFI.zip EDIT: It doesn't have the Thunderbolt ACPI patch since my board doesn't have TB. You might have to add it yourself.
  2. maddie

    OpenCore Discussion

    1. Try to enable Booter->Quirks->AvoidRuntimeDefrag. 2. Which system is this EFI for? You have three in your signature. 3. Some options seem to be missing from your config.plist. Start fresh with the SampleFull.plist corresponding to your OC 0.5.1 build, or compare with it and add missing options. 4. I see you have DSDT.aml defined in the ACPI->Add section, but the file seems to be missing. And DSDT patching isn't recommended anyway. 5. You have multiple ACPI renames in place, and most of them shouldn't be needed, I would suggest you start with no renames at all and fix them one at a time. 6. The `Fix RTC _STA` should be achieved by using SSDT patch provided in OpenCorePkg->Docs->AcpiSamples 7. Although I'm not sure about the ACPI->Block section, I would suggest you disable them until you're sure that it is absolutely required to boot 8. In OC 0.5.1 you shouldn't use AptioMemoryFix since its functionalities are mostly merged into OC and some separated in FwRuntimeServices. Just include FwRuntimeServices and enable the Booter quirks. You can find detailed information in the Configuration.pdf That's all I can see in a glance for now..
  3. maddie

    OpenCore Discussion

    OK, so I've decided to upgrade all my Hacks to Catalina Beta. My ROG rig updates perfectly, and my Z97-A rig updates fine with the secondary monitor turned off (still have no clue what could cause the problem). And as for the Deskmini, this is more of a PSA than an issue: I've reported that the Deskmini 310 rig cannot run macOS updaters or installers at all before, as it reboots instantly right before the installer UI loads on screen. Since this machine will not have any display output with CSM disabled, I have to leave it enabled to make it work. Then it hit me, what if the problem is something related to the CSM? Then I enabled 'ProtectCsmRegion' quirk in OC, and all of a sudden, the update installer runs just fine! Hope that it can help others that have the same problem as me!
  4. maddie

    OpenCore Discussion

    It seems that on some Asrock boards, CSM needs to be Enabled. At least that's how yours and my Deskmini build behaves. My Deskmini won't even have proper graphics working on boot with CSM off (black screen, no signal from DP/HDMI).
  5. maddie

    OpenCore Discussion

    Hmm.. I guess it doesn't always work for everyone with similar setup. But I saw your uploaded config.plist has SanitiseClearScreen set to True so I thought you could give it a shot. UIScale works only when the resolution is correct I think, or it will only make the logo look even bigger.
  6. maddie

    OpenCore Discussion

    Hmm, then I have no clue now It was the same for me too, working in older OC, after updated to 0.0.4 with FwRuntimeServices, it's not working. But that disabling that option indeed solves my problem, so.. ¯\_(ツ)_/¯
  7. maddie

    OpenCore Discussion

    @MacProDude @obus I had the same problem with my Vega 64 (the iMacPro1,1 build in my signature). I solved it by disabling SanitiseClearScreen, but maybe there's some other configuration that might affect it. This is my config.plist with the PlatformInfo section removed, for your reference.config.plist config.plist
  8. maddie

    OpenCore Discussion

    Hey, try disabling SanitiseClearScreen in UEFI->Quirks, that's what fixed for my Vega 64. And Misc->Boot->Resolution, just set it to "Max". "WxH" is not a valid value, what @NorthAmTrans means is that setting it to a specific resolution that fits your screen. Also, since you're using a 4K display, leave UIScale to 02
  9. maddie

    OpenCore Discussion

    Haven't read the code but my guess is the log was in-memory and the memory allocated was set to zero before being written to. Writing the whole memory range into the file results also the unused zero'ed memory being included, so it should be safe to ignore.
  10. maddie

    OpenCore Discussion

    What problem did you encounter when you use createinstallmedia method? I think I have yet to see you tell us what's going wrong with it. OK, my bad. The pictures didn't load when I posted above. It's the Z390 rig in your signature? Can you post your OC EFI folder?
  11. maddie

    OpenCore Discussion

    Totally missed this. I think those warnings should be fine as long as you have working NVRAM. I think it's just being verbose telling you that the NVRAM->Add/Block sections in your config.plist are being parsed. As for the APFS volume scanning, it's fine, don't worry about it.
  12. maddie

    OpenCore Discussion

    Make sure that XHCI hand-off is enabled in your BIOS
  13. maddie

    OpenCore Discussion

    You mean the low resolution first stage boot logo? I've fixed it, disabled SanitiseClearScreen option and it worked perfectly.
  14. maddie

    OpenCore Discussion

    Always read the configuration carefully for every option in the config.plist. I know it's quite tedious, but it's necessary You have a very similar build as mine, I have high hopes that it would work. Good luck!
  15. maddie

    OpenCore Discussion

    To be brutally honest, it doesn't seem that you put much effort into your config.plist :x After each OpenCore update, you have to check the Configuration.pdf from the repository to see if there's any changes to the config.plist. Like the Booter quirks I've mentioned, which is new in v0.0.4, was missing in your config.plist. It seems your version was from on or before v0.0.3, which also lacks the AvoidHighAlloc UEFI quirk. I've added them for you and enabled some useful options in it. You might want to take a look before you're applying the changes. config.plist
×