- Joined
- Mar 6, 2013
- Messages
- 266
- Motherboard
- Gigabyte X299X Designare 10G
- CPU
- i9-10980XE
- Graphics
- AMD 6900XT
- Mobile Phone
Hey guys.. you're not going to believe this.
I think I've found the fix for our Designare 10G boot bug. A vanilla OpenCore fix, not requiring @JTR 's patch.
Set ConnectDrivers to false. That's it.
I've only tested it a couple of times, and only in the latest OpenCore 0.6.8. But I've booted from both USB and SSD using this change, and it boots absolutely fine with normal BIOS settings. No reset after 10 seconds, no safe mode.
From the manual:
"ConnectDrivers: This option is useful for loading drivers following UEFI driver model as they may not start by themselves. Examples of such drivers are filesystem or audio drivers. While effective, this option may not be necessary for drivers performing automatic connection, and may slightly slowdown the boot. Note: Some types of firmware, particularly those made by Apple, only connect the boot drive to speed up the boot process. Enable this option to be able to see all the boot options when running multiple drives."
So without this set I suppose there could theoretical be some side effect, like not being able to boot from certain drives. But I've not noticed anything yet - I get my normal macOS (NVMe drive 1) and Windows (NVMe drive 2) boot entries. It also saw the EFI on my USB stick.
Further time and testing is needed to ensure it definitely solves the problem forever. But so far it's looking great.
EDIT: This does cause at least one problem. With ConnectDrivers=false, it appears not to be possible to boot the macOS installer from a USB drive. You can boot from a USB EFI OK, but it won't find the "Install macOS Big Sur" DMG on the USB. Therefore if you were going to use this parameter for a new install, you'd first need to boot with ConnectDrivers=true (and thus hit the BIOS safe-mode issue, and proceeding at stock speeds with no XMP). Once macOS was installed, you could then set ConnectDrivers=false and booting would be fine after that.
Having thought about this more overnight I've realised that it probably should have been obvious that this parameter would affect things, as @JTR 's patch is to OcDriverConnectionLib, which is I believe disabled by ConnectDrivers=false. So setting that parameter bypasses the issue, but at the expense of the ability to boot from a USB installer. Whereas JTR's patch fixes the issue completely - but currently at the cost of requiring an external patch to standard OpenCore.
I think I've found the fix for our Designare 10G boot bug. A vanilla OpenCore fix, not requiring @JTR 's patch.
Set ConnectDrivers to false. That's it.
I've only tested it a couple of times, and only in the latest OpenCore 0.6.8. But I've booted from both USB and SSD using this change, and it boots absolutely fine with normal BIOS settings. No reset after 10 seconds, no safe mode.
From the manual:
"ConnectDrivers: This option is useful for loading drivers following UEFI driver model as they may not start by themselves. Examples of such drivers are filesystem or audio drivers. While effective, this option may not be necessary for drivers performing automatic connection, and may slightly slowdown the boot. Note: Some types of firmware, particularly those made by Apple, only connect the boot drive to speed up the boot process. Enable this option to be able to see all the boot options when running multiple drives."
So without this set I suppose there could theoretical be some side effect, like not being able to boot from certain drives. But I've not noticed anything yet - I get my normal macOS (NVMe drive 1) and Windows (NVMe drive 2) boot entries. It also saw the EFI on my USB stick.
Further time and testing is needed to ensure it definitely solves the problem forever. But so far it's looking great.
EDIT: This does cause at least one problem. With ConnectDrivers=false, it appears not to be possible to boot the macOS installer from a USB drive. You can boot from a USB EFI OK, but it won't find the "Install macOS Big Sur" DMG on the USB. Therefore if you were going to use this parameter for a new install, you'd first need to boot with ConnectDrivers=true (and thus hit the BIOS safe-mode issue, and proceeding at stock speeds with no XMP). Once macOS was installed, you could then set ConnectDrivers=false and booting would be fine after that.
Having thought about this more overnight I've realised that it probably should have been obvious that this parameter would affect things, as @JTR 's patch is to OcDriverConnectionLib, which is I believe disabled by ConnectDrivers=false. So setting that parameter bypasses the issue, but at the expense of the ability to boot from a USB installer. Whereas JTR's patch fixes the issue completely - but currently at the cost of requiring an external patch to standard OpenCore.
Last edited: