Oh that's such a bummer that I missed that. The BIOS was changed three months ago before logging into this forum, sorry I was not clear about that.
I will try to revert to the F21 version and will also try the EFI and report back.
Removing the AMD card and changing the device properties results in a frozen screen and error when booting. This appears to be the same error as before unfortunately.
I flashed BIOS to the latest version - F22 - using the current BIOS file from the Gigabyte site. Could the file have somehow been corrupted? The BIOS interface seems normal when scrolling through the menus.
Should I downgrade to the F21 version?
Ok, I have been using this AMD card for 3 years with my Mojave build. I pulled the card from that build, and plugged it into this current build. So I know the card did work with no issues for a while.
I have not tried it on any Windows systems though.
I restored default settings to BIOS, then updated as you suggested. I also went in and confirmed the setting for iGPU was auto.
I unplugged the video cable from the motherboard, and used the graphics card but only have a black screen - even after rebooting and trying both displayport and hdmi...
Copied the new EFI onto the drive. Upon boot I am showing a repeating loop of the same error onscreen verbose:
gui/o [100002] <warning>: failed lookup: name = com.apple.dock.fullscreen, requestor = recoveryosd[70] error = 3: No such process
there was no error log entry note created though.
I...
Ok I have started all over again, with OC 0.8.3 debug
ocvalidate now shows no errors
I am encountering this error in my log now when I try to boot:
39:210 00:051 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
39:261 00:050 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
39:312 00:051 OCSMC...
ocvalidate and opencore definitely match - 0.8.4 debug for both.
The original .plist file that I am working from was uploaded by another member here who had the same build as me. I had hoped that this would save time by working from their existing edits, given that they also mapped usb and...
Ok I do see it in the Kernel section in the sample.plist file, but when I added the "child" that's when I received an additional error while also maintaining that same error.
I will follow up on Feartech's recent comment and see if that works.
When I edited the .plist file for the first error and then re-ran ocvalidate, the error is still there:
OCS: Missing key CustomPciSerialDevice, context <Quirks>!
*and* now there is an additional error:
OCS: No schema for CustomPciSerialDevice at 20 index, context <Quirks>!
Is this a normal...
Thanks for your reply.
I am still confused as to how to make these changes.
When comparing my .plist to sample.plist:
I checked every "quirks" folder in the .plist file but I am not able to find CustomPciSerialDevice nor am I able to find how or where to add it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.