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

Dysfunctional DisplayPort #333

Open
5 tasks done
Sooly890 opened this issue Nov 29, 2024 · 8 comments
Open
5 tasks done

Dysfunctional DisplayPort #333

Sooly890 opened this issue Nov 29, 2024 · 8 comments

Comments

@Sooly890
Copy link

Sooly890 commented Nov 29, 2024

macOS Version

macOS Catalina, macOS Big Sur, macOS Monterey

What is the precise OS version on which the bug is occurring?

10.15.7 Release (19H15), 11.7.10 according to recovery (Build number: HDMI output is garbled), 12.7.4 Release (21H1123)

What is your CPU's model?

AMD Ryzen 5600G

Describe the unexpected behaviour in detail.

I installed the latest MacOS Catalina, Big Sur and Monterey, plugged in my monitor through DisplayPort, and my computer turned on, but it didn't display anything, and my monitor showed No Signal. I shutdown, plugged into HDMI, and it showed the login screen. I have tried adding -NRedDPDelay to boot-args.

EDIT: I must note, it did work on Sonoma 14.4.1, on an older version maybe?

What should've happened instead?

I install the latest MacOS Catalina or Big Sur or Monterey, plug in my monitor through DisplayPort, my computer turns on, and it displays the login screen.

Attach any logs related to this issue. For example .gpuRestart, .panic, etc files.

EDIT: I managed to find a .spin file that comes every time I boot with DisplayPort on Catalina (I wasn't sure if it was from my many times attempting to install), but I'm not sure how relevant it is so it's an edit, not a comment.
WindowServer_2024-11-29-140547_Soolys-iMac-Pro.userspace_watchdog_timeout.spin.txt

Issue Submission Terms

  • You have made sure that there are no other reports about this bug.
  • You do not use configurator software (e.g. OpenCore Auxiliary Tools, OpenCore Configurator).
  • You have made your own EFI according to the ChefKiss Hackintosh Guide.
  • You are not using any software that may conflict, including, but not limited to, OpenCore Legacy Patcher, BFixup, WhateverGreen.
  • You acknowledge that violation of these terms may result in your issue being closed or your user being blocked from the organisation.
@Sooly890
Copy link
Author

Sooly890 commented Nov 29, 2024

I've just tested Big Sur, it also happens there.
EDIT: now I can't see the screen beyond the login screnn because I set the HZ to 170, trying to set the Resolution in hopes of seeing some details.

@Sooly890 Sooly890 changed the title DisplayPort doesn't work on Catalina DisplayPort doesn't work on Catalina and Big Sur Nov 29, 2024
@EraserCN
Copy link

On Monterey here with 3500U, DP doesn't work either.

@Sooly890
Copy link
Author

Sooly890 commented Nov 29, 2024

@EraserCN I'm just installing Monterey now, seeing if it persists. I'll get back to this issue.

@Sooly890
Copy link
Author

Yup, indeed, Monterey doesn't work on DisplayPort but is working fine on HDMI.

@Sooly890 Sooly890 changed the title DisplayPort doesn't work on Catalina and Big Sur DisplayPort doesn't work on Catalina, Big Sur and Monterey Nov 29, 2024
@Sooly890
Copy link
Author

I just tested Ventura - that works fine.

@VisualEhrmanntraut VisualEhrmanntraut changed the title DisplayPort doesn't work on Catalina, Big Sur and Monterey Dysfunctional DisplayPort Nov 29, 2024
@Sooly890
Copy link
Author

If it helps - Sonoma and Sequoia are working fine too.

@VisualEhrmanntraut
Copy link
Member

It doesn’t, I don’t have an AMD desktop with integrated graphics, only an AMD laptop with one HDMI port. My main machine is an M3 MacBook Pro.

@VisualEhrmanntraut
Copy link
Member

VisualEhrmanntraut commented Nov 30, 2024

So, I’m going to spend some time improving DiskDbg and creating instructions on how to gather the required debugging information so I don’t repeat myself all the time. Although, I must admit that the issue here isn’t really a bug with NootedRed, rather the AMD drivers, but maybe the fix can be back-ported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants