-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ventura Beta 8 - Does Not Boot #76
Comments
panic(cpu 2 caller 0xffffff801674a763): Kernel trap at 0xffffff8016c63d58, type 14=page fault, registers: Panicked task 0xffffff9548820218: 205 threads: pid 0: kernel_task Process name corresponding to current thread (0xffffff8baab8c0c8): kernel_task Mac OS version: Kernel version: System uptime in nanoseconds: 6895525099 last started kext at 6891095515: es.govost.ryan.Thunderbolt3Unblocker 1 (addr 0xffffff7fad376000, size 319488)
|
Happy to provide any other information you need. |
Ventura beta 8 does not boot with this module enabled +1 |
This also is not working with 9, 10 or 11. Executing: /usr/bin/kmutil install --volume-root / --check-rebuild |
Confirmed not working on the latest beta |
Same issue and can't reboot even in Recovery Mode to run csrutil enable |
reset nvram |
|
The kext provided on Issue #77 worked well for Ventura official release version 13.0, but now that version 13.0.1 is out, it is panicking, like the previous kext. I would rebuild the kext myself, but I don't have a developer account. How can I accomplish this without one? Thanks! |
just for version 13.0.1 |
13.1 Can used |
Should this also work for Ventura 13.2? |
|
no working on Ventura 13.3.1.... |
With 13.2.1 (22D68), I also get:
|
Ventura beta 8 does not boot with this module enabled. I reset PRAM and SMC and was able to boot, but as soon as I re-run the steps to enable the module and reboot, it kernel panics during boot. I will attach logs in a few minutes.
The text was updated successfully, but these errors were encountered: