Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 RefindPlus|OpenCore by MyBootMgr

That's ok, a "normal" user has been into MacOs after 2020-007

But I have FileVault and no uga-bootscreen GPU (that k2000 unflashed at this moment) so I was at least in a position that I cannot boot into MacOs no more as I had not seen my Filevault login screen.

Tried to get me in "blindly" but won't worked, maybe Filevault need response from a GUI.

Full NVram reset wiped the Blessing I guess and got me into the first bootx64.efi the bootloader has found.
 
Last edited:
  • Like
Reactions: Dayo
MyBootMgr v065 installed and working fine on my system. Thanks for adding the option to set Innie to <true/> (for PCIe drives to be seen as Internal) as this saves me having to manually change that.
 
  • Like
Reactions: Dayo
I keep trying to get your latest package to boot Big Sur on my 3.1. Martin Lo's 0.6.5 package boots Big Sur fine? I tried using his config, drivers, kexts with your package and it still won't boot Big Sur? HELP! I need to integrate REFIND for booting Legacy Windows! Do you modify the opencore.efi or something I'm missing? Is there a way to combine/replace Martin Lo's instance of OC with yours? I looked at the config.plist and changed it line for line with the working one I have. It must be something besides the config that is wrong. I have your 0.6.3 package working fine with Big Sur somehow? Just can't seem to upgrade beyond that? I tried with and without telemetrap as I have a patched telemetry kext in Big Sur. Still no BS joy :(

UPDATE!!!: Got it working with Big Sur finally after setting some quirks properly. 0.6.5 in da HOUSE! :)
 
Last edited:
  • Like
Reactions: JedNZ
Presumably other Mac OS versions are working and no, the files are exactly as from the OC Project. You can download the files from there and replace them in your setup if you want ... OC devs removed the need for patching for OC_ALT in one of the recent versions.

There is a link in Post 1 to a thread about a BS implementation using this setup.
The author is apparently open to questions ... Can you try that thread instead?

EDIT: Good to know you got it working ... the 3,1 never dies!
 
Last edited:
I Updated RefindPlus to the latest release (along with OC 0.6.5). Now it is not detecting during scan for the boot selection screen, my non-OC Mojave boot volume as it used to do before. Has something changed in RefindPlus that I need to explicitly enable now, in order to detect that Mojave boot volume? Its also not detecting some other bootable volumes that it used to detect before, some of which I had hidden. I tried to look at the hidden manager to see if they are in there, and it says nothing in there either. So basically non of the OS X boot volumes are showing up during scan, just the OC and OC_ALT.
 
I gather that you have an exotic setup where you have implemented various things outside the process flow. Presumably you fully understood the changes you made.

In terms of the setup outlned in Post 1, everything works as it should and no, you don't need any manual intervention to make basic functionality work nor has anything changed with respect to basics such as volume detection.

A link to the subject specific forum for rEFInd is available in Post 1 and you can also refer to the rEFInd documentation if you need further guidance on your changes. A copy is included in the Docs folder created when you install MyBootMgr.
 
I wasn’t sure where to post this question because it is specific to RefundPlus, not rEFInd.

where can I post questions about RefindPlus that are unrelated to MyBootMgr?

there is nothing exotic or complicated about my setup. I am simply attempting to use RefindPlus, which is part of the title of this thread which is why I asked here. If you prefer me to post the question in the rEFInd forum then I will but this seems to be related to changes you have made in RedfindPlus. Perhaps new bugs as far as I can see
 
RefindPlus is nothing more than rEFInd plus a few additional features so most configuration issues can be posted to the rEFInd forum. There is also a discussion facility on the RefindPlus GitHub repository.

In terms of your question however, I am unable to add anything further apart from what has already been said. That is, there are no changes to volume detection and all my volumes are detected as they should.

There are also other testers and none of these have issues with disappearing volumes which suggests to me that you may have misconfigured something somewhere. While you may see bugs, I see misconfiguration as such a fundamental issue, if a bug, would not just only affect you as it currently seems. If someone else reports an issue, then I will investigate this.

BTW, you could always just use the previous version of RefindPlus that you say works for you and only have OpenCore updated.
 
True but you improved hidpi in current version of refindplus. I’d rather try to figure out why it’s not detecting my Mojave volume any more since upgrading it
 
Run the following command in Terminal and post the result:
system_profiler SPHardwareDataType | grep 'Model Identifier' && system_profiler SPHardwareDataType | grep 'Boot ROM Version'
 
Dayo said:
Run the following command in Terminal and post the result:
system_profiler SPHardwareDataType | grep 'Model Identifier' && system_profiler SPHardwareDataType | grep 'Boot ROM Version'
Click to expand...

Model Identifier: MacPro5,1
Boot ROM Version: 144.0.0.0.0
 
I see. I'm afraid that with BootROM 144.0.0.0.0, I really have no idea why they would not be showing up.
Are you using a GPU flashed by MacVidsCards or a similar outfit?

BTW, please add your BootROM Version and whether your GPU is flashed by MacVidsCards et al (if it is) to your signature as these are important bits of data.
 
Last edited:
run into a kernel panic with MP5,1 Booting to unpatched BigSur 11.1 20C69 thru RP in early Stage 1

"Rooting from the live fs of a sealed volume is not allowed on a RELEASE build"

(thru OC and thru Apple Boot Picker is ok)

Code: 
panic(cpu 0 caller 0xffffff800cafb60c): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.60.23/kext/apfs_vfsops.c:2011
Backtrace (CPU 0), Frame : Return Address
0xffffffa063dcaea0 : 0xffffff8009ab9aed
0xffffffa063dcaef0 : 0xffffff8009bfc6e3
0xffffffa063dcaf30 : 0xffffff8009becd1a
0xffffffa063dcaf80 : 0xffffff8009a5ea2f
0xffffffa063dcafa0 : 0xffffff8009ab938d
0xffffffa063dcb0c0 : 0xffffff8009ab9678
0xffffffa063dcb130 : 0xffffff800a2be3ca
0xffffffa063dcb1a0 : 0xffffff800cafb60c
0xffffffa063dcb990 : 0xffffff800cb0488f
0xffffffa063dcb9c0 : 0xffffff8009d402b0
0xffffffa063dcbb40 : 0xffffff8009ffdf63
0xffffffa063dcbe70 : 0xffffff8009ae72e3
0xffffffa063dcbfa0 : 0xffffff8009a5e13e
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1677.60.23)[1313BE58-4FFF-3553-A2FD-B4CF895BFEBE]@0xffffff800ca81000->0xffffff800cbe3fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[E4DF1D8B-0DA9-33A8-A7B6-17DCA1678FC0]@0xffffff800ae59000->0xffffff800ae62fff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[7587E81D-37C4-3BE3-9B3E-3F81D594121F]@0xffffff800ae6c000->0xffffff800ae71fff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[203FD04E-5295-3A56-A1BC-B04D3B36ACAB]@0xffffff800b2a8000->0xffffff800b2aefff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[AA8F8B9D-BA6E-3EBB-8195-4792042ADF71]@0xffffff800c54c000->0xffffff800c55dfff
            dependency: com.apple.kec.corecrypto(11.1)[42C8D110-EAAE-3AA5-843C-8118CA487862]@0xffffff800cc11000->0xffffff800cca0fff
            dependency: com.apple.security.AppleImage4(3.0.0)[50ECF21B-A875-39D8-8898-ADAF3DE514F5]@0xffffff800aece000->0xffffff800aeddfff

Process name corresponding to current thread: kernel_task
Boot args: -no_compat_check

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec  2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x0000000009800000
KernelCache base:  0xffffff8009a00000
Kernel slide:      0x0000000009810000
Kernel text base:  0xffffff8009a10000
__HIB  text base: 0xffffff8009900000
System model name: MacPro5,1 (Mac-F221BEC8)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 2097293246
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000000007d023022
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000002660adba20 0x0000000000000000
last started kext at 1685084530: >!UDisplays    380 (addr 0xffffff800b1f9000, size 8192)
loaded kexts:
>!UDisplays    380
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.hfs.kext    556.60.1
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
|SCSITaskUserClient    436.40.6
@filesystems.apfs    1677.60.23
>!I82574LEthernet    2.7.2
@private.KextAudit    1.0
>!AAHCIPort    346
>!AHPET    1.8
>!ARTC    2.0
>!AACPIButtons    6.1
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
>!A!ICPUPowerManagementClient    222.0.0
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    310
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
>!A!ICPUPowerManagement    222.0.0
>usb.IOUSBHostHIDDevice    1.2
>!AThunderboltPCIDownAdapter    4.1.1
>!AThunderboltDPOutAdapter    8.1.4
>!AThunderboltDPInAdapter    8.1.4
>!AThunderboltDPAdapter!F    8.1.4
>!AHPM    3.4.4
>!A!ILpssI2C!C    3.0.60
>!A!ILpssI2C    3.0.60
>!A!ILpssDmac    3.0.60
>usb.!UHub    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!ABSDKextStarter    3
|IOSurface    289.3
|IOSkywalk!F    1
>mDNSOffloadUserClient    1.0.1b8
@filesystems.hfs.encodings.kext    1
|IOSCSIMultimediaCommandsDevice    436.40.6
|IOBD!S!F    1.8
|IODVD!S!F    1.8
|IOCD!S!F    1.8
>!AXsanScheme    3
|IOAHCISerialATAPI    268
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
>!AThunderboltNHI    7.2.8
|IOThunderbolt!F    9.3.2
|IOAHCIBlock!S    332
>usb.!UHostPacketFilter    1.0
|IOUSB!F    900.4.2
>usb.!UEHCIPCI    1.2
>usb.!UUHCIPCI    1.2
>usb.!UUHCI    1.2
>usb.!UEHCI    1.2
|IOAHCI!F    294
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
|IOSMBus!F    1.1
|IOHID!F    2.0.0
$!AImage4    3.0.0
|IOTimeSync!F    900.11
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    8.0.2f9
|IOReport!F    47
|IO!BPacketLogger    8.0.2f9
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    511.60.2
|IOUSBMass!SDriver    184.40.6
|IOSCSIBlockCommandsDevice    436.40.6
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    436.40.6
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.corecrypto    11.1
@kec.Libm    1
 

Attachments

  • logs.zip
    19.1 KB · Views: 77
Dewdman42 said:
card is not flashed.
Click to expand...
Try MyBootMgr 065a. It was released unannounced a couple of days or so ago. It might solve your issue.

Macschrauber said:
kernel panic booting to BigSur
Click to expand...
Upstream (rEFInd) does not yet support BigSur. There is a banner on the project page about this: http://www.rodsbooks.com/refind. If/When rEFInd has this, will bring it in or may figure out how to independently but this is at the very bottom of the barrel of priorities.

Side Note:
The premise of MyBootMgr (as per Post 1) is that you should always boot into Mac OS via OpenCore. Booting into Mac OS via RefindPlus is meant to only be for emergencies so the idea is that you only have one instance in RefindPlus which should be no higher than Catalina at this time.

While some functionality from OpenCore has been duplicated in RefindPlus as this enhances the whole it is not intended to replicate OpenCore functionality in RefindPlus. Basically consider the feature set of the the two combined when looking at what is available. That is, if there is something available in OpenCore or RefindPlus, then it is considered done. As said though some things are useful on both sides.

BigSur booting in RefindPlus would be a nice to have but it is a lot more complicated than the standard booting process so OpenCore fills this gap and fits in with the overall philosophy anyway.
 
  • Like
Reactions: JedNZ
writing in Big Sur booted thru RefindPlus

problem was partial sip

something set base system protection in sip to be enabled, all the rest disabled (0x7f)

disabled it completely with RP toggle SIP policy (0x87f)

and it booted Big Sur like OpenCore did

strange thing is that OpenCore had same sip settings.

anyway, it works...
 
Last edited:
  • Like
Reactions: Dayo
Macschrauber said:
anyway, it works...
Click to expand...
So basically need to disable SIP in RefindPlus to use it.

BTW, the RefindPlus "Disable SIP" is different if you say you have BigSur in ConfigFactory from if you say you don't.
So if set up saying there is no BigSur and then adding Big Sur later without rerunning ConfigFactory, thing will not work as expected.

Basically, be aware that "Disable SIP" for Catalina and earlier in RefindPlus disables less of SIP than "Disable SIP" for BigSur in RefindPlus. Also note that you don't need to dsable SIP to run Catalina and earlier on unsupported Macs.
 
Last edited:
  • Like
Reactions: Macschrauber
Macschrauber said:
run into a kernel panic with MP5,1 Booting to unpatched BigSur 11.1 20C69 thru RP in early Stage 1

"Rooting from the live fs of a sealed volume is not allowed on a RELEASE build"

(thru OC and thru Apple Boot Picker is ok)

Code: 
panic(cpu 0 caller 0xffffff800cafb60c): "Rooting from the live fs of a sealed volume is not allowed on a RELEASE build\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.60.23/kext/apfs_vfsops.c:2011
Backtrace (CPU 0), Frame : Return Address
0xffffffa063dcaea0 : 0xffffff8009ab9aed
0xffffffa063dcaef0 : 0xffffff8009bfc6e3
0xffffffa063dcaf30 : 0xffffff8009becd1a
0xffffffa063dcaf80 : 0xffffff8009a5ea2f
0xffffffa063dcafa0 : 0xffffff8009ab938d
0xffffffa063dcb0c0 : 0xffffff8009ab9678
0xffffffa063dcb130 : 0xffffff800a2be3ca
0xffffffa063dcb1a0 : 0xffffff800cafb60c
0xffffffa063dcb990 : 0xffffff800cb0488f
0xffffffa063dcb9c0 : 0xffffff8009d402b0
0xffffffa063dcbb40 : 0xffffff8009ffdf63
0xffffffa063dcbe70 : 0xffffff8009ae72e3
0xffffffa063dcbfa0 : 0xffffff8009a5e13e
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1677.60.23)[1313BE58-4FFF-3553-A2FD-B4CF895BFEBE]@0xffffff800ca81000->0xffffff800cbe3fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[E4DF1D8B-0DA9-33A8-A7B6-17DCA1678FC0]@0xffffff800ae59000->0xffffff800ae62fff
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[7587E81D-37C4-3BE3-9B3E-3F81D594121F]@0xffffff800ae6c000->0xffffff800ae71fff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[203FD04E-5295-3A56-A1BC-B04D3B36ACAB]@0xffffff800b2a8000->0xffffff800b2aefff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[AA8F8B9D-BA6E-3EBB-8195-4792042ADF71]@0xffffff800c54c000->0xffffff800c55dfff
            dependency: com.apple.kec.corecrypto(11.1)[42C8D110-EAAE-3AA5-843C-8118CA487862]@0xffffff800cc11000->0xffffff800cca0fff
            dependency: com.apple.security.AppleImage4(3.0.0)[50ECF21B-A875-39D8-8898-ADAF3DE514F5]@0xffffff800aece000->0xffffff800aeddfff

Process name corresponding to current thread: kernel_task
Boot args: -no_compat_check

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec  2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x0000000009800000
KernelCache base:  0xffffff8009a00000
Kernel slide:      0x0000000009810000
Kernel text base:  0xffffff8009a10000
__HIB  text base: 0xffffff8009900000
System model name: MacPro5,1 (Mac-F221BEC8)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 2097293246
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000000007d023022
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000002660adba20 0x0000000000000000
last started kext at 1685084530: >!UDisplays    380 (addr 0xffffff800b1f9000, size 8192)
loaded kexts:
>!UDisplays    380
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.hfs.kext    556.60.1
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
|SCSITaskUserClient    436.40.6
@filesystems.apfs    1677.60.23
>!I82574LEthernet    2.7.2
@private.KextAudit    1.0
>!AAHCIPort    346
>!AHPET    1.8
>!ARTC    2.0
>!AACPIButtons    6.1
>!ASMBIOS    2.1
>!AACPIEC    6.1
>!AAPIC    1.7
>!A!ICPUPowerManagementClient    222.0.0
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    310
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
>!A!ICPUPowerManagement    222.0.0
>usb.IOUSBHostHIDDevice    1.2
>!AThunderboltPCIDownAdapter    4.1.1
>!AThunderboltDPOutAdapter    8.1.4
>!AThunderboltDPInAdapter    8.1.4
>!AThunderboltDPAdapter!F    8.1.4
>!AHPM    3.4.4
>!A!ILpssI2C!C    3.0.60
>!A!ILpssI2C    3.0.60
>!A!ILpssDmac    3.0.60
>usb.!UHub    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
>!ABSDKextStarter    3
|IOSurface    289.3
|IOSkywalk!F    1
>mDNSOffloadUserClient    1.0.1b8
@filesystems.hfs.encodings.kext    1
|IOSCSIMultimediaCommandsDevice    436.40.6
|IOBD!S!F    1.8
|IODVD!S!F    1.8
|IOCD!S!F    1.8
>!AXsanScheme    3
|IOAHCISerialATAPI    268
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
>!AThunderboltNHI    7.2.8
|IOThunderbolt!F    9.3.2
|IOAHCIBlock!S    332
>usb.!UHostPacketFilter    1.0
|IOUSB!F    900.4.2
>usb.!UEHCIPCI    1.2
>usb.!UUHCIPCI    1.2
>usb.!UUHCI    1.2
>usb.!UEHCI    1.2
|IOAHCI!F    294
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
|IOSMBus!F    1.1
|IOHID!F    2.0.0
$!AImage4    3.0.0
|IOTimeSync!F    900.11
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    8.0.2f9
|IOReport!F    47
|IO!BPacketLogger    8.0.2f9
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    511.60.2
|IOUSBMass!SDriver    184.40.6
|IOSCSIBlockCommandsDevice    436.40.6
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    436.40.6
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.corecrypto    11.1
@kec.Libm    1
Click to expand...
try FFF as a csrutil_rotate argument. I was booting Big Sur.
 
ok, got it:

cleared nvram,
bootet to Mojave Recovery
csrutil disable

got csr 0x77

Big Sur Kernel Panic booted thru RefindPlus

even if Mojave tells:

Code: 
csrutil status
System Integrity Protection status: disabled.
 
startergo said:
try FFF as a csrutil_rotate argument. I was booting Big Sur.
Click to expand...
so summary:

0xFFF and 0x87F is booting Big Sur thru RefindPlus

0x77 (set with csrutil disable in 10.14.6 Recovery) Big Sur Kernel Panics when booting thru RefindPlus

with FFF in Big Sur:

Code: 
csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
    Apple Internal: disabled
    Kext Signing: disabled
    Filesystem Protections: disabled
    Debugging Restrictions: disabled
    DTrace Restrictions: disabled
    NVRAM Protections: disabled
    BaseSystem Verification: disabled

---

with 0x87F in Big Sur:
Code: 
csrutil status
System Integrity Protection status: disabled.
 
Dayo said:
Try MyBootMgr 065a. It was released unannounced a couple of days or so ago. It might solve your issue.
Click to expand...

Not sure what you changed on MyBootMgr 065a, I will check that out anyway. However I did seem to solve my problem by removing an old entry in the RefindPlus overrides.conf file, which was from a month ago when we were playing around with HiDPI stuff...when I remove the following option, suddenly scanning worked:

Code: 
force_hidpi true

and of course the newer version of RefindPlus has other ways to handle HiDPI...so I'm happy with the results now..but anyway, not sure why that option would cause it to not scan my OS X volumes, but there it is.

Thanks for the followup.
 
Sorry for the stupid question, but is there a post someone can link me to that has instructions on installing a second OS on a 5,1 running native Mojave and rEFInd/OC?

In this instance, rEFInd/OC was installed just to take advantage of boot screens on an unflashed Vega 64 card. Not sure however how to best proceed with installing Catalina or even Big Sur.

Is the installation performed via an OpenCore instance?
 
There is a link in Post 1 to a thread about installing Big Sur. Might give you some clues.
 
  • Like
Reactions: amstel78
Dayo said:
There is a link in Post 1 to a thread about installing Big Sur. Might give you some clues.
Click to expand...
Thanks. Had a look at the first post again. So just to confirm, installations of secondary Mac OS takes place under a current OpenCore session, i.e.:

1. Download Catalina in OpenCore Mojave;
2. create a bootable Catalina USB installer, then reboot.
3. rEFInd/OC should then see the bootable USB stick as new OpenCore session option;
4. Proceed with install on new APFS partition or drive;
5. Update config plist / kexts if necessary after install finishes?

Is my understanding of the basic process listed above correct?

I assume once Catalina or Big Sur is running, I can just download your package again to have access to the various tools directly within the new OS rather than having to boot back into Mojave?
 
That should work and you don't need to update your config files etc. You could rerun ConfigFactory and redeploy if it will make you feel better though.

Having said that, I haven't installed any new OS myself so probably better to ask for tips on that other thread.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back