The “xrandr: 1920×1200 not found” error in Linux typically occurs when your desired screen resolution isn’t detected by the system, often due to driver issues or hardware limitations. Research suggests this can usually be resolved by manually adding the custom resolution using tools like xrandr, cvt, or gtf, though success depends on your monitor’s capabilities. It seems likely that following a step-by-step process will work for most users, but if you’re using Wayland instead of X11, alternative methods may be needed as xrandr is X11-specific. The evidence leans toward this being a common issue with straightforward fixes, acknowledging that some cases involving proprietary drivers like NVIDIA might require extra troubleshooting.
Key Points
- Verify compatibility: Ensure your monitor supports 1920×1200@60Hz before proceeding.
- Use X11 session: This guide applies to Xorg/X11; switch from Wayland if necessary.
- Temporary vs. permanent: Changes via xrandr are session-based; add to startup for persistence.
- Potential pitfalls: Errors like “BadMatch” often stem from incorrect output names or invalid modelines—double-check with
xrandroutput.
Understanding the Error
The error means the 1920×1200 resolution isn’t listed in xrandr’s available modes, possibly due to faulty EDID data from your monitor or driver limitations. This is common in Linux setups without automatic detection.
Prerequisites
- Open a terminal (Ctrl+Alt+T).
- Ensure xrandr is installed (it’s usually pre-installed on most distros like Ubuntu, Arch, or Mint).
- Identify your display output: Run
xrandrand note the connected output (e.g., HDMI-1, VGA-1).
Step-by-Step Solution
- Generate a Modeline: Use
cvtfor a modeline string.
cvt 1920 1200 60
Example output: "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync.
- Add the New Mode:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
- Attach to Output: Replace
<output>(e.g., HDMI-1) with your display.
xrandr --addmode <output> "1920x1200_60.00"
- Apply the Resolution:
xrandr --output <output> --mode "1920x1200_60.00"
Making It Permanent
Add the commands to ~/.xprofile:
#!/bin/sh
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode <output> "1920x1200_60.00"
xrandr --output <output> --mode "1920x1200_60.00"
Make executable: chmod +x ~/.xprofile.
Troubleshooting
If you encounter “BadMatch,” verify the output name with xrandr. For NVIDIA, check Xorg logs for EDID issues.
If you’re encountering the “xrandr: 1920×1200 not found” error in Linux, you’re not alone—this is a frequent issue when your monitor’s preferred resolution isn’t automatically detected by the system. Whether you’re using Ubuntu, Arch Linux, Fedora, or another distro, this comprehensive guide will walk you through fixing it step by step. We’ll cover everything from understanding the problem to advanced troubleshooting, ensuring even beginners can follow along. By the end, you’ll have a working custom resolution and tips to make it stick across reboots.
This guide focuses on X11 (Xorg) environments, as xrandr doesn’t work natively on Wayland. If you’re on Wayland (common in newer GNOME setups), consider switching to an X11 session via your login screen or exploring alternatives like gnome-randr or KDE’s display settings.
What Is xrandr and Why Does This Error Happen?
xrandr is a command-line tool in Linux for managing display settings, including resolutions, orientations, and multiple monitors. It stands for “X Resize, Rotate and Reflect Extension” and is part of the X Window System.
The “1920×1200 not found” error occurs when xrandr can’t find the specified resolution in its list of available modes. Common causes include:
- Buggy hardware or drivers: Your monitor’s EDID (Extended Display Identification Data) might be incorrect or not fully read by the driver.
- Missing modes: Resolutions aren’t always auto-detected, especially on older hardware or with open-source drivers like Intel, AMD, or Nouveau.
- Driver-specific issues: Proprietary NVIDIA drivers may limit modes, or AMD/Intel might need tweaks.
- System limitations: Virtual machines (e.g., VirtualBox, VMware) often restrict resolutions until guest additions are installed.
Don’t worry—this is fixable by manually adding the mode. Just ensure your monitor supports 1920×1200 (check its manual or specs) to avoid display issues.
Prerequisites Before Starting
Before diving in, gather these:
- A terminal: Open one with Ctrl+Alt+T.
- xrandr installed: It’s standard on most distros, but install if missing (e.g.,
sudo apt install x11-xserver-utilson Ubuntu). - Display output name: Run
xrandrto see connected displays (e.g., “HDMI-1 connected”). Note this for later. - Backup your config: If editing files like xorg.conf, back them up first.
- Root access: Some steps may need
sudo, but xrandr usually runs without it. - Optional tools:
cvtorgtffor modelines (install viasudo apt install x11-utilsif needed).
If you’re on a laptop or multi-monitor setup, test on a single display first to isolate issues.
Step-by-Step Guide to Fixing the Error
Follow these steps carefully. We’ll use 1920×1200@60Hz as the example, but you can adapt for other resolutions.
- Identify Your Display Output
Run:
xrandr
Look for lines like “HDMI-1 connected primary 1920×1080+0+0”. The name (e.g., HDMI-1) is your <output>. If unsure, use:
xrandr | grep " connected" | cut -f1 -d ' '
This lists connected outputs.
- Generate a Modeline for 1920×1200
Usecvt(preferred for accurate refresh rates) orgtf:
cvt 1920 1200 60
Sample output:
# 1920x1200 59.88 Hz (CVT 2.30MA) hsync: 74.56 kHz; pclk: 193.25 MHz
Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
Copy the line starting from "1920x1200_60.00" onward. If cvt isn’t available, try gtf 1920 1200 60. Tip: For reduced blanking (better for some monitors), use cvt -r 1920 1200 60.
- Create the New Mode
Add the mode to xrandr:
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
This registers the resolution system-wide.
- Add the Mode to Your Output
Attach it to your display:
xrandr --addmode <output> "1920x1200_60.00"
Example: xrandr --addmode HDMI-1 "1920x1200_60.00". Now, the resolution should appear in your display settings.
- Apply the Resolution
Set it immediately:
xrandr --output <output> --mode "1920x1200_60.00"
Or use your distro’s display settings GUI to select it. If the screen goes black, wait 15 seconds—it should revert. Otherwise, reboot to safe mode.
- Test and Verify
Runxrandragain to confirm the mode is listed. Open a few apps to check for stretching or artifacts.
Making the Custom Resolution Permanent
xrandr changes reset on logout or reboot. Here’s how to persist them:
- Using ~/.xprofile (Easiest for Most Users):
Create or edit~/.xprofile:
nano ~/.xprofile
Add:
#!/bin/sh
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode <output> "1920x1200_60.00"
xrandr --output <output> --mode "1920x1200_60.00"
Save, then make executable: chmod +x ~/.xprofile. This runs on login.
- Using xorg.conf (For Advanced Users):
Create/etc/X11/xorg.conf.d/10-monitor.conf:
sudo nano /etc/X11/xorg.conf.d/10-monitor.conf
Add:
Section "Monitor"
Identifier "<output>"
Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
Option "PreferredMode" "1920x1200_60.00"
EndSection
Restart X (logout/login or reboot). This is more reliable for display managers like SDDM or GDM.
- Automation Script for Multi-Monitor or Dynamic Setups:
For hot-plugging monitors, use tools likeautorandr. Install:sudo apt install autorandr. Save a profile:autorandr --save default. It auto-applies on detection. - Display Manager-Specific: For GDM/SDDM, add scripts to
/etc/gdm/Init/Defaultor/usr/share/sddm/scripts/Xsetup.
Troubleshooting Common Errors
Here’s a table of frequent issues and fixes:
| Error/Message | Possible Cause | Solution |
|---|---|---|
| “BadMatch (invalid parameter attributes)” | Wrong output name or invalid modeline. | Verify output with xrandr. Recalculate modeline with cvt. For NVIDIA, check EDID in Xorg logs (startx -- -logverbose 6). |
| “cannot find output ”” | Misspelled or disconnected output. | Use xrandr --listmonitors to confirm name. |
| “BadName (named color or font does not exist)” | Syntax error in modeline. | Copy modeline exactly from cvt output. |
| Resolution reverts after reboot | Not made permanent. | Add to ~/.xprofile or xorg.conf as above. |
| Black screen after applying | Unsupported by hardware. | Wait for revert (15s) or boot to recovery mode and remove changes. Try lower refresh rate (e.g., 50Hz). |
| No effect in VM | Guest additions missing. | Install VMware Tools or VirtualBox Guest Additions. |
| Stretched display | Aspect ratio mismatch. | Use --scale 1x1 with xrandr or adjust in GUI. |
If on NVIDIA, enable “IgnoreEDIDChecksum” in xorg.conf. For Intel/AMD, update drivers: sudo apt update && sudo apt upgrade. If all fails, edit kernel parameters in GRUB: Add video=<output>:1920x1200@60 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then sudo update-grub.
Additional Tips and Variations
- For Other Resolutions: Swap 1920 1200 in
cvtfor your needs (e.g., 2560×1440). - Multi-Monitor Setup: Use
--right-ofor--left-of:xrandr --output HDMI-2 --mode 1920x1200 --right-of HDMI-1. - GUI Alternatives: Install ARandR (
sudo apt install arandr) for a graphical interface to xrandr—save configs easily. - Refresh Rate Tweaks: If 60Hz doesn’t work, try 59.9Hz via
cvt 1920 1200 59.9. - Performance Note: Custom modes might slightly impact performance on older hardware—test with games or videos.
- Driver-Specific Advice:
- Intel: Add modes via xorg.conf “Device” section with driver “intel”.
- AMD: Use reduced blanking (
cvt -r) for better compatibility. - NVIDIA: Generate xorg.conf with
nvidia-xconfigand add frequency ranges.
Conclusion
By following this guide, you should resolve the “xrandr: 1920×1200 not found” error and enjoy your preferred resolution. If issues persist, check forums like Ask Ubuntu or Arch Wiki for your specific hardware. Remember, always verify monitor specs to avoid damage. If this helped, share your experience in the comments!
