Closed pego149 closed 8 months ago
are you using the -NRedDPDelay
boot-arg? If no, can you please try adding it and then try again to see if you get video output on your internal display?
Yes I tried it with this boot-arg option but nothing changed.
I am attaching agdcdiagnose log when HDMI is disconnected, so I can see in connections there is "DCC Failed". Maybe this can be issue. agdcdiagnose.txt
I am using the latest version of NootedRed.
Is this actually true or did you just click it to make the issue
Misclick
Hi, yes I tried many builds of nootedred next, but yes I am sure that I tried last, too.
Hi @jalavoui I tried build from your post but without any success. I am attaching journal file from booting with drm debug boot flag from my kali linux: journal.txt
@pego149 is your BIOS up to date
Hi, I also have a G14 Zephyrus and I follow the guide from this guy's repo. You could check the EFI out there and rebuild your hackintosh. I could confirm it works fine for me with the 2020 G14.
For me, the Ventura
works better than the Sonoma
, so if you want to use it, remember to switch to the Ventura
branch as the main
branch is for Sonoma
. In my case, it's the 2020 model so I get the EFI inside the 2020
folder, I don't know which model you have so you could give it a shot with both the 2020
and 2021
.
@pego149 is your BIOS up to date
Hi, yes my BIOS is up to date
Hi, I also have a G14 Zephyrus and I follow the guide from this guy's repo. You could check the EFI out there and rebuild your hackintosh. I could confirm it works fine for me with the 2020 G14. For me, the
Ventura
works better than theSonoma
, so if you want to use it, remember to switch to theVentura
branch as themain
branch is forSonoma
. In my case, it's the 2020 model so I get the EFI inside the2020
folder, I don't know which model you have so you could give it a shot with both the2020
and2021
.
Hi, thank you for answering. Yes I tried this repo as source of my EFI folder but still without success. If I disable nootedred.kext the internal display works normally but without acceleration. When I enable nootedred.kext the internal display powers off during boot and then the HDMI display turns on and everything is shown only there (doesn't matter if hdmi cable is connected or not)
@pego149 is your BIOS up to date
Hi, yes my BIOS is up to date
Hi, I also have a G14 Zephyrus and I follow the guide from this guy's repo. You could check the EFI out there and rebuild your hackintosh. I could confirm it works fine for me with the 2020 G14. For me, the
Ventura
works better than theSonoma
, so if you want to use it, remember to switch to theVentura
branch as themain
branch is forSonoma
. In my case, it's the 2020 model so I get the EFI inside the2020
folder, I don't know which model you have so you could give it a shot with both the2020
and2021
.Hi, thank you for answering. Yes I tried this repo as source of my EFI folder but still without success. If I disable nootedred.kext the internal display works normally but without acceleration. When I enable nootedred.kext the internal display powers off during boot and then the HDMI display turns on and everything is shown only there (doesn't matter if hdmi cable is connected or not)
That's weird to hear. Maybe your model is not supported well? I think you should wait for updates from NootedRed
as they will be released soon to fix remaining issues and may support some systems as yours.
Please retry with the latest commit.
Hi @VisualEhrmanntraut thank you very much. Last commit works well and finally my laptop booted with working screen.
macOS Version
Sonoma
What is your CPU's model?
Ryzen 9 4900HS
Please describe the behaviour in detail.
When I want to boot on my ASUS zephyrus G15 GA502IV with enabled Nootedred.kext I am not able find my internal screen. Only HDMI output is successfully recognized (doesn't matter if it's connected) internal display on laptop is always black (turned off). When I disabled nootedred the screen works but as unknown display. HW acceleration works well with Nootedred.kext. I tried Ventura, too. Thank you.
What should've happened instead?
Internal display should work. I don't care about HDMI.
If applicable, attach the .gpuRestart, .panic, etc file related to this issue.
No response
Bug report submission terms