Re: Two accelerated xservers on a single G550

[Aivils S. <Aiv...@un...>]

> I stumbled across a XFree86 config file for the G450,
> which had something new to me.  There were two
> device sections referrring to the same BusID,
> but with screen=0 and screen=1.
>
> I decided to try the same on my G550.  Instead of
> running the second head with framebuffer, I used
> the mga accelerated driver and screen=1.
> The first attempt failed, X found "a suitable device
> but no screen" or some such.  So I removed
> the screen=1 thing just to see what happened.
>
> Accelerated mga was already running on the first head
> as :0, and I now started another accelerated server with
> the same configuration as :1, with another keyboard and mouse.
>
> It worked in a weird way - I got two xservers running on the
> _same_ screen.  Each mouse had its own cursor, they could
> chase each other around.  I opened one xterm with each
> mouse. My left keyboard worked with
> the left xterm, the right keyboard witht he right  xterm.
> A "poor man's ruby setup", dual seat with a single screen.

Congratulations! You open new "matrox psyho circus" thread.
IMHO with right config You solutions works. Of course any
cyberpunk may use neighbour display, but that by-product only.

Please test config, whrere both xf86 use _two_ screens without
xinerama. If You use both screens of matrox device, then You
can determine "who is who".
     1st xf86 "matrox device screen=0" as _fisrt_ xf86 Screen
in ServerLayout, but "matrox device screen=1" as second
     2nd xf86 swap order of "matrox device" in ServerLayout.
"matrox device screen=1" is _first_ for this server.

Both servers setup both screens, which one may work according
Your reports above. Because matrox device order is swaped, then
sys admin can determine where runs programs under each xf86.

"xterm -display :0.0" runs on owner display
"xterm -display :0.1" runs on neighbour display

But DISPLAY=":0.0" always.

You might add in .xinirc line
xsetroot -display :0.1 -color most-compatible-colour

This solution cannot be called "technical correct".

You can try patch program Xnest to use independ mouse
and keyboard.

Aivils Stoss