public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Xinerama vs TwinView for dual monitor setup
Date: Mon, 13 Oct 2008 11:32:19 +0930	[thread overview]
Message-ID: <48F2AC2B.10006@netspace.net.au> (raw)
In-Reply-To: <200810112334.10957.alan.mckinnon@gmail.com>

Alan McKinnon wrote:
> 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)

I have a Quadro FX 1600M, using nvidia-drivers...

> 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 have an LCD at 1920x1200, but it's much larger than my laptop 
display, so the dpi is different.  So far I have no working way of 
setting different DPI's on the different monitors.

[snip]

> I've configured it with TwinView

as in:
      Option         "TwinView" "True"
?

> The viewports are aligned along the top edge

you mean move the mouse up and it appears on the next screen?  Don't you 
want them aligned left / right of each other?

>  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.

Sounds like you haven't compiled stuff with the xinerama USE flag.  I 
put it in make.conf, and then did a emerge --newuse.

> 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.

definitely sounds like you haven't recompiled with xinerama.

> 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>

xinerama should make your wm open screens on one window only.  Also your 
log-in screen should be on one screen only, and panels should be on one 
screen only.

> 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.

Why would you do -e world?  How about `emerge -uN world` The N being 
--newuse.  or `emerge -vauDN world`.

It's not that huge, but you need it regardless of whether you use 
twinview or xinerama anyway.

$ equery hasuse xinerama | wc -l
16

check out my blog for how I did it:

http://nthrbldyblg.blogspot.com/2008/08/nvidia-xinerama-on-dell-m6300.html

HTH,
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Chuck Norris once ate a whole cake before his friends could tell him 
there was a stripper in it.



  parent reply	other threads:[~2008-10-13  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 21:34 [gentoo-user] Xinerama vs TwinView for dual monitor setup Alan McKinnon
2008-10-11 22:36 ` [gentoo-user] " 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 [this message]
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=48F2AC2B.10006@netspace.net.au \
    --to=iaindb@netspace.net.au \
    --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