Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
To those who have a MacPro3,1 with Penryn cpu and legacy USB, I made a new working fix for patched BaseSystem.dmg to allow (without OpenCore) an USB BigSur Installer booting and installing (only on internal SATA disk), just follow these steps: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28737950

Even if I already included a patched 0xfff boot.efi, but you might need the @startergo and @Dayo Refind modified , to allow the patched BaseSystem.dmg to boot you can use on refind.conf csr_rotate and csr_values 10,977 or 10,FFF (because those values allow to boot any patched BaseSystem.dmg), moreover their customized Refind version should allow also the bootscreen for non EFI Metal GPU .
 
  • Like
Reactions: macinfo
How are people backing up their Catalina installs? I tried using Carbon Copy Cloner and whilst the backup job goes fine, Opencore won't boot from the USB hard drive with the cloned install. It tries briefly, then displays a circle with a line through it, then returns to the boot picker after a few seconds.

There was an Apple bug with 10.15.5 that caused issues with booting from new CCC backups, but I contacted Mike Bombich, CCC's author, and he confirmed this has all been resolved now. He seemed to think it was a hackintosh issue, but didn't have any further suggestions.
 
Launch OpenCore from a USB stick with no operating system?
Taking a hint from one of the posters here (I might have misread something), I formatted a 16GB USB stick as GPT/APFS and proceeded to copy all relevant OpenCore and config.plist, et cetera to an EFI folder within its EFI volume. The config.plist syntax is confirmed to be valid, and there were no issues blessing its boot. Something is wrong, however. I can see an external "EFI Boot" device when I boot up my Mac Pro 5,1 while pressing Option. If I choose "EFI Boot", the graphical OpenCore picker kicks in and I can see the bootable GPT volumes on my Mac. If I choose "Macintosh HD" (my Catalina disk), the Apple logo is displayed and that's it. No progress bar, no nothing for twenty minutes. Any hints as to what might have gone wrong? May the USB stick itself be incompatible with this procedure?
 
Launch OpenCore from a USB stick with no operating system?
Taking a hint from one of the posters here (I might have misread something), I formatted a 16GB USB stick as GPT/APFS and proceeded to copy all relevant OpenCore and config.plist, et cetera to an EFI folder within its EFI volume. The config.plist syntax is confirmed to be valid, and there were no issues blessing its boot. Something is wrong, however. I can see an external "EFI Boot" device when I boot up my Mac Pro 5,1 while pressing Option. If I choose "EFI Boot", the graphical OpenCore picker kicks in and I can see the bootable GPT volumes on my Mac. If I choose "Macintosh HD" (my Catalina disk), the Apple logo is displayed and that's it. No progress bar, no nothing for twenty minutes. Any hints as to what might have gone wrong? May the USB stick itself be incompatible with this procedure?
Delete your EFI folder and drop mine, do not change anything in it and do not delete it!
 

Attachments

  • EFI.zip
    9.4 MB · Views: 128
@h9826790 beta 4 is released, for incremental update (or full install) I guess VMM flag is not suffice, do you confirm is required SMBIOS spoofing ?
 
installed Big Sur in a new way without problems.

Screenshot 2020-08-05 at 01.07.12.png
 
  • Like
Reactions: macinfo
Does anyone know if OpenCore allows MacOs to run in Hyper-V? I see a single commit / change log item mentioning it but nothing else.

I’m starting to think rather than hassling with dual booting it may make more sense to run MacOS virtualized with a GPU and Wireless (Bluetooth / WiFi) and have Windows booted at all times. Ideally Hyper-V would work but otherwise ESXI could run both.
 
Unsigned DMG loading is implemented as a part of https://github.com/acidanthera/bugtracker/issues/1073. But I should note, that we will likely have EfiBoot patches soon. To me this sounds as a much better way to make EfiBoot Penryn compatible as it will let running unmodified DMG images and do everything on the fly.

Somebody asked for 0.6.0 and Big Sur. Correct, it indeed does provide full KernelCollection injection. Several other products were also updated with partial Big Sur support.

Hyper-V support exists, but macOS does not run on 2nd generation Hyper-V, and for the first generation you will need to force DeviceType in the disk driver in OpenDuetPkg due to a bug in Microsoft implementation. See this issue.
 
Unsigned DMG loading is implemented as a part of https://github.com/acidanthera/bugtracker/issues/1073. But I should note, that we will likely have EfiBoot patches soon. To me this sounds as a much better way to make EfiBoot Penryn compatible as it will let running unmodified DMG images and do everything on the fly.

Somebody asked for 0.6.0 and Big Sur. Correct, it indeed does provide full KernelCollection injection. Several other products were also updated with partial Big Sur support.

Hyper-V support exists, but macOS does not run on 2nd generation Hyper-V, and for the first generation you will need to force DeviceType in the disk driver in OpenDuetPkg due to a bug in Microsoft implementation. See this issue.
How about the DRM streaming?
 
Unsigned DMG loading is implemented as a part of https://github.com/acidanthera/bugtracker/issues/1073.

Tried this, used build_oc.tool for 0.6.1 but seems doesn't worked to load unsigned DMG:
Code:
<key>Misc</key>
<dict>

        <key>Security</key>
        <dict>

            <key>DmgSupport</key>
            <Any/>

Should I use DmgLoading key ?

edit:
My mistake I guess I should retry with <string>Any</string>

but even using this:

<key>DmgLoading</key>
<string>Any</string>

got the same result, can't load an unsigned DMG .
 
Last edited:
Delete your EFI folder and drop mine, do not change anything in it and do not delete it!
Many thanks for your EFI folder. I've noticed it does have at least one nice graphical enhancement, and the addition of AppleALC.kext might to the trick for HDMI functionality. Sadly, once I select my Macintosh HD (Catalina) disk from the OC Picker, it just shows the Apple logo and nothing else. Is there a possibility that my USB flash drive is simply defective?

EDIT: I've repeated the entire process on an old 1GB Cruzer Micro. Both my and your EFIs end up showing the Apple logo when I pick my Catalina disk. No progress bar, no nothing. Should I try with a more recent USB pen drive? I must be missing something, but I don't know what that might be.
 
Last edited:
Wanted to ask those running Catalina on the MacPro5,1 – are none of you occasionally seeing a "watchdog timeout" Kernel Panic upon boot and when waking from sleep?

I haven't had it in 10.15.6 so far (updated a couple of days ago from 10.15.5), but still curious if any of you have had this Kernel Panic on your Catalina installs. The problem seems widespread on several of Apple's computer models, but I'm still trying to figure out if it's a bug in MacOS itself that triggers it or something fixable.

Edit:
Still seeing it with Catalina 10.15.7.
 
Last edited:
Could someone confirm that without using booter-fileset-kernel in config.plist, the BigSur kext injection works from OpenCore 0.6.0 release ?

Since this:
  • Added preview version of KernelCollection injection code
 
I have recently managed to install Catalina on my 3,1 using dosdude1’s patcher and opencore along with dosdude’s Rom flasher.

Everything is working fine however with the opencore bootpicker, I only see my Catalina and the recovery drives. I have an extended formatted SSD drive with El Capitan in one of the bays that does not show up in OC bootpicker.

Does opencore bootpicker only see APFS drives? If not, how do I get my El Capitan drive to show up in bootpicker?
 
Could someone confirm that without using booter-fileset-kernel in config.plist, the BigSur kext injection works from OpenCore 0.6.0 release ?

Since this:
  • Added preview version of KernelCollection injection code
Yes without the user mode space.
 
  • Like
Reactions: jackluke
Does opencore bootpicker only see APFS drives? If not, how do I get my El Capitan drive to show up in bootpicker?

If you want to actually understand how OpenCore works, read the documentation that it comes with.
You will find your question answered under "ScanPolicy" which outlines how to fine tune the policy that determines what is shown in the boot picker.

If you can't be bothered, just set the "ScanPolicy" key in your config to "0" to scan and show everything possible.
Best to take the time to study the docs though.
 
  • Like
Reactions: JedNZ
i have read the OC documentation since 0.5.4
and still don't understand it - maybe i am just too old +g*
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.