Maybe unrelated, but try this: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28174025
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
Maybe unrelated, but try this: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-28174025
The logic is this: We want full control over which EFI files get installed because we want to avoid Windows from ever booting natively (the consequences of this are well known). We achieve this by copying over only the Microsoft folder. The approach does not cause any issues because OpenCore boot management is compatible with it.
I'm curious about this. The installer ISO for version 2004 is available from Microsoft (simply visit the link in the guide using a Mac and you'll be able to download it). On the download page, Microsoft states that
So the ISO is certainly available for creating a USB installer. I suppose that you might be referring to the install.wim file being over 4 GB, which is too big for a Fat-formatted USB drive. That's why the guide uses exFat. Booting from exFat is possible by adding the ExFatDxeLegacy driver with OpenCore. The guide includes instructions for this.
In my case would I be unloading the USB mass storage driver (not the kext for a card adapter, as for the laptop in that thread)? That doesn't sound like something I would want to live without, though could be useful for testing. I'll try just unplugging the hub + card reader and see if the KPs stop though.
One suggestion I've seen suggested is to install the 15.5 combo update. Can I just do this, or would I need to set the VMM flag first?
Monitor is a Monoprice 27" IPS ZERO G.
I give up.... Tried HDMI and one of the DisplayPorts with same results. It's on the boot screen only anyways, after OS loads it looks normal. Reminds me of the EDID overrides... LOL
Last edited:
Something you can live with for sure - but I know it's annoying. I am glad the rest works for you.
With all my respects and admiration for all the people writing in this thread, specially the wiki team:
I have followed all the procedures in the wiki excepting the Windows 10 installation procedure.
Honestly, IMHO it is more simple and straight this other one option (specially for simple users, like me):
Rufus to Install Windows 10 (EFI) on cMacPro Opencore with BootPicker
I have been trying in last few days several options to install Windows 10 in my cMP 5,1 after installing Catalina via Opencore using the excellent wiki here. I tried and failed using VirtualBox VM or Bootcamp adaptations. This is useful if you have no Mac EFI Boot because you use a generic...
forums.macrumors.com
Even more. Days ago I installed EFI Windows 10 (2004) and even I didn't use Brigadier. I Just needed manually install Broadcom (bluetooth). I don't use Bootcamp anymore.
I hope this can help.
Many Thanks again to everyone here. You are really amazing.
Last edited:
I haven't tested combo updates, but I would think that the VMM flag is indeed needed. @mode11 make sure to keep us posted.
[automerge]1594471223[/automerge]
Exactly the same issue as me.
I'm using OC 0.59 for MacPro 5,1 and Catalina 10.15.5 Clean Install.
Has anyone solved this problem?
Exactly the same issue as me.
I'm using OC 0.59 for MacPro 5,1 and Catalina 10.15.5 Clean Install.
Has anyone solved this problem?
After disconnecting my USB 3 hub yesterday, I haven’t had any KPs through various sleep / wake cycles. The SD reader in it has always fluctuated between showing up as USB 2 or 3, so is probably a bit dodgy (shame, as it’s otherwise perfect). Too soon to declare it fixed though; I’ll update here in a few days.
It’s possible it’s related to the USB card itself I guess - without anything connected, maybe there’s no activity to cause issues. I’ll chuck a USB stick in at some point to give it something to do.
Last edited:
I'm glad it's the exact same situation as me.
Following your tips, I'll test it out without my USB 3 hub and SD reader.
Thank you for your interest and help.
Only "issue" after adding csr-active-config on opencore "Delete" is that if I boot from apple startup manager "csrutil disable" is not stored for other supported macOS , I mean it's almost an NVRAM reset , so I need to boot a macOS Recovery or Installer to disable SIP for apple startup manager.
Of course, the config in OpenCore only works when you boot via OpenCore.
If you boot natively, bypassed OpenCore, then none of the OpenCore things can work.
If you want the NVRAM variables to stick, I believe you can enable WriteFlash. This would not be advisable, however, on the Mac Pro because of its frail firmware.
Yes, it appears that the keys are the same.
This kind spoofing also brings other benefits like Night Shift and Boot Camp Assistant. However, we don't yet know the long term effects: with both the board and model identifiers changed but the other identifiers the same, I would advise caution with iCould. In fact, full spoofing is probably safer... We need more testing.
Refind boot loader has csr_rotate for managing SIP (that implies working boot screen). Also I know 77 works but the new SIP value for Big Sur has to be tested. I have setup rEFInd as the first bootloader, which after timeout automatically loads OC. This way I can always boot without OC for testing purposes:
Using rEFInd to Manage SIP
Once rEFInd is installed, you can use it to manage SIP features; however, the rEFInd features needed to do this are disabled by default. You must uncomment or add two lines to your refind.conf file:
Note: Apple code samples and technical discussions are filled with the acronym "CSR." I don't know what this acronym means, but as it appears to be used in preference to "SIP" or "rootless" when referring to specific values, I used it in the refind.conf file's token names.
- showtools—This line specifies tools that appear on the second row of icons in rEFInd. The new tool for managing SIP is called csr_rotate, so you must uncomment showtools and add this option, or create a new showtools line.
- csr_values—This line lists the hexadecimal values through which you can rotate once csr_rotate is active on the showtools line. The trick to this token is selecting appropriate options. Several sites, such as this one, describe the meanings of the various options, but often not in much detail. Apple's own csrutil command sets values of 77 (disabled) or 10 (enabled). Note also that you specify hexadecimal values on this line, but without a leading 0x or other hexadecimal-notation indicator. If you specify gibberish values, or hexadecimal values higher than those used by SIP, rEFInd ignores the bad entries. Thus, if some of your values are being ignored, you should check your csr_values line for typos.
Note that both of these options must be set appropriately. If either of them is missing or misconfigured, rEFInd will not display the SIP tool. A typical configuration using these features might look like this:
showtools shell,memtest,gdisk,csr_rotate,apple_recovery,windows_recovery,about,shutdown,reboot
csr_values 10,77
Once these options are set and you reboot into rEFInd, you should see a new shield icon on the second row, as shown at the right. When you select this tool, rEFInd identifies the next available CSR value from the list you specified and switches to that mode, rotating back to the start of the list once the end is reached. To confirm that the SIP mode has changed, rEFInd displays, for three seconds, a message identifying the new mode.
Whether or not you've enabled these SIP features in refind.conf, rEFInd displays the current SIP status on its "About" page:
[IMG alt="rEFInd presents a graphical menu for selecting your
boot OS."]https://rodsbooks.com/refind/about.png
Note the line that reads "System Integrity Protection is disabled (0x77)" (highlighted in this screen shot). This line will be updated whenever you use the CSR rotation tool, so if you've specified a large number of values and have forgotten where you are in your rotation, you can use the About screen to figure it out.
If your Mac doesn't yet run macOS 10.11, rEFInd claims that SIP is enabled in the "About" screen. If you set the showtools and csr_values options as described earlier, you can adjust the SIP settings on such a Mac, but this will have no effect because neither pre-10.11 version of macOS nor any other OS honors these settings. On UEFI-based PCs, rEFInd won't display SIP status unless you store the csr-active-config NVRAM variable in some way. If you do, rEFInd will enable you to adjust it, but it won't have any effect on the OSes most commonly found on UEFI-based PCs.
I provide these features in rEFInd as a convenience for developers and other advanced users who have a need to adjust their SIP settings. Using rEFInd for this purpose is much faster than booting into the macOS Recovery system to make these adjustments. I discourage others from playing with these settings, since changing them inappropriately could cause problems; that's why they're not enabled in rEFInd by default.
I was able to get Big Sur installation to run using OpenCore 0.5.9 as well as spoofing the SMBIOS to make my Mac Pro 5.1 appear as a IMac 27" 2017 (I stole using this thread). When the computer restarts I see the MacOS installer as a boot option but it continues in a circular reboot. Has anyone had this issue and solved it?
Once the installer has written to the disk and gone to restart, install without open core by removing other disks & drives.
When you get to the startup screen for selecting a language restoring backups etc you can power off and then boot via open core.
Also, I have a permanent ‘MacOS installer’ boot option next to ‘Big Sur HD’ (my name for my Macintosh HD) - ignore it, or I have managed to make it go away by using bless to add another apfs seal over the default one but I wouldn’t recommend that yet, more testing is needed.
When you get to the startup screen for selecting a language restoring backups etc you can power off and then boot via open core.
Also, I have a permanent ‘MacOS installer’ boot option next to ‘Big Sur HD’ (my name for my Macintosh HD) - ignore it, or I have managed to make it go away by using bless to add another apfs seal over the default one but I wouldn’t recommend that yet, more testing is needed.
It should be very straight forward. No need to swap / remove hard drive in between.
I just try the whole Big Sur installation again onto a newly formatted HDD. The whole process is really very native.
1) Boot cMP 5,1 via OpenCore with complete iMac Pro SMBIOS spoofing (VMM flag can stay off, the required code in post 7)
2) Boot to Mojave (or Catalina) desktop.
3) Run the Big Sur installer.
4) Select the newly formatted HDD/SSD as destination
5) Let it finish the whole installation by itself. As long as you have time out function set in boot picker. 100% no need to touch the cMP during installation.
6) After boot to Big Sur desktop. Mount the EFI partition again, and turn off SMBIOS spoofing (N.B. the no compat check boot argument MUST in the config.plist as per post 1).
Query about OpenCore & System Preferences Startup Disk: If I select a drive (i.e., Mojave) from Startup Disk and reboot to that drive, do I lose my OpenCore implementation, or will on a reboot from that drive go back to my OC EFI with my default selection (i.e., Catalina)?
I ask because I have a 5,1 that runs OC in a headless implementation with Catalina selected as default on a 2sec. delay. I'd need to drag out a wired keyboard/mouse combo and HDMI cable if it loses OC or the default selection.
I ask because I have a 5,1 that runs OC in a headless implementation with Catalina selected as default on a 2sec. delay. I'd need to drag out a wired keyboard/mouse combo and HDMI cable if it loses OC or the default selection.
That’s correct, cMP + OpenCore can easily install and run Big Sur (including recovery partition)
In fact, the result is better than I expect. With my current OpenCore config (HWAccel activated by spoofing board ID, but still ident as cMP 5,1), Airdrop and Handoff also work “natively”.
However, haven’t figured out how to enable DRM streaming yet.
The easiest way to upgrade Opencore from 0.5.9 to 0.6.0. Or might someone have a complete package for Mac Pro 5.1?
Thank!
Thank!
Using OpenCanopy encounter this issue: if I have many bootable volumes (example plugging an external USB with other bootable volumes) they don't fit the screen correctly, but if I use keyboard arrows they are selectable even if "out of bounds" compared to the display.
I use this config (but with many volumes they don't fit the screen correctly):
Does anyone know how to "resize Volume icns" when many icons (or volumes) are available using OpenCanopy.efi ?
I use this config (but with many volumes they don't fit the screen correctly):
Code:
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
<key>UIScale</key>
<data>AQ==</data>Does anyone know how to "resize Volume icns" when many icons (or volumes) are available using OpenCanopy.efi ?
If you can't make your own config yet, do NOT use any OpenCore BETA.
There are many versions for OpenCore beta (e.g. may be 10 versions for 0.6 beta), and all of them may need different config to work properly. In some cases, same item can represent different things in different beta.
If you download a pre-created 0.6 beta package now, and then upgrade to newer beta (or official 0.6) later. Your config may not be valid, or in some cases, 100% compatible, but meaning something else (even harder to debug).
So, do NOT do that if you can't follow manual and create your own config.
[automerge]1594713446[/automerge]
Depends on your config.
If you set
RequestBootVarRouting to true, then you are selecting the default boot drive of the OpenCore boot picker.But if you keep that off (false), then you are selecting to boot to that drive natively, and disable OpenCore.