Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
View attachment 2214656Atheros WiFi is also working
Hi, need some help,
I built Opencore 0.9.4 and OCLP 0.6.8-n
From Opencore 0.9.4, i copied
OpenCorePkg/Binaries/X64/EFI/OC/OpenCore.efi (the Debug version) to the /var/tmp/.../build from OCLP 0.6.8-n to get Drivers, Kexts from OCLP and use the installer to mount the EFI partition and copy the all directories to the drives.
Great I can boot Opencore 0.9.4 with the Kexts from OCLP, i see the Debug.
But i'm not understanding where to modify the Kexts for wifi ? lilu ? Whatevergreen ?
Well i know : RTFM
Thanks for explanation.
 
The OCLP-Sonoma password B.S. is still being circulated. Reading and understanding the OCLP documention, fully reveals the Sonoma-centric version of OCLP is readily available w/o any limts whatsoever. The sole limit is ignorance and spreading counterproductive B.S. on these forums.🧐
Where would I happen to find it tho ?
 
Did you understand what @K two wrote? There's no password anywhere. So what are you searching for? Use Google if you want to find out the progress on the Sonoma patch.
Uses Google to find out about macOS 14 Sonoma on Unsupported Macs despite being in the macOS 14 Sonoma on Unsupported Macs Thread. Too rich 🤪
 
Sonoma OCLP progress

Overall timeline for support

As with every new major release of macOS, developing a patcher becomes more and more challenging for our small group of hobbyists. As it stands, we're unsure when we'll be able to resolve all these issues.

Regarding proper support for macOS Sonoma on OpenCore Legacy Patcher, no accurate prediction can be made. But for those who'd wish for a rough estimate, we'd say 6 months from now when we're able to support Sonoma. The challenges presented with 3802, non-Metal and legacy wireless will unfortunately require extensive time and research to develop functional patch sets.

However otherwise, we hope everyone's excited for what's to come!
 
  • Like
Reactions: K two
Hello to all,
Installed Sonoma Beta2 on MacBook Pro 5,2 Mid 2009 17", EVO 860 SSD. It resides on its own volume (not partition).

Downloaded Sonoma Beta2 OTC (I have Apple developer account and I am enrolled in Apple Developer Beta program)

Installation went without major problems; took several installer-triggered reboots to finally arrive at the desktop.

MacBook Pro 5,2 requires external keyboard and mouse to be attached to the computer via a USB hub (USB hub is then plugged into USB port on the computer) in order to allow cursor movement and password entry. I installed latest OCLP 0.6.8n patches (I know it does not fully support Sonoma), and rebooted. There is no GPU acceleration, no WIFI, and no Bluetooth, but Ethernet port works fine, and CPU is "usable" for simpler tasks. Keyboard and track-pad are also fully functional. This report is posted from this Mac via Firefox; Safari has page rendition problems.

Hope this "data point" may be of help.


View attachment 2221758View attachment 2221759
Successfully installed Sonoma 14.0b2 on a very similar MBP5,2.
This time made a clean install using standard methodology. Using OCLP 0.6.7 release for EFI and root patches.
- erased the macOS partition on an external SSD
- installed 14.0b2 to it from a USB installer (InstallAssistant.pkg downloaded via MrMacintosh)
- with Migration Assistant imported all data from a Ventura 13.4.1 drive
- applied post-install root patches.
Result is equivalent to what RogueB obtained:
Writing from Firefox as Safari has rendering problems with the patch set (which is not made for Sonoma).
No WLAN but cabled Ethernet working fine.
No graphics acceleration, but usable system.
Need USB hub connected keyboard and mouse while running the installer and in Sonoma before applying root patches.

Very good result in this early Sonoma beta stage. Thanks to all developers and early testers!


[I did the clean install because my usual method (using CCC to update user data on the target SSD, then install over it) has failed his time with OTA installation as well as with USB installer - installation made volumes named "macOS - Data - Data - Data"... with an extra Data after each failed attempt. Could be CCC (which isn't Sonoma-ready yet) or the unorthodox method reaches its limits now.]
 

Attachments

  • thissys.png
    thissys.png
    64.3 KB · Views: 133
Successfully installed Sonoma 14.0b2 on a very similar MBP5,2.
This time made a clean install using standard methodology. Using OCLP 0.6.7 release for EFI and root patches.
- erased the macOS partition on an external SSD
- installed 14.0b2 to it from a USB installer (InstallAssistant.pkg downloaded via MrMacintosh)
- with Migration Assistant imported all data from a Ventura 13.4.1 drive
- applied post-install root patches.
Result is equivalent to what RogueB obtained:
Writing from Firefox as Safari has rendering problems with the patch set (which is not made for Sonoma).
No WLAN but cabled Ethernet working fine.
No graphics acceleration, but usable system.
Need USB hub connected keyboard and mouse while running the installer and in Sonoma before applying root patches.

Very good result in this early Sonoma beta stage. Thanks to all developers and early testers!


[I did the clean install because my usual method (using CCC to update user data on the target SSD, then install over it) has failed his time with OTA installation as well as with USB installer - installation made volumes named "macOS - Data - Data - Data"... with an extra Data after each failed attempt. Could be CCC (which isn't Sonoma-ready yet) or the unorthodox method reaches its limits now.]
It's unlikely that the volumes named -Data -Data -Data are a CCC problem. The same happened when trying to ran OTA installations on my iMac 13,1, which does not use CCC. So far, it has not been possible to install Sonoma on the iMac. Various attempts using OTA all hung at different stages of the installation, in spite of being allowed to run for 12 hours and more. USB patchers were not able to see the external HDD that is used to beta software. Sonoma can wait until the final release is available.
 
It's unlikely that the volumes named -Data -Data -Data are a CCC problem. The same happened when trying to ran OTA installations on my iMac 13,1, which does not use CCC. So far, it has not been possible to install Sonoma on the iMac. Various attempts using OTA all hung at different stages of the installation, in spite of being allowed to run for 12 hours and more. USB patchers were not able to see the external HDD that is used to beta software. Sonoma can wait until the final release is available.
Thanks, good to know that the multiple-Data happened on iMacs.
RogueB was successful with OTA 14.0b1 -> b2 on MBP5,2, in my case it was possible to install b2 from USB installer to a USB disk. But you are right, Sonoma can wait.

Anyway I am happy to have a way forward for exercising Sonoma on my MBP5,2 without bothering developers with it (I hope I didn't).

Just continued the CCC exercise - ran it to bring the latest data from my production machine (MBP16,1, 13.4.1) to the properly working 14.0b2 on the external disk of MBP5,2.
The disk was not bootable afterwards. It seems the system volume was gone, and the data volume was renamed to without - Data. I think I know that from Big Sur times (was fine with Monterey and Ventura).
But it was possible to install b2 over it from USB installer, data were still in place, running fine again with latest state of my production data. Enjoying new Photos as a test.
So yes, no multiple-Data despite CCC usage.
 
Thanks, good to know that the multiple-Data happened on iMacs.
...
Anyway I am happy to have a way forward for exercising Sonoma on my MBP5,2 without bothering developers with it (I hope I didn't).
...
The data data data plague is prominent on many of my systems without CCC´ing anything. Even the disk utility of the recovery/install seems to be faulty: If you rename volume or containers, it affects the naming upwards in the hierarchy as well. Also name changes only properly show after closing and re-opening the disk utility tool.

As to bothering the devs: I consider the self-censoring and some folks speaking on behalf of others/devs encountered here from time to time rather irritating. You might have noticed the silence in this thread after the cumulated faux-pax a couple of weeks earlier. Apparently took some time to recover...
 
  • Like
Reactions: K two and hvds
I've come to the realization that while some macs may be easy to patch to run Sonoma and other unsupported OS releases in Beta or Public, that it is in later releases that Apple strips away those portions of the OS that allow support to be hacked in until eventually, the old kexts, drivers, etc. are completely removed or just plain incompatible with the updates.

This will all end when the first Apple Silicon Only release of MacOS comes out and Intel machines are left unupdateable like PowerPC was back when 10.7 Lion came out in 2011 (about 5 years after the last PPC Macs were sold). I'm happy my 2013 iMac 14,2 can still run enough Ventura to meet my needs.

I heartily thank the developers for their hard work and support.
 
Last edited:
I've come to the realization that while some macs may be easy to patch to run Sonoma and other unsupported OS releases in Beta or Public, that it is in later releases that Apple strips away those portions of the OS that allow support to be hacked in until eventually, the old kexts, drivers, etc. are completely removed or plain incompatible with the updates.

This will all end when the first Apple Silicon Only release of MacOS comes out and Intel machines are left unupdateable like PowerPC was back when 10.7 Lion came out in 2011 (about 5 years after the last PPC Macs were sold). I'm happy my 2013 iMac 14,2 can still run enough Ventura to meet my needs.

I heartily thank the developers for their hard work and support.
Minor correction: 10.6 was already not supporting PPC architecture any more, not 10.7.
Minor hope: 10.6 developer betas supplied PPC kext and framework support that allowed special version mix to run on PPC (found many years later, also covered by a thread on MR). So it could be done again in a similar form, though requiring even more effort than the devs currently invest. It remains to be seen when we all come to that bridge ;-)
 
Last edited:
I've come to the realization that while some macs may be easy to patch to run Sonoma and other unsupported OS releases in Beta or Public, that it is in later releases that Apple strips away those portions of the OS that allow support to be hacked in until eventually, the old kexts, drivers, etc. are completely removed or plain incompatible with the updates.

This will all end when the first Apple Silicon Only release of MacOS comes out and Intel machines are left unupdateable like PowerPC was back when 10.7 Lion came out in 2011 (about 5 years after the last PPC Macs were sold). I'm happy my 2013 iMac 14,2 can still run enough Ventura to meet my needs.

I heartily thank the developers for their hard work and support.
You need to sue APPLE for knowingly deleting drivers and so on. After all, on any computer with x86_64 architecture, any system will work fine. We cannot afford expensive computers. And they (Apple) are very rich, and they also treat us like that...
The security of the 10.6.8 system is very good. The newer the system, the worse the security.
 
WTF are you talking about? 😐
Developers OCLP help poor guys to keep old computers. And the rich people from apple mock the poor guys. They make poor guys cry out money for new computers. Is this normal? They are forced to change the system every year. Is this normal?
That's why all the guys should sue together for apple's negligent attitude.
 
You need to sue APPLE for knowingly deleting drivers and so on. After all, on any computer with x86_64 architecture, any system will work fine. We cannot afford expensive computers. And they (Apple) are very rich, and they also treat us like that...
The security of the 10.6.8 system is very good. The newer the system, the worse the security.
HAHAHAHAHA Apple utilizes the best lawyers on earth. Straight from Stanford Law School to your suit. Suing Apple is willingly subjecting yourself to the bloodbath, and the blood is entirely yours. Apple's lawyer lobbiests have ensured that the federal law preserves their oligopoly for generstions, maybe forever. Apple can do whatever it wants. You have to decide for yourself if you want to continue making the choices Apple has decided you will make (if you decide to stick in their ecosystem).

I myself am well on my way to extricating myself from it.


OCLP has been great, but is ultimately a dead end. We all know this.
 
HAHAHAHAHA Apple utilizes the best lawyers on earth. Straight from Stanford Law School to your suit. Suing Apple is willingly subjecting yourself to the bloodbath, and the blood is entirely yours. Apple's lawyer lobbiests have ensured that the federal law preserves their oligopoly for generstions, maybe forever. Apple can do whatever it wants. You have to decide for yourself if you want to continue making the choices Apple has decided you will make (if you decide to stick in their ecosystem).

I myself am well on my way to extricating myself from it.


OCLP has been great, but is ultimately a dead end. We all know this.
Ultimately - yes, but this is true for everything.
OCLP and predecessor patchers have helped keep old Apple hardware up-to-date with new OS versions over many years now, and can do so for a few more years. I find that very good and have benefit for two legacy MBPs.
 
HAHAHAHAHA Apple utilizes the best lawyers on earth. Straight from Stanford Law School to your suit. Suing Apple is willingly subjecting yourself to the bloodbath, and the blood is entirely yours. Apple's lawyer lobbiests have ensured that the federal law preserves their oligopoly for generstions, maybe forever. Apple can do whatever it wants. You have to decide for yourself if you want to continue making the choices Apple has decided you will make (if you decide to stick in their ecosystem).

I myself am well on my way to extricating myself from it.


OCLP has been great, but is ultimately a dead end. We all know this.
And the institutions and frameworks within which lawyers from the Stanford Law School do operate will be here forever, right?
 
  • Like
Reactions: Larsvonhier
You need to sue APPLE for knowingly deleting drivers and so on. After all, on any computer with x86_64 architecture, any system will work fine. We cannot afford expensive computers. And they (Apple) are very rich, and they also treat us like that...
The security of the 10.6.8 system is very good. The newer the system, the worse the security.
macOS is apples Software. since they drop support for a specific system they no longer need the drivers in the system. it would unnecessary bulk up the system even more if they left old drivers in there. before posting maybe you should think
 
You need to sue APPLE for knowingly deleting drivers and so on. After all, on any computer with x86_64 architecture, any system will work fine. We cannot afford expensive computers. And they (Apple) are very rich, and they also treat us like that...
The security of the 10.6.8 system is very good. The newer the system, the worse the security.
I guess, WIndows will suit you more.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.