- Joined
- Mar 6, 2013
- Messages
- 266
- Motherboard
- Gigabyte X299X Designare 10G
- CPU
- i9-10980XE
- Graphics
- AMD 6900XT
- Mobile Phone
0.6.3 is working fine for me and many other people.who's able to upgrade OC 0.6.3?
What problem are you having?
0.6.3 is working fine for me and many other people.who's able to upgrade OC 0.6.3?
You'll need to provide a lot more information than that if you want someone to help you.not able to boot it with x299x aorus master
You're missing SSDT-RTC0-RANGE-HEDTstuck here
Ah yes, the EFIs in this thread have all had SecureBootModel at Default. Strange it's causing you problems, it worked fine for me and others. Maybe related to your WiFi card, given that's causing problems elsewhere apparently.Good day @TheBloke . Yes I edited the smbios and put in my machine's personal info. i went in and edited each that was labeled "changeme" with my own.
The other things I changed was SecureBootModel with value Disabled and another change I can't currently recall, as it wouldn't allow the SSDT's to run without them. I was running into the following error (which I eventually got past):
"CSB: No suitable signature - Security Violation OCB: Apple Secure Boot prohibits this boot entry, enforcing! OCB: LoadImage failed - Security Violation"
Yes, setting AllowNvramReset to true will enable the Reset NVRam option in the BIOS boot picker menu, allowing you to reset NVRAM at any time from the OpenCore menu. I added a comment in the latest EFI to point it out.Hmmm This i don't believe I did (I saw your next instructional post response to me. I'll be sure to do that next time around). Can you clarity how this is done for me? Are you reffering to "AllowNvramReset"?
When installing Windows I recommend doing so with no other SSDs installed, otherwise it may put its bootloader on the wrong drive. It did that for me - I installed Windows with my macOS NVMe also installed, and it put the Windows bootloader on the macOS drive instead, probably because it was the first drive on the system.So this one is an interesting one. I have my MacOS on a gygabyte ssd and my windows on a sabrent ssd. I've always found interesting that when I installed windows, my bios would still display/recognize my windows drive (installed on my sabrent ssd) as a gigabyte partition (where macOS is installed). Perhaps it was an error on my part during installation. I am planning on reinstalling windows shortly, so i'll be able to find out if it was user error soon enough.
Do you have a Broadcom wireless device then? If not, just disable that kext. If you do, then that's odd it's causing problems. I don't have a Broadcom wireless device so I have no experience of how they work and can't test personally.Yes I was referring the Airportbrcmfixup kext...it would instruct the computer to reboot, and unfortunately never stop rebooting. i'll disable it just to be safe next time till get the system booting up. Then enable it and see what behavior it does after.
Yes, I recommend keeping a record of the EFI partitions you try. I take a backup before any major change.I was booting an existing installation of Mojave. And yes, I had my thunderbolt devices connected and USB drives, but only PCIE devices were my Wifi card and GPU. As the EFI I created crashed for the upgrade crashed, I didn't save it. However, moving forward I will create a folder and keep track of each specific EFI I use regardless if it works or not.
--------------------------------------------------
Now onto your next post (the instructions). Great load of information. I haven't read through all of it, but I'll print it out just to make sure i'm not missing anything. Guess I'll report back in a couple days. Again, many many thanks @TheBloke . Grateful for all your help!
Do you have a Working OC EFI for Catalina and big sure you could share with me? I've been using the one in the (with updated kext) op (that works fine with a little tweaking/updating) but I'm trying to update to the latest 0.6.3 and I can boot all but my clover EFI works flawlessly (minus the downsides clover bring). I have the same MB X299X GB 10G with the 5700XT. I tried your TheBloke.OpenCore.0.6.3-DEBUG.EFI.17112020, but I can't get to the Big Sur install screen. It loads everything up (verbose degug) then black screen then shut down. I'm just trying to migrate clover to OC on Catalina first, then move to getting a fully functional Big Sur... I also have your been using your bios version FC3macOSAuto. Im not a newbie at this at all its' just OC the new to me and I've stayed up the last 3 days until 5am just to get OC to work with the least 0.6.3.0.6.3 is working fine for me and many other people.
What problem are you having?
As per reply in other thread: try agdpmod=pikera boot-arg.Do you have a Working OC EFI for Catalina and big sure you could share with me? I've been using the one in the (with updated kext) op (that works fine with a little tweaking/updating) but I'm trying to update to the latest 0.6.3 and I can boot all but my clover EFI works flawlessly (minus the downsides clover bring). I have the same MB X299X GB 10G with the 5700XT. I tried your TheBloke.OpenCore.0.6.3-DEBUG.EFI.17112020, but I can't get to the Big Sur install screen. It loads everything up (verbose degug) then black screen then shut down. I'm just trying to migrate clover to OC on Catalina first, then move to getting a fully functional Big Sur... I also have your been using your bios version FC3macOSAuto. Im not a newbie at this at all its' just OC the new to me and I've stayed up the last 3 days until 5am just to get OC to work with the least 0.6.3.
Thanks in advanced bro for any help, I appreciate it fr.