[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#595189: marked as done (xserver-xorg-input-all: no support for WALTOP tablets)

Your message dated Sat, 12 Feb 2011 13:37:43 +0100
with message-id <20110212123743.GZ21179@debian.org>
and subject line Re: Bug#595189: xserver-xorg-input-all: no support for WALTOP tablets
has caused the Debian Bug report #595189,
regarding xserver-xorg-input-all: no support for WALTOP tablets
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

595189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595189
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-input-all
Version: 1:7.5+6
Severity: normal

After xorg has switched to direct udev-based hardware detection instead of
using HAL, I've been unable to get my tablet working. I've been using patched
waltop driver and since I don't really understand the udev rules system, I
can't prevent evdev driver (which is not working) from taking it over.

Anyway, this doesn't change the fact, that WALTOP tablets don't work in Debian
without self-help and good knowledge about udev etc. (virtually every how-to
found on the web still refers to getting it working using HAL).

There are three possible ways, how to get it working:

1) Patched version of xserver-xorg-input-wacom driver with disabled vendor-ID
check. linuxacom driver was working well with WALTOP tablets until the vendor-
ID check blocked any devices other than Wacom.
More information for example at https://bugs.launchpad.net/ubuntu/+source/xf86

2) There are several reports in Ubuntu bug tracking system, that some people
succeeded by installing the wizardpen driver (now available from
https://launchpad.net/~doctormo/+archive/xorg-wizardpen, it was dead project
for several years).

3) Fixing the xserver-xorg-input-evdev driver.
At this moment, when I plug in the tablet (Genius G-pen F350), evdev is loaded
to handle it. It appears to be working at first, but as soon as I "click" at
the surface (or push any button at the pen) the cursor stops moving. It moves
only when i hold some button, the tip is in contact with the tablet, or if the
pen is taken out of range and back again.

By loading a evbug module I've found out, that even though the cursor doesn't
move anymore, the events are generated as usual, so the problem is most likely
somewhere in the xorg evdev driver, not in the kernel support.

( 4) there's also the official driver from Wacom, but it doesn't work with new
kernel and xorg and as far as I know, it's probably based on the linuxwacom

The best solution would be using the Wacom driver because it includes tools for
testing and setting some advanced options. The same goes for wizardpen, but one
can't be sure, if the development won't stop again...

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.36-rc3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---

H:S /he29 <he29.hs@gmail.com> (05/09/2010):
> I've tried to install latest git version of the driver as you
> suggested and it is working quite well (I was just surprised, that
> the x11 driver selection is based on
> /usr/share/X11/xorg.conf.d/50-wacom.conf, not on the udev rules;
> that's why evdev was always taking over the wacom driver :)) ).
> […]

AFAICT, there's no bug in -input-all, which pulls -input-wacom through
Recommends. If you have issues with that driver, please open a bug
against it with appropriate versioning information (due to the lack of
it here, I'm not reassigning this bug report to -input-wacom).


Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: