Closed eaglebh closed 10 months ago
Duplicate of #52
Creating new issues won’t help us fix it.
Creating new issues won’t help us fix it.
Sorry for that, the idea was not to fill the issues tab, but adding a probably different scenario. As the other issue worked for the person with some workaround.
@eaglebh Issues of software are not specific to people. Besides, the issue is still open.
Thanks for keeping it on radar. Do you have any tip on what to try, look for?
I've seen some stuff specific to intel igpus, but I'm not sure if nootedred shares some options with it, is it worthy trying tips from this docs: https://dortania.github.io/OpenCore-Post-Install/gpu-patching/intel-patching/connector.html ?
I've also tried these tips, but ioreg was not able to show any display under the framebuffer: https://dortania.github.io/OpenCore-Post-Install/gpu-patching/intel-patching/connector.html
@eaglebh Not connector issue. Some missing logic; it fails sending the DPCD command to set the panel mode
Is it better to add info on the #52 instead of here? I don't know if it helps but the dmesg and agdcdiagnose outputs when booting using whatevergreen are here: dmesg agdcdiagnose
if you give some direction on what to look for, or some material on kext development related to this part, I can try to jump in and help on coding. It would be an interesting journey for me on my "free" time. I've worked on some Linux kernel very small stuff, still very newbie on the area, but would be happy to enter this new world and try to learn and help.
@eaglebh AMDRadeonX6000Framebuffer is the kext. Good luck with that :^)
First of all, congrats for the great work on this, I'm seeing a lot of users reporting success using nootedred kext. Please, when you have some time, please take a look on my issue. Maybe solving this will help someone else with similar problem.
I'm using the last build.
Describe the bug I used the NootInc Guide, then Dortania's opencore guide, and some other guides/forums on the Internet.
I've installed MacOS Ventura using whatevergreen kext, and it boots fine using it, no acceleration of course. When I change to nooted red, after the debug messages (I've verbose mode enabled), when it tries to go into GUI mode, the screen turns off/goes black. I'm using 2GB shared memory to vram, and enabled above 4g decoding, both using UMAF tool.
Steps to reproduce the behavior:
Expected behavior We expected to see login screen instead of black screen.
Screenshots Screen with whatevergreen:![image](https://github.com/NootInc/NootedRed/assets/2046899/eb3b7a67-1fd4-4844-a044-e12e2a51d14e)
Screen with nooted red:![image](https://github.com/NootInc/NootedRed/assets/2046899/2f29e386-46cb-4ce1-872f-0ca49adbca7e)
System Information:
Additional context Sorry to bother you with this one, but I've tried everything that I could. I've seen similar but not same issues reported here, like issue #52 , #120 and #124 . But with what was said I was not able to make it work. Please, let me know if you need more info, I can run commands using the ssh access or using VNC access, one weird thing is that using VNC when nootedred is enabled is more responsive than using whatevergreen.
sudo /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose | curl --progress-bar -Ffile=@- https://0x0.st
Output of AGDCDiagnose, above commandsudo dmesg | curl --progress-bar -Ffile=@- https://0x0.st
Output of dmesg command as aboveMy plist file
Thanks in advance.