From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Rp4Qc-0000ef-2q for garchives@archives.gentoo.org; Sun, 22 Jan 2012 20:54:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7A96FE07F4; Sun, 22 Jan 2012 20:54:03 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 22AA1E07D0 for ; Sun, 22 Jan 2012 20:53:06 +0000 (UTC) Received: by werb10 with SMTP id b10so1808593wer.40 for ; Sun, 22 Jan 2012 12:53:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:mime-version:content-type:content-transfer-encoding; bh=OaGR0ma/QlHRn7aE+JQdwU54Bwv6cB7FjAcy9c+0SIc=; b=S8/uAUoxMLz2/dBxYObGwuRhbLb8QnPcELE9sG5YIuYSSwhkgdwMtQWmrWYx68WUrT mNw4BPH3Hyk+vVwGaEC+M04tCrqSdIcUipDV9PEEFy2+O//cf9FtGX2YkKwsf/7AzSNP MYcreudUBiCQmK5fQFO604IrsDToq4alvWDYM= Received: by 10.216.131.102 with SMTP id l80mr2261443wei.59.1327265586370; Sun, 22 Jan 2012 12:53:06 -0800 (PST) Received: from khamul.example.con (196-215-2-107.dynamic.isadsl.co.za. [196.215.2.107]) by mx.google.com with ESMTPS id n3sm33650673wiz.9.2012.01.22.12.53.03 (version=SSLv3 cipher=OTHER); Sun, 22 Jan 2012 12:53:05 -0800 (PST) Date: Sun, 22 Jan 2012 22:52:37 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] KVM problems - anyone know _why_ it happens? Message-ID: <20120122225237.6474b7a8@khamul.example.con> In-Reply-To: References: <4F1C504D.6010105@gmail.com> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.8; x86_64-pc-linux-gnu) 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=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 4c114be3-d980-4814-a794-9e71a2826487 X-Archives-Hash: 786a0492ad3310ba282db4688fbb0374 On Sun, 22 Jan 2012 12:18:17 -0800 Mark Knecht wrote: > On Sun, Jan 22, 2012 at 12:07 PM, Michael Mol > wrote: > > On Sun, Jan 22, 2012 at 2:30 PM, Mark Knecht > > wrote: > > >> > >> Also, thanks for the pointer to xvidtune. Interesting little app. > >> QUESTION: Do you know how to get the data for each monitor/video > >> card combo? So far I haven't figured out how to tell it Screen2. > >> Seems to only give me Screen0 as best I can tell. > >> > >> I'm a bit nervous to just start trying things. > > > > If you're not using Xinerama, you can specify screens by changing > > $DISPLAY. e.g. :0.0 is screen 0, :0.1 is screen 1, :0.2 is screen > > 2... > > > > I am using xinerama. 3 monitors across 2 NVidia adpaters. Same on my > friends system. > > One interesting thing about this configuration. On his machine he uses > two identical 8400GS adapters. He can run glxgears and is able to move > the gears to any screen and see the gears. He can also use the KDE > features to look at all desktops and application using (Ctrl-F8 I > think) or by dragging his mouse to the upper left corner. > > On my setup I use a GTX465 for screen 0 & 1 but have an NVidia 8400GS > for screen 2. On this system I only see the gears on screen 0 & 1. On > screen 2 I see just a black box and the FPS count skyrockets as the > CPU/GPU aren't really doing anything so it goes through the loop very > fast. Also, on this system the Ctrl-F8 thing mouse to the upper left > corner don't work at all. > > I've assumed that's because I'm using two different NVidia cards. > > - Mark > The docs for the nVidia driver go into this in quite some detail, and it's related to how the nVidia hardware is built plus how the nVidia software works plus how Xinerama works. Basically, not all combinations are supported, especially when you have different "screens" (that's the nVidia concept of a screen, not the X concept) with different resolutions on different GPUs. Or something like that, but I don;t have the docs to have anymore since my last 8600M went to visit the silicon daddy in the sky -- Alan McKinnnon alan.mckinnon@gmail.com