Random HWLibs failures in macOS Ventura
Zormeister opened this issue · comments
macOS Version
Ventura
What is your CPU's model?
AMD Ryzen 5 5625U
Please describe the behaviour in detail.
Boils down to:
Early init in the accel stack fails, TTL::initialise returns kIOReturnError
What should've happened instead?
Should be booting with full acceleration, instead when it happens it reverts to the Framebuffer.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
Greetings. It seems like this is the first issue you open on this repository.
We are letting you know that these are for bug reports or feature requests. Most of the reports we receive in this GitHub Organisation are user errors.
For the sake of saving time, here are the most common cases:
- Outdated version of this kext.
- Conflicts with other kexts (e.g.
WhateverGreen
). - Issues caused by other kexts like memory corruption (e.g.
AirportItlwm
). - Intended behaviour by Apple (e.g. V-Sync or cursor rendering).
- Using cheap hacks like kext/library downgrades (e.g.
OCLP
,BFixup
). - Duplicate kexts.
- Malformed config.plist caused by configurator software (
OCAT
,OCC
, etc). - Lack of TSC synchronisation or use of badly programmed TSC kext (only use
ForgedInvariant
). - Outdated macOS minor version (e.g. macOS 11.0.0 instead of latest).
- Using beta versions of macOS.
- Using the kext during installation or update. There is a Lilu bug which makes macOS stall during the last install phase.
- Incorrect SMBIOS. Please use
iMac20,1
,MacBookPro16,3
,MacPro7,1
oriMacPro1,1
. - (e)DP link training failure.
-NRedDPDelay
will fix this as mentioned in the README. This is last resort, black screen can be caused by other factors mentioned. - Insufficient VRAM size.
We will never support the use of configurator software, solutions like OCLP
/BFixup
, or using macOS beta versions.
This issue will be looked over by the respective maintainer when they can. In the meantime, look if you can resolve this yourself via checking the above.
Be patient, we are hobbyists.
We cannot replicate this issue, therefore further information will be required for resolution. I will update you further in the coming days with further instructions.
With the latest commit if you have -NRedDebug
in your boot-args you will get a shit ton of logs in dmesg. Using https://github.com/ChefKissInc/DiskDbg you will be able to have it saved in /Users
and send them here for further inspection. You will need to use https://github.com/acidanthera/DebugEnhancer as per usual as the dmesg will be several MBs. You know how to do this, so I hope you don't ask me to hold your hand through the process again.
Timed out waiting for response.