Skip to content

← All issues

Kernel panic on MacBookPro15,2 when booting into full working installation of macOS Tahoe 26.0

· by @dingustech-git

So I installed macOS Tahoe to an external drive via another computer that CAN run Tahoe, then attempted to boot off that drive using OCLP-T2 on my MacBookPro15,2

It goes to a kernel panic

Comments

@albert-mueller ·

So I installed macOS Tahoe to an external drive via another computer that CAN run Tahoe, then attempted to boot off that drive using OCLP-T2 on my MacBookPro15,2

It goes to a kernel panic

I have the same issue. I'm unfortunately on the same boat. And when I tried to format a partition or run First Aid I found that the UUID for the drive wasn't detected properly and traces back to OpenCorePkg bug. Just pushed a PR so the OpenCorePkg devs can fix this UUID mismatch. Once fixed, I think we should get a bit further.

@albert-mueller ·

I had found this issue while I was testing on my Mac mini 2018:
acidanthera/OpenCorePkg#620
The UUID being 0 when trying to run First Aid helped me find and pinpoint this issue easier than the Needs authenticator (81) or AMFI kernel panic this time.
@dingustech-git

@ma2thiasfiedler ·

Look into thedescriptopn of OCLP 2 it can not run an Tahoe 26.0. Minimum requirment ist Toahe 26.5

@albert-mueller · · edited

So I installed macOS Tahoe to an external drive via another computer that CAN run Tahoe, then attempted to boot off that drive using OCLP-T2 on my MacBookPro15,2

It goes to a kernel panic

macOS 26.5 is otherwise the absolute oldest version where some T2 patches are working. Though, even on that release, the UUID being 0 is another issue that causes kernel panic at the moment.