Skip to content
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

USB C display causes generic display to crash [BUG] #29

Open
carelw opened this issue Aug 29, 2021 · 4 comments
Open

USB C display causes generic display to crash [BUG] #29

carelw opened this issue Aug 29, 2021 · 4 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@carelw
Copy link

carelw commented Aug 29, 2021

Describe the bug
When booting with a USB type-C display connected (mini DP doesn't seem to work and HDMI doesn't work due to external graphics card connectivity) the main laptop display seems to crash.

To Reproduce
Steps to reproduce the behavior:

  1. Boot with USB type-C display connected
  2. Screen seems to be zoomed in whilst booting
  3. Apple boot screen starts loading on main laptop screen, then stops working (goes black) and screen appears on the connected USB type-C display

Desktop (please complete the following information):

  • OS: Big Sur
  • Version latest supported
@carelw carelw added the bug Something isn't working label Aug 29, 2021
@brightplastik
Copy link

Hello. Same issue here too. It's a well known problem with the CPU family, and to my knowledge nobody has solved the issue.
BUT!
Easily enough, wait for the pc to fully bootup. Modify the OS to NOT go to sleep when you close the lid (google it).
When you apply this setting, the OS will move all your active windows on the external display by closing the lid.
Wait a few seconds, and by reopening it the pc will finally output on both screens, just a few seconds after the bootup (*).

*someone was suggesting the display eventually lights up after some minutes. It does not with my pc, but in exchange this works without waiting.

@zacmks
Copy link
Owner

zacmks commented Dec 6, 2021

There's another workaround as well:

  1. Go to:
    System Preferences -> Displays -> Arrangement.

  2. There, tick twice the checkbox "Mirror Displays" (enable/disable)
    image

  3. Then, your internal display should work fine.

*I do suggest keeping your external (USB-C) monitor as the main monitor (so you can do this operation after reboots)

If anyone could find the root cause of the issue (or even a fix for it), I'll be much glad.
I tried several video + framebuffers + connectors configurations but they didn't work.
Also, as the monitor via USB-C has different behavior with -wegnoegpu or SSDT eGPU disable patches, this might even need some ACPI patches (which IMO is a bit harder to solve)

@zacmks zacmks added the help wanted Extra attention is needed label Dec 6, 2021
@brightplastik
Copy link

Unfortunately this workaround does not work for me, at least with my current devices/settings/kexts. The builtin screen is turned on, as I can see the backlight, but signal does not come after clicking two times on "mirror displays". Close-opening the lid does work.
My external display is an old VGA, plugged in through a Dell TB16 TB3 dock.
VGA is an old and rudimental protocol, that's why, maybe.
I cannot test right now, but maybe a different external signal (being either HDMI or DVI or else) could surely wake up the builtin screen, with your method.

My two cents, purely for debugging purpose.

@zacmks
Copy link
Owner

zacmks commented Dec 8, 2021

Unfortunately this workaround does not work for me, at least with my current devices/settings/kexts. The builtin screen is turned on, as I can see the backlight, but signal does not come after clicking two times on "mirror displays". Close-opening the lid does work. My external display is an old VGA, plugged in through a Dell TB16 TB3 dock. VGA is an old and rudimental protocol, that's why, maybe. I cannot test right now, but maybe a different external signal (being either HDMI or DVI or else) could surely wake up the builtin screen, with your method.

My two cents, purely for debugging purpose.

Yes that could be the case. VGA uses analog signals which in my point of view should be harder to send/receive 'commands', considering the nature of analog signals (compared to the DVI/HDMI digital interfaces). I have a simple USB-C to HDMI adapter. If I get my hands on an VGA monitor + adapter I'll test here as well.

Imo this is the worst 'maybe solvable' issue of this hackintosh setup (not considering unsupported dGPU here), personally the machine that I use performs better compared to actual Mac machines hahaha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants