GOP is something that we need to look into. I could not get it to work in my early testing.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Awesome news!
Any chance this could activate a TB3 TitanRidge card natively without the windows handshake workaround?
Any chance this could activate a TB3 TitanRidge card natively without the windows handshake workaround?
Guys, Clover and OpenCore won't brick your Macs as long as you keep Brain.app active. If a real Mac gets bricked by those bootloaders it's by enabling Hackintosh specific features or EFI drivers. Just keep your hands off that stuff if you use those bootloaders on a real Mac. Spoofing a different SMBIOS won't do any harm. It doesn't change anything on your machines firmware.
That is correct. This is what I am referring to. Now I am not talking about Opencore I never tested it, but i know clover may cause damages if used incorrectly. The problem is nobody can confirm how to "correctly" use clover on a real mac as it was designed for hackintosh only, but OC was designed for both hacks and real macs so it should be safe to use.
That is exactly how I used it, but it did not help. I noticed it happened when the smbios info was left blank. With previous testing I had copied the cMP 5,1 properties from the real smbios and it was ok. Anyway I will personally stay away from clover.
Correct, obey the native Apple fan profile as per factory setting.
I’ve been trying to get that to work on my 3,1
i can get GOP display on my 3,1 in refind with my stock PC RX 580 but so far I’ve not figured out the magic for it via OC. I even tried launching oc from inside refind and it seems to just hang / black screen and touching the power button results in instant power off vs needing to hold it to force a reboot suggesting it’s hung.
[automerge]1572574337[/automerge]
You should be able to. The block of file vault was just a board id check. But unless you have an EFI flashed GPU in a 4,1/5,1 you won’t have a boot screen for now anyways.
cMP3.1 outputs to GOP on RX-580 with proper efi driver and refind. We never got cMP5.1 work with neither Clover nor refind for the GOP protocol. Have you tried this:
" Boot Properties
- ConsoleMode
Failsafe: Empty string
Description: Sets console output mode as specified with the WxH (e.g. 80x24) formatted string. Set to empty string not to change console mode. Set to Max to try to use largest available console mode.
Note: This field is best to be left empty on most firmwares.
- ConsoleBehaviourOs Type: plist string Failsafe: Empty string
Console control is a legacy protocol used for switching between text and graphics screen output. Some firmwares do not provide it, yet select operating systems require its presence, which is what ConsoleControl UEFI protocol is for.
When console control is available, OpenCore can be made console control aware, and set different modes for the operating system booter (ConsoleBehaviourOs), which normally runs in graphics mode, and its own user interface (ConsoleBehaviourUi), which normally runs in text mode.
- On Apple firmwares ConsoleBehaviourOs set to Graphics and ConsoleBehaviourUi set to Text is supposed to work best."
yes im aware, it’s what I’m using on my 3,1.
going from memory here:
I set ConsoleMode to Max
I set ConsoleBehaviourOs to Graphics
i set ConsoleBehaviourUi to Text
that being said I’ve tried doing these but ive also had zero success getting OC to boot to any OS yet.
![Nick [D]vB](/data/avatars/m/1132/1132239.jpg?1552018909){kind=avatar}
I didn't get UEFI GOP boot-screens on the 2011 iMac, but I tested a very early OC version.
Maybe try it with the AptioFix ? (I think it was required for rEFInd on the 3,1?)
Those SetCon / GOP Tools might be useful to debug this?
forums.macrumors.com
Maybe try it with the AptioFix ? (I think it was required for rEFInd on the 3,1?)
Those SetCon / GOP Tools might be useful to debug this?
Boot menus for graphics output protocol.(AMD only)see page 13
Pardon my ignorance but how do I pass that to the boot efi?
forums.macrumors.com
Mu understand, Command + R only works when your Mac selected to boot to macOS natively. When selected to boot Windows, Linux, or any other boot loader, Command + R won't work anymore.
[automerge]1572619052[/automerge]
Anyway, I found something interesting.
If I leave the APPLE, BOOT, and OC folders in the EFI folder. Then even I perform NVRAM reset, my Mac still default to boot OpenCore. This is handy in some point of view. But can be very troublesome for those who are not prepared for it (or when testing some config that may not work).
|--EFI
| |--APPLE
| | |--EXTENSIONS
| | | |--Firmware.scap
| |--BOOT
| | |--BOOTx64.efi
| |--OC
| | |--ACPI
| | |--Drivers
| | | |--FWRuntimeServices.efi
| | |--Kexts
| | |--Tools
| | |--OpenCore.efi
| | |--Config.plist
But if I further make an EFI folder inside the EFI folder, and put the BOOT folder into it. Then bless the OpenCore.efi but not the partition (Yes, I know, should not do this. However, it works). OpenCore still works as expected. But I can go back to native macOS by performing NVRAM reset.
|--EFI
| |--APPLE
| | |--EXTENSIONS
| | | |--Firmware.scap
| |--EFI
| | |--BOOT
| | | |--BOOTx64.efi
| |--OC
| | |--ACPI
| | |--Drivers
| | | |--FWRuntimeServices.efi
| | |--Kexts
| | |--Tools
| | |--OpenCore.efi
| | |--Config.plist
[automerge]1572619052[/automerge]
Anyway, I found something interesting.
If I leave the APPLE, BOOT, and OC folders in the EFI folder. Then even I perform NVRAM reset, my Mac still default to boot OpenCore. This is handy in some point of view. But can be very troublesome for those who are not prepared for it (or when testing some config that may not work).
|--EFI
| |--APPLE
| | |--EXTENSIONS
| | | |--Firmware.scap
| |--BOOT
| | |--BOOTx64.efi
| |--OC
| | |--ACPI
| | |--Drivers
| | | |--FWRuntimeServices.efi
| | |--Kexts
| | |--Tools
| | |--OpenCore.efi
| | |--Config.plist
But if I further make an EFI folder inside the EFI folder, and put the BOOT folder into it. Then bless the OpenCore.efi but not the partition (Yes, I know, should not do this. However, it works). OpenCore still works as expected. But I can go back to native macOS by performing NVRAM reset.
|--EFI
| |--APPLE
| | |--EXTENSIONS
| | | |--Firmware.scap
| |--EFI
| | |--BOOT
| | | |--BOOTx64.efi
| |--OC
| | |--ACPI
| | |--Drivers
| | | |--FWRuntimeServices.efi
| | |--Kexts
| | |--Tools
| | |--OpenCore.efi
| | |--Config.plist
Last edited:
This is something that I would like to figure out: According to the manual, it is possible for OpenCore to interpret the Apple key combinations. In theory, Command + R is possible through OC. Of course, if pressed too early, the key presses will be captured by the firmware instead, so timing is important.
This is troublesome indeed. It seems that native booting is restored to the first disk that the firmware scans. In my case, this is SATA bay 1, where Mojave is installed. I can see this being a problem if the first disk has the EFI partition where OC is installed.
Hi Nick. I think Aptiofix is included in the AppleSupportPackage. :I didn't get UEFI GOP boot-screens on the 2011 iMac, but I tested a very early OC version.
Maybe try it with the AptioFix ? (I think it was required for rEFInd on the 3,1?)
Those SetCon / GOP Tools might be useful to debug this?
Boot menus for graphics output protocol.(AMD only)see page 13
Pardon my ignorance but how do I pass that to the boot efi?
" AptioFixPkg
AptioFixPkg is now part of AppleSupportPkg and OpenCore, please use them instead:
- AptioMemoryFix.efi is split into OpenCore and FwRuntimeServices.efi.
- AptioInputFix.efi is moved to AppleGenericInput.efi.
- CleanNvram.efi and VerifyMsrE2.efi are now part of AppleSupportPkg."
[automerge]1572621283[/automerge]
Why not installing OC on a USB drive and booting from there. If not needed just remove the drive.
Last edited:
You're right, not sure if this is bonded to the same target usb port/number chosen, but if I don't get wrong when you bless an external usb UEFI bootloader (either pointing to an OSX installation or whatelse), if you plug it before power-on it should always boot from the usb drive, if you unplug it will boot from the internal disk EFI bootloader (typically the apple startup manager).
So this should be safer to avoid a bootloop if some bad config of OpenCore occurs.
Well I made *some* progress I guess... got logging to work with OC, oddly it only seems to detect one of my processors, not both.
GOP display on the 3,1 in OC _almost_ seems to work, meaning i can get the display to be blank vs not even detecting a signal, and OC must have loaded as I can toggle caps lock on / off on the keyboard so the light goes on/off.
it never goes beyond the line of finding 19 potentially bootable systems, so no OS ever loads.
This may be because i set the config.plist to showpicker=yes, but right now I'm out of time to test tonight.
I'm just happy I was able to get it to log something finally.
GOP display on the 3,1 in OC _almost_ seems to work, meaning i can get the display to be blank vs not even detecting a signal, and OC must have loaded as I can toggle caps lock on / off on the keyboard so the light goes on/off.
Code:
00:000 00:000 OC: OpenCore is now loading (Vault: 0/0, Sign 0/0)...
00:072 00:072 OC: Boot timestamp - 2019.11.02 05:37:14
00:129 00:056 OCCPU: Hypervisor: 0
00:181 00:052 OCCPU: Found Intel(R) Xeon(R) CPU X5482 @ 3.20GHz
00:234 00:052 OCCPU: Signature 10676 Stepping 6 Model 17 Family 6 Type 0 ExtModel 1 ExtFamily 0
00:286 00:052 OCCPU: Detected Apple Processor Type: 05 -> 0301
00:345 00:058 OCCPU: Ratio Min 0 Max 8 Current 0 Turbo 0 0 0 0
00:396 00:051 OCCPU: Timer address is 408 from LPC
00:549 00:152 OCCPU: CPUFrequencyFromTSC 3191996938Hz 3191MHz
00:601 00:052 OCCPU: CPUFrequency 3191996938Hz 3191MHz
00:651 00:050 OCCPU: FSBFrequency 398999617Hz 398MHz
00:704 00:052 OCCPU: Pkg 1 Cores 4 Threads 4
00:757 00:053 OC: OcLoadUefiSupport...
00:810 00:052 OCC: Install console control 1 - Success
00:860 00:050 AmiEfiKeycodeProtocol is unavailable on gST->ConsoleHandle - Unsupported
00:913 00:053 EfiSimpleTextInputExProtocol is unavailable on gST->ConsoleHandle - Unsupported
00:965 00:052 gST->ConIn 7E777870 vs found 7E777870
01:018 00:052 OC: Missing GOP on ConsoleOutHandle, will install - Unsupported
01:068 00:050 OCC: Configuring console ignore 0 san clear 0 clear switch 0 replace tab 0s
01:126 00:058 OCC: Configuring behaviour 1
01:179 00:052 OCC: Setting cc mode 0 -> 0
01:234 00:054 OC: Got 1 drivers
01:286 00:052 OC: Driver FwRuntimeServices.efi at 0 is being loaded...
01:354 00:067 OC: Driver FwRuntimeServices.efi at 0 is successfully loaded!
01:408 00:054 OC: Connecting drivers...
01:512 00:104 OC: OcLoadAcpiSupport...
01:563 00:050 OCA: Found 26 ACPI tables
01:615 00:052 OCA: Detected table 50434146 (003030656C707041) at 7F740000 of 244 bytes at index 0
01:667 00:052 OCA: Detected table 54444345 (003030656C707041) at 7F742000 of 83 bytes at index 1
01:720 00:052 OCA: Detected table 54455048 (003030656C707041) at 7F73F000 of 56 bytes at index 2
01:772 00:052 OCA: Detected table 43495041 (003030656C707041) at 7F73D000 of 188 bytes at index 3
01:825 00:052 OCA: Detected table 4746434D (003030656C707041) at 7F73C000 of 60 bytes at index 4
01:875 00:050 OCA: Detected table 54445353 (0074734330757043) at 7F736000 of 326 bytes at index 5
01:927 00:052 OCA: Detected table 54445353 (0074734930757043) at 7F735000 of 843 bytes at index 6
01:980 00:052 OCA: Detected table 54445353 (0074734331757043) at 7F734000 of 71 bytes at index 7
02:032 00:052 OCA: Detected table 54445353 (0074734931757043) at 7F733000 of 823 bytes at index 8
02:083 00:051 OCA: Detected table 54445353 (0074734332757043) at 7F732000 of 71 bytes at index 9
02:136 00:052 OCA: Detected table 54445353 (0074734932757043) at 7F731000 of 823 bytes at index 10
02:188 00:052 OCA: Detected table 54445353 (0074734333757043) at 7F730000 of 71 bytes at index 11
02:238 00:050 OCA: Detected table 54445353 (0074734933757043) at 7F72F000 of 823 bytes at index 12
02:301 00:062 OCA: Detected table 54445353 (0074734334757043) at 7F72E000 of 71 bytes at index 13
02:353 00:052 OCA: Detected table 54445353 (0074734934757043) at 7F72D000 of 823 bytes at index 14
02:404 00:050 OCA: Detected table 54445353 (0074734335757043) at 7F72C000 of 71 bytes at index 15
02:453 00:049 OCA: Detected table 54445353 (0074734935757043) at 7F72B000 of 823 bytes at index 16
02:501 00:048 OCA: Detected table 54445353 (0074734336757043) at 7F72A000 of 71 bytes at index 17
02:554 00:052 OCA: Detected table 54445353 (0074734936757043) at 7F729000 of 823 bytes at index 18
02:606 00:052 OCA: Detected table 54445353 (0074734337757043) at 7F728000 of 71 bytes at index 19
02:658 00:052 OCA: Detected table 54445353 (0074734937757043) at 7F727000 of 823 bytes at index 20
02:711 00:052 OCA: Detected table 54445353 (0000006D50757043) at 7F726000 of 61 bytes at index 21
02:761 00:050 OCA: Detected table 54445353 (6963684161746153) at 7F722000 of 358 bytes at index 22
02:811 00:050 OCA: Detected table 54445353 (0034343838696350) at 7F71D000 of 1214 bytes at index 23
02:864 00:052 OCA: Detected table 52414D44 (003030656C707041) at 7F71A000 of 136 bytes at index 24
02:916 00:052 OCA: Detected table 54434656 (003030656C707041) at 7F70B000 of 60548 bytes at index 25
02:969 00:052 OCA: FACS signature is 0 (0)
03:021 00:052 OCA: Exposing XSDT table 50434146 (003030656C707041) at 7F740000 of 244 bytes at index 0
03:073 00:052 OCA: Exposing XSDT table 54444345 (003030656C707041) at 7F742000 of 83 bytes at index 1
03:125 00:051 OCA: Exposing XSDT table 54455048 (003030656C707041) at 7F73F000 of 56 bytes at index 2
03:177 00:052 OCA: Exposing XSDT table 43495041 (003030656C707041) at 7F73D000 of 188 bytes at index 3
03:231 00:053 OCA: Exposing XSDT table 4746434D (003030656C707041) at 7F73C000 of 60 bytes at index 4
03:287 00:056 OCA: Exposing XSDT table 54445353 (0074734330757043) at 7F736000 of 326 bytes at index 5
03:344 00:056 OCA: Exposing XSDT table 54445353 (0074734930757043) at 7F735000 of 843 bytes at index 6
03:396 00:052 OCA: Exposing XSDT table 54445353 (0074734331757043) at 7F734000 of 71 bytes at index 7
03:446 00:050 OCA: Exposing XSDT table 54445353 (0074734931757043) at 7F733000 of 823 bytes at index 8
03:499 00:052 OCA: Exposing XSDT table 54445353 (0074734332757043) at 7F732000 of 71 bytes at index 9
03:550 00:051 OCA: Exposing XSDT table 54445353 (0074734932757043) at 7F731000 of 823 bytes at index 10
03:602 00:052 OCA: Exposing XSDT table 54445353 (0074734333757043) at 7F730000 of 71 bytes at index 11
03:653 00:050 OCA: Exposing XSDT table 54445353 (0074734933757043) at 7F72F000 of 823 bytes at index 12
03:704 00:051 OCA: Exposing XSDT table 54445353 (0074734334757043) at 7F72E000 of 71 bytes at index 13
03:754 00:050 OCA: Exposing XSDT table 54445353 (0074734934757043) at 7F72D000 of 823 bytes at index 14
03:805 00:050 OCA: Exposing XSDT table 54445353 (0074734335757043) at 7F72C000 of 71 bytes at index 15
03:857 00:052 OCA: Exposing XSDT table 54445353 (0074734935757043) at 7F72B000 of 823 bytes at index 16
03:909 00:052 OCA: Exposing XSDT table 54445353 (0074734336757043) at 7F72A000 of 71 bytes at index 17
03:962 00:052 OCA: Exposing XSDT table 54445353 (0074734936757043) at 7F729000 of 823 bytes at index 18
04:014 00:052 OCA: Exposing XSDT table 54445353 (0074734337757043) at 7F728000 of 71 bytes at index 19
04:065 00:050 OCA: Exposing XSDT table 54445353 (0074734937757043) at 7F727000 of 823 bytes at index 20
04:115 00:050 OCA: Exposing XSDT table 54445353 (0000006D50757043) at 7F726000 of 61 bytes at index 21
04:165 00:050 OCA: Exposing XSDT table 54445353 (6963684161746153) at 7F722000 of 358 bytes at index 22
04:218 00:052 OCA: Exposing XSDT table 54445353 (0034343838696350) at 7F71D000 of 1214 bytes at index 23
04:272 00:054 OCA: Exposing XSDT table 52414D44 (003030656C707041) at 7F71A000 of 136 bytes at index 24
04:333 00:060 OCA: Exposing XSDT table 54434656 (003030656C707041) at 7F70B000 of 60548 bytes at index 25
04:383 00:050 OCA: Exposing RSDT table 50434146 (003030656C707041) at 7F740000 of 244 bytes at index 0
04:433 00:050 OCA: Exposing RSDT table 54444345 (003030656C707041) at 7F742000 of 83 bytes at index 1
04:487 00:053 OCA: Exposing RSDT table 54455048 (003030656C707041) at 7F73F000 of 56 bytes at index 2
04:539 00:052 OCA: Exposing RSDT table 43495041 (003030656C707041) at 7F73D000 of 188 bytes at index 3
04:590 00:050 OCA: Exposing RSDT table 4746434D (003030656C707041) at 7F73C000 of 60 bytes at index 4
04:642 00:052 OCA: Exposing RSDT table 54445353 (0074734330757043) at 7F736000 of 326 bytes at index 5
04:694 00:052 OCA: Exposing RSDT table 54445353 (0074734930757043) at 7F735000 of 843 bytes at index 6
04:745 00:050 OCA: Exposing RSDT table 54445353 (0074734331757043) at 7F734000 of 71 bytes at index 7
04:797 00:052 OCA: Exposing RSDT table 54445353 (0074734931757043) at 7F733000 of 823 bytes at index 8
04:849 00:052 OCA: Exposing RSDT table 54445353 (0074734332757043) at 7F732000 of 71 bytes at index 9
04:902 00:052 OCA: Exposing RSDT table 54445353 (0074734932757043) at 7F731000 of 823 bytes at index 10
04:952 00:050 OCA: Exposing RSDT table 54445353 (0074734333757043) at 7F730000 of 71 bytes at index 11
05:004 00:052 OCA: Exposing RSDT table 54445353 (0074734933757043) at 7F72F000 of 823 bytes at index 12
05:057 00:052 OCA: Exposing RSDT table 54445353 (0074734334757043) at 7F72E000 of 71 bytes at index 13
05:107 00:050 OCA: Exposing RSDT table 54445353 (0074734934757043) at 7F72D000 of 823 bytes at index 14
05:160 00:052 OCA: Exposing RSDT table 54445353 (0074734335757043) at 7F72C000 of 71 bytes at index 15
05:212 00:052 OCA: Exposing RSDT table 54445353 (0074734935757043) at 7F72B000 of 823 bytes at index 16
05:264 00:052 OCA: Exposing RSDT table 54445353 (0074734336757043) at 7F72A000 of 71 bytes at index 17
05:323 00:058 OCA: Exposing RSDT table 54445353 (0074734936757043) at 7F729000 of 823 bytes at index 18
05:375 00:052 OCA: Exposing RSDT table 54445353 (0074734337757043) at 7F728000 of 71 bytes at index 19
05:428 00:052 OCA: Exposing RSDT table 54445353 (0074734937757043) at 7F727000 of 823 bytes at index 20
05:478 00:050 OCA: Exposing RSDT table 54445353 (0000006D50757043) at 7F726000 of 61 bytes at index 21
05:529 00:051 OCA: Exposing RSDT table 54445353 (6963684161746153) at 7F722000 of 358 bytes at index 22
05:580 00:050 OCA: Exposing RSDT table 54445353 (0034343838696350) at 7F71D000 of 1214 bytes at index 23
05:632 00:052 OCA: Exposing RSDT table 52414D44 (003030656C707041) at 7F71A000 of 136 bytes at index 24
05:684 00:052 OCA: Exposing RSDT table 54434656 (003030656C707041) at 7F70B000 of 60548 bytes at index 25
05:736 00:051 OC: OcLoadPlatformSupport...
05:785 00:049 OC: OcLoadDevPropsSupport...
05:836 00:050 OC: OcLoadNvramSupport...
05:892 00:056 OC: Deleting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args - Not Found
05:949 00:057 OC: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args - Success
06:001 00:052 OC: Current version is DBG-052-2019-10-30
06:056 00:054 OC: OcMiscLateInit...
06:108 00:051 OC: LoadHandle is 7DD64798 - Success
06:157 00:049 OC: Requested resolution is 1920x1080@0 (max: 0) from 1920x1080
06:206 00:049 OCC: Requesting 1920x1080@0 (max: 0) resolution, curr 4294967295, total 7
06:261 00:054 OCC: Mode 0 - 1920x1080:1
06:321 00:060 OCC: Setting mode 0 with 1920x1080 resolution
06:373 00:052 OCC: Changed resolution mode to 0
06:424 00:050 OC: Changed resolution to 1920x1080@0 (max: 0) from 1920x1080 - Success
06:476 00:052 OC: Requested console mode is 0x0 (max: 1) from Max
06:529 00:052 OCC: Requesting 0x0 (max: 1) console mode, curr 0, max 1
06:579 00:050 OCC: Mode 0 - 80x25
06:629 00:050 OCC: Current console mode matches desired mode 0, forcing update
06:682 00:052 OCC: Setting mode 0 (prev 0) with 80x25 console mode
06:734 00:052 OCC: Changed console mode to 0
06:782 00:048 OC: Changed console mode to 0x0 (max: 1) from Max - Success
06:835 00:052 OC: Translated HibernateMode None to 0
06:887 00:052 OC: Hibernation detection status is Not Found
06:941 00:053 OC: OcLoadKernelSupport...
06:994 00:053 OC: OpenCore is loaded, showing boot menu...
07:044 00:050 OCB: Performing OcScanForBootEntries...
07:097 00:052 OCB: Found 19 potentially bootable filesystemsThis may be because i set the config.plist to showpicker=yes, but right now I'm out of time to test tonight.
I'm just happy I was able to get it to log something finally.
For SMBIOS spoofing setup, HWMonitor also work as expect.
So, it seems some softwares like iStat were programmed to look for some specific SMC keys according to the Mac's ident. Therefore, when we spoof the SMBIOS, they stop to function correctly.
On the other hand, some softwares simply show all SMC keys that they can find. And let the user to decide if the associated numbers are meaningful. In this case, they work better.
So, it seems some softwares like iStat were programmed to look for some specific SMC keys according to the Mac's ident. Therefore, when we spoof the SMBIOS, they stop to function correctly.
On the other hand, some softwares simply show all SMC keys that they can find. And let the user to decide if the associated numbers are meaningful. In this case, they work better.
Boot from recovery and you should be able to bless the partition or disable SIP if you want to execute it from within macOS
Edit: Another option is to bless the BOOTx64.efi file:
Code:
sudo bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efi
Last edited:
To those experts who used and tested OpenCore so far:
- Can I use Refind as my main internal disk EFI bootloader and load from there manually the OpenCore.efi (that surely Refind scans for it if put on any FAT32 Volume ) , or OpenCore itself needs to be loaded right after the power-on chime to be more effective in its "on-the-fly EFI patches" ?
- If through OpenCore I spoof a Mac machine (a MacBook for example) as a "VMM flag" or as a "iMac 2012" , is this almost the same thing ?
(I mean I want the Catalina Software-Update.prefpane to detect the OTA updates)
- Can I use Refind as my main internal disk EFI bootloader and load from there manually the OpenCore.efi (that surely Refind scans for it if put on any FAT32 Volume ) , or OpenCore itself needs to be loaded right after the power-on chime to be more effective in its "on-the-fly EFI patches" ?
- If through OpenCore I spoof a Mac machine (a MacBook for example) as a "VMM flag" or as a "iMac 2012" , is this almost the same thing ?
(I mean I want the Catalina Software-Update.prefpane to detect the OTA updates)
Setting the VMM flag is probably the least intrusive modification for just getting Software Update to work. On the other hand, there may be side effects to changing the model identifier (desirable or not).
yes refind can see the opencore.efi loader and can chain load into it.
Ive still not been able to get to an OS yet with opencore on my 3,1 but it’s making some progress. (Can’t get GOP display working yet in OC but it works in refind, so cant see anything to be able to boot from and likely due to the large number of ”bootable” partitions I have it’s not using one that is actually a valid bootable partition)
I've tried that but after chainloaded "OpenCore.efi" asks for a "mach_kernel" and goes in apple logo bootloop , after Yosemite OSX I guess they used kernel/prelinkedkernel, so apparently the only way is to set OC as a default standalone bootloader, I am bit worried because I want to try OpenCore on a MacBook 2010.