Yes, I'm using one of those adapters as well right now. They work just fine. The problem for me is that I don't see the boot screen through that adapter. If I have my LED Cinema Display connected to the DisplayPort instead I can see the boot screen (but then the screen goes black when Catalina boots up).
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
@h9826790 @startergo have you looked at the Vault settings? Right now is set to Optional. I'm concerned because an attacker who takes over OSX will usually have a hard time gaining persistence due to SIP, but if they discover the computer is OpenCore based, they can just use OpenCore as a conduit for boot-persistance.
Vault allows you to sign a hash of every file OpenCore uses (all the patches, configuration, injected drivers, etc) and then embed the public key into the OpenCore EFI binary itself. OpenCore will then check the integrity of all the files on boot.
Vault allows you to sign a hash of every file OpenCore uses (all the patches, configuration, injected drivers, etc) and then embed the public key into the OpenCore EFI binary itself. OpenCore will then check the integrity of all the files on boot.
Not sure what you mean by aluminum keyboard - mine is also aluminum with white plastic buttons (model A1243)?
Anyway, I am having another problem which is happening before the OS is loaded as well. Whenever I restart my Mac Pro boots to Mojave drive, even though it was on Big Sur when restarted, and Big Sur disk was selected in Startup Items.
There is no reaction from the keyboard or mouse (logitech dongle in keyboard) so I cannot use the bootpicker when it appears (I changed the config back to 'true'). When Mojave boots it complains there is an "incompatible disk that has features that are not supported" - and obviously this is the Big Sur setup. neither the Big Sur drive (NVMe) nor its Carbon Copy appear on desktop or in Startup Items.
To get around I restart and plug in a second keyboad (older white plastic extended Apple one) and attached Mighty Mouse (front panel USB). They work to get to use bootpicker for me to choose Big Sur ("Untitled") drive. Mojave is first on left in bootpicker which is probably why it defaults there.
If I reboot or shutdown the Mac restarts back into Mojave!
I have been using the same EFI and config from the HWAccel thread since Catalina where I had no issues. The Big Sur install was done from Catalina and Migration Assistant to pull everything across. The only customisation in the config is the UIScale for 4K.
I am going to try the original Config from this thread now to see if that helps at all. All very weird because there were no issues with Catalina before, and the fact that USB keyboard (back panel) is 'dead' on startup (works fine after OS has booted), long before OS is loaded implies to me that it has nothing to do with the OS.
This is very weird, maybe something else is going on besides OC config. Did you tried flashing 144.0.0.0.0 MP51.fd to see if the HID problems stop?
Doesn't anyone have an idea on what to do? Happens regularly. Every cold boot this happens, after second boot it's alright, no panic. Always the first cold boot.
Here the panic of today:
Hi tsialex - how do I do that? Its already 144.0.0.0.0. so does that mean I need to use some other software?
I did a text compare on the CDF config in this thread and the one I am currently using and there were so many differences that I don't really understand so I didn't replace the config yet.
Other than the keyboard stopping functioning now and again the biggest issue is the booting -- which seems to switch randomly between mojave and big sur -- and the lack of the regular keyboard to use the picker (I leave another plugged in front panel at the moment to switch the picker if necessary).
Alright, I may have found my first "problem" with Catalina on OpenCore. If anyone has any ideas about this, please let me know.
The problem is that in LogicPro 10.6, there is a feature where you can hover the mouse over a certain plugin button and a little popup alert normally shows up displaying some information (plugin latency is the info for anyone interested). I can confirm with other users that this feature still works on LogicPro 10.6. And it works for me with older versions of LogicPro on Mojave also. It does not work for me though on this 5,1 OC Catalina setup. I get nothing.
All other aspects of hardware acceleration and metal GPU seem to be working fine for me, I haven't encountered any other problem....so I don't know for sure if this is related to OC or not...but just wondering if anyone has any ideas about something like that not quite working right under this OC setup.
I am using the exact OC setup as defined by cdf in post #1, including hardware acceleration.
The problem is that in LogicPro 10.6, there is a feature where you can hover the mouse over a certain plugin button and a little popup alert normally shows up displaying some information (plugin latency is the info for anyone interested). I can confirm with other users that this feature still works on LogicPro 10.6. And it works for me with older versions of LogicPro on Mojave also. It does not work for me though on this 5,1 OC Catalina setup. I get nothing.
All other aspects of hardware acceleration and metal GPU seem to be working fine for me, I haven't encountered any other problem....so I don't know for sure if this is related to OC or not...but just wondering if anyone has any ideas about something like that not quite working right under this OC setup.
I am using the exact OC setup as defined by cdf in post #1, including hardware acceleration.
I have the same 5,1 OC Catalina setup over here and I can confirm that the pop up works as expected. I can see the plugin latency when hovering over any insert plugin. I'm using Opencore 0.6.3 from h9826790's package.
Not sure if there are any differences at all. It's just a pre-configured package. I have the exact same computer as you minus the bluetooth/wifi upgrade.
Can you point me to somewhere I can get that pre-configured package or info about it to find out what is different then post#1? It must be different in some way or it would not exist. I need to find out if something he did for hardware acceleration is perhaps the reason its working for you and not for me. It may or may not be related to OC at all...but I'd like to get to the bottom of it if so..
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...
forums.macrumors.com
Thanks I will look to see what he may have done differently then cdf.
Now that this has come up I am noticing that NONE of my tooltips in any applications are working. Absolutely none. Not just LogicPro.
I haven't had any other strange problems related to hardware acceleration or metal GPU.... but... maybe that's it..
Now that this has come up I am noticing that NONE of my tooltips in any applications are working. Absolutely none. Not just LogicPro.
I haven't had any other strange problems related to hardware acceleration or metal GPU.... but... maybe that's it..
I looked at that link. Its hard to decipher what exactly is different between his setup and cdf's, which was probably discussed in these forum threads over the course of months...but anyway... I will have to investigate that more to find out.
One thing I also noticed in his notes is that he did something to get TRIM support and that reminds me that I noticed my SSD's had TRIM disabled...I manually enabled them, but this makes me wonder if I have done the right thing since he apparently determined some solution a "TRIM problem". aye...this is probably a dozen issues that he solved in some way with lots of forum posts scattered all over the place explaining it... I'm hesitant to use his OC config without understanding exactly what's in it though. I'll try to do some research. Perhaps that is why my tooltips aren't working, some little thing that he or others have figured out and written about somewhere in this 5000+ post thread... perhaps something different then tooltips specifically that just happens to fix tooltips too.. I dunno...
(sigh)...and I thought I was done...
One thing I also noticed in his notes is that he did something to get TRIM support and that reminds me that I noticed my SSD's had TRIM disabled...I manually enabled them, but this makes me wonder if I have done the right thing since he apparently determined some solution a "TRIM problem". aye...this is probably a dozen issues that he solved in some way with lots of forum posts scattered all over the place explaining it... I'm hesitant to use his OC config without understanding exactly what's in it though. I'll try to do some research. Perhaps that is why my tooltips aren't working, some little thing that he or others have figured out and written about somewhere in this 5000+ post thread... perhaps something different then tooltips specifically that just happens to fix tooltips too.. I dunno...
(sigh)...and I thought I was done...
I really don't think OC could or would cause tooltips to not display. More likely to be some app/tweak that is installed.
Maybe a long shot, but check out the suggestions on this page, with the caveat being that it dates back to the "big cat" era--I have no idea if those terminal commands are still applicable on 10.15. But easy enough to try and see.
Maybe a long shot, but check out the suggestions on this page, with the caveat being that it dates back to the "big cat" era--I have no idea if those terminal commands are still applicable on 10.15. But easy enough to try and see.
Interestingly... this is what I see is the currently value...which is obviously the problem
Code:
defaults read -g NSInitialToolTipDelay
1000000I don't know how that could been set to that high value... but...anyway, deleting it fixed the issue.
Code:
defaults delete -g NSInitialToolTipDelayOn a side note....
While I was looking at h98's package mentioned above I noticed a comment about
TRIM support...does anyone know what that issue was about?I have the LP 10.6 and for me it works ok. GTX 680 flash, without any modification in OC for it.
Attachments
My package is aim for providing HWAccel. That aim for one package fit all with as many functions (that requested by the users) as possible.
If you want to properly config OpenCore for your own cMP (e.g. keep that as clean as possible), then post #1 in this thread has everything you need to know.
For your tooltips issue, you can boot Catalina without OC, then you will know if that's OpenCore related in few minutes. And if not, then you better open another thread in the Catalina forum for this particular issue.
And enable TRIM by using the trimforce command is the correct way to do it.
I can't see anything wrong, you said that's a newly installed Catalina, then TRIM should be disabled by default (apart from NVMe). That's completely normal.
The "easy to install package", (I think) is not more than the first post, but specific to AMD Hardware Acceleration, in various versions of OC. What I would like to know how I enable TRIM through OC ...
Sorry for my English: Google Translate.
Yes yes, the Model (A1243)
In Big Sur a MIDI Controller Piano was not shown through any USB port of the cMP, and for the HUB keyboard (A1243) it works ok.