macOS 14 Sonoma on Unsupported Macs Thread

[MarvenSmith28]

My MBP10,1 2012 rMBP 15" with 3802-based graphics card still crashes with OCLP 1.1 on Sonoma 14.0 but it ran for 35 hours before doing so, so this is still progress. It sounds like from the documentation the team is still working on fixing issues and providing full support for 3802 based graphic cards in Sonoma, so I will hang tight.

Latest crash log data here:

Spoiler: Crash Log

panic(cpu 2 caller 0xffffff800464889b): userspace watchdog timeout: no successful checkins from WindowServer (2 induced crashes) in 120 seconds

Spoiler: Crash Log

​

​

WindowServer has not exited since first loaded​

​

​

service: logd, total successful checkins in 128210 seconds: 12820, last successful checkin: 0 seconds ago​

​

​

service: WindowServer (2 induced crashes), total successful checkins in 128163 seconds: 12804, last successful checkin: 120 seconds ago​

​

​

service: opendirectoryd, total successful checkins in 128210 seconds: 12819, last successful checkin: 0 seconds ago​

​

​

service: configd, total successful checkins in 128210 seconds: 12819, last successful checkin: 0 seconds ago​

​

​

​

​

​

Panicked task 0xffffffa9b0f2f9d8: 3 threads: pid 117: watchdogd​

​

​

Backtrace (CPU 2), panicked thread: 0xffffff9b4b3525a8, Frame : Return Address​

​

​

0xfffffff40b763550 : 0xffffff8001a3a111 mach_kernel : _handle_debugger_trap + 0x4b1​

​

​

0xfffffff40b7635a0 : 0xffffff8001b97be0 mach_kernel : _kdp_i386_trap + 0x110​

​

​

0xfffffff40b7635e0 : 0xffffff8001b8732c mach_kernel : _kernel_trap + 0x55c​

​

​

0xfffffff40b763660 : 0xffffff80019d6951 mach_kernel : _return_from_trap + 0xc1​

​

​

0xfffffff40b763680 : 0xffffff8001a3a3fd mach_kernel : _DebuggerTrapWithState + 0x5d​

​

​

0xfffffff40b763770 : 0xffffff8001a39aa3 mach_kernel : _panic_trap_to_debugger + 0x1e3​

​

​

0xfffffff40b7637d0 : 0xffffff80021d916e mach_kernel : _panic_with_options + 0x89​

​

​

0xfffffff40b7638c0 : 0xffffff800464889b com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27​

​

​

0xfffffff40b7638d0 : 0xffffff8004648364 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments + 0x2e​

​

​

0xfffffff40b7638f0 : 0xffffff800464742b com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x83​

​

​

0xfffffff40b763a20 : 0xffffff800214ec5f mach_kernel : _is_io_connect_method + 0x37f​

​

​

0xfffffff40b763b80 : 0xffffff8001b42d9f mach_kernel : _iokit_server_routine + 0x3a8f​

​

​

0xfffffff40b763ca0 : 0xffffff8001a12d90 mach_kernel : _ipc_kmsg_send + 0x570​

​

​

0xfffffff40b763d60 : 0xffffff8001a2ab68 mach_kernel : _mach_msg_overwrite_trap + 0x5d8​

​

​

0xfffffff40b763dd0 : 0xffffff8001a2b1d8 mach_kernel : _mach_msg2_trap + 0x3b8​

​

​

0xfffffff40b763ef0 : 0xffffff8001b6c8d2 mach_kernel : _mach_call_munger64 + 0x1f2​

​

​

0xfffffff40b763fa0 : 0xffffff80019d6db6 mach_kernel : _hndl_mach_scall64 + 0x16​

​

​

Kernel Extensions in backtrace:​

​

​

com.apple.driver.watchdog(1.0)[314A006B-0D2F-300C-97E5-414583A002FC]@0xffffff8004646000->0xffffff8004648fff​

​

​

​

​

​

Process name corresponding to current thread (0xffffff9b4b3525a8): watchdogd​

​

​

Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0 -nokcmismatchpanic -lilubetaall​

​

​

​

​

​

Mac OS version:​

​

​

23A344​

​

​

​

​

​

Kernel version:​

​

​

Darwin Kernel Version 23.0.0: Fri Sep 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64​

​

​

Kernel UUID: 0905511D-D697-32D8-8069-EA653FED4635​

​

​

roots installed: 0​

​

​

KernelCache slide: 0x0000000001600000​

​

​

KernelCache base: 0xffffff8001800000​

​

​

Kernel slide: 0x00000000016e0000​

​

​

Kernel text base: 0xffffff80018e0000​

​

​

__HIB text base: 0xffffff8001700000​

​

​

System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)​

​

​

System shutdown begun: NO​

​

​

Panic diags file available: YES (0x0)​

​

​

Hibernation exit count: 0​

​

​

​

​

​

System uptime in nanoseconds: 128210933477702​

​

​

Last Sleep: absolute base_tsc base_nano​

​

​

Uptime : 0x0000749b6f258688​

​

​

Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000​

​

​

Wake : 0x0000000000000000 0x000000066acf4d42 0x0000000000000000​

​

​

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 1 swapfiles and OK swap space​

​

​

Zone info:​

​

​

Zone map: 0xffffff9017553000 - 0xffffffb017553000​

​

​

. PGZ : 0xffffff9017553000 - 0xffffff9019554000​

​

​

. VM : 0xffffff9019554000 - 0xffffff94e5d53000​

​

​

. RO : 0xffffff94e5d53000 - 0xffffff967f553000​

​

​

. GEN0 : 0xffffff967f553000 - 0xffffff9b4bd53000​

​

​

. GEN1 : 0xffffff9b4bd53000 - 0xffffffa018553000​

​

​

. GEN2 : 0xffffffa018553000 - 0xffffffa4e4d53000​

​

​

. GEN3 : 0xffffffa4e4d53000 - 0xffffffa9b1553000​

​

​

. DATA : 0xffffffa9b1553000 - 0xffffffb017553000​

​

​

Metadata: 0xffffffdfefa35000 - 0xffffffe00fa35000​

​

​

Bitmaps : 0xffffffe00fa35000 - 0xffffffe012a35000​

​

​

Extra : 0 - 0​

​

 

[RogueB]

MBP5,2: 14.0 runs well with latest OCLP 1.0.1n (i.e. EFI and post-install patches). Only the show-desktop doesn't work (windows don't go away), as was already the case for earlier OCLPs.

Tried 14.1 beta on MBP5,2. Booting the USB installer hangs at an early stage. Same when using OTA, MacOS Installer hangs early while earlier phases of upgrade went well. This is the case with OCLP 0.6.9n, 1.0.0, and 1.0.1n.
I first did these trials on external USB target SSD, then plugged the same SSD to internal SATA, same behaviour.
KP logs attached.

Doesn't matter much as the existing 14.0 installation on this SSD survives the tests. Just to inform.
Thanks to developers for all the fantastic work!

I had the same experience with my MacBook Pro 5,2.
The KP log incorporated (as a "spoiler") into post #2284 on page 92 is identical to yours. The internal SSD is on SATA, while external SSD drive (Samsung Shield T7) is connected via a USB. Booting into either configuration caused an early hang irrespective of installation method, whether OTA or via USB installer.
No problem rebooting into Sonoma 14.1 beta1 after failure of the update.
I took one more step in testing, and attempted to boot via a USB thumb drive inserted into the USB hub I use to successfully login into MacBook Pro 5,2 after each system upgrade. The result was the same early KP. The USB hub test was prompted by the panic report, which nominally seems to center on the IOkit and USB interface(?), and the need to use the hub after each system update.
Hope a solution can be found. Latest OCLP 1.1n, from October 12, 2023 does not change the result.
Thank you to developers for their incredible work.

 

[BeatCrazy]

Again, if you can wipe it all and use an OCLP EFI on a USB for the install and then recreate the other partitions after that, that is what has worked for me a few times. Start fresh. Good luck.

Well I took a couple more runs at it.. Starting from Monterey, build/install OCLP to the EFI. Build a fresh Sonoma install from OCLP, right from the host Mac Pro. Wipe SSD and try to install. Gets stuck every time.

Sometime weird/different around Sonoma, as my Monterey clean installs always work great. I've probably tried six times now. I suppose I'll have to try again if we think OCLP 1.1 has substantial changes for my situation.

 

[Sven G]

This pmset option may help;
sudo pmset -b tcpkeepalive 0
--This command may produce a warning saying some features may not work properly. This is fine, it simply disables Internet access during sleep. This is the same as disabling "PowerNap" Apple's badly implemented (demented?) attempt to have apps update themselves during sleep behind the users back.
I found this command in a Japanese text file related to sleep and hibernation. I have used it for years and never seen any related issues, on both laptops and desktop computers.

Thanks; and, indeed, switching off Wake on LAN and PowerNap seems to have mitigated the issue: so far, no kernel panics. Now, it remains to be understood why leaving those features on crashes some Macs, after the displays go to sleep…

 

[Sven G]

One thing that maybe help is switching off the wake on LAN feature. Wake on LAN will cause the Mac to periodically "dark wake" for some seconds, refreshing the LAN and WLAN connections.
Maybe the Mac crashes during dark wake - but without dark wakes it would probably crash upon waking it up manually...

Thanks; and an interesting explanation, indeed (see also above): strange that this seemingly good and useful feature can crash a whole system…

 

[davidlv]

An interesting explanation, indeed (see also above): strange that this seemingly good and useful feature can crash a whole system…

@Sven; I think it is much more important to "cure" those crash on wake episodes than to understand why they happen, which is probably due to bad or incomplete programing on Apple's part. The pmset command <sudo pmset -b tcpkeepalive 0> is one of a set I found years ago, on a Japanese blog (all in Japanese of course, except for the command themself). I have used them all for years with no adverse affects. All shown below:

macOSã®å¯ç¸ã«ã¤ãã¦èããã㨠-- `pmset` - ã°ãããã ã

é»æºã¾ããã®è¨å®ï¼ åãããä½ã¨ãªãæ°ã«ãªã£ã¦ãã¦ï¼ãªãä½æãããããªãï¼åæ¥ã触ãã¾ãããï¼ãã·ã³ã®æ°èª¿ãã£ããã§ï¼ãã®è¾ºãæ´çãã¦ãããï¼ã¨æã£ãããã§ãï¼ å¿è«"ããã¾ã§èªåã¬ãã«"ã§æµãð ã¤ãï¼ã¹ãªã¼ãï¼ããããããªãï¼ å¾ã§è§¦ããããã¨ã¯æã£ã¦ããã®ã§ããï¼ãã¾ãã¡ã¹ãã¨å¥ã£ã¦ããªããã§ãããï¼ æãã«ï¼"ä½å¦ãåãããªãã®ãï¼ãï¼åãã£ã¦ããªã"ï¼...

baqamore.hatenablog.com

pmset -g Shows the settings you have set now.
sudo pmset -a hibernatemode 0 standby 0 autopoweroff 0
sudo rm /var/vm/sleepimage or sudo rm /private/var/vm/sleepimage
--Ignore any message saying there is no such file
Create a blanked zero-byte file so the OS cannot rewrite the file:

sudo touch /var/vm/sleepimage or sudo touch /private/var/vm/sleepimage

Make file immutable:
(sudo chflags nouchg ... to revert)
sudo chflags uchg /var/vm/sleepimage
or
sudo chflags uchg /private/var/vm/sleepimage
The sleep image file is actually in /private/var/vm/ but /var/vm/ is a symbolic link to that location.

sudo pmset -a proximitywake 0
sudo pmset -b tcpkeepalive 0
--This command may produce a warning saying some features may not work properly. This is fine, it simply disables Internet access during sleep. This is the same as disabling "PowerNap" Apple's badly implemented (demented?) attempt to have apps update themselves during sleep behind the users back.

sudo pmset -a standbydelaylow 86400
sudo pmset -a standbydelayhigh 86400
sudo pmset -a highstandbythreshold 0

If necessary;
sudo pmset restoredefaults

 

[OKonnel]

Maybe someone can give me an explanation and/or perhaps useful for OCLP Sonoma Developers
iMac 14,2 - CPU i7 - nVidia GTX780M

1) I tried to restart macOS Sonoma 14.0 (OCLP 1.1.0 Nightly) in Safe Mode, but the progress bar stops halfway and I am forced to forcefully shut down the Mac and then restart normally.

2) If an external USB-3 HD (in JHFS+) is connected directly to the USB sockets it prevents Bluetooth when starting the Mac which therefore does not recognize the Magic Keyboard and the Magic Mouse and Magic TrackPad.
(However, if I connect this HD to an USB-3 HUB, Bluetooth works well when restarted).
The problem does not occur with the other identical HD, but formatted in APFS and Time Machine.

Never had these problems with Ventura 13.3

 

[rbart]

For those who are concerned, OCLP is bringing back T1 support for Sonoma in latest nightly …
Very impressive !

 

[matsno]

Does anyone use a macbook 14.3? i have lost touchbar and touchid. Appreciate any advice I can get on this.

 

[rbart]

Does anyone use a macbook 14.3? i have lost touchbar and touchid. Appreciate any advice I can get on this.

Because it’s not supported (yet) in OCLP 1.0.1
But it’s coming (see upper)

 

[ChrisOSX]

This is a fresh install, and what I use works. For the most part it runs pretty flawless on my machine.

Idle standby / screensaver and or sleep causes black screen when resuming. Entering password brings me home like normal. It does cause WindowServer to error and throw a report in the DiagnosticReports folder.

The occasional login window error adds to that DiagnosticReports folder as well.

Thank you devs, keep up the outstanding work 👍

 

[davidlv]

For those who are concerned, OCLP is bringing back T1 support for Sonoma in latest nightly …
Very impressive !

Can you tell from the change log for the latest 1.1 nightly if any of the changes are related to macOS 14.1 beta 3?
That beta 3 absolutely refuses to work on my iMac 15,1. I have tried 2 times to install it but it crashes with a black screen and a bright Apple shining after the root patches and a reboot. Had to use a CCC backup and revert to 14.0, which runs fine (OCLP 1.1n (10-13-23). Just installed the latest OCLP nightly and noticed no issues on Sonoma 14.0.

 

[grumpy_Garrett]

hello! just wanted to ask if oclp 1.1.0 nightly fixed the widgets issue where it doesnt show text/information?

 

[jxid]

Hi to all. I am new to this forum. I want t ask about an issue that i have with my Mac and OCPL.
I installed the latest MacOS Sonoma in my iMac 27" Late 2009 10.1 and the blutooth does not working.
I use USB mouse and keyboard with no problem.
Before that i had install MacOS Ventura and blutooth was working just fine.
Is this a bug of OCPL 1.0.1 or is it something wrong with my Mac?
Thanks in advace for your time and help.

 

[Sven G]

For those who are concerned, OCLP is bringing back T1 support for Sonoma in latest nightly …
Very impressive !

… And it also fixes the not detected FaceTime PCIe camera in Sonoma 14.1b3: absolutely great! Now, if only also paravirtualized graphics in macOS VMs could be really fixed…

 

[Sven G]

Maybe someone can give me an explanation and/or perhaps useful for OCLP Sonoma Developers
iMac 14,2 - CPU i7 - nVidia GTX780M

1) I tried to restart macOS Sonoma 14.0 (OCLP 1.1.0 Nightly) in Safe Mode, but the progress bar stops halfway and I am forced to forcefully shut down the Mac and then restart normally.

2) If an external USB-3 HD (in JHFS+) is connected directly to the USB sockets it prevents Bluetooth when starting the Mac which therefore does not recognize the Magic Keyboard and the Magic Mouse and Magic TrackPad.
(However, if I connect this HD to an USB-3 HUB, Bluetooth works well when restarted).
The problem does not occur with the other identical HD, but formatted in APFS and Time Machine.

Never had these problems with Ventura 13.3

Yes, these are known problems, and for different Mac models.

 

[rbart]

Can you tell from the change log for the latest 1.1 nightly if any of the changes are related to macOS 14.1 beta 3?
That beta 3 absolutely refuses to work on my iMac 15,1. I have tried 2 times to install it but it crashes with a black screen and a bright Apple shining after the root patches and a reboot. Had to use a CCC backup and revert to 14.0, which runs fine (OCLP 1.1n (10-13-23). Just installed the latest OCLP nightly and noticed no issues on Sonoma 14.0.

You can easily read the changelog ...

 

[deeveedee]

@alissonss - Thank @rbart for the heads-up on coming OCLP attractions. This commit to OCLP might solve your problem. Wait for the new OCLP before spending any time on the camera issue.

EDIT:

For those who are concerned, OCLP is bringing back T1 support for Sonoma in latest nightly …
Very impressive !

I'm not concerned and I'm still impressed!

 

[davidlv]

You can easily read the changelog ...

@rbart Of course I read it, before asking that question. It is difficult to say if any of the 14.1 related changes are changes that would be related to the fact that 14.1 beta 3 won't install correctly on my iMac 15,1. Others have had success installing that beta, on different hardware. Sorry to bother you.

 

[roysterdoyster]

I used OCLP 1.0.1 to upgrade my MBP 4,1 15-inch from Ventura to Sonoma yesterday. I used a USB mouse attached to an external USB Apple keyboard.

Root patching was something I had to do twice. The first time, keyboard functionality wasn't installed. No BT, but wifi is functional.

The performance isn't great, but it's not terrible either. Considering the laptop is 15 years old, it is more than decent! So, congrats and great appreciation to the OCLP team.

Thanks. Did you do a clean install via external drive, or did you update OTA?

 

[deeveedee]

*** Hackintoshes are not supported by OCLP Devs. Do not ask for help with a hackintosh. ****

It's not a secret that I use OCLP to patch a Dell Latitude E6410 (emulating MBP6,2). Getting passed the anger and controversy that surrounds that, there's something amazing about what the Devs have accomplished...

When I was patching my Dell laptop with DosDude patches (also amazing) to run Mojave and Catalina, I needed to use a "heavier" Dell power brick to operate my patched/unsupported hack. With DosDude patcher and without the "heavier" power adapter, I experienced problems related to insufficient power being supplied to the laptop. Because of the heat dissipation, I even needed to modify the graphics and CPU heat pipes by augmenting them with copper heat spreaders.

With OCLP and Big Sur, Monterey, Ventura and Sonoma, I am able to use the much lighter Dell power adapter for my laptop without any problems. The Devs have achieved outstanding power management on my unsupported MBP6,2. Truly amazing.

*** Hackintoshes are not supported by OCLP Devs. Do not ask for help with a hackintosh. ****

 

[grumpy_Garrett]

hey guys how to install 1.1.0 nightly?

 

[rbart]

Nightlies are for people who are able to find how to install them...

 

[alissonss]

@alissonss - Thank @rbart for the heads-up on coming OCLP attractions. This commit to OCLP might solve your problem. Wait for the new OCLP before spending any time on the camera issue.

View attachment 2295938


EDIT:

I'm not concerned and I'm still impressed!

Thanks a lot, @deeveedee, I'll wait for this new update!

By the way, thanks @rbart for the awesome news!

 

[davidlv]

hey guys how to install 1.1.0 nightly?

Do you realize that this forum has a search function? That is how I found out about the nightly versions of OCLP.
Maybe you can use it too to find them. BTW, I am not being difficult, just practicing educational policies. Learning to use the search function will decrease pointless posts and save bandwidth.