DISPLAY MANAGER
Match the headless cloud display to your client
Noland manages the virtual display presented by the Linux host so Sunshine can stream a resolution appropriate for the client instead of depending on a physical monitor.
QUICK ANSWER
What you need to know
The Display Manager compares the host's current EDID profile with Noland's client-aware multi-resolution profile. It can install a new profile and restart Xorg and Sunshine when required, or use a faster resolution switch when the correct profile is already active.
DETECT
Read the host's real display state before changing it
The client asks the remote machine for its current mode, available resolutions, refresh information, EDID fingerprint, and Sunshine health. The UI uses that capability result to distinguish a compatible Noland display profile from a stale or different virtual display configuration.
This avoids treating every resolution selection as the same operation. A machine with the expected multi-resolution EDID can usually switch modes without rebuilding the display stack, while a mismatched profile needs a controlled update.
- Current and supported remote modes
- Client-native display profile comparison
- Explicit Sunshine and Xorg health verification
- Clear distinction between profile replacement and mode switching
APPLY
Use the least disruptive path that can produce the requested mode
When the remote host already advertises the current Noland multi-resolution EDID, applying another listed mode uses the fast switch path. If the profile differs, Noland installs the current client-native profile and briefly restarts Xorg and Sunshine so the virtual display and streaming host agree on the new capabilities.
The operation verifies the resulting display and Sunshine state rather than assuming that a command returning successfully means the stream is ready. The selected display configuration is persisted so the managed session can be reconstructed after service or display-manager changes.
- Fast resolution switching for an existing compatible profile
- Controlled Xorg and Sunshine restart when EDID changes
- Post-change verification before reporting success
- Persistent display selection for managed session recovery
LIMITS
Resolution support still depends on the complete video path
Advertising a mode does not guarantee that every GPU, encoder, decoder, client display, network route, or game will sustain it. Stream resolution, frame rate, bitrate, codec support, local decoding, and the physical client display all contribute to the final experience.
Noland manages a headless Xorg display for the provisioned Linux environment. It does not reconfigure the physical monitor attached to your client computer, and applying an EDID replacement can briefly interrupt an active remote desktop session.
FAQ
Questions about display manager
01Why does a headless cloud machine need an EDID?
The virtual display stack needs monitor capabilities to expose usable resolutions and refresh modes. Noland supplies a managed profile because the cloud host normally has no physical monitor connected.
02Does every resolution change restart Xorg?
No. When the expected multi-resolution EDID is already active, Noland can use a faster mode switch. A different or stale profile requires installation and a controlled Xorg and Sunshine restart.
03Will changing the EDID interrupt the stream?
It can briefly interrupt the remote desktop because Xorg and Sunshine may need to restart. The UI identifies this path before applying the change and verifies service health afterward.
04Does selecting a high resolution guarantee smooth streaming?
No. Smooth playback also depends on host rendering and encoding, network bandwidth and loss, client decoding, stream settings, and the client display.
