Xrandr 1.2

Since I got my 20" widescreen monitor in the summer, I discovered how bad X's support for resizing displays is. I wanted to have the ability to plug my laptop into the 20" display in the office and expand the desktop to 1680x1050, or remove the 20" display and shrink the desktop back down to the native resolution of 1024x768. It turns out that a number of factors were stopping this, and the only way to do it would have been to restart X. Because of this I ended up using the display at 1024x768 when I did use it, but mostly I stayed on the sofa.

Then I heard about xrandr 1.2, the all-singing all-dancing revision of the X Resize and Rotate extension. Basically, it would solve my problem, and as luck would have it my laptop has an Intel chipset and the people hacking on it work at Intel. Yesterday after lots of poking I finally made it all work for this. This involved a lot of poking and a little black magic.

The first step is getting an X server new enough. First, you'll need to update some X protocol headers. We'll start with the easy ones that have had releases (grab the latest release you can find):

Then you'll need to update various other bits of X:

Once this is done and X still works, it's time to brave the perilous world of git. If you've never used git before, it's quite simple for this. Go to the git browser and find the module you want to check out. Click on it, and you'll see two URLs: you want the anongit one. Do git clone [url], and then if I've specified a branch other than master, cd into the directory and do git checkout [branch]. For example:

git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel
cd xf86-video-intel
git checkout modesetting

You'll need to grab:

Build it all in that order. The order is important as if you build the Intel driver against randr 1.0 instead of 1.2, it won't do what you want. By now you should have an X that looks no different. But...

$ xrandr
Screen 0: minimum 320 x 240, current 1024 x 768, maximum 1680 x 1050
VGA disconnected 0mm x 0mm
LVDS connected 1024x768+0+0 246mm x 185mm
   1024x768       50.0 +   60.0*    40.0  
   800x600        60.3  
   640x480        60.0     59.9  
TV disconnected 0mm x 0mm

Now that is clever. Here you can see that I don't have anything connected via VGA, my LVDS (no idea what this stands for, but it means the laptop's panel) has a preferred mode of 1024x768 (thats what the * means), and I have nothing connected to the TV output (because Lenovo didn't wire it up). Now if I plug something into the VGA and run xrandr -s 0 (select default screen size), the external display should power on. Xrandr doesn't try to be too clever, it will leave that to desktop daemons, but by default it will try and make something appear on all of the connected displays. In this case, my 20" TFT gets a clone of my laptop panel, at 1024x768.

That is no good though, I want to turn off the laptop panel (as I'll be shutting the laptop) and switch the external display to 1680x1050. This is where the black magic starts... Currently the Intel driver cannot resize the physical framebuffer in memory after X has started, so it defaults to a framebuffer of 1200x1024 (IIRC). That isn't big enough to hold 1680x1050. Also the Intel driver doesn't detect any modes from the TFT. This may be Dell being stupid, or the EDID parser in the driver being too restrictive, I don't know. Luckily we can still use modelines in xorg.conf so I added this:

Section "Monitor"
        Identifier "Dell TFT"
        # This is a standard modeline for 1680x1050 at 60Hz
        Modeline "1680x1050" 149.00  1680 1760 1944 2280  1050 1050 1052 1089
EndSection
        
Section "Screen"
        Identifier      "Screen"
        Device          "Intel"
        Monitor         "Monitor"
        # This says that when using a monitor on the output called VGA, use the
        # settings in the monitor "Dell TFT"
        Option "monitor-VGA" "Dell TFT"
        DefaultDepth    24
        SubSection "Display"
                Depth 24
                # This tells the screen to allocate a frame buffer up to
                # 1680x1050.
                Virtual 1680 1050
        EndSubSection
EndSection

With this, everything just works. If I xrandr with various displays plugged in I can see what they support and can switch modes. To make everything nice and easy I wrote a small script that I bound to an unused function key:

if xrandr -q | grep -q  "VGA connected"; then
  xrandr --output LVDS --off --output VGA --mode 1680x1050
else
  xrandr --output VGA --off --output LVDS --mode 1024x768
fi

(thanks to Eric for pointing out that I don't need to use the hex values). Simple! As you can see the new xrandr is very powerful. If you want to do Xinerama-style dual screen you can do that too: xrandr 1.2 encompasses that behaviour.

The final thing to point out is how glad I am that GNOME seems to handle the screen resizing like this so nicely already. When the desktop shrinks Metacity moves windows so they are visible, and when the desktop expands the panel applets on the right stay on the right instead of sitting in the middle. The script I run when I change screens does more than I pasted here: it changes the wallpaper to match the aspect ratio, and also changes the fonts.

I hope this has made sense, I know there are a few people out there who were waiting for me to test this before they gave it a go. If anything is too vague, leave a comment and I'll expand it. I should also mention that I've got Ubuntu Edgy packages for everything here in my repository.

NP: Animal Magic, Bonobo

17:50 Tuesday, 06 Feb 2007 [#] [computers] (53 comments)

Posted by Mattias at Tue Feb 6 18:22:19 2007:
Real neat. What i eventually hope happens, when this is default in stable distributions, is that someone (me even?) codes a desktop applet or daemon with notification area-icon that lets you chose between some common behavior related to plugging in a new monitor. Like for example autoswitch to that display or to set what resolution to use on that external display etc.
Posted by resiak at Tue Feb 6 18:32:18 2007:
You omitted the '>' from the opening tag of the link to your repository.

Otherwise, thanks for the excellent guide.  I will be stealing your packages!
Posted by Andrew Barr at Tue Feb 6 18:43:32 2007:
Great! I've been following the development of the modesetting driver and the randr-1.2 code for a while now but this shows how to tie it all together nicely.
Posted by Britt Selvitelle at Tue Feb 6 19:07:49 2007:
Could you post a bit more detail on getting the fdo git packages, for those who haven't used them before?
Posted by Eric Anholt at Tue Feb 6 19:23:47 2007:
You don't have to use the hex.  You can use the output names (LVDS, VGA) and mode names (1024x768, 1680x1050).
Posted by Rss at Tue Feb 6 19:33:00 2007:
Eric: oh, of course, that's logical. Thanks!

Britt: done.

resiak: doh, thanks.
Posted by liquidat at Tue Feb 6 22:11:14 2007:
I think LVDS is "Low voltage differential signaling", see here: LVDS in Wikipedia.

Thanks for the interesting insight into the new Xrandr!
Posted by Adam Williamson at Tue Feb 6 22:14:44 2007:
Thanks for posting this, Ross! I totally didn't have the time to figure out all the gotchas myself, too busy playing with VirtualBox. I'll let you know how it goes for me.
Posted by Andreas Leitner at Tue Feb 6 23:21:45 2007:
Cool stuff. I also have been waiting for this well, forever! How much of this is actually driver specific? Or in other words what is needed to get other video cards to work like this too (thinking radeon, fglrx, nv, nvidia drivers here)?
Posted by Adam Williamson at Wed Feb 7 00:17:13 2007:
There's quite some driver specific stuff involved, each driver must be moved to support xrandr 1.2 before this can work for it. i810 (now called intel) is the testbed - once it's stable there the work will be done for other drivers.

having fun getting this working myself, permissions issues galore and it looks like I need to rebuild libglx, sigh...
Posted by Adam Williamson at Wed Feb 7 02:29:36 2007:
Well, I just surprised the crap out of myself. Having never done any package building stuff before I just hacked this entire bunch of stuff into the MDV X.org packages and it works FIRST TIME.

[adamw@lenovo ~]$ xrandr
Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1200
VGA connected 1680x1050+0+0 (normal left inverted right) 433mm x 271mm

...

LVDS connected 1280x800+0+0 (normal left inverted right) 261mm x 163mm

craaaazy. Thanks a lot for the guide, ross :)
Posted by Ross at Wed Feb 7 08:34:16 2007:
Andreas: most of the magic is in Xrandr code in the xserver.  Drivers need to implement the hooks, i810 was the first driver to support it and I believe work has started on the new nVidia driver and the free ATI driver.
Posted by Javier Ruiz at Wed Feb 7 11:01:27 2007:
Wow, Ross you're my hero! I've been looking for this for ages, and on top with edgy packages no less! :-)

Do you know how well it behaves with two monitors? I've got a 1280x1024 at work and 1440x900 at home (plus the 1280x800 in the laptop), i'll give it a try later and see what happens...
Posted by Ross at Wed Feb 7 11:14:12 2007:
Javier: I only had problems because i810 wouldn't recognise the modes my monitor should be advertising over EDID. With decent displays, randr should automatically be able to switch to the preferred modes.

With more people trying this we'll be able to figure out if its the EDID parser in X which is broken, or my monitor.
Posted by Jon at Wed Feb 7 11:35:13 2007:
Thanks for the writeup! I've been wanting to go on this particular journey ever since I saw mjg59 demonstrating some of it at the debian bbq last year, but I've shied away from it...
Posted by dave at Wed Feb 7 15:02:57 2007:
A somewhat related question:

I don't know if we have the same monitor but lately I've been using my Dell 2005FPW 20" widescreen 1680x1050 monitor turned on its side to portrait mode.

Does anyone know if sub-pixel aliasing (for Ubuntu specifically in my case) takes account of this rotation without having to manually change it from RGB to VRGB and back?
Posted by Ross at Wed Feb 7 15:30:16 2007:
X has no idea you've rotated the screen, so you'll need to tell it.
Posted by Eric Anholt at Wed Feb 7 18:02:26 2007:
Yeah, calling your laptop screen "LVDS" and your DVI panel "TMDS" sucks.  But for the naming for the tool, we wanted a single-word description of the output.  Anyone have better suggestions?  Note: We have no way of determining whether what's connected to SDVO DVI output is an analog CRT or a digital panel.  So the outputs we need to name, off the top of my head:

Analog VGA output
LVDS laptop integrated panel output
SDVO DVI/DMS-59 output
integrated TV output
SDVO TV output
DVO DVI output
DVO TV output

dave:
When you rotate a CRTC, the rotation should be reflected in the subpixel ordering field of the CRTC.  Additionally, the compatibility RandR 1.0 output should report the rotated order if the compatibility RandR CRTC is the one rotated.

However, if you've got your laptop panel non-rotated, and your panel to the side rotated, don't expect your apps to do the right thing with their subpixel rendering on both (yet?)
Posted by Dave at Wed Feb 7 22:29:23 2007:
Yeah, that sucks about, say, GTK, not respecting per-screen subpixel ordering.  Lower level stuff like xft seems to though (via per-screen xresources xft.rgba).
Posted by Eric Anholt at Thu Feb 8 05:35:01 2007:
Dave: yeah, but it's not really possible to get right in some cases: for example, I display my stuff on a projector and a laptop, cloned, for a presentation.  Does my app go subpixel for the laptop, or non-subpixel for the projector?  In a dualhead setup, should my app have to render my text twice, once for the piece of it that's on my RGB-ordered panel, and once for the piece that's on the BGR-ordered panel displaying next to it?  This is ugly stuff.

Also, I was wrong.  The driver doesn't rotate the RGB ordering it reports, apparently.  It just tells what the monitor is, and the app gets to account for rotation/reflection.
Posted by Nils-Anders Nøttseter at Thu Feb 8 07:28:51 2007:
I also have an X60, and I am having a bit of trouble with the xorg.conf, could you share yours? Your packages went in perfectly on Edgy by the way, thanks!
Posted by deubeulyou at Thu Feb 8 21:44:04 2007:
Thanks for the article and packages ! Also I'd second Nils; my xorg.conf seems to be somewhat incomplete... for instance, does this setup need any of the screen LeftOf/RightOf stuff, or multiple devices, etc...
Posted by Ross at Thu Feb 8 22:17:00 2007:
You don't need anything in xorg.conf.
Posted by Nils-Anders Nøttseter at Mon Feb 12 09:56:05 2007:
Ah, it seems I was missing the xserver-xorg-video-intel package, and I wrongfully blamed it at xorg.conf.

Now it all works and I finally have a pleasant xinerama-like setup at work.

The only thing that annoys me now is that DRI no longer works. I have my laptop at 1024x768 and my external monitor at 1600x1200 which means that I need a Virtual 2624 1200 in xorg.conf. The intel driver complains "(EE) intel(0): Cannot support DRI with frame buffer width > 2048." Do you know (yes, you are my oracle) if there is a way around this, or if the hardware is limiting this?
Posted by frenki at Mon Feb 19 10:25:20 2007:
is it posible to run xrandr 1.2 with 2 displays (:0.0 and :0.1)? is that the default setup?

i still have trouble compiling it to 1.2,  but in the meantime it just ignores te xorg setup and clones the picture on the other screen with randr 1.1.
Posted by Eyal Oren at Thu Mar 8 15:21:00 2007:
Ross, thanks a lot for this howto! I've been looking for a way to setup my X60 with docking station for a while, this seems perfect!

I'm running feisty and your repository seems to miss some debs in the feisty dir: If I only install the xrandr package the server still reports xrandr v1.1. If I also install xserver-xorg-core then I have to uninstall xserver-xorg-input-kbd and xserver-xorg-input-mouse (they conflict) but then the xserver doesn't start anymore because he can't find the keyboard/mouse.

I thought about using the packages from experimental or from Daniel Stone's edgy repository but wasn't sure if that's a good idea. Do you have a suggestion? Which packages do I actually need? Would this work with feisty?
Posted by Ross at Thu Mar 8 15:36:18 2007:
Eyal: I'm running feisty now.  You'll want need the new intel driver, the new server itself (the -core package) and obviously to keep the kbd and mouse driver on your system.

I have -intel and -core from my feisty repository, and -kdb 1.1.0-0ubuntu1 -mouse 1.1.1-0ubuntu1.  I should rebuild those at some point against the new server, or rebuild a server with a correct version.

Welcome to the bleeding edge.  These packages will break your system. :)
Posted by Bug at Tue Apr 3 12:26:59 2007:
Hi,

Just found your site while searching for a solution ;) I just bought a subnotebook with an intel graphics chip. Now when I'm working at home I'd like to use my 21" tft. I'm using feisty but as of now I haven't found a working solution.
Now I'm wondering if your solution (including your packages) is working. Your statement "Welcome to the bleeding edge.  These packages will break your system. :)" worries me a littel bit ;)

Any hints for me? ;) thanks
Posted by Ross at Tue Apr 3 14:14:22 2007:
If you add my feisty source to your sources.list, and upgrade the xrandr, the -intel driver and xserver-xorg-core, it should work.
Posted by Magnus at Wed Apr 4 22:00:05 2007:
Switching monitors etc works fine with your feisty packages. However, I cannot get xv working. Anyone had any luck with xv?
Posted by Ross at Wed Apr 4 22:05:29 2007:
Xv works fine for me and always has (both xine and gstreamer).
Posted by Magnus at Thu Apr 5 21:27:04 2007:
Did some more testing, and Xv works when using metacity (no compositing), but does not work under beryl.
Posted by Tom Harris at Mon Apr 16 00:50:33 2007:
hey ross,

i somewhat new to linux and am trying to get my x60 working with an external monitor at 1280x1024.  When reading your how-to, I'm not sure how to do a few things:

1) how to update xproto, glproto, inputproto,libXi, and libdrm.  ..not sure how to update a protocal header

2)i'm also not sure how to "build" xorg/proto/x11proto etc.

many thanks,
tom
Posted by Bronosky at Fri Apr 27 11:29:56 2007:
So, where does all of this code come from?  I can't find xproto, glproto, inputproto, libXi, or libdrm in http://burtonini.com/debian/edgy/

It's really frustrating to know that, just out of my reach, there is a soliution to the one problem that has me wanting to replace my ThinkPad T60 with a MacBook Pro.
Posted by Ross at Fri Apr 27 11:37:27 2007: Posted by RichardBronosky at Wed May 2 21:41:31 2007:
Okay, I found this all very confusing.  I kept trying to apt-get install xproto glproto... and it does not work.  I even repartitioned my HD and installed feisty.  Still couldn't figure it out.

What I finally came up with is this: (Make sure this doesn't line wrap; Only 3 lines.)
echo deb http://burtonini.com/debian/ feisty/|sudo tee -a /etc/apt/sources.list
sudo apt-key advanced --keyserver subkeys.pgp.net --recv-keys 0x510E0293
sudo apt-get -V install  xrandr  xserver-xorg-video-intel  xserver-xorg-core

The -V will show you the versions to be installed.  Make sure they correspond with the file names here: http://burtonini.com/debian/feisty/

After a reboot, the new intel driver and xrandr was working:
~$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1600
VGA connected 1600x1200+0+0 (normal left inverted right) 367mm x 275mm
  1600x1200  60.0*+  59.9 
  1280x1024  59.9 
  640x480  60.0 
LVDS connected 1024x768+0+0 (normal left inverted right) 286mm x 214mm
  1024x768  60.0*+  50.0 
  800x600  60.3 
  640x480  60.0  59.9 
TMDS-1 disconnected (normal left inverted right)
TV disconnected (normal left inverted right)

I'd expect that replacing feisty with edgy would work for those not on the bleeding (now released as stable) edge.

Now I just have to figure out what to do with it!  I want to get into a dual desktop situation... I'll follow up if I figure it out.

I hope that helps Tom Harris and anyone else who was confused like me.
Posted by Felix schalck at Wed May 9 11:01:39 2007:
hi Ross,

Thank you for your quick randr 1.2 "howto". I install everything from your depots, and got it quite a bit working. Config: laptop panel 1280x800 + External 1680x1050; intel 855gm. Unfortunatly, I noticed a few annoying problms:

1. Is it possible to get the FIRST output to the LVDS panel, and to handle the external screen as an extension ? What would be the VIRTUAL config needed ?

2. Subpixel hinting on the external screen is very bad; xrandr --verbose shows "Subpixel: Unknown" for the external panel. Is it possible to force/fix it ?

3. The "man xrandr" page is quite poor; is there a more complete documentation/manual for xrandr 1.2 somewhere ?

Again: thank you very much,

Felix
Posted by Brian Ristuccia at Wed May 16 21:24:39 2007:
Could you add 64-bit packages or give a pointer to the .orig.tar.gz for those of us on 64-bit systems?
Posted by Ross at Wed May 16 21:34:11 2007:
Freedesktop has the original tarballs, but it would be easier now to simply rebuild the packages from Debian Sid (which is what I've been doing now).
Posted by Sean at Thu May 17 13:32:10 2007:
This works on my X60s, and was really the only thing left to get working, so thank you!

One small problem - when the xserver first starts, both displays are always enabled. Normally when I have the external screen plugged in, the laptop display won't turn on at all when X starts.

Is it possible to keep one display off at startup?
Posted by Zach at Mon May 21 19:51:39 2007:
Many thanks for pioneering this method--I've been using it on a Dell Inspiron 700m and various external monitors for a few weeks now, and the results have been superb.  One problem that persists is that play video on my LVDS screen never seems to work (in any player, including VLC), even with the VGA screen not attached.  When the VGA external is attached, the video renders normally in the VGA screen, but not the LVDS.  I presume (hope?) that this is a matter of setting the active or primary screen to my LVDS, but I haven't found any command that successfully changes it so that video works. 

Regarding Sean's comment above, I've found that my "best practices" involve leaving the external unplugged at startup, and then changing screens.  To do so otherwise, with my Dell 2005FPW, will query the screen resolution of the 2005FPW (1680x1050) and will set the maximum screen area to 1680x1680 instead of 2048x2048.  Starting up with nothing attached gives me the full range of options, and I've just created an alias that turns the external on and the laptop screen off.
Posted by Han-Wen at Fri Jun 8 00:46:21 2007:
Any tips for doing this on fedora? I'm on fedora 7, and not afraid of Git, but not up the task of compiling X myself.
Posted by Thomas at Sun Jun 10 21:56:12 2007:
I thought xrandr1.2 was allready included in fedora 7!
Posted by ccamacho at Fri Jun 22 16:39:31 2007:
Nice guide :)

Somewhere you said "If you want to do Xinerama-style dual screen you can do that too: xrandr 1.2 encompasses that behaviour"

How can I do this with a monitor using 1024x768 (laptop) and the other one using 1440x900 (external LCD)?

I have been trying... but not success till now
Posted by Ken Mandelberg at Thu Aug 23 05:33:03 2007:
I'm running on feisty with an upgrade to your packages. The results switching between a 1920x1200 VGA monitor and the 1024x768 LVDS are erratic.

Going from VGA to LVDS mostly works. In the other direction the gnome-terminals always die. Some other clients live, others come up in a bad state.

Some times the session dies and goes back to a login screen on a switch.

Any ideas?
Posted by Ross at Thu Aug 23 08:07:09 2007:
I've seen that, but I think it got fixed at some point.  I'm not sure if it was a bug in libxrandr or GTk+ though.
Posted by Ken Mandelberg at Fri Aug 24 07:38:54 2007:
>I've seen that, but I think it got fixed at some point.  I'm not sure if it was a bug in libxrandr or GTk+ though.

Are you running the standard feisty libxrandr and GTk+?

Here is what the segfault looks like on a client

#0  init_xinerama_support (screen=<value optimized out>) at gdkscreen-x11.c:617
#1  0xb7c06090 in _gdk_x11_screen_size_changed (screen=0x80680d0,
  event=0xbffdb618) at gdkscreen-x11.c:753
#2  0xb7bf85d9 in gdk_event_translate (display=0x8065098, event=0x80695f8,
  xevent=0xbffdb618, return_exposes=0) at gdkevents-x11.c:1825
#3  0xb7bf9cfb in _gdk_events_queue (display=0x8065098) at gdkevents-x11.c:2252
#4  0xb7bfa0ff in gdk_event_dispatch (source=0x806cec0, callback=0,
  user_data=0x0) at gdkevents-x11.c:2312
#5  0xb78a7df2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#6  0xb78aadcf in ?? () from /usr/lib/libglib-2.0.so.0


Looks kind of like its in gdkscreen. Does it make sense  that xinerama is being called?
Posted by Roger at Mon Sep 17 22:23:45 2007:
Thanks a million for providing the updated Feisty packages to get dual-screen running with XRandR. 

IMHO the XRandR in conjunction with the intel driver make dual-screening stupidly simple.
Posted by orangeek at Mon Mar 3 21:33:24 2008:
Hi Ross.
I tried to find the feisty packages in your repository but I didnt find any x package...
Do I miss something?
thank you
Posted by Ross at Tue Mar 4 06:54:56 2008:
The archive got deleted, but the feisty packages were very out of date.

That said, Gutsy has been out for a long time now, and has everything working (the packages were rebuilds of Gutsy packages).
Posted by Sam at Wed Jun 4 05:09:22 2008:
Problem with Xrandr 1.2 utility's query command

Hi Ross,

I have Xrandr 1.2 version, when I give Xrandr -q or xrand -query
I get following output::::

# xrandr --query
SZ:  Pixels  Physical  Refresh
0  1600 x 1200  ( 310mm x 231mm )  69  68  67
1  1280 x 1024  ( 310mm x 231mm )  80  79  78
2  1024 x 768  ( 310mm x 231mm )  105  104  103
3  800 x 600  ( 310mm x 231mm )  133  132  131
4  1400 x 1050  ( 310mm x 231mm )  75  60
5  1280 x 960  ( 310mm x 231mm )  85  60
6  1152 x 864  ( 310mm x 231mm )  75
7  1152 x 768  ( 310mm x 231mm )  55
8  928 x 696  ( 310mm x 231mm )  60
9  896 x 672  ( 310mm x 231mm )  60
10  832 x 624  ( 310mm x 231mm )  75
11  700 x 525  ( 310mm x 231mm )  75  60
12  640 x 512  ( 310mm x 231mm )  75  60
13  640 x 480  ( 310mm x 231mm )  85  75  73  60
14  720 x 400  ( 310mm x 231mm )  85
15  640 x 400  ( 310mm x 231mm )  85
16  576 x 432  ( 310mm x 231mm )  75
17  640 x 350  ( 310mm x 231mm )  85
18  576 x 384  ( 310mm x 231mm )  55
19  512 x 384  ( 310mm x 231mm )  85  75  70  60  87
20  416 x 312  ( 310mm x 231mm )  75
21  400 x 300  ( 310mm x 231mm )  85  75  72  60  56
22  320 x 240  ( 310mm x 231mm )  85  75  73  60
23  360 x 200  ( 310mm x 231mm )  85
24  320 x 200  ( 310mm x 231mm )  85
25  320 x 175  ( 310mm x 231mm )  85
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none


Thus, I am unable to know which mode is currently connected(i.e VGA, LVSD, DVI etc.)

Basically I want to simulate turning on and off of my Monitor.

I am doing
$ xrandr –output VGA-0 –off

but, its not working.

Any help in this respect is greatly appreciated.

- Sam
Posted by Sam at Wed Jun 4 05:17:48 2008:
Problem with Xrandr 1.2 utility's query command

Hi Ross,

I have Xrandr 1.2 version, when I give Xrandr -q or xrand -query
I get following output::::

# xrandr --query
SZ:  Pixels  Physical  Refresh
0  1600 x 1200  ( 310mm x 231mm )  69  68  67
1  1280 x 1024  ( 310mm x 231mm )  80  79  78
2  1024 x 768  ( 310mm x 231mm )  105  104  103
3  800 x 600  ( 310mm x 231mm )  133  132  131
4  1400 x 1050  ( 310mm x 231mm )  75  60
5  1280 x 960  ( 310mm x 231mm )  85  60
6  1152 x 864  ( 310mm x 231mm )  75
7  1152 x 768  ( 310mm x 231mm )  55
8  928 x 696  ( 310mm x 231mm )  60
9  896 x 672  ( 310mm x 231mm )  60
10  832 x 624  ( 310mm x 231mm )  75
11  700 x 525  ( 310mm x 231mm )  75  60
12  640 x 512  ( 310mm x 231mm )  75  60
13  640 x 480  ( 310mm x 231mm )  85  75  73  60
14  720 x 400  ( 310mm x 231mm )  85
15  640 x 400  ( 310mm x 231mm )  85
16  576 x 432  ( 310mm x 231mm )  75
17  640 x 350  ( 310mm x 231mm )  85
18  576 x 384  ( 310mm x 231mm )  55
19  512 x 384  ( 310mm x 231mm )  85  75  70  60  87
20  416 x 312  ( 310mm x 231mm )  75
21  400 x 300  ( 310mm x 231mm )  85  75  72  60  56
22  320 x 240  ( 310mm x 231mm )  85  75  73  60
23  360 x 200  ( 310mm x 231mm )  85
24  320 x 200  ( 310mm x 231mm )  85
25  320 x 175  ( 310mm x 231mm )  85
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none


Thus, I am unable to know which mode is currently connected(i.e VGA, LVSD, DVI etc.)

Basically I want to simulate turning on and off of my Monitor.

I am doing
$ xrandr –output VGA-0 –off

but, its not working.

Any help in this respect is greatly appreciated.

- Sam
Posted by acer at Fri Jul 4 10:57:31 2008:
Thus, I am unable to know which mode is currently connected(i.e VGA, LVSD, DVI etc.)

Basically I want to simulate turning on and off of my Monitor.

Name:


E-mail:


URL:


Add 8 and 8 (required):


Comment: