 |
I've come across this error before, on a different Sandy Bridge build that I tried to install High Sierra 10.13.6 on using OpenCore. I'm certain it's an OpenCore issue, because after having no success solving it on that box, I gave up, deleted the entire OpenCore EFI on my USB stick, installed Clover to the EFI instead, and the High Sierra/Sandy Bridge install went from start to finish without any drama -- or this error message: I imagine I can install High Sierra on this box using Clover once again, but I want to do an OpenCore Sandy Bridge build this time. CASE: Mini-Box m350 • MOBO: AsRock H67M-ITX • CPU: i3-2125 • OC version: 0.6.6 • Kexts: RealtekRTL8111-V2.2.2; AppleALC; VirtualSMC; Lilu; WhateverGreen; USBInjectAll (per Dortania Guide, which says it's needed because "AsRock is dumb"); XHCI-Unsupported; BIOS: v.2.10 DRIVERS: Default recommendations. Using Duet package & HFSPlusLegacy, also OpenUsbKbDxe I followed Dortania's Sandy Bridge guide to the letter when setting up my config.plist, including correct DeviceProperties, SMBIOS, Quirks, BIOS settings & SSDT (only have SSDT-EC-DESKTOP at this point). I did enable the HD3000 Quirk under ReservedMemory and am having no issues with iGPU graphics at this point. NOTE: The only changes I made to the default Sandy Bridge recommendations were to add the XHCI-Unsupported kext, and toggle the Quirk "ReleaseUSBOwnership" from "False" to "True," since at first attempt on verbose boot I got a screen full of garbled text and a Stop sign right after I saw the line, "Unable to obtain USB ownership from BIOS" or something like that. So I shut down, added XHCI-Unsupported and changed that Quirk boolean in my config. My USB Installer booted up fine afterward and took me to the Installer GUI. The install was proceeding smoothly until the fatal error with 2 minutes remaining. I re-tried the install and got the same error. Next, I went into Disk Utility, reformatted the disk and started the install from scratch. Still getting the same error. The Troubleshooting Guide says this issue occurs when macOS is attempting to write variables to NVRAM. It suggests making the following changes to the NVRAM section of the config.plist (which I did): LegacyEnable -> YES LegacyOverwrite -> YES WriteFlash -> YES (this was already set that way) But this didn't do anything to help the install go any further. It's still stalling at 2 minutes remaining. The motherboard originally shipped with BIOS v.1.30. It had been upgraded to v2.10. There is a 2.20 version on the website, but nothing lower than that available (in the event I wanted to revert to an older BIOS version to see if that would help the install to go through, as I recently did on a Haswell Big Sur installation. However, that Big Sur install was on an ASUS board with previously-discussed NVRAM issues on several reddits here. I haven't come across anything similar for AsRock). Any suggestions as to what I might try next? Besides upgrading the BIOS in the hope that might make any difference? Or is there something obvious I'm missing? And why would Clover not fail in this instance like OpenCore does? [link] [comments] |
Comments
Post a Comment