Re: XInput: Atmel maXTouch Digitizer touch screen

2011-12-26 Thread Ben Bucksch
On 22.12.2011 16:47, Chase Douglas wrote: If I had to guess, BTN_TOOL_FINGER is likely still getting in the way of things in the evdev driver. ... the maXTouch chips are handled by atmel_mx_ts in drivers/input/touchscreen/atmel_mx_ts.c. I now hacked this file in a very crude way, by removing

Re: How to get two monitors working in Linux?

2011-12-28 Thread Ben Bucksch
On 28.12.2011 03:34, monitorxxx wrote: Hi, I have Arch Linux in this system: -video card: nvidia 6150 -monitor 1: LG, 1440x900 (right side) -monitor 2: Samsung, 1360x760 (left side) -desktop environment: Lxde 1) no matter how hard I try, write to xorg.conf, set up and reboot, the monitors' posi

Re: XInput: Atmel maXTouch Digitizer touch screen

2012-01-06 Thread Ben Bucksch
On 03.01.2012 03:14, Chase Douglas wrote: On 12/26/2011 09:59 AM, Ben Bucksch wrote: I now hacked this file in a very crude way, by removing some of the finger code. Patch below. This has the effect that the random spurious clicks are gone, but I now need a double-tap ("double-click

Re: XInput: Atmel maXTouch Digitizer touch screen

2012-01-07 Thread Ben Bucksch
On 07.01.2012 08:04, Chase Douglas wrote: On 01/06/2012 10:57 AM, Ben Bucksch wrote: There is no mention of "BTN_TOOL_FINGER" anywhere in that file. If you want, you can post the entire source file for your driver. I'll try to point out what needs to be changed. http://gi

Re: XInput: Atmel maXTouch Digitizer touch screen

2012-01-07 Thread Ben Bucksch
On 07.01.2012 17:40, Chase Douglas wrote: Are you sure you are running that version of the driver? Did you change drivers since you posted your evtest log? The evtest log shows BTN_TOOL_FINGER being registered, but the upstream driver does not register it. The log I posted was from an older Lin

Re: Triple-head setup advice sought

2012-04-06 Thread Ben Bucksch
On 06.04.2012 12:23, Alan Cox wrote: I'm using a cheap Radeon (HD5430 I think). Does the job, runs three heads. Probably useless for high end gaming but that wasn't on my requirement list. Thanks, Alan, for the recommendation. But that's a notebook chip. Could you double-check the model number

X server crash due to evdev device - regression

2012-05-11 Thread Ben Bucksch
I've upgraded from Ubuntu 11.10 to 12.04, and the X server is now crashing. Log excerpt below. lsusb -vv attached. This happens (probably not surprisingly) with both the stock Linux 3.2 kernel as well as a self-compiled Linux 3.1 kernel. Log (end): [15.883] (II) config/udev: Adding input

Re: X server crash due to evdev device - regression

2012-05-11 Thread Ben Bucksch
Workaround (in case another victim happens to find this): Put the following in /etc/X11/xorg.conf.d/conexant.conf Section "InputClass" Identifier "Disable Conexant USB Audio due to crash" MatchProduct"Conexant USB Audio" Driver "none" EndSection

Re: X server crash due to evdev device - regression

2012-05-11 Thread Ben Bucksch
On 11.05.2012 20:36, Ben Bucksch wrote: I've upgraded from Ubuntu 11.10 to 12.04, and the X server is now crashing. Log excerpt below. lsusb -vv attached. Forgot to add: Obviously, that's not an input device. With Ubuntu 11.10, this was already in the Xorg log as event device (I

Re: X server crash due to evdev device - regression

2012-05-14 Thread Ben Bucksch
On 14.05.2012 08:01, Peter Hutterer wrote: Please try to reproduce with the stock 1.12 server and file a bug. Attach your evemu recording so I can try to reproduce this. Sorry, but I can't do anything that involves changing my Xserver on my production system, installing a separate OS, or compi