Re: Local Multi-User X (?) problems

[Svetoslav S. <sv...@gm...>]

Hi again,

second try :-)


> I think I've been through all the pitfalls that one can possibly be 
> going into. Since I'm on Debian Sid, I've been bothering Andreas 
> Schuldei a lot. I'm using his great packages. 

do you use his kernel binaries ?
have you cmpiled the kernel yourself ?

do you have the kernel configuration file ?

IIRC he used to build all input drivers as modules,
but in your lsmod i see only the driver for usb controler
no mention of input driver modules 
 

> To do the short version first: Everything seems to work fine, except 
> that when I try to get KDM to launch the two X servers, the first 
> server comes up fine, but the second does not. Instead, the server 
> takes the whole CPU, but apparently does nothing. If I kill the second 
> X-server with -9, it comes back up and then it runs fine on the second 
> screen, but the first locks up and the first X server runs along. 
> There are tons of messages like:
> (EE) MGA(0): [dri] Idle timed out, resetting engine...
> in my logs afterwards.
> Now, for the details:
> 
> My system has a Matrox G450 DH and Mystique card. Since I'm now going 
> for a 2.4 kernel (I'll (re)turn to 2.6 later, for sure!), I'm not 
> trying to use the second head of the G450. Rather, I'm trying to use 
> the Mystique for the second user. 
> 
> I have a Logitech Keyboard on the normal PS/2 port, then a cheap 
> keyboard on the usual mouse PS/2 port. I have two mice connected on the 
> USB ports. I might want to change this setup later, but I don't want to 
> buy a USB keyboard. 
> 
> One of the things Svetoslav asks for at 
> http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/final_words.html is 
> contents of /proc/bus/input/devices, and since this sums up the setup 
> rather nice, I paste it here:
> I: Bus=0011 Vendor=0001 Product=0002 Version=ab02
> N: Name="AT Set 2 keyboard"
> P: Phys=isa0060/serio0/input0
> H: Handlers=kbd event0 
> B: EV=120003 
> B: KEY=4 2000000 8061f9 fbc9d621 efdfffdf ffefffff ffffffff fffffffe 
> B: LED=7 
> 
> I: Bus=0011 Vendor=0001 Product=0002 Version=ab83
> N: Name="AT Set 2 keyboard"
> P: Phys=isa0060/serio1/input0
> H: Handlers=kbd event1 
> B: EV=120003 
> B: KEY=4 2000000 8061f9 fbc9d621 efdfffdf ffefffff ffffffff fffffffe 
> B: LED=7 
> 
> I: Bus=0003 Vendor=046d Product=c00e Version=1110
> N: Name="Logitech USB-PS/2 Optical Mouse"
> P: Phys=usb-00:04.2-1/input0
> H: Handlers=mouse0 event2 
> B: EV=7 
> B: KEY=70000 0 0 0 0 0 0 0 0 
> B: REL=103 
> 
> I: Bus=0003 Vendor=09da Product=0006 Version=0001
> N: Name="A4Tech USB Optical Mouse"
> P: Phys=usb-00:04.2-2/input0
> H: Handlers=mouse1 event3 
> B: EV=7 
> B: KEY=7f0000 0 0 0 0 0 0 0 0 
> B: REL=103 
> 
> BTW, /proc/bus/usb/devices does not exist on my system, 

this is somewhat strange
you must have it 

/proc/bus/input/devices llocks perfectly OK
do you have in /dev/input/ 
mouse0, mouse1, event0  to event3 ?

>and 
> cat /proc/bus/console/*/* says 
> isa0060/serio0/input0
> isa0060/serio1/input0
> 
> This looks good, doesn't it?

it does :-)
> 
> (I'll paste in just the things that I assume is relevant, the rest I'll 
> attach. Hope that's OK. XFree86.[12].logs I had to trim, this mail is 
> large enough as it is.) 
> 
> I've configured Xinerama, and it works fine. I have preferred keeping 
> the whole X config in a single file, so I take the approach with 
> specifying different "layouts". I maintain four different layouts, 
> "Simple", "Xinerama", "X0" and "X1". The two latter are the ones for 
> the multi-user config.
> 
> They look like this:
> Section "ServerLayout"
>         Identifier     "X0"
>         Screen      0  "Screen0" 0 0
>         InputDevice    "Mouse0" "CorePointer"
>         InputDevice    "Keyboard0" "CoreKeyboard"
>         Option "PrefBusID" "1:5:0"
> EndSection
> Section "ServerLayout"
>         Identifier     "X1"
>         Screen      0  "Screen1" 0 0
>         InputDevice    "Mouse1" "CorePointer"
>         InputDevice    "Keyboard1" "CoreKeyboard"
>         Option "PrefBusID" "0:11:0"
> EndSection
> 
> 
> devfs is up and running, allthough there are some weird issues; 
> specifically mount doesn't report that devfs is mounted, whereas 
> /proc/mounts does. This put me off for a long time. 

smth debian specific ?
have you installed devfsd ?

does your bootloader line contains " devfs=mount",
or if you have compiled your kernel have you enabled 
automatic mounting of devfs ? 

> It is easy enough to get X running on either screen with corresponding 
> keyboard and mouse. Also, I have been able to run it on both, 
> simultaneously, running 
> startx -- /usr/X11R6/bin/X1 :1 -layout X1 vt8 & startx -- /usr/X11R6/
> bin/X0 :0 -layout X0 vt7
> I could type on both keyboards, it showed on their respective screens. 
> Mice worked. 
> 
> So far, so good, it seems, but then I tried to get KDM to start them for 
> me, by adding the following lines to /etc/kde3/kdm/Xservers:
> :0 local /usr/bin/nice -n -10 /usr/X11R6/bin/X0 :0 -layout X0 
> -deferglyphs 16 vt7
> :1 local /usr/bin/nice -n -9  /usr/X11R6/bin/X1 :1 -layout X1 vt9
> 

may be try adding here "-prefbusid x:xx:x" for each card,

another idea woud be to switch to gdm (cause it follows
the order of starting X servers as specified)
and try exchanging the start order
in your command line first is started X1 then X0,
with xdm/kdm you can never be sure which one will be started 
first, but with gdm it's up to you to specify the order

> Booting up, things go wrong. X comes slowly up, but only on one screen.
> Upon inspection, it is clear why it is so slow, because the X1 process 
> runs at 99% of the CPU according to top. Other than that, things are 
> normal on the display that is running, but obviously, the idea was to 
> have both... :-) 
> 
> In syslog, I find things like this:
> Oct 29 16:04:15 owl kdm[720]: Hung in XOpenDisplay(:1), aborting
> Oct 29 16:04:15 owl kdm[720]: server open failed for :1, giving up
> Oct 29 16:04:15 owl kdm[686]: Display :1 cannot be opened
> 
> 
> I didn't really have much of an idea on where to start, but I noticed 
> two things. One thing was that in kdm.log, I found lines:
> (EE) MGA(0): Need at least 4608 kB video memory at this resolution, bit 
> depth

i think i've got smth similar when i found out that DRI is not supported on
multiple graphic cards
(IIRC primary G550 , secondary SiS6326 but i think both X servers started
the second without DRI of course)

> (My G450 has 16MB, I don't know what the Mystique has). So, I tried 
> setting the bit depth to 8 and the resolution for both cards to 
> 800x600. That didn't help, and besides, I run Xinerama at 16 bpp and 
> 1280x960 and 1024x768 respectively, so that shouldn't suddenly be a 
> problem, I figured. Turned it back up. 
> 
> Then, I was in doubt whether I had entered the PCI bus id's correctly. 
> The autoconfig I ran when making the Xinerama config had them in the 
> form PCI:0:11:0, but in the examples, the PrefBusID strings did not 
> have the PCI:-prefix. I had left it like that initially, as it seems to 
> be that way in the examples. However, I see lines like
> (WW) MGA: No matching Device section for instance (BusID PCI:1:5:0) 
> found
> (WW) MGA: No matching Device section for instance (BusID PCI:0:11:0) 
> found

this probably just information,
that the driver found additional device which is not specified in the
current
layout 

waiting for more info,

svetljo

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++