[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Xephyr on AMD64 Etch a.k.a multiseat



On Fri, Jun 08, 2007 at 10:14:38AM -0500, Igor TAmara wrote:
> Hi, I'm following this howto[1] to make a multiseat system on AMD64,
> I saw there were precompiled binaries for Xephyr, and I started to
> create some packages with apt-get source applying the patches on
> that page[1]
> ...

> Mi questions :
>  * Does anyone have experiences of multiseat with AMD64?
>  * If so, the Xephyr approach or something else? (documents?)
>  * If with Xephyr, do you have a recommendation for applying the
>  necessary patches? Maybe a pointing to a howto or a manual? I
>  suspect that I'm applying the patch incorrectly, how to do that in
>  a correct way?


 Sorry, this is an old email, but I'm digging through my Debian mailbox
archives...

 xorg now supports sharing virtual terminals, so you can run multiple full X
servers, with no need for xephyr anymore.  They get device input from evdev,
instead of from the console keyboard.

 I have a working g965 + PCI r128 multiseat system (two PS/2 keyboards and
two USB mice plugged into an Intel DG965WH mobo).

 I have to get the PCI card initialized with int10, but if int10 is enabled
when I start two X servers at once, they both get the g965 video BIOS or
something, and it can't initialize.

 So my normal xorg.conf has i2c, ddc, int10, and vbe commented out.  I was
going to post some snippets of my xorg.conf, but it's going to be a lot more
useful to actually post the whole thing.  (and the number of snippets was
climbing...)

 And the Device and Serverlayout sections have sprinklings of
        Option          "NoInt10" "true"
        Option "NoDDC" "true"  # somehow r128 sees the i810's VBE BIOS...

        Option          "SingleCard" "true"  # like IsolateDevice
        Option "InitPrimary" "true"

 I'm sure not all of these are necessary, but that's where I got to by trial
and error.

 I have a normal (multihead single seat) xorg config that doesn't disable
POSTing the video cards, which I use to get the video cards initialized.

#  sudo X -config xorg.conf.probe -probeonly
# then 
#  startx /usr/bin/fluxbox -- :1 -layout seat1 -sharevts vt8 &
#  startx /usr/bin/fluxbox -- :0 -layout seat0 -sharevts vt7 &

 The key of course is the -sharevts.  If you google around, you can find how
to configure gdm to start the X servers, and for more tutorials on this.

http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html
http://en.wikibooks.org/wiki/Multiterminal_with_evdev

 I had been hoping to give the PCI video card to a Xen hardware-virtualized
domain, and give my dad a windows desktop.  That doesn't work (yet?).  I
might do more with multihead when I get more RAM (2GB DIMMs are becoming
available :), but I still need to reboot occasionally when the g965 driver
crashes.  (It doesn't lock the machine at all, but rebooting (or
suspend-resume, when that works at all), is the only way I've found to get
the g965 video hardware back to a useable state.)

 I have used multiseat while playing vegastrike on the g965 head, with
out-of-game tools on the r128 head.  Having a separate keyboard is a big win
when using games that take over the X server and can't be switched away from
easily.  Well, CTRL+ALT+Fx to another X server might work.  But anyway.

-- 
#define X(x,y) x##y
Peter Cordes ;  e-mail: X(peter@cor , des.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BC

Attachment: signature.asc
Description: Digital signature


Reply to: