Re: [Xorg] Local Multi Users

[Aivils <ai...@un...>]

On Saturday 26 June 2004 00:27, Alexandre wrote:
> > > Having to use an "order" is no good.  People on a multi-user
> > > machine logs in and out on the different consoles all the time, and X
> > > obviously restarts everytime. 
> > 
> > does X restarts really ? :-)
> > <snip from my gdm conf>
> > # If you are having trouble with using a single server for a long time and
> > # want gdm to kill/restart the server, turn this on
> > #AlwaysRestartServer=false
> > </snip>

I allways bypass restart of xf86. I use "AlwaysRestartServer=false"
So i keep "order". That is possible Nvidia driver issues.

> > > Gdm might be capable of starting the initial
> > > login sessions in the "right" order, but then two users logs in, the one
> > > with the card that must be loaded "first" then logs out and someone else
> > > logs in - restarting X on that card "last".
> > 
> > IIRC gdm follows the order in which the servers are specified 
> > in it's config file
> > on start : 1,2,3,.....
> > on shutdown : ...,3,2,1
> > 
> > IMO user logins/logouts doesn't metter 
> > 
> 
> As a matter of fact the logins/logouts do *NOT* matter. Once loaded they
> will reamin loaded untill the next reboot.
> 
> There is something really interesting here. When we log on with three
> monitors any user can logout and X won't shutdown (as we intended). 
> 
> However, with four monitors the order in gdm's session list is getting
> strange... 
> 
> Since this is not a simple problem I will try to simulate a little of
> what's going on here. Please try to understand this simulation:
> 
> => I try load gdm in an given order wich I configure in gdm.conf
>    (for example, let's imagine X0, X1, X2, X3 for our example).
> 
>    Now gdm is trying to bring X0 up.... SUCCESS!!
>    Now gdm is trying to bring X1 up.... SUCCESS!!
>    Now gdm is trying to bring X2 up.... FAILED.
>    But magically the X0 monitor _and_ X2 are frozen-up!!
>    Also X3 is not loaded, since we didn't get there.
> 
>    Now I do a "kill <gdm and his childs AND the X server>".
>    Now X0, X1, X2, X3 and the X server are dead.
> 
> => Now I edit my gdm.conf and try (X2, X0, X1, X3). Let's try it...
> 
>    Now gdm is trying to bring X2 up.... SUCCESS!!
>    Now gdm is trying to bring X0 up.... SUCCESS!!
>    Now gdm is trying to bring X1 up.... SUCCESS!!
>    Now gdm is trying to bring X3 up.... SUCCESS!!
>    Everything works now!! I am lucky!
>    Users may login and logout and everything works alright!!
> 
> => Now, I'm in heaven. I am kind of the hill... so now I am going to
> reboot and load everything again.

This suxcess story looks similar my.
Historical review.
TNT2(PCI) + TNT2(PCI)  all flawless , all xf86 are restartable.

GeForceMX440(AGP)+TNT2(PCI) + TNT2(PCI)
xf86 on AGP restart works nearly 90%

GeForceMX440(AGP)+GeForceFX5200(PCI) + TNT2(PCI)
system becames totaly capricious. restart of xf86 works nearly 50%.
nvidia.o wrote in dmesg

nvidia: rm_init_adapter() failed

That adpater will work only after reboot. Any kernel reinstall
make Nvidia driver unexcpected. I try various "order" "-probeonly"
and so on. All tests under 2.4.XX serie, nvidia driver versions
are forgotten. I just use latest nvidia closed source driver.
It works allways.

What does "X -probeonly"?

If You use -isolateDevice (-prefbusid), then xf86 can see only
one video adapter, which is allowed by Your commandline.
Some specific drivers (Nvidia) for good start must have
all adapters available, because have only one kernel module.
Kernel module may not do proper initialisation of all adapters,
if xf86 will not call all adapters, because some adapters are
hidden by commandline of xf86.
"X -probeonly" during initialisation call all adapters. Kernel
module keep all adapters in working state. Later restart of separate
xf86 will work nice.
This is my work hypothesis.

What does "order"?

%-( Truth is out of here

Aivils Stoss