- Joined
- Aug 13, 2011
- Messages
- 55
- Motherboard
- Gigabyte GA-Z68X-UD4-B3
- CPU
- i7 2600K
- Graphics
- RX 560
Same problem with a Haswell CPU on a Gigabyte Z87 motherboard. Also solved by disabling BootProtect.
FYI, I filed a bug report - it was instantly closed, on the basis that this is a BIOS problem. I do think that the guides should be updated to specifically warn of the Haswell issue, but it doesn't look like that's going to happen.Probably best to file a bug report with OC devs I guess, with a complete log file. Just checked the bug tracker, and no one has reported this issue...
I think it's slightly unfair to say its a bad feature if no one has told the devs that it's broken, especially if only on some "older" motherboards (not that Z97 is that old) which the devs themselves probably don't use anymore.
Hi Danny,I've been using a hackintosh with clover for a long time now and decided to try opencore. The installation went smoothly and everything is working well except for my bios. Now with opencore, when I try to access my bios, I'll get a blackscreen with an underscore "_" flashing on the top left. I've read that people had this issue but trying things like a CMOS reset didn't fix it.
The only way I fixed it was removing all my drives, and flashing the latest bios version with Q-Flash and it worked again. Booting into windows and back into my bios worked perfectly, except when I connected my opencore drive and booted into macOS. Booting back into my bios results in the same problem. Any luck on this? I'm using opencore 0.6.1
Motherboard: GA-Z97X-UD5H rev 1.1
Processor: i5 4690k
GPU: iGPU
Yeah, I saw.FYI, I filed a bug report - it was instantly closed, on the basis that this is a BIOS problem. I do think that the guides should be updated to specifically warn of the Haswell issue, but it doesn't look like that's going to happen.
Sorry, I don't know. But I think the warning would be a very good idea.Yeah, I saw.
Do you know if Haswell laptops have this, or if updated BIOSes have this issue?
Was gonna merge this in: https://github.com/dortania/OpenCore-Install-Guide/pull/173
The BIOS might not be liking an RTC write - could try using Kernel->DisableRtcChecksum. I think it only became an issue in 10.15.4 iirc? It blocks writing to locations 0x58-0x59 in the RTC.I would be interested to hear what BIOS version (F3-F5) people are using for GA-Z97N Gaming 5 (Rev 1.0) with OpenCore. I'm wondering if there's a stable set up for this board.
One thing I've noticed is that if the system starts up and the GPU fan remains at full speed the POST has failed and I have to wait around 10mins before booting again. Once the system settles and boots into macOS its stable and will wake from sleep without any issues. If I have a real problem booting I disconnect the clock battery for a period (couple of hours or overnight) and then the system will boot.
The simple fix would be to go back to Clover but as there seems to be a transition to OpenCore happening I think its best to keep with it and learn the new quirks.
The devs know and even warn about it, read the latest OpenCore setup tutorial. At this stage they can do nothing to rectify it as it seems to be a bios, chipset anomaly that is not widespread and manifests itself in in some Haswell incarnations only.Probably best to file a bug report with OC devs I guess, with a complete log file. Just checked the bug tracker, and no one has reported this issue...
I think it's slightly unfair to say its a bad feature if no one has told the devs that it's broken, especially if only on some "older" motherboards (not that Z97 is that old) which the devs themselves probably don't use anymore.
I second @Henties. I would strongly suggest avoiding Bootstrap. Windows 10 in the other hand will give you a hard time if dual booting using OpenCore without Bootstrap, specially after windows updates since it will change and even disable OpenCore booting entries. For me it has been a challenge from time to time. Fortunately I don’t use Windows a lot. As soon as I’m able to boot BS using Clover, for sure I’ll revert to Clover or at least install Clover in a separate EFI partition.The devs know and even warn about it, read the latest OpenCore setup tutorial. At this stage they can do nothing to rectify it as it seems to be a bios, chipset anomaly that is not widespread and manifests itself in in some Haswell incarnations only.
Greetings Henties