Its actually not as difficult/risky as it appears and most of the initial issues that you may have seen in the earlier posts were overcome a long time ago.I have to try this Opencore stuff some day. But it´s a bit intimidating all the things to configure.
The suggestion is to run the debug version and enable logging for further evaluation. I have seen colors in the code for the boot kicker perhaps they are somewhere else in the code and they mean something.Hi There,
First off I wanted to say a Huge Thank You to the OP and everyone involved in this guide and all the magic that allowed me to Install OpenCore and get Catalina on my 5,1.
It works and from a complete techno dunce like me being able to follow along and get this done is massive.
I am running into a few small aesthetic issues that if someone has a solution to resolve it would be awesome but if not then its an aesthetic issue so ill just deal with it.
I followed the basic installation parts 1 - 5 to the letter in post #1. and I also Enabled the Graphical Boot Picker in "Part II Advanced Configuration".
When I boot up the Mac the wild and negative colours appear on boot. Much like when I first installed OpenCore. I can make out that the Graphical Boot Picker is working but those pinks and yellows and rainbow spectrum colours don't look the greatest. Once I select the Boot Drive the Black screen with the white apple logo kicks in and everything is fine from there on.
I went and repeated all the Post Install actions again (made sure the changes were correct) I even re enabled some like HiDPI Display, GOP Renderer but reboots with those reverted were still the same.
Could someone let me know if the initial boot screen is supposed to be crazy colours and if not if you have any suggestions on what the issue might be that would be awesome.
End of day though is a small aesthetic issue when I first boot up so if that's just how it is I won't complain.
Awesome Job once again
Edit: Attached are photos of the screens I see in order, Ive seen this (Apart from the Graphic Icon of the Boot Drive) on boot up ever since going to Open Core (incase that in itself is unusual). a second after the last photo in the series it goes to the black apple boot screen for a second before logging into Catalina
View attachment 964769
View attachment 964770
View attachment 964771View attachment 964772
Thanks!Its actually not as difficult/risky as it appears and most of the initial issues that you may have seen in the earlier posts were overcome a long time ago.
Having said that, some still do feel unsure and a potentially easier setup process (largely automated) can be found here: https://forums.macrumors.com/threads/thread.2231693.
Disadvantage of that though, is that you don't get to understand the steps as the tools just do them for you but it might be useful in getting started.
Not sure, you may try to completely spoof the cMP with the 7,1 SMBIOS, and see it if can boot MacOS with 32GB DIMM.It does actually, if you get 32GB module DDR3 LRDIMM it will work, I wanted to know if there was something that I could potentially turn on in the config.plist so that mine that was given to me for freecould be recognized. The machine boots but hang on the Apple logo...
I may by the LRDIMM instead the one I got was RDIMM only ..![]()
As my signature states, I am fully spoofing the MacPro7,1 and I means the RDIMM's don't give me a red light whatsoever , I can hear the chime, it will show bootlicker and Apple logo, but the it hangs and no loading bar...Not sure, you may try to completely spoof the cMP with the 7,1 SMBIOS, and see it if can boot MacOS with 32GB DIMM.
For Windows and Linux, your cMP can boot 32GB DIMM natively without any spoofing.
These are all the expected outcome.I means the RDIMM's don't give me a red light whatsoever , I can hear the chime, it will show bootlicker and Apple logo, but the it hangs and no loading bar...
Its actually not as difficult/risky as it appears and most of the initial issues that you may have seen in the earlier posts were overcome a long time ago.
Having said that, some still do feel unsure and a potentially easier setup process (largely automated) can be found here: https://forums.macrumors.com/threads/thread.2231693.
Disadvantage of that though, is that you don't get to understand the steps as the tools just do them for you but it might be useful in getting started.
The suggestion is to run the debug version and enable logging for further evaluation. I have seen colors in the code for the boot kicker perhaps they are somewhere else in the code and they mean something.
We don't know until we see the log file:So does that mean that what I am seeing when I initially boot up is normal or did something go wrong in my process?
Thanks for the feedback. There is no intention to change anything on how that is set up at this point.I checked out your suggestion ...
I checked out your suggestion and it sounds very nice for someone like me to have the process automated as much as possible but and this is just some advice from your potential audience (i.e. someone that doesn't know much and could use the help) you take a great concept of a simplified process and present SO MANY options.
I get you want to allow users to take what they need, but really your target audience is guys like me so I start reading the guide and I'm not even through the pre prep and I already have multiple points where I've been confused and bewildered by options.... options I don't fully understand the result of those options.
If the goal is to make it a super simple automated process for those that don't know or simply have the time to know/understand then I would make it a very "on the rails" guide.
Step 1 - Do This
Step 2 - Do This
etc etc
It might be that the guide you wrote and your efforts to create a "Brain Dead, can do it in your sleep" guide / process is exactly that for you and those like you but speaking as someone who doesn't know his ass from his elbow when it comes to this stuff I felt my anxiety go through the roof a short way in.
I think its great your providing the automated process and trying to simplify things as much as possible for the layman. It really is appreciated, but read your audience what is elementary for you might as well be written in Ancient Greek for the rest of us.
Also the first reply you had was from another member and it said something like "why is this so complicated?"
That should be warning bells for you, instead you replied with something like "Well its a lot of info but its not complicated, for example in this section you could do steps one, two and five but not the others"
Once again MAJOR RESPECT to you for doing this (I really don't want you to feel its not appreciated) but if you sincerely want to help others like myself (who are technology dumb) with these guides and the automated tools I would suggest you strip the guide and step by step down to a simple one path guide that literally tells them exactly what to do, no options (at that point) no lengthy explanations.... or if you want to keep the explanations and options have the core instructions bolded so all I need to do is look for the bolded parts and get the job done, or if I want to learn it and feel comfortable exploring options I can read the non bolded stuff too.
I think you need to play your part and spend time to read and learn what OC can do, words like technology dumb are irrelevant. If you cannot afford this time, you cannot ask others to spoon feed you. You must be good at something, if you are not technologically inclined, you became good at it because you persisted. I personally find the guide made by @cdf extremely clear and easy to follow, everyone here took their time to read the OP and ask questions, you will get answers if you ask them.if you sincerely want to help others like myself (who are technology dumb) with these guides and the automated tools
I think you need to play your part and spend time to read and learn what OC can do, words like technology dumb are irrelevant. If you cannot afford this time, you cannot ask others to spoon feed you. You must be good at something, if you are not technologically inclined, you became good at it because you persisted. I personally find the guide made by @cdf extremely clear and easy to follow, everyone here took their time to read the OP and ask questions, you will get answers if you ask them.
I enjoy reading this thread much more, now that I have learned the basics. The one tool I wish I had is to be able to use SuperDuper! (or CCC if necessary) on disk A (Catalina) to create a clone that will boot. I remember reading a post, but I can't find it again, searching at MacRumors, and manually. I came away from what I read originally with the understanding that it can be done. Can anyone help?
Check out post #3,062Hi There,
First off I wanted to say a Huge Thank You to the OP and everyone involved in this guide and all the magic that allowed me to Install OpenCore and get Catalina on my 5,1.
It works and from a complete techno dunce like me being able to follow along and get this done is massive.
I am running into a few small aesthetic issues that if someone has a solution to resolve it would be awesome but if not then its an aesthetic issue so ill just deal with it.
I followed the basic installation parts 1 - 5 to the letter in post #1. and I also Enabled the Graphical Boot Picker in "Part II Advanced Configuration".
When I boot up the Mac the wild and negative colours appear on boot. Much like when I first installed OpenCore. I can make out that the Graphical Boot Picker is working but those pinks and yellows and rainbow spectrum colours don't look the greatest. Once I select the Boot Drive the Black screen with the white apple logo kicks in and everything is fine from there on.
I went and repeated all the Post Install actions again (made sure the changes were correct) I even re enabled some like HiDPI Display, GOP Renderer but reboots with those reverted were still the same.
Could someone let me know if the initial boot screen is supposed to be crazy colours and if not if you have any suggestions on what the issue might be that would be awesome.
End of day though is a small aesthetic issue when I first boot up so if that's just how it is I won't complain.
Awesome Job once again
Edit: Attached are photos of the screens I see in order, Ive seen this (Apart from the Graphic Icon of the Boot Drive) on boot up ever since going to Open Core (incase that in itself is unusual). a second after the last photo in the series it goes to the black apple boot screen for a second before logging into Catalina
View attachment 964769
View attachment 964770
View attachment 964771View attachment 964772
I used CCC tp clone my Mojave disk, then installed OC, then updated the cloned Mojave to Catalina. Worked fineYou want to make sure to clone the EFI partition of Disk A. There are scripts that can automate the process:
![]()
GitHub - kobaltcore/EFIClone: macOS Shell Script to automatically clone the EFI partition from either Carbon Copy Cloner or SuperDuper! when run on a Hackintosh.
macOS Shell Script to automatically clone the EFI partition from either Carbon Copy Cloner or SuperDuper! when run on a Hackintosh. - kobaltcore/EFIClonegithub.com
This is clearly off-topic, so this isn't the place to dwell on this issue. Let me give you a couple of hints, though. The first one is that, even if Mojave or Catalina won't help you with Boot Camp Assistant or provide Boot Camp drivers, you can still run Windows, provided you install it on your own (for instance, booting your computer off a Windows install DVD and installing it to a MBR FAT32 or NTFS disk). The second one is you might get a functional Boot Camp Assistant if you boot into an earlier iteration of macOS/OS X, perhaps as late as High Sierra.I'm not sure if my question should go in the "I got a new, used, rebuilt cMP," or if it should go here in the "OpenCore" discussion.
I just got an upgraded 4,1 to 5,1 cMP with Radeon RX580 and Westmere 3.33 6 logical (12 virtual) dual cores. It is running Mojave. I cannot install Windows using Boot Camp, so I need to find another way to get Windows on this Mac. My purpose is to be able to do CAD (2 PC and 1 Mac) on this cMP.
The discussion here seems to be mainly about putting Catalina on a cMP. Will that help me get where I want to go - getting Windows 10 on this Mac so that I can use Creo Parametric and SolidWorks (I know that SolidWorks does not support Macs, but I think that I can a video card that will work). The other CAD package is Cobalt by Ashlar Vellum for Mac.
Is this the right place to post to get some answers?
cMP with 32gb modules did boot Linux without issues for me, but not macOS. I tried all combinations, and the kernel is crashing for me. My take is that Mojave (without opencore) and Catalina don't support this configuration.It does actually, if you get 32GB module DDR3 LRDIMM it will work, I wanted to know if there was something that I could potentially turn on in the config.plist so that mine that was given to me for freecould be recognized. The machine boots but hang on the Apple logo...
I may by the LRDIMM instead the one I got was RDIMM only ..![]()
Look at it.I'm not sure if my question should go in the "I got a new, used, rebuilt cMP," or if it should go here in the "OpenCore" discussion.
I just got an upgraded 4,1 to 5,1 cMP with Radeon RX580 and Westmere 3.33 6 logical (12 virtual) dual cores. It is running Mojave. I cannot install Windows using Boot Camp, so I need to find another way to get Windows on this Mac. My purpose is to be able to do CAD (2 PC and 1 Mac) on this cMP.
The discussion here seems to be mainly about putting Catalina on a cMP. Will that help me get where I want to go - getting Windows 10 on this Mac so that I can use Creo Parametric and SolidWorks (I know that SolidWorks does not support Macs, but I think that I can a video card that will work). The other CAD package is Cobalt by Ashlar Vellum for Mac.
Is this the right place to post to get some answers?