- Feb 23, 2020
- Gigabyte Aorus Z390 Pro
- i9 9900K
- Mobile Phone
are you sure you have config-lock disabled in bios? on F9i the default is enabled, so you need to go into bios settings and disable it. then save and exit. also, as another poster suggested, turn on verbose boot in your config.plist boot arguments and tell us where the boot stalls.Hi, hope you all had a nice Christmas.
I've used the time to try to get my Mojave system up to date to Big Sur. I managed upgrading with Clover to Catalina but the update to Big Sur failed. So I loaded my Mojave backup back on the system.
Now I'm trying to change from Clover to OpenCore before updating. Somehow I always end up with the white Apple logo on the black screen without any loading bar, and then nothing else happens.
I've followed this this guide and created the config.plist using the provided link and the AMD selection.
Any Idea what I'm doing wrong?Hey there @CaseySJ -and maybe @Stork can weigh-in on this: If I have a binned i9 9900KS that has core-sync ability via its own accord and the BIOS setting, do I still need the Contents/MacOS/CpuTscSync kext? Also, I have a question about a conflict for this dGPU-only setup in relation to the...www.tonymacx86.com
I have some bad news for everyone with a flashed GC-Titan Ridge. Mine has been flashed with NVM 23 (GC-Titan Ridge version 1.0):Just tried NVM23 again, also tried Designare's NVM33 as I saw someone using it on a GC Titan Ridge V1, but still nothing.
Good news — I successfully upgrade to OpenCore 0.6.4 / Catalina. I had been using that set up for a couple days now and it was rock solid.We can certainly go directly to Big Sur from Mojave, but we need to disable CFG-Lock and switch to OpenCore. Hopefully all of the software and plugins you use are or will be compatible with Big Sur soon because Big Sur is just a delightful environment...
Thanks =)@patele ,
I just replaced Clover with OC on Mojave. Here is what helped me:
1. You may want to turn on verbose mode in you config.plist. Load your plist into OC configurator. boot-args values should be listed by selecting one of your UUID's on the left. Modify boot-args string by adding -v to the line. Save your config.plist and reboot. A link below may give you some clue on where in the boot process of macOS you got stuck.
2. Make sure you do not have extra kexts in /L/E and /S/L/E. run: "sudo kextcache -i /" in the terminal. It will give you a list of kexts that are not supposed to be in those 2 directories. I was using the output of the command above to to clean my kexts.
3. sudo touch /System/Library/Extensions
sudo touch /Library/Extensions
Good news — I successfully upgrade to OpenCore 0.6.4 / Catalina. I had been using that set up for a couple days now and it was rock solid.
Bad news — I decided to push my luck a little bit and tried to upgrade to Big Sur. It went through a couple restarts and then unfortunately it hung on the Apple loading screen. I let it sit for about 45 min. If I restart the computer I am presented with the power button error screen, followed by the Apple loading screen where it once again will hang at about 1/3 loaded.
I currently have GC-Titan Ridge v2 that appears to be running properly on MacOS 11.1. I'm running the patched NVM50 firmware. I run a 4K Ultrafine Monitor and CalDigit TS3+ dock on it. Should I look for something particular in my IOREG to see if everything is populating correctly?If anyone is using a flashed GC-Titan Ridge v1 or v2 with Catalina 10.15.7 or Big Sur 11.1 (or later), please let us know if the card works.