From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 13:35:09 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4005816A46D for ; Mon, 4 Jun 2007 13:35:09 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from a.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2232513C4B0 for ; Mon, 4 Jun 2007 13:35:09 +0000 (UTC) (envelope-from lreid@cs.okstate.edu) Received: from [172.18.0.137] (sky_cpfw-1.tulsatech.org [70.168.226.130]) by a.cs.okstate.edu (Postfix) with ESMTP id 27CA3A0635; Mon, 4 Jun 2007 08:35:08 -0500 (CDT) Message-ID: <4664150A.2000709@cs.okstate.edu> Date: Mon, 04 Jun 2007 08:35:06 -0500 From: Reid Linnemann User-Agent: Thunderbird 2.0.0.0 (X11/20070517) MIME-Version: 1.0 To: Norberto Meijome References: <20070601131600.16d9cb11@localhost> <05c72d5684132cc1d65b1cfb1846c669@mail.schlossadler.net> <20070604114351.3df9b5b3@localhost> In-Reply-To: <20070604114351.3df9b5b3@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd@schlossadler.net, freebsd-questions@freebsd.org Subject: Re: 6.2/i386 X/DRI issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 13:35:09 -0000 Written by Norberto Meijome on 06/03/07 20:43>> > On Fri, 1 Jun 2007 15:11:26 +1000 > Alex R wrote: > >>> it's in the archives of the list - you need to install the mesa-demos >>> port. >> Installed it. >> >> [alex@desktop ~]$ glxinfo >> Error: unable to open display >> >> But thats because I am ssh'd into the box from work, I dare say it will work when I get home and test from within X. > > ( X forwarding over ssh to your local display ..? I am just not sure whether glxinfo calculations would be based on your remote display or your local one....) > glxinfo over X-forward will report on the display the client is drawing on - X clients are not aware of any other displays unless explicitly instructed (e.g. glxinfo -display localhost:0), and even then you'll have to fight xauth. Incidentally, you can never do direct rendering over remote X connection because the client (which is executed on a remote system) does not have direct access to the memory of the display.