Xdmx -input device problem
Hello list, since a couple of weeks I've been trying to get Xdmx working correctly. Almost everything works fine, but I recognize a strange behaviour regarding the input devices, especially my mouse: I'm not able to move the cursor through all areas of the desktop. The accessible area is limited to the upper left display and the one above it. I could notice that on two different setups: 1. I'm using my laptop to connect to a PC with 4 monitors, so I'm able to move the cursor to access elements on monitors 1 and 2. +++ | 1| 3| +++ | 2| 4| +++ 2. I'm using my laptop to connect to a PC with 6 monitors, still the same behaviour. The cursor can only be moved through the parts of the desktop displayed in monitor 1 and 2. +++ | 1| 4| +++ | 2| 5| +++ | 3| 6| +++ My intention was that Xdmx is choosing the wrong mouse driver, so I tried the command line option -input, but either I misunderstood Xdmx's manpage or sth. in Xdmx's code is broken, since Xdmx dosen't accept this and all I get is: "(Fatal Error) dmx: Unknown input argument: ps2" (using: startx -- /usr/X11R7/bin/Xdmx :1 -configfile /home/leif/doc/xsite/xdmx.conf -config keller -input kbd,ps2) I've tried to connect via another Pc than my laptop and Xdmx works fine there - without these mouse problems. I'm using Xdmx from xorg-server-1.4.0.90. Thanks, Leif ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Mon, Dec 15, 2008 at 02:26:28PM +, Tony Houghton wrote: > I thought I could prevent it by configuriong HAL to remove the > properties that say it's a keyboard though, but I failed. The Linux input layer will deliver the events to /dev/console unless the device is grabbed (which will disable just that device) or the console is put in raw mode (which will disable all devices). When you're using the kbd driver, the kernel is actually delivering a multiplexed stream of all keyboard-type devices. By removing the entries from hal you're preventing evdev from automatically picking up that device, but not doing anything to prevent them being delivered through the console device. THe kernel pays no attention to any information from hal. -- Matthew Garrett | mj...@srcf.ucam.org ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Mon, 15 Dec 2008 13:26:57 +1000 Peter Hutterer wrote: > On Sun, Dec 14, 2008 at 10:25:29PM +, Tony Houghton wrote: > > > On Sat, Dec 13, 2008 at 07:51:50PM +, Tony Houghton wrote: > > > > I've got a DVB card (saa7146 chip) with a remote control which appears > > > > as a Linux input device. The trouble is certain keys which correspond to > > > > keys on an ordinary keyboard also appear on /dev/console when pressed, > > > > which I don't want. > > > > > > try upgrading to xserver 1.5.2. > > > > This is happening even on the console though, not just in X. > > well, if it pretends to be a keyboard then it's only natural that the keys end > up on the console. The only way to get around that is to grab the event device > (google for EVIOCGRAB). I thought I could prevent it by configuriong HAL to remove the properties that say it's a keyboard though, but I failed. > > The trouble is X would probably crash or whatever it's doing before I > > got to see the result of evtest, although I suppose I could run it > > in a console or over ssh with DISPLAY set. > > evtest is a console program. Oh, it logs console events, not X events? -- TH * http://www.realh.co.uk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Sun, Dec 14, 2008 at 10:25:29PM +, Tony Houghton wrote: > > On Sat, Dec 13, 2008 at 07:51:50PM +, Tony Houghton wrote: > > > I've got a DVB card (saa7146 chip) with a remote control which appears > > > as a Linux input device. The trouble is certain keys which correspond to > > > keys on an ordinary keyboard also appear on /dev/console when pressed, > > > which I don't want. > > > > try upgrading to xserver 1.5.2. > > This is happening even on the console though, not just in X. well, if it pretends to be a keyboard then it's only natural that the keys end up on the console. The only way to get around that is to grab the event device (google for EVIOCGRAB). > The trouble is X would probably crash or whatever it's doing before I > got to see the result of evtest, although I suppose I could run it > in a console or over ssh with DISPLAY set. evtest is a console program. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Sun, 2008-12-14 at 22:25 +, Tony Houghton wrote: > On Mon, 15 Dec 2008 08:01:07 +1000 > Peter Hutterer wrote: > > try upgrading to xserver 1.5.2. > > This is happening even on the console though, not just in X. > > I forgot to mention I'm using Debian (unstable), so unless it has > xserver 1.5.2 in "experimental" upgrading could take a lot of work. It's > currently based on 1.4.2. (2:1.4.2-9) with xorg in general being R7.3 > (1:7.3+18). > X.Org 7.4 is indeed staged in experimental, with xorg-server 1.5.3. Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Mon, 15 Dec 2008 08:01:07 +1000 Peter Hutterer wrote: > On Sat, Dec 13, 2008 at 07:51:50PM +, Tony Houghton wrote: > > I've got a DVB card (saa7146 chip) with a remote control which appears > > as a Linux input device. The trouble is certain keys which correspond to > > keys on an ordinary keyboard also appear on /dev/console when pressed, > > which I don't want. > > try upgrading to xserver 1.5.2. This is happening even on the console though, not just in X. I forgot to mention I'm using Debian (unstable), so unless it has xserver 1.5.2 in "experimental" upgrading could take a lot of work. It's currently based on 1.4.2. (2:1.4.2-9) with xorg in general being R7.3 (1:7.3+18). > > I thought I could stop this being a problem in X by changing my > > keyboard's "InputDevice" section to use the "evdev" driver with Option > > "Device" "/dev/input/event0" instead of the "keyboard" driver. It seemed > > to do the trick at first, but I soon discovered that with this setup > > pressing the "4" key on my remote would abruptly terminate my X session, > > as if I'd pressed Alt-Ctrl-Backspace, and there would be no explanation > > in /var/log/Xorg.0.log. Anywhere else I can look for clues? > > please run evtest against the device and check what key is actually emitted > when you press 4. That and the output of xkbcomp -xkb :0 - should give us a > hint. The trouble is X would probably crash or whatever it's doing before I got to see the result of evtest, although I suppose I could run it in a console or over ssh with DISPLAY set. Anyway, the problem's gone away. I tried making some HAL rules to remove the device's input.key* properties to see if that would stop /dev/console responding to it. It didn't, but I thought I might as well try X's evdev driver again and now I can safely press "4". If it isn't broken any more I guess I should stop trying to fix it even if I'm not sure what cured it. Thanks for your help anyway. -- TH * http://www.realh.co.uk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Input device problem
On Sat, Dec 13, 2008 at 07:51:50PM +, Tony Houghton wrote: > I've got a DVB card (saa7146 chip) with a remote control which appears > as a Linux input device. The trouble is certain keys which correspond to > keys on an ordinary keyboard also appear on /dev/console when pressed, > which I don't want. try upgrading to xserver 1.5.2. > I thought I could stop this being a problem in X by changing my > keyboard's "InputDevice" section to use the "evdev" driver with Option > "Device" "/dev/input/event0" instead of the "keyboard" driver. It seemed > to do the trick at first, but I soon discovered that with this setup > pressing the "4" key on my remote would abruptly terminate my X session, > as if I'd pressed Alt-Ctrl-Backspace, and there would be no explanation > in /var/log/Xorg.0.log. Anywhere else I can look for clues? please run evtest against the device and check what key is actually emitted when you press 4. That and the output of xkbcomp -xkb :0 - should give us a hint. Cheers, Peter ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Input device problem
I've got a DVB card (saa7146 chip) with a remote control which appears as a Linux input device. The trouble is certain keys which correspond to keys on an ordinary keyboard also appear on /dev/console when pressed, which I don't want. I thought I could stop this being a problem in X by changing my keyboard's "InputDevice" section to use the "evdev" driver with Option "Device" "/dev/input/event0" instead of the "keyboard" driver. It seemed to do the trick at first, but I soon discovered that with this setup pressing the "4" key on my remote would abruptly terminate my X session, as if I'd pressed Alt-Ctrl-Backspace, and there would be no explanation in /var/log/Xorg.0.log. Anywhere else I can look for clues? -- TH * http://www.realh.co.uk ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
