just making technically suggestions, as you all may hear from my writing my english is kinda very creative variant from a non native speaker
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
just making technically suggestions, as you all may hear from my writing my english is kinda very creative variant from a non native speaker
Would be quite pleased with myself if/when I get half as good in German!
"DIY OpenCore" was not a bad suggestion btw but as "DIY" can carry connotations of an imitation of a "real" deal, it was always going to get the thumbs down.
On acronyms and initialisms:
How to use articles before abbreviations - Editarians
I use a few abbreviations when I write, including FBI and NATO. Sometimes I use 'the' before them, but other times it seems wrong.
www.editarians.com
What I kind of knew but couldn't put my finger on is explained there: "if it would be used with the expanded form" of an initialism. I would think this applies to the OCLP, mainly because of "patcher" at the end, although I suppose some would use the full form without such.
Using Articles (A, An, The) Before Acronyms and Initialisms | Proofed
When do you need to use articles (i.e., "a," "an," or "the") before acronyms and intialisms? Check out our simple guide to find out.
proofed.com
All said though, about time to get back to normal. Especially given the announcement of the pathetic new Mac Pro.
Last edited:
Not sure I buy into that, or any, rule as being the absolute be all and end all. However it does sound a lot more convincing then the previous - good job for digging it out. However, in that case, are we encouraging people who use the OpenCore Legacy Patcher to use that project's Discord for their support queries? Or are we encouraging people who use OpenCore Legacy Patcher to use that project's Discord for their support queries? I would (genuinely!) still stick with the second. (If you can find anybody with a convincing explanation of when we do and don't use 'the' before band names, I'll be very impressed! ;-) )Would be quite pleased with myself if/when I get half as good in German!
"DIY OpenCore" was not a bad suggestion btw but as "DIY" can carry connotations of an imitation of a "real" deal, it was always going to get the thumbs down.
On acronyms and initialisms:
How to use articles before abbreviations - Editarians
I use a few abbreviations when I write, including FBI and NATO. Sometimes I use 'the' before them, but other times it seems wrong.
What I kind of knew but couldn't put my finger on is explained there: "if it would be used with the expanded form" of an initialism. I would think this applies to the OCLP, mainly because of "patcher" at the end, although I suppose some would use the full form without such.
Using Articles (A, An, The) Before Acronyms and Initialisms | Proofed
When do you need to use articles (i.e., "a," "an," or "the") before acronyms and intialisms? Check out our simple guide to find out.
All said though, about time to get back to normal. Especially given the announcement of the pathetic new Mac Pro.
Ignoring what had clearly been said before and looking at the first page linked:
Best to leave things where they are and close the subject.
Enough time has been wasted on yet another inanity and it would be insane to waste yet more.
As a final insane note, you don't use articles before names (band or any other). Pretty much for the same reason they are not used for abbreviations such as "NASA" where the abbreviation is effectively a name.
A band may however, for artistic reasons, have an abbreviation that is not a "name" or may have co-opted an article into their name themselves. Who knows what some crazy self anointed rocker decides to do on anything?
I am pretty sure you knew all that.
Best to leave things where they are and close the subject.
Enough time has been wasted on yet another inanity and it would be insane to waste yet more.
As a final insane note, you don't use articles before names (band or any other). Pretty much for the same reason they are not used for abbreviations such as "NASA" where the abbreviation is effectively a name.
A band may however, for artistic reasons, have an abbreviation that is not a "name" or may have co-opted an article into their name themselves. Who knows what some crazy self anointed rocker decides to do on anything?
I am pretty sure you knew all that.
Last edited:
From what I've seen in the Acidanthera OpenCore repository, it appears they are transparently changing references to macOS 13 (Ventura) to macOS 14 (Sonoma). I assume that probably means no big changes to OpenCore are foreseen in order to accommodate Sonoma at this time. And I also take it for granted that OC 0.9.3 won't be released this week.
Now that Sonoma has been announced and that, presumably (how terrible!), OCLP will be able to support it via patching on our ailing Mac Pros, I wonder if someone can share some light as to the possible progress in a project that is/was/used to be attempting to inject AVX/AVX2 functionality into the Mac Pro 5,1 bootrom. Is that still foreseeable or should we, at long last, seriously consider the unavoidability of using OCLP?
Now that Sonoma has been announced and that, presumably (how terrible!), OCLP will be able to support it via patching on our ailing Mac Pros, I wonder if someone can share some light as to the possible progress in a project that is/was/used to be attempting to inject AVX/AVX2 functionality into the Mac Pro 5,1 bootrom. Is that still foreseeable or should we, at long last, seriously consider the unavoidability of using OCLP?
Now with the new name firmly established, I think it is important not to forget the past. I suggest you add “Formerly known as OpenCore on the Mac Pro” somewhere.
Correct - from Github "Delay for a week to account for WWDC."
I think the situation is that Ventura and now Sonoma fundamentally do depend on AVX. So even though OCLP successfully (and impressively) manages to find compatible drivers for some parts of the system (using parts of Rosetta, iirc) it does not patch all of the system - some things still crash if you use them: voice assist, right? What else? Syncretic's project would (will?) be amazing, but I think I've understood (based on what he has said) that it's incredibly hard to trap AVX early enough, and in a way that catches everything.
Failing that, it is still not unavoidable to use OCLP - one could consider that Monterey is the final truly supported (by community efforts) macOS on the MP5,1. And even failing that, there's the possibility of manually adding the AVX support from OCLP to the config of this thread... (I suspect that might not happen, not least because that still doesn't provide full, as-native, support.)
Actually, hmm, the last one's probably even less of a flier than I just said, since it requires OCLP (or something) to repatch for you after each update. (Which I guess does indeed just leave two options, for now, full support on Monterey (via this thread or OCLP methods) or possibly quite good but definitely partial support on OCLP, for Ventura+.)
EDIT: @cdf - I wonder if a brief comment about the highlights of this issue could also be appropriate in the first post.... (sorry!):
Maybe "macOS Ventura and now Sonoma cannot be supported using the clean, unpatched approach given here. Ventura support is available via OCLP - but the support is partial - some operations crash the operating system, and so need to be avoided - and it requires a patched OS (with repatching after each upgrade) and lowered security settings."
That's a very rough first draft - and maybe something like that, even if it were to be added (by you!
), would not need to be right in para. 1.
Last edited:
While I don't think it is strictly necessary, given that Mac OS versions covered are listed in the very first sentence of Post 1, I suppose an explicit statement on limit of support in terms of Mac OS versions can be made.
In such a case however, the thread should just focus on itself and skip what any other method does or does not do, whether they do such fully or partially, and whether you need to increase or lower your security settings with them or not etc ... all of which are simply not the concern of Post 1; which is to explain what an approach is and how to implement the approach.
Hence, in my view, anything more that adding "Ventura and later are not currently supported" to Para 1 is too much.
As I help a little in a german forum:
When it comes to OCLP most of the guys and gals simply do not read the instructions.
Pointing to them is one step.
So why not link to the OCLP manual in post 1 when OCLP is written:
When it comes to OCLP most of the guys and gals simply do not read the instructions.
Pointing to them is one step.
So why not link to the OCLP manual in post 1 when OCLP is written:
That's an option but I am not so sure it is up to Post 1 to be the OCLP way finder.
It has already pointed to their official support channel and that should be enough.
An alternative is to point to their "ReadMe" on GitHub where a link to their official support channel and other stuff can be found. This might be more useful without taking on undue responsibility for guiding people looking for OCLP help.
It has already pointed to their official support channel and that should be enough.
An alternative is to point to their "ReadMe" on GitHub where a link to their official support channel and other stuff can be found. This might be more useful without taking on undue responsibility for guiding people looking for OCLP help.
That's not really a discussion for here, but there are other efforts to try and improve the 5,1 bootrom underway.
However it will get to a point when the 5,1 is simply too old to keep going - as new MacOS versions come along (we have Ventura, now Sonoma Beta) inevitably the time must come where it's game over for the old machines, perhaps unless you want to jump to Windows on them and then you have some more options.
Or do we just bite the bullet and everyone tries to procure second hand 7,1 machines... I jumped long ago and got one new at huge price - great machine but fuming at the future GPU situation. Even Hackintosh builds will probably go extinct as time goes on and Apple focuses on ASI.
@avro707: I can't quite understand the reason behind some of your remarks. For instance, you've stated that (like the rest of the universe) the MP 5,1 is aging. No surprise there. You also say it can be used to run Windows; yes, I would have thought so. You further point out that a cMP owner can choose to buy a different computer; thank you for that pointer. That's good stuff.
In any case, thank you for the piece of news that there are "efforts to try and improve the 5,1 bootrom underway".
In any case, thank you for the piece of news that there are "efforts to try and improve the 5,1 bootrom underway".
Hi,
I am still on 0.8.2, Mac Pro 5,1 running Big Sur and a AMD Radeon RX 580 8 GB
Since updating to 11.7.7 I get strange short "black outs" .. the screen gets black for a second or two, then works again.
Are there anyknown issues with 11.7.7 or is my GPU dying ?
best zac
I am still on 0.8.2, Mac Pro 5,1 running Big Sur and a AMD Radeon RX 580 8 GB
Since updating to 11.7.7 I get strange short "black outs" .. the screen gets black for a second or two, then works again.
Are there anyknown issues with 11.7.7 or is my GPU dying ?
best zac
Last edited:
Could be a few things. Check the least expensive and basics first
1. Check both cable ends and make sure they're fully connected
2. Try a different video cable
3. Try a different port on the GPU
4. Try a different monitor (if one is available)
5. If all else fails, its likely the GPU
Yes, sounds like a sync issue. What monitor are you using & at what resolution? Perhaps you might change resolution back to 1080p & see if that helps if you are viewing in 2K or above.
its a Dell U2715H (2560 x 1440 Pixels, 27")
didn't change the resolution for years.
is it possible that it has something to do with the 11.7.7 and 0.8.2 combination?
what OC settings could be related?
ps. the behaviour is strange..
sometimes it happens often right one after another time...
sometimes nothing happens for longer periods ...
you didn't update opencore because it's hard for you to deal with the settings?
what I would try if I were you:
there is already a standard preconfigured opencore packadge made by Martin Lo - you can try it - if the bug does not disappear - it means something in the methodology described earlier (cables, outputs, or the video card itself, although it may also be a power failure)
you can also try to rewrite in the kext folder Lilu, whatevergreen and featureunlock and replace with new versions from github - maybe it will help
but first recommend try Matrin's packadge (if post#1 is hard for you now)
no, bc i'm still on Big Sur and all worked fine until now
but updating to 0.9.2 is the next thing to try ...
I have updated to 0.9.2 now, but this didn't change anything.. the black screen still happens.
Usually it takes 5-10mins after booting but then the effect builds up...
sometimes to several 1s blackouts per minute.
Anyone with an idea if this could have anything to do with BigSur 10.7.7 / OpenCore Settings ?
Otherwise I need to find a new GPU.
Or... I remember baking a GPU in the past.. maybe I try that .-)
Usually it takes 5-10mins after booting but then the effect builds up...
sometimes to several 1s blackouts per minute.
Anyone with an idea if this could have anything to do with BigSur 10.7.7 / OpenCore Settings ?
Otherwise I need to find a new GPU.
Or... I remember baking a GPU in the past.. maybe I try that .-)
Last edited:
if i had to bet, id say the monitor is having incompatibility with this version of big sur, you can try installing mojave and see how it behaves. if nothing changes then i would suspect the rx580