macOS 14 Sonoma on Unsupported Macs Thread

[LlamaLarry]

Anyone having issues with 1.4.0n and a Sintech adapter+3rd party NVMe? I bumped up my daily MBA to 1.4.0 a week or so ago and have been running into panic'd lockup several times a day, including sometimes immediately on reboot. I went back to 1.3.0 and seem to be stable for the past few hours.

Panic example below:

Spoiler

panic(cpu 2 caller 0xffffff80100c843e): nvme: "3rd party NVMe controller. Command timeout. Write. fBuiltIn=1 MODEL=Sabrent FW=RKT303.3 CSTS=0xffffffff US[1]=0x0 US[0]=0x7b VID=0x1987 DID=0x5012 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6147
Panicked task 0xffffff94e7f4adf8: 193 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff8682ae0b30, Frame : Return Address
0xffffffff00bdba80 : 0xffffff800e036c41 mach_kernel : _handle_debugger_trap + 0x4b1
0xffffffff00bdbad0 : 0xffffff800e1955c0 mach_kernel : _kdp_i386_trap + 0x110
0xffffffff00bdbb10 : 0xffffff800e184d0c mach_kernel : _kernel_trap + 0x55c
0xffffffff00bdbb90 : 0xffffff800dfd3971 mach_kernel : _return_from_trap + 0xc1
0xffffffff00bdbbb0 : 0xffffff800e036f2d mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffffff00bdbca0 : 0xffffff800e0365d3 mach_kernel : _panic_trap_to_debugger + 0x1e3
0xffffffff00bdbd00 : 0xffffff800e7d8d0b mach_kernel : _panic + 0x84
0xffffffff00bdbdf0 : 0xffffff80100c843e com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffffff00bdbe20 : 0xffffff800e713b9c mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0x8c
0xffffffff00bdbe70 : 0xffffff800e713ab6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffff00bdbea0 : 0xffffff800e090638 mach_kernel : _thread_call_delayed_timer + 0x508
0xffffffff00bdbee0 : 0xffffff800e0916c8 mach_kernel : _thread_call_delayed_timer + 0x1598
0xffffffff00bdbfa0 : 0xffffff800dfd319e mach_kernel : _call_continuation + 0x2e
     Kernel Extensions in backtrace:
        com.apple.iokit.IONVMeFamily(2.1)[5985F50F-0A7D-3A4B-88B3-9D4C9EC4E43B]@0xffffff80100c1000->0xffffff80100ebfff
           dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[07852425-8607-3C1A-B273-92FC0221EC02]@0xffffff800f69e000->0xffffff800f6d4fff
           dependency: com.apple.iokit.IOPCIFamily(2.9)[1B194276-D13F-32DD-8B6D-4751C1C73603]@0xffffff8010355000->0xffffff8010386fff
           dependency: com.apple.iokit.IOReportFamily(47)[7EE0B816-0F22-3141-992C-ECEA9CA4B021]@0xffffff8010397000->0xffffff8010399fff
           dependency: com.apple.iokit.IOStorageFamily(2.1)[A96D850A-038F-31D7-9F3D-A6775064548E]@0xffffff801048d000->0xffffff80104a4fff

 

[sfalatko]

iMac 13.1 plays perfectly unlike Mac pro 5.1... Mac Pro does not have AVX while iMac 13.1 does not have AVX2

MacPro5,1 does have AVX just not AVX2.

 

[tsialex]

MacPro5,1 does have AVX just not AVX2.

Nope.

MacPro6,1 have AVX and is the first Mac Pro to have Advanced Vector Extensions.

 

[webg3]

rbart,

Thanks. That's exactly what I expected - everything is working fine (except for some apps that need AVX2.0). I appreciate the confirmation that with DRM it isn't something with my system but is most likely part of patching Sonoma to fit on older systems that don't support AVX2.0

regards,
sfalatko

GPU needs to be compatible with Metal 1 at least to have the requirements met by the OCLP patch-root.

Working Intel HD Graphics 4000, MBA 2012.

 

[Mystere65]

Nope.

MacPro6,1 have AVX and is the first Mac Pro to have Advanced Vector Extensions.

This is why Apple TV doesn't work on Mac Pro 5.1... AVX support for the processors is missing, while on Ivy Bridge (iMac 13.1) it is present then with Haswell (iMac 14.1) AVX2 support begins.

 

[deeveedee]

Anyone having issues with 1.4.0n and a Sintech adapter+3rd party NVMe? I bumped up my daily MBA to 1.4.0 a week or so ago and have been running into panic'd lockup several times a day, including sometimes immediately on reboot. I went back to 1.3.0 and seem to be stable for the past few hours.

Did you already see this?

 

[MacRumors3590]

I'm having a oclp issue
1. I'm using oclp 1.4.0n and Sonoma 14.4 beta 3
2. My Video card is a polaris RX580 Non-Flashed
3. Everthing installs fine but when I Patch the system I get a black screen and have to re-install Sonoma to get back to a desktop
4. I also have a FLASHED for mac RX580 and that works fine when Patched
Note: I even tried disabling AMFI and also i'm using enableGOP for the Non-Flashed card

Any help would be great!!

 

[RumorChaser]

I am on Monterey, it's the last officially supported OS for this iMac 17,1. It's what to do after it's out of support. OCLP isn't a set it and forget it option as there are specific that wouldn't work as expected for me. Monterey is stable, but should i just forget about security risks since Chrome and Firefox will still receive updates after Apple is finished? That's my only real concern about upgrading. I could care less about features macOS already has what I need. since before Monterey.

It is difficult to talk security without a very narrow context. There are too many scenarios and "what if".

Very generally, if you keep your browsers up to date and you only run trusted software, and you don't have any big organization going after you, then you should be fine with an out of date system that has one way access to the internet (e.g. not receiving inbound traffic from the internet).

If you do have stronger requirements, look into Linux desktop on Mac. (Haven't tried personally)

 

[nekton1]

Anyone having issues with 1.4.0n and a Sintech adapter+3rd party NVMe? I bumped up my daily MBA to 1.4.0 a week or so ago and have been running into panic'd lockup several times a day, including sometimes immediately on reboot. I went back to 1.3.0 and seem to be stable for the past few hours.

Panic example below:

Spoiler

panic(cpu 2 caller 0xffffff80100c843e): nvme: "3rd party NVMe controller. Command timeout. Write. fBuiltIn=1 MODEL=Sabrent FW=RKT303.3 CSTS=0xffffffff US[1]=0x0 US[0]=0x7b VID=0x1987 DID=0x5012 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6147
Panicked task 0xffffff94e7f4adf8: 193 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff8682ae0b30, Frame : Return Address
0xffffffff00bdba80 : 0xffffff800e036c41 mach_kernel : _handle_debugger_trap + 0x4b1
0xffffffff00bdbad0 : 0xffffff800e1955c0 mach_kernel : _kdp_i386_trap + 0x110
0xffffffff00bdbb10 : 0xffffff800e184d0c mach_kernel : _kernel_trap + 0x55c
0xffffffff00bdbb90 : 0xffffff800dfd3971 mach_kernel : _return_from_trap + 0xc1
0xffffffff00bdbbb0 : 0xffffff800e036f2d mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffffff00bdbca0 : 0xffffff800e0365d3 mach_kernel : _panic_trap_to_debugger + 0x1e3
0xffffffff00bdbd00 : 0xffffff800e7d8d0b mach_kernel : _panic + 0x84
0xffffffff00bdbdf0 : 0xffffff80100c843e com.apple.iokit.IONVMeFamily : __ZN16IONVMeController18RequestAsyncEventsEj
0xffffffff00bdbe20 : 0xffffff800e713b9c mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0x8c
0xffffffff00bdbe70 : 0xffffff800e713ab6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffff00bdbea0 : 0xffffff800e090638 mach_kernel : _thread_call_delayed_timer + 0x508
0xffffffff00bdbee0 : 0xffffff800e0916c8 mach_kernel : _thread_call_delayed_timer + 0x1598
0xffffffff00bdbfa0 : 0xffffff800dfd319e mach_kernel : _call_continuation + 0x2e
     Kernel Extensions in backtrace:
        com.apple.iokit.IONVMeFamily(2.1)[5985F50F-0A7D-3A4B-88B3-9D4C9EC4E43B]@0xffffff80100c1000->0xffffff80100ebfff
           dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[07852425-8607-3C1A-B273-92FC0221EC02]@0xffffff800f69e000->0xffffff800f6d4fff
           dependency: com.apple.iokit.IOPCIFamily(2.9)[1B194276-D13F-32DD-8B6D-4751C1C73603]@0xffffff8010355000->0xffffff8010386fff
           dependency: com.apple.iokit.IOReportFamily(47)[7EE0B816-0F22-3141-992C-ECEA9CA4B021]@0xffffff8010397000->0xffffff8010399fff
           dependency: com.apple.iokit.IOStorageFamily(2.1)[A96D850A-038F-31D7-9F3D-A6775064548E]@0xffffff801048d000->0xffffff80104a4fff

I use a Sintech adapter with M.2 NVMe blade SSD in MacMini 2014 and have no problems running 14.4 RC with yesterday's 1.4n.

 

[Dummymac]

To revert back to Big Sur you must erase your disk as there is no uninstall option.

Option 1
- Backup all you data
- Download the latest Big Sur 11.7.10 from Mr. machintosh
InstallAssistant.pkg
- Create a USB installer using Apple instructions on the following link:
https://support.apple.com/en-eg/101578
- Boot from the created Install USB holding Option/ALT Key while after you hear the Chim.
- Using Disk Utility erase your Apple SSD Disk as APFS.
- Install macOS.

Option 2
- Boot into internet recovery using Option-Command-R
- Using Disk Utility erase your Apple SSD Disk as APFS.
- Install macOS wil download and install the latest supported macOS for your machine.

Good Luck

Which one should I erase? Disk0s2 or disk1s2? What does it mean “Not Mounted”? Any difference “Erase” and “Restore”?

 

[RogueB]

Hello Nekton1,

In the post above you mentioned OCLP 1.4n from "yesterday". Latest compiled OCLP 1.4n is from 2.20.24; is there a new OCLP 1.4n variant which can be build from source?

 

[steve123]

Which one should I erase? Disk0s2 or disk1s2? What does it mean “Not Mounted”? Any difference “Erase” and “Restore”?

It looks like you have a Fusion drive? The smaller 120GB disk is an SSD and the larger 1TB is a spinning disk?

 

[shafez]

Which one should I erase? Disk0s2 or disk1s2? What does it mean “Not Mounted”? Any difference “Erase” and “Restore”?

Select View All from the View menu next to Disk Utility in top bar then erase Apple SSD.

 

[MacinMan]

It is difficult to talk security without a very narrow context. There are too many scenarios and "what if".

Very generally, if you keep your browsers up to date and you only run trusted software, and you don't have any big organization going after you, then you should be fine with an out of date system that has one way access to the internet (e.g. not receiving inbound traffic from the internet).

If you do have stronger requirements, look into Linux desktop on Mac. (Haven't tried personally)

Thanks, and yes I have considered Linux for the Mac, and I am following a thread on MacRumors for that topic. As far as your guidelines in considering security. No one bothers me, in fact, in terms of online activity I just do messaging, access trusted sites like my bank site (also can do that on the phone via mobile app), YouTube, etc.The only two way communication I have on the Mac are mainly my media solutions such as Plex Media server, and I keep those up to date, and don't do betas. I think at this point, it would be reasonable to explain why I've tried to stick with the mac over going to a different platform, and why I gave Open Core a go. The plain up front fact is, I don't like touch screens for typing, and the speech to text dictation functions aren't reliable in always typing correctly for me on the phone. So I like to have the mac available for text messaging forwarding so I can have that physical keyboard access. Now, I don't need to use an unsupported OS for that function as that's been in macOS for several years, so the need to do open core in my situation would come down to what we've talked about the security concerns and also app support. What makes things easier for me is I've found cross platform solutions for many daily tasks that aren't specific to macOS, and I did that knowing Apple may go in a direction that wouldn't work for me. So, I was wiling to try Open Core, and I like it's potential. However, I think my overall requirements at too specific to make it a "it just works" solution.

Thanks again for the feedback and I'll take it into consideration.

 

[rbart]

I am not sure it's the best place to question yourself every couple of days about your personal usage of Linux/VM/Monterey/OCLP for your situation ...
I think you have all the information and tools to decide yourself what's the best solution for YOU !

 

[trifero]

I am not sure it's the best place to question yourself every couple of days about your personal usage of Linux/VM/Monterey/OCLP for your usages ...
I think you have all the information and tools to decide yourself what's the best solution for YOU !

For me, it´s not. It´s clear he needs a supported mac , or another platform. Not OC.

 

[Dummymac]

It looks like you have a Fusion drive? The smaller 120GB disk is an SSD and the larger 1TB is a spinning disk?

this is what the screen shows. So far, I just learnt that I have 1 TB fusion as hard disk.

 

[LlamaLarry]

Did you already see this?

No, but that is exactly what I am running into. I didn't update OC outside of OCLP, just updated with OCLP and not even my macOS. Took me a while to try rolling back because I just figured something was going wonky with my adapter or SSD.

I use a Sintech adapter with M.2 NVMe blade SSD in MacMini 2014 and have no problems running 14.4 RC with yesterday's 1.4n.

Thanks, can you tell me what version of NVMEFix.kext you're running? I suppose it could still be my stick as it was a cheaper one from 4 years ago.

 

[amaze1499]

Lads, this might be a little bit off topic or better pretty sure it is, but did anyone of you ever tried to use a USB C power adapter 96W or 35W with a USB C to MagSafe adapter for one of your 2012 MacBook Pros?

It’s my understanding it adjusts the power accordingly to what the MBP needs.

My power adapter died and I thought I could upgrade to one of the newer ones. Thoughts?

 

[tsialex]

Lads, this might be a little bit off topic or better pretty sure it is, but did anyone of you ever tried to use a USB C power adapter 96W or 35W with a USB C to MagSafe adapter for one of your 2012 MacBook Pros?

It’s my understanding it adjusts the power accordingly to what the MBP needs.

My power adapter died and I thought I could upgrade to one of the newer ones. Thoughts?

Some people that I know use the combo Baseus 100W power adapter + USB-C->MagSafe successfully, I even bought the combo to try myself, waiting for the MagSafe adapter to arrive from AliExpress, Baseus 100W already arrived sometime ago.

 

[deeveedee]

No, but that is exactly what I am running into. I didn't update OC outside of OCLP, just updated with OCLP and not even my macOS. Took me a while to try rolling back because I just figured something was going wonky with my adapter or SSD.


Thanks, can you tell me what version of NVMEFix.kext you're running? I suppose it could still be my stick as it was a cheaper one from 4 years ago.

In addition to dropping back to a previous version of NVMEFix.kext, you might want to review this and this.

 

[macinfo]

Apple released macOS Sonoma 14.4 (23E214)

 

[K two]

Apple released macOS Sonoma 14.4 (23E214)

Same build as the RC.

 

[rehkram]

Apple released macOS Sonoma 14.4 (23E214)

Good to know, thanks.

In an overabundance of caution I'll be sticking with 14.3.1 until the OCLP 1.4.0 public release appears and a few others have tested everything!

 

[K two]

Hello Nekton1,

In the post above you mentioned OCLP 1.4n from "yesterday". Latest compiled OCLP 1.4n is from 2.20.24; is there a new OCLP 1.4n variant which can be build from source?

Nope.