Introduction
Ce tutoriel rapide explique ce qu'est OpenCore Legacy Patcher, comment il fonctionne et comment il peut servir à améliorer votre Mac.
-
-
Bon, c'est quoi OpenCore Legacy Patcher ? Et en quoi va-t-il améliorer votre Mac ?
-
En gros, OpenCore Legacy Patcher permet d'installer facilement macOS sur les Mac non pris en charge.
-
-
-
-
OpenCore Legacy PAtcher fonctionne uniquement sur les Mac listés ci-dessous. De même, vous devez utiliser OS X Yosemite ou une version ultérieure pour pouvoir utiliser l'application GUI.
-
MacBook 5,1 (fin 2008, aluminium) ou plus récent.
-
MacBook Air 2,1 (fin 2008) ou plus récent.
-
MacBook Pro 4,1 (15 pouces, début 2008) ou plus récent.
-
Mac Mini 3,1 (début 2009) ou plus récent.
-
iMac 7,1 (mi-2007)* ou plus récent. *Les modèles 2007 nécessitent une upgrade du processeur vers un processeur Penryn.
-
Mac Pro 3,1 (début 2008) ou plus récent.
-
Xserve 2,1 (début 2008) ou plus récent.
-
-
-
OpenCore Legacy Patcher ne modifie aucun fichier de démarrage dans macOS. La seule modification qu'OpenCore effectuera ultérieurement s'appelle « Root Patching » (modification de la racine) et consiste à installer des kexts personnalisés dans votre dossier /System/Library/Extensions/.
-
Cela permet principalement de réutiliser votre ancien hardware. Nous y reviendrons plus en détail ultérieurement.
-
Passez maintenant au tutoriel suivant : Tutoriel #2
Annulation : je n'ai pas terminé ce tutoriel.
77 autres ont terminé cette réparation.
Merci à ces traducteurs :
100%
Claire Miesch nous aide à réparer le monde ! Vous voulez contribuer ?
Commencez à traduire ›
5 commentaires de tutoriel
One problem I've seen with the tool is as soon as you start it, OCLP will want to patch the system you're on, whether you wanted that one patched or not. If you've previously used that system to build an installer for a different machine, it wants to install itself and then reboot your machine. Once it's running, if it has an issue with your current confioguration, it gives you NO way to exit the application. And it doesn't appear to have a way of clearing out or resetting any residual configuration.
All of this could be readily addressed, except there is no way to report an issue on Github, and their Discord community DEMANDS your cell number (no one gets my cell number except family members). So there is no way to get this bug fixed.
I must say, I have not seen this issue with OpenCore, but I will check into this.
Also, reporting information to Github is impossible. I tried it even by doing everything "correct." I still could get to forum, nor could I report a bug. I gave up there. It would be nice if this was easier.
Seems that if you hit this bug you have to dig through the "Library" settings for your user and remove any files/directories for OpenCore and dortania. I don't remember if there was anything else as well, but eventually got that working.
NOW my major problem with the iMac is it will only get part way through the install of any of the newer MacOS releases, and completely hang somewhere between 30%-50% of the way into loading the install. And it's not just MacOS either; Fedora39 also hangs around 30% (MSWin10 would crash/reboot before it even finished copying over it's installer files). This may end up being a parts machine (or I'll remove the guts and make it a monitor-only unit).
I have a few questions regarding OCLP that maybe someone can answer:
1- How to report an issue to the dev team as a regular user?
2- What will become of OCLP once the D at Apple decide to remove support for intel-based machine?
Thanks
Hey there. I would be happy to answer your questions.
So, reporting issues to GitHub is nearly impossible. I have tried everything from going on as a guest, adding a user account, joining the team, and I still can’t figure out why they make it so hard to report issues. So, if you have any issues with OpenCore, feel free to report them here, or simply ask a question.
As for the future with Apple Silicone and Intel-Based Macs… no one really has a straight answer as of now. I do have a theory regarding what will happen.
1. Someone is going to have to figure out how to add kexts into macOS so it will run applications on Intel-Based, even if the apps are for Apple Silicone.
2. When the Apple Silicone loses support (i.e. the first M1) my guess is Apple will blacklist it from updating, so OpenCore will have to spoof the model in order to update.
If something does happen in the upcoming WWDCs and Apple eventually removes all support for Intel-Based Macs, my guess is patching macOS will be very different.
