From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KpHZk-0004Nt-74 for garchives@archives.gentoo.org; Mon, 13 Oct 2008 07:10:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3421DE027E; Mon, 13 Oct 2008 07:10:43 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.148]) by pigeon.gentoo.org (Postfix) with ESMTP id CCB18E027E for ; Mon, 13 Oct 2008 07:10:42 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 4so495354eyk.10 for ; Mon, 13 Oct 2008 00:10:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=Eg+1Wn1IC5FljsfSI70FmQIWcqhOAFc1G1CMGk7KDp4=; b=RvQ+4erGj6dOrTF4eFj6T0r/u1T5mW4jPPVjkcwARcHRqECIxep12dQd0B4raCPlgW vwdByF+u965XlYRnsKrOQXmD64hw0RqvMaSASPdCfMl642PkWxNw6WEcAxuuY1p63kGb UUA9J6NnFpRvjeJNGeqwghEB5/fGLLLPNvjg0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=gGMNyfaA/51w9M7443iL4PRMnd+vltzb+Hy3E6JtJgsFBOSv15T0jeWPW1wrq36JJo I5mQ1RSOy7L85VXOWZltj2yZAqLFqJ6QCOTXf/Cp7TPMkxM5MZljI99f1aqC1o0RqH7d LkcYNbuecDKxeNRkx5FefKXejK1liSgGXgDE0= Received: by 10.210.30.1 with SMTP id d1mr5016940ebd.127.1223881841433; Mon, 13 Oct 2008 00:10:41 -0700 (PDT) Received: from ?10.1.245.102? (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id p10sm9392055gvf.7.2008.10.13.00.10.37 (version=SSLv3 cipher=RC4-MD5); Mon, 13 Oct 2008 00:10:39 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Xinerama vs TwinView for dual monitor setup Date: Mon, 13 Oct 2008 09:10:34 +0200 User-Agent: KMail/1.9.10 References: <200810112334.10957.alan.mckinnon@gmail.com> <48F2AC2B.10006@netspace.net.au> In-Reply-To: <48F2AC2B.10006@netspace.net.au> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810130910.34455.alan.mckinnon@gmail.com> X-Archives-Salt: 657f78db-5cba-49d8-87b4-09fe8692e72c X-Archives-Hash: 71e487bb5d0fe89d786705f3c1322f34 On Monday 13 October 2008 04:02:19 Iain Buchanan wrote: > [snip] > > > I've configured it with TwinView > > as in: > Option "TwinView" "True" Yes. Some output : $ sudo grep -i -e xinerama -e twinview /var/log/Xorg.0.log (**) Option "Xinerama" "1" (**) Xinerama: enabled (**) NVIDIA(0): Option "TwinView" "1" (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0" (**) NVIDIA(0): TwinView enabled (II) Initializing built-in extension XINERAMA $ sudo grep -i -e xinerama -e twinview /etc/X11/xorg.conf Option "Xinerama" "1" Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-0" > > 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? My description wasn't clear. I mean the screens are physically and logically laid out like so: +------------------------------+ | | | | 1 | 2 | | |-----------+ +------------------+ 1 is the notebook screen 2 is the external lcd below 2 is dead space. The mouse works correctly. > > 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. OK, I did that. The packages that got rebuilt are: $ equery hasuse xinerama [ Searching for USE flag xinerama in all categories among: ] * installed packages [I--] [ ~] x11-apps/xdpyinfo-1.0.3 (0) [I--] [ ~] x11-libs/qt-3.3.8b (3) [I--] [ ~] x11-libs/gtk+-2.14.3-r2 (2) [I--] [ ~] x11-libs/qt-gui-4.4.2 (4) [I--] [ ] x11-misc/engage-9999 (0) [I--] [ ~] kde-base/ksplash-4.1.2 (4.1) [I--] [ ~] kde-base/plasma-workspace-4.1.2 (4.1) [I--] [ ~] kde-base/ksplashml-3.5.10 (3.5) [I--] [ ~] kde-base/systemsettings-4.1.2 (4.1) [I--] [ ~] kde-base/kwin-4.1.2 (4.1) [I--] [ ~] kde-base/libplasma-4.1.2 (4.1) [I--] [ ~] kde-misc/knetworkmanager-0.2.2_p20080528 (0) [I--] [ ~] kde-misc/filelight-1.0-r1 (0) [I--] [ ] media-libs/libsdl-1.2.13 (0) [I--] [ ] media-libs/xine-lib-1.1.15-r1 (1) [I--] [ ] net-libs/xulrunner-1.8.1.17 (1.8) [I--] [ ~] media-sound/kid3-1.0 (0) [I--] [ ~] media-sound/amarok-1.4.10-r1 (0) [I--] [ ~] media-video/mplayer-1.0_rc2_p27725-r1 (0) [I--] [ ] media-video/xine-ui-0.99.5-r1 (0) [I--] [ ~] media-video/gxine-0.5.903 (0) [I--] [ ~] app-cdr/k3b-1.0.5-r3 (0) Seems like the only things that would affect kde-3 apps is qt-3.3.8b. Plus x11-libs/libXinerama and x11-proto/xineramaproto (both latest unstable) are installed. [snip] > > 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`. I was running /bin/think --exaggerate --frustrated --logic-level -3 when I typed that :-) > check out my blog for how I did it: > > http://nthrbldyblg.blogspot.com/2008/08/nvidia-xinerama-on-dell-m6300.html Nice blog :-) I'll fiddle some more with these tips later in the day, but first a conceptual question: I read that huge collection of docs from nvidia-drivers, and concluded that Xinerama and TwinView are fundamentally different and incompatible. i.e. Xinerama starts with two classic X screens and joins them in software to make one big display - an abstraction layer if you will. TwinView rips out the guts of X, dispenses with the notion of separate screens for a TwinView display and gives you one giant screen with no API for an app to see how this big screen is composed. So, you either use Xinerama or TwinView, but not both. Obviously, this understanding of mine is flawed. Which bit did I get wrong? -- alan dot mckinnon at gmail dot com