Re: evdev devices in xorg.conf
On Tue, May 03, 2011 at 07:47:24AM +0200, Zoltan Szecsei wrote: On 2011-05-03 07:32, Peter Hutterer wrote: On Sat, Apr 30, 2011 at 07:52:42PM +0200, Zoltan Szecsei wrote: Kubuntu 11.04 fresh install I'm trying to set up a 3-seat multiseat system but for now I have installed only 1 VGA card and want to get the correct xorg.conf contents before I add the other two seats. The system comes up OK, but after a minute or two, the desktop freezes. I'd be grateful if someone could pass comment on the attached xorg.conf and Xorg.0.log files. Thanks in advance, Zoltan -- [...] [11.444] (II) No input driver/identifier specified (ignoring) [ 221.625] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0xf7f7, 0x0004fe20) [ 222.235] [mi] EQ overflowing. The server is probably stuck in an infinite loop. looks like the nvidia driver is at fault here. note that this is not an evdev bug, evdev just exposes it because it tries to enqueue more input events but the server isn't processing them anymore. Cheers, Peter Hi All, I've got it to a stage where I get the KDM login screen with full mouse keyboard functionality. After I login, the mouse keyboard drops out before the desktop appears. Using ssh I get into the system and check Xorg.0.log, to find that the 'EE' error points to: (EE) PreInit returned 8 for Logitech USB Receiver that just means that the device didn't get added for some reason. Nothing that should affect the working of the server (other than that you obviously can't use this device). If you ssh in before, you'll probably notice that this line is already in the log while you're logging in. from your last backtrace, it's the graphics driver that hangs. Cheers, Peter I can include the dmesg, Xorg.0.log and xorg.conf files if anyone would like. BTW: In ubuntu 6.06 (2.6.15-29) with gdm, I used to have pci=nommconf and vmalloc=256M in the bootstring - I'm using default bootstrings for this install. Is this a problem? TIA, Zoltan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev devices in xorg.conf
On Mon, May 2, 2011 at 11:50 PM, Zoltan Szecsei zolt...@geograph.co.za wrote: On 2011-05-03 08:21, Peter Hutterer wrote: On Tue, May 03, 2011 at 07:47:24AM +0200, Zoltan Szecsei wrote: that just means that the device didn't get added for some reason. Nothing that should affect the working of the server (other than that you obviously can't use this device). If you ssh in before, you'll probably notice that this line is already in the log while you're logging in. from your last backtrace, it's the graphics driver that hangs. Hi Peter, Nope - I have had the machine on for a while this morning, and not logged in via the consoe. I've just dived in over ssh and extracted these files: [12.888] (II) Using input driver 'evdev' for 'Mousetop' [12.888] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [12.888] (**) Option CorePointer [12.888] (**) Mousetop: always reports core events [12.888] (EE) Mousetop: No device specified. [12.888] (EE) PreInit returned 2 for Mousetop As the log suggests, you're not specifying a device for Mousetop since it's commented out: Section InputDevice Identifier Mousetop #Driver mouse #OptionPhys usb-:00:1d.7-4.3/input1 Driver evdev OptionPhys pci-:00:1d.1-usb-0:2:1.1-event-mouse # Option Device /dev/input/event3 Option Protocol auto Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection On the one hand, you can fix it, but you'll probably get duplicate devices since the server is adding devices automatically. Here's your keyboard getting added: [12.977] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2) [12.977] (**) Logitech USB Receiver: Applying InputClass evdev keyboard catchall [12.977] (II) Using input driver 'evdev' for 'Logitech USB Receiver' [12.977] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so Unless you have a good reason to keep the static InputDevice sections, you may just want to comment them out and let the server add the devices as it finds them. If you find that you prefer to keep the static device configuration for one reason or another, I suggest adding Option AutoAddDevices false to your server flags. However, Peter's right that your freeze was caused by the nvidia driver. Fixing these PreInit errors won't change that situation. -- Dan ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
When was xrender 0.11 introduced?q
Hi, Does anybody remember which xorg-server version brought support for xrender 0.11? I think about not using some paths for render 0.11, however if its too recent I would probably exclude more xorg-server versions than required. Thanks, Clemens ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: When was xrender 0.11 introduced?q
On Tue, May 03, 2011 at 08:22:08PM +0200, Clemens Eisserer wrote: Hi, Does anybody remember which xorg-server version brought support for xrender 0.11? commit c65280ce8df4836bd7424a90482e8aa00ab6f447 Refs: xorg-server-1.8.99.904-16-gc65280c Cheers, Peter I think about not using some paths for render 0.11, however if its too recent I would probably exclude more xorg-server versions than required. Thanks, Clemens ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: evdev devices in xorg.conf
On Tue, May 3, 2011 at 17:30:06 +0200, Zoltan Szecsei wrote: I'm setting up 3 seat multiseat (I use it in my company) but getting things embedded down on 1 seat, then I will add the other two. I took Device setting out, and tried to use Phys instead, as I wondered if /dev/input/event3 would remain event 3 if evdev was wavering for some reason. No, you can't rely on these remaining stable. You might want to use the /dev/input/by-path/ symlinks instead, which (I think) won't change randomly. And either disable AutoAddDevices or set the GrabDevice option to avoid duplicated events. Cheers, Julien ___ xorg@lists.freedesktop.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
