github-actions[bot]
commented
2 months ago 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,1oriMacPro1,1. - (e)DP link training failure.
-NRedDPDelaywill 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.
CrystalVortex
macOS Version
Big Sur
What is your CPU's model?
AMD Ryzen 75700G
Please describe the behaviour in detail.
this happens when I add the NootedRed kext. The cable itself isn’t faulty since it works on Windows and without the nooted red kext on macOS
What should've happened instead?
It should display things correctly
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
No response