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.
Out of curiosity why are you still on Sierra? I know a lot of people who never upgrade but I would like to know what people’s reasoning is. I can never run old OS’s due to continually degrading software support

it works fine. dont wanna fuss with boot camp either it works fine with win10 and all my home-brew stuff.
32-bit support.

No reason to upgrade really, for a period of time of several years it was my primary and only machine so the risk wasn't worth the possible benefits.

My primary is now M1 Air on Monterrey

as I said before the difference is the Generation of CPU 2016 Models use the i5-6360U / i7-6660U while the 2017 models use i5-7360U / i7-7660U. the difference is the support of 10Bit HEVC Enc/Dec-oding Capability of the 2017 machines and the 2016 doesn't support it and its a core feature of Ventura so the 2016 ones got dropped mostly because of HEVC
Could've still been supported without HEVC
 
it works fine. dont wanna fuss with boot camp either it works fine with win10 and all my home-brew stuff.
32-bit support.

No reason to upgrade really, for a period of time of several years it was my primary and only machine so the risk wasn't worth the possible benefits.

My primary is now M1 Air on Monterrey


Could've still been supported without HEVC
Possible but 10 Bit HEVC is advertised as a CORE FEATURE meaning any System which don't support it won't run it Out of Box. That's the Same with Windows 11 Requirement for TPM2.0. Machine doesn't support it so the OS won't support the Machine Out of the Box
 
  • Like
Reactions: macpro_mid2014
You can always tell when someone(s) don't bother reading the posts in the thread before theirs. 🤦🏻‍♂️🤣
 
  • Like
Reactions: TheStork
[...]

Not officially supported in macOS Ventura, but currently not or only partly capable of running it
  • Machines without AVX2 support will no longer boot
  • This means devices with Ivy Bridge CPUs and older, basically all Macs older than Late 2013
  • Would require an opcode emulator to work around it
  • GPU drivers from before Kaby Lake (Intel) or Polaris (AMD) are removed
  • Even if you can boot, you might not have GPU acceleration
Developers will investigate readding support. No guarantees

*More information will be posted as time goes by. Thank you for your patience as the developers and testers tirelessly work on getting new patches ready.

This is the command in terminal to see if mac CPU support AVX2

sysctl -a | grep machdep.cpu.features

You'll get a report out like this:


machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C


So MacMini late 2012 Ivy Bridge and iMac late 2013 Core i5 out off race at the moment ...
 
Last edited:
  • Like
Reactions: 0xCUBE
MacBook Pro 13” mid 2014:

machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C

So am I good as it seems?

Just an OpenCore Legacy Patcher update needed if I understand correctly?
 
MacBook Pro 13” mid 2014:

machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C

So am I good as it seems?

Just an OpenCore Legacy Patcher update needed if I understand correctly?
sorry but i do not think that AVX1.0 is AVX2.0 🤔
 
This is the command in terminal to see if mac CPU support AVX2

sysctl -a | grep machdep.cpu.features

You'll get a report out like this:


machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C


So MacMini late 2012 and iMac late 2013 out off race at the moment ...
The late 2013 iMac, Haswell processor, supports AVX2
 
  • Like
Reactions: Lucky736 and tchek
both my 2014 and 2012 macmini's dont support AVX2 unfortionetly.
And other 2012 ,2011 and 2009 mac's I have also dont support it.
 
this thread aren't going to be as great as other unsupported thread.
all amd drivers of type x86_64h, h is for haswell, that basically mean avx2.0 is required, and those binaries are really using avx2:
just an example from x6000 gl driver bundle:
000000000001491e vbroadcastss %xmm5, %xmm5

only haswell based models has some chances, like mini2014, but intel graphics driver are KBL+ only
Ah well, they have only made trashcan usable with macos starting with 12.3.1 and now dropped it, previously had 8 years of reboots, rendering the machine mostly unusable.
 
Last edited:
Summarizing from my Monterey's post (https://forums.macrumors.com/thread...unsupported-macs-thread.2299557/post-31155260):

1- MacBookPro11,2 installs and boots (on external USB SSD) Ventura just by using a supported board ID on config.plist. No Kext was used in the experiment.

2- The display is recognized as a 47in monitor without any acceleration (dropped support for Intel Iris Pro - Metal 1)

3- Touchpad only clicks and moves the cursor around (no scroll, etc.)

Can't wait to try out future versions of OCLP...

Thanks

I have the exact same config (MacBookPro11,2), I was able to install and boot Ventura by using 14,3 as the spoofed model in SMBIOS settings. Have the same issues as reported by you.
 
  • Like
Reactions: macpro_mid2014
AVX 2.0 using the leaf7_features command on MacBook Pro mid 2014 i7 was hoping for 10 years out of MacBook Pro 2014 and at 8 years support plus security fixes it will have made it will be interesting to see if M1 gets that length of support good luck to those attempting.
 
Last edited:
  • Like
Reactions: macpro_mid2014
MacMini Late 2014 with Dual-Core i5:

@MacMini ~ % sysctl -a | grep machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
 
  • Like
Reactions: TOM1211
May I still be in business to run Ventura OSX13 under OCLP if it can be revised for OSX13?

My mid-2015 iMac 15.1 27" Retina has an Intel i5 4590 3.3 GHz Haswell processor that does support AVX2 according to the site below. (I am currently running OSX12.4 Monterey under OCLP 0.4.5 with no issues)


 
Screen Shot 2022-06-07 at 10.33.52 AM.png


Late 2015 27" iMac with Core i7.
No AVX2 support.

FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C

Looks like Apple is disabling it or not reporting it correctly in Monterey.

According to Intel, my CPU supports AVX2.
Instruction Set Extensions - Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.