macOS 15 Sequoia on Unsupported Macs Thread

[Mystere65]

@Mystere65 That's interesting, because here WhatsApp Desktop is crashing at startup, too.

Unfortunately, you cannot use older versions of WhatsApp Desktop, the program expires and can no longer be used afterwards. You are therefore forced to update. In our case, this means that you can no longer use the program.

Is there perhaps some kind of add-on that simulates AVX2?

AVX 2 is an additional extension to the AVX instruction set and was only available in later Haswell processors.
Late 2013 MacPros appear to be using E5 v2 processors, which is too early to get those additional AVX 2 instructions. AVX2 requires Haswell family processors.

 

[deeveedee]

I had the same bootloop problem until I installed yesterdays OCLP 2.3n with the new KDK 15.4, and updated to 15.4 OTA.
Works great now. I used recovery to reinstall 15.3 first.

Good to know that's an option for some. Even with OCLP 2.3n and new KDK, I'm still unable to boot MBP6,2. Will continue to wait for Dev updates.

EDIT: After unsuccessfully testing OCLP 2.3n post-install patches, I was able to revert 15.4 to a bootable state (without OCLP root patches) by doing this.

 

[TOM1211]

Good to know that's an option for some. Even with OCLP 2.3n and new KDK, I'm still unable to boot MBP6,2. Will continue to wait for Dev updates.

EDIT: After unsuccessfully testing OCLP 2.3n post-install patches, I was able to revert 15.4 to a bootable state (without OCLP root patches) by doing this.

Haven’t seen anything listed in the nightly that effects 15.4 submitted also haven’t seen any success stories on discord either but could depend on how old the model is or maybe luck.

 

[ronton3]

Haven’t seen anything listed in the nightly that effects 15.4 submitted also haven’t seen any success stories on discord either but could depend on how old the model is or maybe luck.

Did you see the link I posted on #2722, that appears with the nightly.

 

[deeveedee]

Did you see the link I posted on #2722, that appears with the nightly.

I think all he was saying (don't want to put words in any mouths) is that there were no post-2.2.0 commits to OCLP that would fix the 15.4 issue that some have reported. The most recent KDK is downloaded by both OCLP 2.2.0 and OCLP 2.3.0nightly.

 

[ronton3]

I think all he was saying (don't want to put words in any mouths) is that there were no post-2.2.0 commits to OCLP that would fix the 15.4 issue that some have reported. The most recent KDK is downloaded by both OCLP 2.2.0 and OCLP 2.3.0nightly.

View attachment 2486258
View attachment 2486259

Thank you for the clarification, I am not a software expert, I may have gotten lucky and thought it was progress. I do have 15.4 working well on internalHD and externalSSD. I may have misunderstood when I saw the message that a new KDK was just released. Sorry for the confusion.

 

[TOM1211]

Thank you for the clarification, I am not a software expert, I may have gotten lucky and thought it was progress. I do have 15.4 working well on internalHD and externalSSD. I may have misunderstood when I saw the message that a new KDK was just released. Sorry for the confusion.

deeveedee is correct in what I meant by my answer , also what I meant by might depend on machine/luck .

 

[Blackriton]

I have a iMac 2017 2,3 Ghz Intel Core i5 under Sequoia 15.3.1 and the last OCLP.Since last week, the Bluetooth module BCM_4350C2 stopped to work even after multi post-install with OCLP. Thanks in advance for ideas on what went wrong ??? and how to correct before thinking to change the module (if possible)

 

[houser]

I have a iMac 2017 2,3 Ghz Intel Core i5 under Sequoia 15.3.1 and the last OCLP.Since last week, the Bluetooth module BCM_4350C2 stopped to work even after multi post-install with OCLP. Thanks in advance for ideas on what went wrong ??? and how to correct before thinking to change the module (if possible)

Undo and then redo patches would be my first port of call. Installing 15.3.1 on top of existing install would be my second. And then redo patches, twice if needed. Good luck.

 

[macpro_mid2014]

Similar here on MBP11,1 but usable for now...

Installed 15.4b over root-patched 15.3.1 OTA on external SSD. Using OCLP 2.2.0.

After installation boots OK to login and desktop.
After root patching boot hangs (when the mouse pointer first appears) then reboots. Due to Window Server crash as the log says.
Boot completes in safe mode. Then removed AppleIntelHD5000Graphics.kext from /Library/Extensions, an old habit, then also boots in normal mode. No full graphics acceleration, wrong screen resolution etc but good enough to write this post.

WLAN OK after patching. Was using Ethernet during patching for metallib downloading.
Photos app seems OK.

Thank you!
It worked for me too, after I removed AppleIntelHD5000Graphics.kext from /Library/Extensions my MBP11,2 booted normaly again. Now, let's wait for a fix in OCLP.

 

[cab_007]

Thank you!
It worked for me too, after I removed AppleIntelHD5000Graphics.kext from /Library/Extensions my MBP11,2 booted normaly again. Now, let's wait for a fix in OCLP.

To save those with other machines like mine (10,1) with HD4000s, removing the AppleIntelHD4000Graphics.kext from /Library/Extensions does not resolve the boot hang. If you want to try, be ready to revert back to the last-sealed-snapshot

 

[nekton1]

Just for the record, I have 15.4 b1 running on a supported intel Mac mini 8,1 2018. No issues detected so far.

Pulled 15.4 beta 1 problems seem model specific with latest M4 Mac mini (Pro?) worst affected. Also pulled 18.4 beta bricked some iPhone models.

 

[macpro_mid2014]

Pulled 15.4 beta 1 problems seem model specific with latest M4 Mac mini (Pro?) worst affected. Also pulled 18.4 beta bricked some iPhone models.

I'll give it a try!

 

[ronton3]

I have a iMac 2017 2,3 Ghz Intel Core i5 under Sequoia 15.3.1 and the last OCLP.Since last week, the Bluetooth module BCM_4350C2 stopped to work even after multi post-install with OCLP. Thanks in advance for ideas on what went wrong ??? and how to correct before thinking to change the module (if possible)

Did you turn off Btooth restart then try it again.

 

[Larsvonhier]

I'll give it a try!

Works fine here on my 2020 M1 Air.

 

[Larsvonhier]

Did you turn off Btooth restart then try it again.

On some of our Mac Pro machines, it helped plugging in a (compatible, patch-supported) USB BT dongle to an external USB 2 hub, boot & patch for that, and remove it again after it was detected (which takes some time in some cases). Then the internal vintage BT fires up again...