not possible to start two X servers, only the one launched later works

[Zhang Weiwu]

Hi. See the end.

On Sun, 4 Jun 2006, Zhang Weiwu wrote:

> On Sat, 3 Jun 2006, Stefan Dirsch wrote:
>
> > On Sat, Jun 03, 2006 at 10:56:24PM +0800, Zhang Weiwu wrote:
> > > Hello. I just posted question about the problem of dual-head cannot
> > > initialize the second card. I just managed to make both video card work with
> > > two PCI slots (the bug Stefan mensioned also state it is problemaic to work
> > > with dual-head with one of the video card is on-board card).
> > >
> > > Currently both video card can work the same time with one single X server in
> > > xinerama style, I can move cursor from this screen to the other one just
> > > fine. My original purpose is to run one X server per card so that I can make
> > > 'multi-seat' host.
> > >
> > > I have two sets of keyboard/monitor/mouse attached. starting any of them
> > > works fine
> > > X -layout seat0 => result, the first set of keyboard/monitor/mouse works
> > > X -layout seat1 => result, the first set of keyboard/monitor/mouse works
> > >
> > > (seat0 is configured to work with a Voodoo Banshee card on the 2nd PCI slot)
> > > (seat1 is configured to work with a SiS 300 card on the 1st PCI slot)
> > >
> > > However, they don't work together. Examples: (KMV = Keyboard/Mouse/Video):
> > >
> > > ========== Start seat0 first ===========
> > > X :0 -layout seat0 => result, the first KMV works
> > > X :1 -layout seat1 => result, the second KMV works, the first KMV shows a
> > > text cursor (an underline) on the upper-left corner of screen and hang
> > > there, the process 'X :0' doesn't quit.
> > >
> > > ========== Start seat1 first ===========
> > > X :0 -layout seat1 => result, the second KMV works
> > > X :1 -layout seat0 => result, the first KMV works, the second KMV shows a
> > > irregular white band on the middle of the screen, taking up 1/3 of the
> > > screen heigh and fill the width, and keep flashing
> > >
> > > So, is this a novell bug too? (that way I go report it) This time I was
> > > using SuSE 10.0 and Xorg 6.8.2. I am happy to do an upgrade if that can
> > > solve the problem.
> >
> > I don't think so. I never tried any multiseat setup, but IIRC you need
> > at least the "-sharevts" Xserver option.
> >
> > Best regards,
> > Stefan
>
> Thank you for your help again. I forgot to mension I tried -sharevts but I
> removed it because -sharevts creates this error:
>
> Fatal server error:
> Unrecognized option: -sharevts
>
> This error happen on both SuSE 10.0 and SuSE 10.1. I also think perhaps
> -noswitchvts is important but that creates the same error too:
>
> Fatal server error:
> Unrecognized option: -noswitchvts

I just realized -novtswitch and -sharevts are new options added for Xorg
6.9/7.x

I tried this option on Xorg 6.8.2 on Ubuntu and it works, Ubuntu must have
6.8.2 patched.

For SuSE even 6.9.0 doesn't have this option. That's not surprising. I
always have the impression that when Ubuntu said it's version a.b.c actually
it is using a.b.c+1 because they get it patched, and for SuSE when they say
it is a.b.c actually it is using a.b.c-1 because they used PRE/RC version
(the story of SuSE 10.0 with OOO 2.0 is an example). I just find it
difficult to google out an xorg 7.0 RPM for SuSE 10.1 or SuSE 10.0