[Bug] Black screen and flickers while using DisplayPort
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reviewing the attached flicker video and the submitted log reports, then trace the DisplayPort display path in the Rust driver and compare it with HDMI behavior. The report identifies an ASUS VG27A at 2560×1440 and a GeForce RTX 5060 Ti; determine what log or reproduction evidence isolates the cause and confirm the black screen and flickering no longer occur over DisplayPort.
Written by the indexing model from the issue text.
Description
Send logs report ID
NM-DGV9W6C3, NM-HG7BABC5, NM-EPVABVEY, NM-3XW0V41M, NM-5M2NDEM0, NM-1VGE98ED, NM-GP3FJAHH, NM-QK05RCPB, NM-RPWFF1EP, NM-486VT688, NM-3WPQ0TNN, NM-HAZQH2E0, NM-ZDTJNK6N, NM-VY2BWX6F, NM-H1AH9DDR, NM-R5P2JFFS
Where does it go wrong?
On the desktop (flicker, lag, displays, sleep)
What happens
Using DisplayPort show black screen and flickers, with HDMI I don't have same problems
Display: ASUS VG27A 2560x1440 165GHz
GPU: RTX 5060 Ti (16GB)
https://github.com/user-attachments/assets/466e5cf0-5c27-4499-b9bd-fd67303ae2d1
App or game (if it is one)
No response
Did you change anything yourself?
Notning
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nullmoth/nvidia-macos-driver
-
[Bug] `nullmoth-wsreset.sh` never restarts WindowServer at the real login window: `/dev/console` is `_windowserver`, not `root` (guard + test blind spot)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nullmoth/nvidia-macos-driver#141 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
nullmoth/nvidia-macos-driver#28 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 10/100
nullmoth/nvidia-macos-driver#212 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 12/100
nullmoth/nvidia-macos-driver#211 ·
Maintainers usually reply within 1 day
-
[Bug] <what happens>Openbug
Difficulty 5/5 Over a week Newbie friendliness 8/100
nullmoth/nvidia-macos-driver#210 ·
Maintainers usually reply within 1 day
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
Custom hosts written as trailing-dot FQDNs (`host.local.`) aren't detected as local backendsPossibly taken @roboomp claimed this today. Openbug prio:p2 providers triaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
can1357/oh-my-pi#15798 · 3 comments ·
Maintainers usually reply within 1 day
-
requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/datafusion-comet#7001 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Add a Storybook section to CONTRIBUTING.mdPossibly taken @ChanakyaG2004 claimed this today. Opendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#995 · 2 comments ·
Maintainers usually reply within 1 day