Last os for intel macs probably ? (Leopard was the last for ppc macs)
Next year they start dropping m1 macs ? (like they did with the first intel chips that was not core2duo)
I know its a wild guess, but Apple .... ?
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.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Next year they start dropping m1 macs ? (like they did with the first intel chips that was not core2duo)
I know its a wild guess, but Apple .... ?
I don't think so M1 and M2 are very simliar in arch. Also the M1 Pro, M1 Max share the same CPU and GPU cores just more of them.
M1 will be here for a while
Thank you OpenCore developers for all your hard work. Take your time. We'll be patiently waiting for the patcher to come.
Last edited by a moderator:
Apple will find a reason to dump my 2020 m1 mac soon 😉 ($$$)
Installed on iMac 21.5 Late 2013 Iris Pro, everything works, only video acceleration is missing, no errors found OCLP 0.4.6
Not until 2019 Mac Pro is replaced and dropped from retail.(5-7 years from that date)
M1 might be dropped by 2026 Mac OS release.(as 32 bit Intel was drooped by Lion.)
Last edited:
Hope you are right !
But ... I bought my iphone 7 less than 3 year ago from appstore is now ... booted ...
Last edited:
Have you triee a regular thumb drive? It can be a real chore trying to boot off an SD. I've made it work a few times, but more often than not failed and ended up going to a regular USB thumb, just to stop the aggrevation.
I'm encouraged to try this on a 2015 iMac i7 32gb 1Tb NVMe ... time to delve into OCLP 0.4.6 process
As for MacOs Ventura, I hope that eventually the devs will find a way to get this on older machines, it was already difficult to run Monterey on those machines, I got it to work on my 2012 ac Mini, this time it might take a lot longer.
Might buy an up to date Mac, it's already 10 years old, runs well though for the things I use it for.
Lots of praise for the Developers.
Might buy an up to date Mac, it's already 10 years old, runs well though for the things I use it for.
Lots of praise for the Developers.
The OCLP developers have announced on GitHub (posted here many times now) that we will have to wait about 6 months to see if there may be a possible solution via OCLP. So, we won’t know for some time about ivy bridge macs from 2012.
If the goal of this thread is to help get Ventura running on legacy macs and spread helpful information, the above comment is cute, but also is neither healthy nor helpful speculation. It is probably best just to wait and check in here or GitHub from time to time over the next 6 months to see if any solution emerges via OCLP or another source. It is also entirely possible that a solution will emerge after a full year has passed. Remember how long it took to get graphics acceleration on pre-2012 macs for Big Sur? It took quite some time—more than 9 months from the first public beta, if memory serves me correct. So all of these comments are quite premature and short-sighted. If you look at the history of macOS on unsupported machines, you will see that solutions emerge sometimes a full year or years after a release. I would wager that after a year, some kind of solution will have emerged for Ventura.
You can read for yourself here about OCLP’s best guess:
https://github.com/dortania/OpenCore-Legacy-Patcher/issues/998
N.B.:
It might be a good idea to post this blurb below from GitHub clearly in the first post of this thread. That may help reduce the “are we there yet? Are we there yet?” posts and the “goodbye, my beloved 2012 Mac“ posts.
Overall estimate time for support
Looking at all the issues in front of us, I don't believe there's any short term possible fixes for the commuity to use. Best time frame would be 6 months from now when a proper build of OpenCore Legacy Patcher can be released, but even this is difficult to promise.
Last edited:
MacBookPro13,3 (the only computer with a Polaris GPU and no Ventura support) does in fact have dGPU acceleration, but sleep and brightness aren't working and the GPU shows as "AMD Radeon Polaris". This appears to be because ATY,Berbice support was removed from AMD9500Controller. I am going to see if spoofing as ATY,Longavi (the 2017 MBP; same connector config) works.
He just needs to install M1 Mini logic board into 6200’s housing.😂
Sad to hear all this, got myself a base early 2013 Retina 15" 7 months ago, because I had too many troubles with my older model without Metal support, but it seems like the troubles are about to begin again.
At worst ill have to spend all my money (which i funnily dont even have) on something like a used 2018 15", cant go for the M1 14" or the M1 Air/Pro, as its too small.
Or stick around with Monterey, if Apple manages to perfect it.
At worst ill have to spend all my money (which i funnily dont even have) on something like a used 2018 15", cant go for the M1 14" or the M1 Air/Pro, as its too small.
Or stick around with Monterey, if Apple manages to perfect it.
It does, and adding AppleIntelSKL*.kext/bundle fixes sleep and brightness!
Instructions:
- Install Kernel Debug Kit
- Copy AMD9500Controller.kext from /Library/Developer/KDKs to somewhere else
- In a hex editor, replace all instances of Longavi with Berbice in the kext's executable
- Mount writable system volume
- Copy the modified kext along with AppleIntelSKL* from Monterey to writable volume's SLE. Skip AppleIntelSKLGraphicsMTLDriver. It doesn't work yet.
- Rebuild kernel collections with kmutil
- Create new snapshot with bless and reboot
These instructions are intentionally written in a way that requires some patching knowledge to understand because they aren't ready for the average person to use yet.
Last edited:
Ventura's Patcher as difficult as Sierra(which is the first version to drop support for Intel processors without SSE4.1,and nobody had written an opcode emulator for it)
Because Woodcrest(Mac Pro 2006) or Merom have SSE3!
SSE 4.2(Nehalem) can be emulated on 4.1 processors(Penryn)
MP3,1 (& others?) SSE 4.2 emulation (to enable AMD Metal driver)
MouSSE (Partial SSE4.2 Emulator) Public Release Current version: 0.95 (8 Jun 2021) When referring folks to MouSSE, please just link directly to this post, which will always contain the latest version & info. EDIT (8 Jun 2021/1 Sep 2021): Monterey changed things up, so a new version was...
forums.macrumors.com
...so I ended up with a wrong / mismatching root hash after copying the three files from my M1 Ventura crypto folder in preboot. This prevents further booting on i.e. i5 MacBook Pro 6,1.
Flags for root auth. are already set by OCLP and don't seem to do the trick.
What am I missing - is volume sealing or snapshotting involved? Can the hash be re-calculated and thus fixed somehow?
btw, I found the tool "Mountain" very handy to mount the preboot volume(s). It's available in a 30min. free usage version. Full version also very affordable - and I talked to the author, update for more APFS functions will be worked on soon...
Flags for root auth. are already set by OCLP and don't seem to do the trick.
What am I missing - is volume sealing or snapshotting involved? Can the hash be re-calculated and thus fixed somehow?
btw, I found the tool "Mountain" very handy to mount the preboot volume(s). It's available in a 30min. free usage version. Full version also very affordable - and I talked to the author, update for more APFS functions will be worked on soon...