From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Xinerama vs TwinView for dual monitor setup
Date: Sat, 11 Oct 2008 23:34:10 +0200 [thread overview]
Message-ID: <200810112334.10957.alan.mckinnon@gmail.com> (raw)
Hi,
My notebook has this graphics hardware.
alan@nazgul ~ $ sudo lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev
a1)
alan@nazgul ~ $ sudo xdpyinfo | grep -A4 'screen #0'
screen #0:
print screen: no
dimensions: 1920x1200 pixels (332x210 millimeters)
resolution: 147x145 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
I also have a second LCD monitor at work, a 1280x1024 that is physically
slightly larger than the notebook screen, with a corresponding lower dpi.
I've configured it with TwinView to have the second monitor on the right, and
how I usually use it is to put a user's support mail on that where I can read
it and fix their issues using the tools on the main monitor. So it's a very
unsophisticated setup, I have no need for massive 3D accel for eg games, or
even for placing windows across two monitors. Windows are always on one
screen or the other (because of the huge dpi difference). There are two
smallish issues:
The viewports are aligned along the top edge and the
panel/kicker/plasma/whatever on every desktop environment insists on trying
to stretch across both monitors, into dead space on the right hand one. I'm
getting use to right-click on panel, configure, set width to 57% at work,
100% at home. If I align the viewports on the bottom edges, windows managers
tend to want to position new windows with their title bars in the dead space
at the top.
kdm and entrance want to stretch over both monitors. I definitely do not want
this. Murphy dictates that all useful DM menus will end up in the dead space
regardless of the theme I use <grrrr>
My research into nvidia's docs leads me to believe that TwinView is designed
to make the presence of two physical monitors invisible and present one giant
X screen, with a funky API for dead spaces (which may or may not work). I'm
thinking Xinerama is the better option, despite the fact that it's old,
clunky, hopeless at dealing with XRandR and can't be changed on the fly. I'm
happy to set up two ServerLayouts to deal with this.
I'd appreciate some pros and cons feedback from the list before I embark on a
huge emerge -e world to include Xinerama support.
--
alan dot mckinnon at gmail dot com
next reply other threads:[~2008-10-11 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 21:34 Alan McKinnon [this message]
2008-10-11 22:36 ` [gentoo-user] Re: Xinerama vs TwinView for dual monitor setup Grant Edwards
2008-10-12 8:04 ` Alan McKinnon
2008-10-12 14:30 ` Grant Edwards
2008-10-13 1:29 ` Iain Buchanan
2008-10-13 14:39 ` Grant Edwards
2008-10-13 15:48 ` Grant Edwards
2008-10-12 15:27 ` [gentoo-user] " YoYo siska
2008-10-13 2:02 ` Iain Buchanan
2008-10-13 7:10 ` Alan McKinnon
2008-10-13 11:53 ` YoYo siska
2008-10-13 12:05 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810112334.10957.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox