- Joined
- Aug 17, 2010
- Messages
- 175
- Motherboard
- Z390 Aorus Elite-CF
- CPU
- i7-8700K
- Graphics
- RX 580
- Mac
- Mobile Phone
I have the latest version of Big Sur Beta 11.0.1 (20B5012d) with OpenCore 0.6.3 which is working perfectly. However, I noticed a new problem after the last update.
Upon using Hackintool I noticed that the "Boot" tab doesn't recognize the bootloader and I get this:
I don't have Clover anywhere on my computer/disks. It's a completely wiped clean installation of Big Sur using OpenCore. And this is the only disk with a Mac. There are two other disks that have Windows and Ubuntu respectively.
If I manually change Bootloader dropdown to OpenCore, I see this:
Also, when I try opening OpenCore Configurator, I see this message:
The bootloader looks like it is not installed or your NVRAM isn't native.
This problem is new because in previous versions Hackintool did pick the right bootloader and OpenCore Configurator never complained. The problem hs started only after a recent clean install of Big Sur.
Also, I know that I have NVRAM, because, I checked for it:
1. Manually set a variable with sudo nvram foo=bar
2. Used nvram -p | grep -i "foo" and got foo bar as output
3. Rebooted, and tried nvram -p | grep -i "foo" again and got back foo bar again
Any suggestions as to what I might be missing?
Also, attached is my config.plist (personal info removed) in case that helps.
Upon using Hackintool I noticed that the "Boot" tab doesn't recognize the bootloader and I get this:
I don't have Clover anywhere on my computer/disks. It's a completely wiped clean installation of Big Sur using OpenCore. And this is the only disk with a Mac. There are two other disks that have Windows and Ubuntu respectively.
If I manually change Bootloader dropdown to OpenCore, I see this:
Also, when I try opening OpenCore Configurator, I see this message:
The bootloader looks like it is not installed or your NVRAM isn't native.
This problem is new because in previous versions Hackintool did pick the right bootloader and OpenCore Configurator never complained. The problem hs started only after a recent clean install of Big Sur.
Also, I know that I have NVRAM, because, I checked for it:
1. Manually set a variable with sudo nvram foo=bar
2. Used nvram -p | grep -i "foo" and got foo bar as output
3. Rebooted, and tried nvram -p | grep -i "foo" again and got back foo bar again
Any suggestions as to what I might be missing?
Also, attached is my config.plist (personal info removed) in case that helps.
