#xrandr — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xrandr, aggregated by home.social.
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
Es más fuerte que yo, si un comando medianamente largo lo tengo que ejecutar más de dos veces, sale alias xD
Y lo peor, he creado un script que lo ejecuta sólo cuando inicio sesión en #lxqt, y ya no necesito ejecutar el comando 😅
Más sobre alias en la terminal de comandos? 👇
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
RE: https://mstdn.io/@d1cor/115906601058645890
Va perfecto esto en #X11, el único tema es que, cuando suspendo el sistema, al despertarlo, tengo que ejecutar el comando xrandr de nuevo porque pierde el escalado de pantalla...
He probado varias cositas pero nada parece funcionar... habrá que actualizar y seguir buscando info 🙂
La otra, pasar mi #lxqt a #wayland, y cruzar los dedos con el driver de la #nvidia, mientras no se me joda el #minecraft, todo bien 😅
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
Wrote a blogpost about simple (I mean with a shell and a text editor) #X11 configuration.
Covered topics:
1) #Trackball configuration for left hand. Also remapping of some buttons to have scrolling and middle button (not exists out of the box).
2) Theming: #GTK2 #GTK3 #QT , installing cursor(s), fonts and icons.
3) #Xrandr for multimonitor configuration
4) #Xserver settings for #HighDPI
5) #XDG utils and #Emacs as a system file manager
6) #XDM login windowhttps://eugene-andrienko.com/en/it/2025/07/24/x11-configuration-simple.html
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
OTT: Extreme Multihead For Gaming (on Linux PC):
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/All these hoops are basically obsolete with #gamescope nowadays, because this micro compositor allows to configure any virtual display size that games get to see - and handles upscaling on top.
#gamingonlinux #linux #linuxgaming #xrandr #x11 #xorg #xserver #multihead #widescreen #ultrawide #widescreen
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
This is how the Apple Cinema Display 23 responded when I tried to overclock its refresh rate. I knew it wouldn't work, but I still wanted to try using:
cvt 1920 1200 61.
I also tried 75 Hz, but the display turned off.
-
Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.
Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.
I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.
Updated graphics docs with new res section.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
#linuxTip: create alias ghist (stands for grep history). It allows you to check how you called your command (I'm mostly checking how I ran #xrandr
`alias ghist="history | grep $1"`
```
9763 history | grep xrandr
9765 xrandr --query
9786 xrandr --listmonitors
9787 xrandr --eDP1 --mode 1920x1080 --output DP1 --mode 2200x1650 --left-of eDP1
9905 xrandr-tv
9951 xrandr --auto
```You can call commands by writing `!<num-before-command>` in your terminal if you just want to repeat it.
-
So, the question is, in #icewm can I port each workspace to work independently to run each package I need to see? I've extensively read all the man pages for #icewm (I do use arch btw! 😅) but only find the typical #xrandr response. Without going thru the painstaking experimental road of which I've not enough time in this instance. For any #icewm experts out there, is it possible? Or should I just return to #i3? I love them both but found #icewm to be a tad more suitable for me.
2/2 -
my next mission id to move the giant ws for a smaller sff variant replacement - tomorrow - new box has 64gb ram - originally was going to be ids and probably still will be - making it the daily driver will help sort out and get up to speed a big quicker? machine should be a bit faster and more ram is great - also have 3 monitor option - one is just cheesy dumpster find but was still in box - it will do, more screen real estate is helpful usually, fairly confident linux will find and auto setup monitors rather than what it was like in the old days #xrandr
-
my next mission id to move the giant ws for a smaller sff variant replacement - tomorrow - new box has 64gb ram - originally was going to be ids and probably still will be - making it the daily driver will help sort out and get up to speed a big quicker? machine should be a bit faster and more ram is great - also have 3 monitor option - one is just cheesy dumpster find but was still in box - it will do, more screen real estate is helpful usually, fairly confident linux will find and auto setup monitors rather than what it was like in the old days #xrandr
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
Finally managed. Cannot really tell what helped. I added the command to ~.config/i3/config as an exec without startup id at the very beginning.
It works there but if I type it in after the system started, I receive the same error and the screen goes dark again.
-
@fell I've never tried this myself but I believe that you could point the desktop shortcut to an app-startup script created by you, where you change the refresh with #xrandr, then launch the app and when closed, change back to native.
Something on the line as:
xrandr --rate 24
start app
xrandr --rate 60Hope this helps: https://wiki.ubuntu.com/X/Config/Resolution
-
One day I'll find a window manager that supports creating virtual monitors via #xrandr on the fly for _easy_ fullscreen usage over multiple monitors:
> xrandr --setmonitor UWU auto DisplayPort-0,HDMI-A-0,DisplayPort-2
This is a good moment to mention how awesome #gamescope is.
i.a.: I know it's not a #MST display but the same principle applies, no?
-
"Verbessere deine Benutzerfreundlichkeit in Linux mit dem Befehl 'xrandr'. Du kannst Auflösungen anpassen, Bildschirme klonen oder erweitern und vieles mehr. Ein mächtiger Open-Source-Befehl, der deine Display-Konfiguration zum Kinderspiel macht! 💻🐧 #Linux #OpenSource #xrandr"
-
"Verbessere deine Benutzerfreundlichkeit in Linux mit dem Befehl 'xrandr'. Du kannst Auflösungen anpassen, Bildschirme klonen oder erweitern und vieles mehr. Ein mächtiger Open-Source-Befehl, der deine Display-Konfiguration zum Kinderspiel macht! 💻🐧 #Linux #OpenSource #xrandr"
-
Some nice datasets and issues for #inxi - Got a rooted #Android dataset, and realized I can detect the #SurfaceFlinger compositor and thus show some data for Display: Also, the recent #Vulkan API upgrade works on android in #termux if you install the vulkan-tools package. Also fixed some partition stuff.
Even better, and also now running in #pinxi is finally finding a way to lock down #DRM vs #Xorg port ID string mapping without using hacks. Works on all DRM driver + #xrandr situations.
-
How To Find Linux Desktop Screen Resolution From Command Line #Linux #Screenresolution #Commandline #xrandr #xdpyinfo #desktopresolution #Displaysettings #Monitorresolution #Terminal #Linuxhowto #Linuxtips
https://ostechnix.com/find-linux-desktop-screen-resolution-from-command-line/ -
How To Find Linux Desktop Screen Resolution From Command Line #Linux #Screenresolution #Commandline #xrandr #xdpyinfo #desktopresolution #Displaysettings #Monitorresolution #Terminal #Linuxhowto #Linuxtips
https://ostechnix.com/find-linux-desktop-screen-resolution-from-command-line/ -
Ugh, I soooo wish, this #KDE #sddm would NOT show itself in 3840x1080 on the external display but use it's best (5120x1440) instead. It's just so wrong.
I *guess* it comes because for some reason (no idea why), this display lists 3840x1080 before 3840x2160 before finally 5120x1440 - which is broken in itself. Still, #xrandr calls in a Xsetup file don't work and I can't find how else I could convince this thing to do it right. 😒 -
Ugh, I soooo wish, this #KDE #sddm would NOT show itself in 3840x1080 on the external display but use it's best (5120x1440) instead. It's just so wrong.
I *guess* it comes because for some reason (no idea why), this display lists 3840x1080 before 3840x2160 before finally 5120x1440 - which is broken in itself. Still, #xrandr calls in a Xsetup file don't work and I can't find how else I could convince this thing to do it right. 😒 -
My first over-simplified wrapper over #xrandr (but it works for quick connect/disconnect): https://github.com/myTerminal/dotfiles/blob/master/.bin/linux/mt-xrandr #commonlisp #lisp
-
My first over-simplified wrapper over #xrandr (but it works for quick connect/disconnect): https://github.com/myTerminal/dotfiles/blob/master/.bin/linux/mt-xrandr #commonlisp #lisp
-
Hey there! I made a writeup about turning a #RaspberryPi into an additional HDMI port for my #linux laptop over ethernet. It uses #ffmpeg, #tcpdump, #xrandr and #udhcpd.
I learnt a lot about all these topics while working on it, and I did my best to help fellow tinkerers reproduce the project.
I really hope to find the time and inspiration to write many more articles in the future.
https://pierre-couy.dev/tinkering/2023/03/turning-rpi-into-external-monitor-driver.html
-
#TIL `autorandr` saves the color information in a profile for multi-monitor setup [0]. Don't save the autorandr profile while gammastep or redshift is running.
[0]: https://github.com/phillipberndt/autorandr/blob/master/autorandr.py#L71
-
So it turns out that xrandr --verbose actually provides the Serial Numbers of the monitors.
With that, I can finally do an automatic screen placement for my different work spaces.
#Linux #qtile #xrandr[setting up you rmonitor layout once]
> setmons.py --save "officeXY"
*beep boop* Okilidokili[..next time]
> setmons.py
*beep boop beep* officeXY detected, switching to preferred layout *brrrrrrrr BING!* -
So it turns out that xrandr --verbose actually provides the Serial Numbers of the monitors.
With that, I can finally do an automatic screen placement for my different work spaces.
#Linux #qtile #xrandr[setting up you rmonitor layout once]
> setmons.py --save "officeXY"
*beep boop* Okilidokili[..next time]
> setmons.py
*beep boop beep* officeXY detected, switching to preferred layout *brrrrrrrr BING!* -
Extreme Multihead For Gaming (on Linux PC)I love gaming over multiple monitors. It’s my current choice for work and games – especially simulations. Having several monitors attached to one computer (or graphic card) is not a big deal in 2021 any more. The framebuffer in recent graphic cards is insanely huge compared to some years ago, when one really had to think twice about the possible resolution when e.g. connecting a beamer to a laptop (good old SiS 630 anyone?).
xfce4-display-settings for my refurbished “new” set of displaysThis couldn’t be easier nowadays. Even mixing the integrated graphic card of a recent Intel CPU with an NVIDIA or AMD dedicated graphic card does usually “just work”. Some driver specific mode may have to be set but that’s it. The workspace easily expands over multiple displays and windows can be moved around freely.
Games do not see one huge desktop but individual displays
There is however a catch. Games tend to read the primary display only and the maximum resolution offered usually comes with the readout of this very first display – or worse – the first display connected. This sucks especially when the monitors have different resolutions, as it was the case for me for several years now, because I didn’t just purchase a set but collected discarded monitors over the time. This can often be omitted by temporary disabling the “false” ones or by force window mode.
This results in hacky scripts involving
xrandr,wmctrlandxdotool. This is for example how I hammered X4: Foundations into shape _after_ it started, because it would allow me to select a single display only. Set to window mode it can be freely scaled but that comes with a disturbing window decorations so with this the X4 window gets positioned to 0x0, expanded to 5770×1210 and the window decorations purged:
X4: Foundations on Extreme Multiheadxdotool search --class "X4" windowmove --sync %@ 0 0 windowsize %@ 5770 1210 set_window --overrideredirect 1 %@That’s a pain to find out and the fun really stops when it comes to Proton or some games that would not allow resizing over their maximum detected resolution – like for example Everspace.
How about a virtual monitor?
So the idea was to introduce a completely virtual monitor to the systems with the resolution of choice. VNC servers do that all the time so it must be possible. The usual approach won’t work in this case though: When loading the dummy driver the real displays can usually no longer be used and the drivers for AMD and NVIDIA do not really offer such a feature at all.
It is perfectly possible to define virtual monitors with a recent
xrandbut they have to be mapped on an existing output (a real port). One can use an unused port (as in: no monitor connected) for this, add a Modeline and even force it as “online” like so:echo on > /sys/kernel/debug/dri/0/HDMI-A-1/forceI was delighted to see the display showing up briefly but the AMD driver made short work of my soaring hopes by forcing it off again in an instant. So close and yet so far. This would require some hardware hacking by creating a dummy plug for the port. That’s basically some resistors in the right place making the computer think a display is connected. I hear they can also be purchased and this may be a way for others.
Others seem to have had success by compiling the experimental DisplayLink driver that seems to offer (virtual) monitors but I really didn’t feel like fiddling with something even more alien that will probably break on the next kernel update again.
Intel to my aid!
The success for me was in the end to use of the Intel driver and it’s VirtualHeads feature. The caveat is that one probably needs an Intel CPU for this to work and has to create a X11 config file. If this is done without adding the usual driver people will experience black screens on reboot only. This may be a show stopper for inexperienced Linux users who don’t know how to recover from a broken X11 config (yet :D). For me this is an amdgpu so my file
/etc/X11/xorg.conf.d/20-intel-virtual-and-amd.confhas to look like this:Section "Device" Identifier "amdgpu0" Driver "amdgpu" Endsection Section "Device" Identifier "IntelVirtual0" Driver "intel" Option "VirtualHeads" "1" EndSectionTriple check that your driver is used in there instead or you will end up with a broken config without the possibility to log in to a graphical window manager. When in doubt start e.g. a new session to your liking on the next display server where you can switch back with the key combination ctrl+alt+F[1-0]:
startx /usr/bin/startxfce4 :2Once started a new provider shows up and the new output “VIRTUAL1” is available:
xrandr --listprovidersProviders: number : 2 Provider 0: id: 0x59 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 1 name:AMD Radeon RX 5600 XT @ pci:0000:03:00.0 Provider 1: id: 0x9e cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 5 outputs: 4 associated providers: 1 name:IntelConfiguring the virtual monitor with xrandr
Now that we have a virtual monitor we need a Modeline for it. This is usually the current screen (of the framebuffer) and can be calculated (e.g. sum of all monitors x height and Hz of one monitor) or by asking the system:
xrandr | grep Screengtf(orcvt) helps obtaining the Modeline:gtf 5760 1200 60# 5760x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 579.47 MHz Modeline "5760x1200_60.00" 579.47 5760 6144 6768 7776 1200 1201 1204 1242 -HSync +VsyncNow all information needed to finally set up the virtual display is there. I’m creating the virtual display on top of the three real displays because I also want to see what’s drawn on it. That’s not strictly required though and in fact most graphical tools to configure the monitor location will even refuse this – because this use case is simply not considered or supported. Gnome for example really didn’t like this. XFCE4 didn’t care. Ymmv:
xrandr --newmode "5760x1200_60.00" 579.47 5760 6144 6768 7776 1200 1201 1204 1242 -HSync +Vsync xrandr --addmode VIRTUAL1 "5760x1200_60.00" xrandr --setmonitor Virtual 5760/1554x1200/324+0+0 VIRTUAL1 xrandr --output VIRTUAL1 --mode "5760x1200_60.00" --pos 0x0 --primaryIt’s done.
The virtual monitor becomes visible in display settings (xfce4-display-settings here)And it works!
After a lot of research and fiddling (and breaking my X config several times) I finally found a working solution. Games let me select the virtual monitor or see at least my primary with my “maximum” resolution. Sometimes this still requires window mode but I could care less – the decorations are optional. And it works like a charm! Here is a small selection of the games I play most at the moment:
This is how my set-up looks:
Now I’ve another problem. With this my usual 1080p gaming resolution is no longer and my graphic card is simply not up for the job any more 🤣
At least gaming itself is easy as pie on Linux in 2021. Complex display set-ups? Not so much.
This content is licensed under a Creative Commons Attribution-NonCommercial 4.0 International license.
https://beko.famkos.net/2021/05/31/extreme-multihead-for-gaming-on-linux-pc/ #gamingonlinux #linux #linuxgaming #xrandr