search

ChefKissInc / NootedRed

The AMD Vega iGPU support patch kext. No commercial use.
https://ChefKissInc.github.io/nred
Other
1.55k stars 659 forks source link

Black screen on internal display #270

Open tlfares opened 1 month ago

tlfares commented 1 month ago

macOS Version

Ventura

What is your CPU's model?

AMD Ryzen 7 3700U with Radeon Vega 10

Please describe the behaviour in detail.

When NootedRed is enabled, only the external monitor works, and the graphics acceleration works fine. But the internal display stays completely black. The screen works when NootedRed is disabled but without GPU acceleration. I use the latest commit of NootedRed. image

What should've happened instead?

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

No response

MizuKumi commented 1 month ago

Put the laptop in sleep mode, then bring it out and see 2 active screens. Or try to activate 2 monitors via a third-party application. This is also the case with real macintosh. ¯_(ツ)_/¯

tlfares commented 1 month ago

Put the laptop in sleep mode, then bring it out and see 2 active screens. Or try to activate 2 monitors via a third-party application. This is also the case with real macintosh. ¯(ツ)/¯

I tried but after I reopened the laptop, the laptop screen is still off :/ What third party application can I try to activate it?

tlfares commented 1 month ago

In the system report, the internal screen is not even detected, only the external monitor image

VisualEhrmanntraut commented 1 month ago

I had a bug with my workflow and the bot did not reply to the issue with the first interaction greeting:

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.

tlfares commented 1 month ago

I had a bug with my workflow and the bot did not reply to the issue with the first interaction greeting:

Thx for your reply, I saw this in other issues threads and I already tried all of that 🥲

VisualEhrmanntraut commented 1 month ago

The greeting in the other issues is out of date in the TSC sync part.

tlfares commented 1 month ago

Yes the AmdTscSync kext is enabled

VisualEhrmanntraut commented 1 month ago

I sent the outdated text by accident. Check it again.

tlfares commented 1 month ago

Oh ok, I replaced it with ForgedInvariant but I still have the same issue

arquicion333 commented 3 weeks ago

Hello! I have a similar issue too. I've installed Ventura on my Dell Inspiron 3525 that works with a Ryzen 5 5625U and Radeon Vega 7. I having no luck with the internal display. It does not work, it has not signal at all most the time. I managed to end ud with the installation using and external monitor (hdmi). Ive already tried so many things. Debugs kexts, DSDT patches, etc... Some times the external display shows up as the second monitor and the internal display shows some black light. I could share my EFI or the Ioreg. The internal display is not even detected in the ioregistry. I may think it is relate to the iGPU EDID, but I just don't what to do with it. The Bios Setup of this Laptop is really basic. I'd read that it is necessary to increase the VRAM in order to have a proper performance but there is no way to change that using the bios setup. System Report shows the iGPU as Radeon Graphics 512mb. I'd checked all the stuff you marked on common cases with no luck. :(

tlfares commented 3 weeks ago

I'd read that it is necessary to increase the VRAM in order to have a proper performance but there is no way to change that using the bios setup.

I've tried to increase the VRAM set by the BIOS to 1 or 2Gb (using this tool https://github.com/DavidS95/Smokeless_UMAF) but that didn't changed anything for me 🥲

arquicion333 commented 3 weeks ago

I'd read that it is necessary to increase the VRAM in order to have a proper performance but there is no way to change that using the bios setup.

I've tried to increase the VRAM set by the BIOS to 1 or 2Gb (using this tool https://github.com/DavidS95/Smokeless_UMAF) but that didn't changed anything for me 🥲

I didn't try increasing de VRAM, because that is mostly related to the IGPU performance. This issue is related to the EDP (Embedded Display Port), or the EDID. Someone suggested me to use the Smoless_UMAF tool to change some Edp settings. I'm running the Smokeless_UMAF tool right now. At the PBS, I only have 2 options related: DP0, where I can choose EDP, DP or HDMI, and DP1, where I can choose DP or HDMI. There are no others settings related to the EDP that I can see. By default, the EDP is assigned to DP0. I guess that changing these variables won't fix the problem. And I'm a little afraid of missing the regular bios, because of the warnings related to dell's laptop users. I'd read about the fix for Dell's laptop but I found no way to delete Misc options by accessing to the tool's Boot Manager... Anyways, I think I could re-flash the chip bios with a programmer if something wrong happens.

Any ideas?

techmare commented 3 weeks ago

@tlfares Boot windows and go to ur task manager and then performance and then ram and check how much of your ram is reserved. If it is 2 GB then u have to 2 GB of VRAM

arquicion333 commented 3 weeks ago

@tlfares Boot windows and go to ur task manager and then performance and then ram and check how much of your ram is reserved. If it is 2 GB then u have to 2 GB of VRAM

Thanks, already did that! I can handle easily 4GB of VRAM cause the laptop have 16GB of RAM... Unfortunately it didn't work. I believe I have to create some special DSDT to have the EDP working, or create devices properties to address the EDID properly. I'm just burned out with this issue, but I'm not giving up. I will report myself later! Thanks, mate!

MacintoshSSD commented 3 weeks ago

Have you ever tried to add the dpdelay command into boot-args?

tlfares commented 3 weeks ago

Have you ever tried to add the dpdelay command into boot-args?

I did and nothing changed unfortunately

arquicion333 commented 3 weeks ago

Have you ever tried to add the dpdelay command into boot-args?

Hola amigo, Well, I did not, how would it be? I've found the internal display now, and the other connector. They go through the AMDRadeon kexts a frame buffer. But I can't figure it out how to creat a DSDT, or to make a custom EDID. Can you tell me about dp command into boot args? I will research about it. Thanks!

arquicion333 commented 3 weeks ago

Have you ever tried to add the dpdelay command into boot-args?

God yeah! -NRedDPDelay works flawlessly! Don't how I made it to ignore this point of the troubleshooting. It must be the devil... Muchas gracias, amigo!

tlfares commented 3 weeks ago

@tlfares Boot windows and go to ur task manager and then performance and then ram and check how much of your ram is reserved. If it is 2 GB then u have to 2 GB of VRAM

Yes for the dedicated GPU memory, it shows 2Gb