RTX 4060 Laptop: USB-C/DP hot-plug blacks out both displays; unplugging does not restore the internal panel
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, rust
- Domain
- desktop-dev
Research direction
Start by reading related issues #66, #67, and #38, then identify the driver's display hot-plug and modesetting entry points. The report does not name source files or provide fresh failure logs, so first gather minimal logs and display-state data that distinguish driver behavior from saved WindowServer settings. Done means both displays recover after connecting and disconnecting the USB-C/DP monitor, with a safe way to restore a known display configuration.
Written by the indexing model from the issue text.
Description
Summary
On an ASUS ROG Strix G16 with an RTX 4060 Laptop GPU, the internal display currently works when macOS is started with the external monitor disconnected. Connecting the external monitor after login makes both displays go black / show no signal. Disconnecting it does not restore the internal display; restarting with the external monitor disconnected is required.
This is a user-observed report. The installed driver release and fresh failure logs have not yet been verified. I am not claiming reproduction on 1.9.0 or a confirmed driver-only cause: saved display settings may also contribute.
Hardware / OS
- ASUS ROG Strix G16 G614JVR; Intel Core i9-14900HX; 32 GB RAM.
- NVIDIA GeForce RTX 4060 Laptop GPU, 8 GB, PCI 10DE:28E0, subsystem 1043:3488; laptop set to dGPU/Ultimate mode.
- macOS Sequoia 15.8.1 (24H32), OpenCore 1.0.9.
- Internal panel: NE160QDM-NZ8, native 2560x1600, advertised 240 Hz.
- External monitor: SG27Q, 2560x1440, connected through a USB-C / Thunderbolt 4 port using a DP adapter/cable. HDMI has not been tested.
Current reproduction / recovery
- Boot macOS with the external monitor disconnected; the internal desktop is usable.
- Connect the external monitor through USB-C/DP.
- Both displays become black / lose signal.
- Unplug the external monitor; the internal display remains black.
- Restart with the external monitor disconnected; the internal display works again.
Relevant timeline and tests
- The external monitor previously worked, although display-mode changes were unstable.
- Changing refresh rate from 60 Hz to higher modes caused flickering. Returning to 60 Hz did not reliably recover output during that session.
- The sRGB color-profile workaround from #66 allowed the external monitor to run at 120 Hz, but did not resolve the internal-panel problem.
- Enabling HiDPI in BetterDisplay then caused the external display to become unusable too.
- Subsequent scaling experiments used CoreGraphics mode-setting calls, including a permanent configuration attempt. A recorded internal-only baseline remained 2560x1600 at 240 Hz with 1x scaling, despite calls returning CGError=0. This does not establish that all saved display configurations remained unchanged.
- The persistent external-display failure was already present after those scaling experiments. A later SMBIOS test from MacBookPro16,2 to MacBookPro16,1 did not improve UI scaling; that model test has been reverted in the boot configuration. The hot-plug failure predates that model test.
- Basic acceleration had become usable earlier: scrolling improved and LocalSend could render its window. The previous Metal-device startup failure was reported separately in #38 and should not be conflated with this display-mode problem.
Related reports / request
Related: #66 (refresh-rate/color-profile workaround), #67 (DP hot-plug and multiple displays).
Is this combination of dual-display blackout and failure to recover after unplugging a known modesetting/hot-plug issue? Which minimal logs or display-state data would help distinguish a driver failure from persisted WindowServer display settings? A safe way to restore both displays to a known configuration would also be useful.
No EFI identity values, account details, Wi-Fi credentials, or unredacted logs are included.
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 233
- PR merge metrics
- No merged PRs in 30d
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
-
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 75/100
nullmoth/nvidia-macos-driver#126 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nullmoth/nvidia-macos-driver#108 · 6 comments ·
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
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nullmoth/nvidia-macos-driver#170 ·
Maintainers usually reply within 1 day
All issues in nullmoth/nvidia-macos-driver
Similar issues
-
area::tern difficulty::easy good first issue kind::cleanup triage::ready
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-zenoh/zenoh#2842 · 2 comments ·
Maintainers usually reply within 1 day
-
中文字符导致软件崩溃Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Y-ASLant/ElegantClipboard#172 ·
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SaboLabs/soroban-devkit#341 ·
Maintainers usually reply within 1 day
-
agent:sonnet-high enhancement priority: P2 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
shep-pm/shep-kelpie#652 ·
Maintainers usually reply within 1 day