-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Did you find a solution? #1
Comments
inconclusive solution; it happens less but ... it happens |
Ok, I find a solution for my black screen problem; it’s not an orthodox solution, but … it works, for the moment. I discovered we can solve the problem restarting WindowServer process, so I create a new user with admin privileges (I called it "reset”, but this is a personal choice) and i build a simple AppleScript to add in login element. The script is very simple: do shell script "killall -HUP WindowServer" password "password" with administrator privileges insert “reset” password and save it as application and then add to user “reset” elements login. Now, you can use it in case of black screen; you can do a blind login into “reset” account. |
Hi. Today i've updated to the latest Lilu, WEG and VirtualSMC. Removed the 4 pci references from deviceproperties. mount -uw /Volumes/[DISKNAME] Finally i updated to BigSur 11.2 and for now it's working. I've done several reboots and no black screen. |
mnmmm, I think it isn't a cache problem. |
Did you upgrade any kext?
|
I use the last release for all my kext, OC 0.66 |
The latest Lilu, WEG and VirtualSMC are 3 days old. Try upgrading those files, upgrade big sur to 11.2 and restore the PCIe x16 switch. I can confirm it’s still working and it never worked this way before. Before those operations I got black screen after few reboots. BTW i've just updated my bios to v4.0 and it still works without problems.
|
do not mind. the latest cold start gave me black screen :( |
Today black screen on cold start. Restored Pcie x16 switch to Auto and then OK. It's very random, BAH |
yes, PCIe switch does not solve. It could also be the driver of the card not working very well |
same issue |
no news at this moment |
my solution for now enable ssh login in settings/share sudo killall -HUP WindowServer |
https://forum.amd-osx.com/index.php?threads/blackscreen-handcrafted-solution.1507/#post-7729 in this post I suggest an handcrafted solution Ok, I find a solution for my black screen problem; it’s not an orthodox solution, but … it works, for the moment. I discovered we can solve the problem restarting WindowServer process, so I create a new user with admin privileges (I called it "reset”, but this is a personal choice) and i build a simple AppleScript to add in login element. The script is very simple: AppleScript: insert “reset” password and save it as application and then add to user “reset” elements login. Now, you can use it in case of black screen; you can do a blind login into “reset” account.
|
Seems that Bigsur 11.3 update solved the issue |
I solved before 11.3 with SSDT-PLUG.aml |
can you explain?
|
I add SSDT-PLUG.aml in EFI, the one in my posted EFI is modified for AMD
…--
il baronerosso via Android
Il sab 1 mag 2021, 15:08 sgufa ***@***.***> ha scritto:
can you explain?
I solved before 11.3 with SSDT-PLUG.aml
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3XOM2MNSYX2ISH5BUEMCDTLP4MRANCNFSM4WNWYGBQ>
.
|
can you ecplain what that patch does? |
the .aml affects the motherboard controls, using it will also show "Enable Power Nap" in Energy Saver in System Preferences. Honestly, I find it in a ryzentosh forum, I realize it has something to do with the behavior of the motherboard and trie it with a pleasant surprise. |
I have the same issues, but bit different hardware:
3900x
asus x470 prime pro
asus strix rx 5700
Sometimes it boots to a black screen, and sometimes i can login but it freezes after +-15 min.
It worked perfect until 2 days ago :(
The text was updated successfully, but these errors were encountered: