Re: [Chromium-users] [DMX-Devel] Chromium and DMX beginner troubles

[Andres F. M. V. <af....@un...>]

First off, thank you very much for your reply.

So far the only way DMX runs is if in fact there is a window manager running
on the back-end nodes. Otherwise, how am I able to run xhost+... so that my
front-end can connect?

I am using the xorg code. Version according to rpm retrieved by yum:
xorg-x11-server-Xdmx-1.1.1-48.41.el5

The good news is that I finally got chromium and dmx to work. Turns out that
I had an error with my dmx.conf file. I was only declaring the backend
machine in the hosts array and it created conflicts elsewhere. 

This leads me to my new problem. I've been running frame rate tests using
the glxgears app on chromium+dmx seems to run considerably slower than dmx
by itself (~1700 FPS vs ~9800 FPS, respectively). More so, I don't see any
GL_CR_dmx in the list of OpenGL Extensions given by glxinfo (according to
the docs page I should). Is there any other way of checking if chromium is
running?

I am running glxgears manually, like so:
--------------------
guaviare $: python dmx.conf
*start crservers on guaviare and guaviare3*
guaviare $: crappfaker glxgears
--------------------

To be honest, this is kind of a miss-matched setup I have going on. Chromium
1.9 has been compiled from source. DMX was entirely different story. I
downloaded the sourceforge source .tar and compiled it in order to get the
libdmx.a library needed by chromium, following the instructions on the Docs
site. I this must be wrong on several levels, but this was before I found
out dmx had been integrated into Xorg.

What would be the correct way of installing these two?

Thanks,
-Andres


-----Original Message-----
From: Sean Ahern [mailto:ah...@or...] 
Sent: Sunday, October 19, 2008 3:50 PM
To: Andres Felipe Molina Villamizar
Cc: chr...@li...; dmx...@li...
Subject: Re: [DMX-Devel] Chromium and DMX beginner troubles

Andres Felipe Molina Villamizar wrote:
> The only way to get DMX to run is when each node is started in TWM. When 
> logged in Gnome or KDE it fails to connect? Any particular reason?

You shouldn't run a window manager on the back-end nodes.  It's 
superfluous and would likely give strange visual artifacts anyway.  (I'm 
not sure whether DMX operates in OverrideRedirect mode on the back-ends.)

> Once DMX runs, UI elements such as icons and text don't show up properly 
> (specially under Gnome). Only way to make it visualize properly is to 
> use the -norender parameter when running the Dmx command (just two 
> displays for testing purposes):
> 
> $ startx -- /usr/bin/Xdmx :1 -display guaviare:0 -display guaviare3:0 
> +xinerama -norender

That's correct.  However, I think this problem has been alleviated by 
the recent X.org builds.  What version of DMX are you running, code from 
the deprecated DMX sourceforge web site, or the DMX that comes from the 
X.org code tree?  More precisely, what DMX is yum giving you?

> I am unable to run chromium once DMX is running. I followed the steps 
> detailed in the chromium docs page (manual run), but I get the following 
> message from the mothership:
> 
> $ CR Warning(guaviare:22281): Tilesort bucket_mode = Non-Uniform Grid, 
> but tiles don't form a non-uniform grid!  Falling back to Test All Tiles 
> mode.

That's not a problem, it's just a warning.  And you'll get it when your 
chromium configuration forms a non-uniform grid.  Some powerwalls 
(TwinView comes to mind) are designed like this.  If yours is not, if it 
truly is a uniform grid, then you have a bug somewhere in your chromium 
config file.

Have you been able to successfully run Chromium across your system 
without DMX in the picture?  That's a good "walk before you run" test.

> And the following repeated message from the crserver on guaviare3:
> 
> $ CR Warning(guaviare3:10322): Render SPU: render_to_app/crut_window 
> option is set but the window ID 0x1400002 is invalid on the display 
> named guaviare3:0.0

Not sure why you would have a CRUT problem.  Why are you setting CRUT 
options?  I would try running a serial non-CRUT application first 
(glxgears comes to mind) before you try anything more complex.

-Sean

__
Sean Ahern
Oak Ridge National Laboratory
AIM: ornlsean
865-241-3748