Random black screen when booting macOS Monterey and up

[CoolSoulz]

macOS Version

Monterey

What is your CPU's model?

AMD Ryzen 3 2200G

Please describe the behaviour in detail.

First, I added the NootedRed kext. Now whenever I try to boot, sometimes I get black screen and sometimes I get to my login screen.

What should've happened instead?

When I boot, I should get to my login screen all of the time.

If applicable, attach the .gpuRestart, .panic, etc file related to this issue.

No response

[github-actions]

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 or iMacPro1,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.

[CoolSoulz]

ok

[CoolSoulz]

Anyone ?

[treydb]

Greetings,

Have you tried any of these solutions ?

• Incorrect SMBIOS. Please use iMac20,1, MacBookPro16,3, MacPro7,1 or iMacPro1,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.

[alvindimas05]

Greetings,

Have you tried any of these solutions ?

* Incorrect SMBIOS. Please use iMac20,1, MacBookPro16,3, MacPro7,1 or iMacPro1,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.

I helped him and tried all of that and no luck. He can't change his VRAM, but I'm sure VRAM size isn't related to blackscreen issue.

[VisualEhrmanntraut]

I have seen an instance where manually specifying the EDID of the screen can fix the issue. You can do this using the AAPL00,override-no-connect device property. The type must be data and the value must be your display's EDID data. How to get this data varies between the operating system you will be using to do this, however I do not know the specifics myself. You can likely find information on this online. I hope this might help with your issue. I am not sure why this could be happening myself.

[CoolSoulz]

how would I get EDID on MacOS when I reinstall it?

[VisualEhrmanntraut]

You need to do this from an OS that is already working, like Windows or Linux. You can also use live media, like Windows PE or a Linux live CD.

[CoolSoulz]

Okay Sent from Proton Mail Android

…

-------- Original Message --------

On 9/16/24 5:15 PM, Visual Ehrmanntraut wrote: You need to do this from an OS that is already working, like Windows or Linux. You can also use live media, like Windows PE or a Linux live CD. — Reply to this email directly, [view it on GitHub](#297 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A46YGPWMZONMDCKB3ECONJDZW5J6TAVCNFSM6AAAAABN2DLKEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGEZDGMBXGI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[CoolSoulz]

@VisualEhrmanntraut I injected EDID, but black screen issue persists