In my fork, I still encounter the same issue. Even though I have already reverse engineered it, the problem has still not been resolved, and it has caused delays in the development of the forked project.
In my fork, I still encounter the same issue. Even though I have already reverse engineered it, the problem has still not been resolved, and it has caused delays in the development of the forked project.
In 4.0.0.16023, a major bug is solved that was preventing certain patches from being injected and working properly. The cause was SIP was set to 0x803 instead of 0xFFF, or in other words, completely disabled. On my side of the project, the kernel panic is not gone yet, but Failed to find bridge device is gone among other issues. @GUTY345@dingustech-git
Not really. I’m trying to fix the problem together with the community, but couldn’t find a solution yet. So I’m still researching on how to fix that issue.
In my fork, I still encounter the same issue. Even though I have already reverse engineered it, the problem has still not been resolved, and it has caused delays in the development of the forked project.
There are also bugs in OpenCorePkg itself that prevents unsupported T2 Macs from booting into macOS 26 Tahoe, I just found at least one. So I forked OpenCorePkg to find and fix these bugs together with the community. If you want, you can join me with finding bugs in OpenCorePkg, you can ask me and I can add you as a contributor or fork my own fork and then push a PR to my OpenCorePkg fork. @GUTY345
Kommentare
@albert-mueller ·
I'm working with @DrDonk to fix this issue.
#130
@GUTY345 ·
In my fork, I still encounter the same issue. Even though I have already reverse engineered it, the problem has still not been resolved, and it has caused delays in the development of the forked project.
@albert-mueller · · bearbeitet
In 4.0.0.16023, a major bug is solved that was preventing certain patches from being injected and working properly. The cause was SIP was set to 0x803 instead of 0xFFF, or in other words, completely disabled. On my side of the project, the kernel panic is not gone yet, but Failed to find bridge device is gone among other issues.
@GUTY345 @dingustech-git
@nkyzr929hc-netizen ·
Any news?
@albert-mueller ·
Not really. I’m trying to fix the problem together with the community, but couldn’t find a solution yet. So I’m still researching on how to fix that issue.
@albert-mueller ·
There are also bugs in OpenCorePkg itself that prevents unsupported T2 Macs from booting into macOS 26 Tahoe, I just found at least one. So I forked OpenCorePkg to find and fix these bugs together with the community. If you want, you can join me with finding bugs in OpenCorePkg, you can ask me and I can add you as a contributor or fork my own fork and then push a PR to my OpenCorePkg fork.
@GUTY345