I thought OpenCore was needed at all times for Catalina (unpatched) to run on a 5,1 but maybe I'm misunderstanding things. Is OpenCore only needed for the installation part?
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
This is NOT correct.
We can install unpatch Catalina from a VM, or another Mac. Then all we need is just a no compat check boot argument to boot unpatch Catalina on cMP.
Obsolete, Use OpenCore instead | What you need to do to make Catalina work with MacPro5,1
Obsolete, please use OpenCore to have native installs of Catalina with MP5,1. https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/
forums.macrumors.com
OpenCore is our recommended method, which can provide boot picker, HWAccel, and allow us to boot to Catalina recovery partition etc. However, never a requirement to install / run vanilla Catalina on cMP.
Since you already have Catalina installed, all you need now is just that boot argument to boot Catalina, and test if tooltips can work properly.
This I knew. But according to the stickey adding the boot argument isn't the preferred method since the creation of OpenCore. So, it's not a consideration anymore per @tsialex.This is NOT correct.
We can install unpatch Catalina from a VM, or another Mac. Then all we need is just a no compat check boot argument to boot unpatch Catalina on cMP.
Obsolete, Use OpenCore instead | What you need to do to make Catalina work with MacPro5,1
Obsolete, please use OpenCore to have native installs of Catalina with MP5,1. https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/
OpenCore is our recommended method, which can provide boot picker, HWAccel, and allow us to boot to Catalina recovery partition etc. However, never a requirement to install / run vanilla Catalina on cMP.
Since you already have Catalina installed, all you need now is just that boot argument to boot Catalina, and test if tooltips can work properly.
"Preferred method" is NOT "required / needed".
And if you follow the entire story, you should know that I suggested him to boot Catalina without OC for diagnostic purpose (because he suspect OC cause tooltips issue). I never say that's my recommended way to run Catalina on cMP.
Last edited:
You are being too literal, the intention is to try to identify what is really causing the problem, taking OC out of the picture is useful in this diagnostic scenario.
Using -no_compat_check is extremely inconvenient nowadays, OpenCore can provide native installs and updates while disabling the compatibility check can't, but it's very useful to identify if some problem is related to OC configuration or the Catalina install itself.
As was posted earlier already: here
the problem I was having with tooltips, was NOT related to OC in any way, shape or form.... see above post for the details. Tooltip problem NOT related to OC or hardware acceleration or anything related to OC. Sorry for the bandwidth and thanks to others for pointing me in the right direction to figure it out.
the problem I was having with tooltips, was NOT related to OC in any way, shape or form.... see above post for the details. Tooltip problem NOT related to OC or hardware acceleration or anything related to OC. Sorry for the bandwidth and thanks to others for pointing me in the right direction to figure it out.
Does OpenCore resolve the USB issues for Big Sur?
- USB HID devices on system bus not recognized if inserted after boot
- USB 3 add on media devices (auto and video) not smooth
This was not an issue with earlier Big Sur betas, but is a problem now.
- USB HID devices on system bus not recognized if inserted after boot
- USB 3 add on media devices (auto and video) not smooth
This was not an issue with earlier Big Sur betas, but is a problem now.
SMBIOS spoofing? I honestly have no idea. I have the Logitec G512 Keyboard and have my MX Master 3 dongle plugged into the keyboard itself. Then, the keyboard is plugged into the back.
To answer your question though, the same problem occurs when the mouse or keyboard is plugged into the front USB ports.
That answer was to another user who claimed there were no problems on his computer. I know there are problems with the USB and they actually are related to Big Sur itself not particularly to the cMP.
URGENT QUESTION: I want to enable hardware acceleration according to this post, but there's a mention of danger with dual booting.
Since I have no boot screen, I currently use System Preferences to select my startup disk if I want to get into Windows 10, and from Windows I use Bootcamp Assistant if I want to get back to macOS.
If I install this hwaccel patch, am I going to wreck my ability to get back and forth between OSs?
Since I have no boot screen, I currently use System Preferences to select my startup disk if I want to get into Windows 10, and from Windows I use Bootcamp Assistant if I want to get back to macOS.
If I install this hwaccel patch, am I going to wreck my ability to get back and forth between OSs?
for me some devices have this issue and some others don't.
I also have the compact apple aluminum wired keyboard and I can reconnect it just fine, but my Logitech mouse doesn't .
he even admitted he had to use a hub to fix his midi issues lol.
bottom line is, some devices reconnect, some don't.
why don't you have boot screen? what's stopping you from following the guide and getting it?
I'm also dual booting windows and Catalina on one 5,1 with full HW acc. it works just fine.
I must preface this answer by saying that I am an amateur who has simply tried to follow the instructions in the earlier posts.
I assume that you mean you have not yet set up OpenCore and, if so, your system is essentially the same as the one I had before moving to an OpenCore setup. If this is the case then your Windows 10 SSD will be legacy boot and you will have to change that to UEFI fo make it work with OpenCore. I followed the instructions in the first post to the letter and reinstalled both MacOS and Windows 10 on NVMe drives (using really cheap PCIe cards). It took a while to get it right, but I now have the OpenCore boot screen, which allows me to switch between Catalina and Windows 10 by simply selecting the disk rather than having to reset the NVRAM to get back to MacOS (I didn't use Bootcamp).
The bottom line is that if you want the hwaccel patch you will have to install OpenCore and if you install OpenCore your current legacy boot Windows will have to be changed to UEFI in order for OpenCore to recognise it.
I hope this helps.
Hello
I tried to start my Mac Pro today without lilu and WhateverGreen, it didn't work. My Mac boots normally up but then my monitor just stayed black. I use in my Mac the Readeon RX 560. Does anyone have an idea what this is due to?
Thanks in advance!
I tried to start my Mac Pro today without lilu and WhateverGreen, it didn't work. My Mac boots normally up but then my monitor just stayed black. I use in my Mac the Readeon RX 560. Does anyone have an idea what this is due to?
Thanks in advance!
The iMac Pro board ID which to activate HWAccel makes the macOS believe that you are running an iMac Pro with just one internal monitor. Therefore, only one of the graphic card's port still work.
To work around this, we use Lilu + WEG, then make the "board id -> board ix" patch. So that all ports can work again.
You removed Lilu and WEG, which also disabled the board ix patch. And most likely you haven't connected the monitor to the "right port", that's why stay back.
Are the notifications and sensors fixed yet with this method? I’m awaiting for a good method with almost no compromises before upgrading from Catalina to Big Sur
OpenCore on the Mac Pro
Open config.plist in any text editor (e.g. TextEdit) Search Mac-7BA5B2D9E42DDD94 Replace it by Mac-27AD2F918AE68F61 This will inject the 7,1 board ID rather than iMac Pro board ID.
forums.macrumors.com