xrandr --query for X11 or wlr-randr/swaymsg for Wayland compositors. These tools query the display server directly to reveal active outputs, including those managed by DisplayLink drivers or native USB-C alt-mode controllers.
Understanding the Display Server Environment
Before running any diagnostic commands, you must determine which display server your session is using. The method for identifying connected monitors differs significantly between X11 and Wayland. Most traditional desktop environments like GNOME (on older versions) or KDE Plasma often default to X11, while newer installations of Fedora, Ubuntu, or Arch Linux may use Wayland by default. You can check this by looking at the environment variable$XDG_SESSION_TYPE. If it returns x11, you will use X11-specific tools. If it returns wayland, you need Wayland-compatible queries. This distinction is critical because a command that works perfectly on X11 will fail silently or return errors on Wayland, leading to confusion when trying to manage multiple displays.
Listing Monitors on X11 Systems
For systems running the X Window System, the standard utility isxrandr. This tool provides a comprehensive view of all detected outputs, their current resolution, refresh rate, and connection status. To get a clean list of only the connected monitors, you can pipe the output through grep to filter for the word "connected". Run the following command in your terminal:
xrandr --query | grep " connected"
This command will output lines similar to HDMI-1 connected primary 1920x1080+0+0 or DP-2 connected. For USB-C connections, look for outputs named USB-C-1, DP-1 (if using DisplayPort Alt Mode), or sometimes HDMI-A-1 depending on the adapter hardware. If you are using a DisplayLink dock, the driver might create virtual outputs such as DisplayLink or specific model names. Note that xrandr does not always distinguish between the physical port type (USB-C vs HDMI) in its name; it lists the logical output interface recognized by the X server. Therefore, you must correlate the output name with your physical setup. If a monitor is physically connected but not listed, the driver may not have loaded correctly, or the kernel module for the specific USB controller might be missing.
Listing Monitors on Wayland Systems
Wayland handles display configuration differently because it does not allow client applications to query the global state of other windows or outputs in the same way X11 does. Instead, you query the compositor itself. If you are using Sway, the command is:swaymsg -t get_outputs
This returns a JSON structure detailing each output, its name, make, model, serial number, and current mode. Look for the name field, which typically follows naming conventions like usb-c-1 or dp-1. If you are using GNOME under Wayland, there is no single standard CLI tool exposed to users for querying outputs directly in the same verbose manner as xrandr. However, you can use gnome-shell --replace in debug mode or rely on third-party tools like hyprctl if using Hyprland. A more universal approach for Wayland is using wlroots-based tools if available. In many cases, simply checking the system settings GUI is the most reliable method on pure Wayland sessions, as the CLI exposure is limited by design for security and stability reasons.
Handling DisplayLink and Docking Stations
A significant portion of USB-C monitor issues stem from DisplayLink technology. Unlike native USB-C Alt Mode, which passes video signals directly over the USB-C cable, DisplayLink uses compression and requires a proprietary driver stack. If you are using a docking station, ensure that theevdi kernel module and the displaylink-driver package are installed. You can check if the driver is active by running:
lsmod | grep evdi
If this returns nothing, the driver is not loaded, and your monitors will not appear in xrandr or Wayland queries regardless of the command used. Additionally, some docks require firmware updates to function correctly with modern kernels. If the monitor appears in xrandr but shows as disconnected or black, try reseating the USB-C cable or switching to a different USB port on the host machine. USB bandwidth limitations can also cause flickering or failure to initialize high-resolution displays, especially if multiple peripherals are connected to the same hub.
Troubleshooting Common Issues
If your command returns no connected outputs despite having a working monitor, consider the following steps. First, verify that the kernel recognizes the USB device usinglsusb. Look for entries related to DisplayLink or the monitor manufacturer. Second, check the system journal for errors related to DRM (Direct Rendering Manager) or GPU drivers using dmesg | grep -i drm. Third, ensure that your graphics drivers (NVIDIA, AMD, or Intel) are properly installed and that they support the output port in question. NVIDIA cards, in particular, have historically had complex configurations with DisplayLink and USB-C outputs, often requiring specific nvidia-xconfig setups or PRIME offloading modes. Finally, remember that some USB-C ports on laptops are data-only and do not support video output. Check your laptop's specifications to confirm whether the specific USB-C port supports DisplayPort Alt Mode or Thunderbolt 3/4 protocols.
Frequently Asked Questions
Why does xrandr show my monitor as disconnected?
This usually indicates that the display server cannot establish a handshake with the monitor or that the necessary kernel modules are not loaded. Ensure that the correct graphics drivers are installed and that the USB-C cable supports video transmission, as not all cables carry display signals.
Can I use xrandr on a Wayland session?
No, xrandr is an X11-specific tool and will not work on Wayland sessions. You must use compositor-specific commands like swaymsg for Sway or rely on GUI tools provided by your desktop environment like GNOME Settings or KDE System Settings.
How do I identify if my USB-C port supports video?
Check your laptop's technical specifications for keywords like "DisplayPort Alt Mode," "Thunderbolt," or "Video Out." Physically, look for a lightning bolt icon next to the USB-C port, which typically indicates Thunderbolt support capable of driving external displays.
What should I do if DisplayLink monitors are not detected?
Ensure the evdi kernel module is loaded and the DisplayLink manager service is running. You may need to install the proprietary DisplayLink driver from the manufacturer's website, as open-source drivers often lack full feature support for these devices.
Does the order of connecting monitors matter?
In some cases, yes. Some docking stations enumerate devices based on detection order during boot. If a monitor fails to appear, try disconnecting all displays, powering on the dock, connecting the dock to the PC, and then attaching the monitors one by one to force re-enumeration.