- Mar 6, 2013
- Gigabyte X299X Designare 10G
- AMD 6900XT
- Mobile Phone
If the system shuts down 8-10 seconds after you start booting, and when it comes back you get a BIOS error (and if you check the BIOS, you'll see your RAM XMP is not applied, and any overclock settings you might have had are not applied) then that's definitely the BIOS boot bug.@TheBloke
Question about the DigiCal TS3 Pro.
So I got it today, and first booted with my Sonnet Thunderbolt on TB Port 1, CalDigit on TB Port 2 [No Displayport Connected]
When getting in OC and selecting the Boot Drive, Apple logo shows up and reboot system, with BIOS Error.
Changed the ports so CalDigit on TB Port 1 and Sonnet on TB Port 2, System boots fine.
CalDigit is seen in IOREG and fully connected.
Then system shutdown, plugged the DP from the GPU to DP In of the TB 1 Port and Screen on DigiCal.
Getting image on the screen, when OC and selecting Boot drive, got Apple logo and directly system reboot with BIOS Error and this stays happening.
Is this the so called Boot BUG of the BIOS ?
Most likely the reason you are seeing it with some TB configs and not others is that the bug is timing related. If boot happens quicker, you can avoid the bug. So anything that slows down booting - as having an extra TB device connected could do - can trigger it. For example on my system I found the bug always triggered once I added my Intel X520 10GBe NIC; presumably its UEFI drivers slowed down the firmware enough to cause the bug to always trigger.
This can be avoided in one of two ways:
1. Set ConnectDrivers=false in OpenCore config.plist. This avoids the bug, but also prevents the loading of HfsPlus.efi, meaning you can't boot DMGs like the macOS installer. But it won't be an issue for booting an existing installation.
2. Use the patched OC 0.6.7 I uploaded last month - this allows ConnectDrivers=true.
I've applied the patch for OpenCore 0.6.8 and am using it myself, but I haven't uploaded it here yet. I'll try and do that later today.