On 21/04/07, Greg Folkert <[EMAIL PROTECTED]> wrote:
Sent to Emmanuele and the list to make sure he sees it. On Thu, 2007-04-19 at 16:47 +0100, Emmanuele Massimi wrote: > Hi all, [snippage to reduce e-mail size] Okay, I found that the Linux Wacom stuff has a website. It appears Debian doesn't use the /dev/input/wacom but /dev/input/event[0-9] (event0, event1, event2, etc...) (I've looked for references to "wacom" case-insensitive throughout my machine) http://linuxwacom.sourceforge.net/index.php/main If that doesn't work, nothing will.
I just want to point out that wacom-tools creates the /dev/input/wacom device. It only appears after I plug in my pen tablet. Also, on that link I read: As of Nov. 15, 2006, both FC5 (kernel 2.6.18-1.2239.fc5) and FC6 (kernel 2.6.18-1.2849.fc6) work. Bad news: link Wacom device to /dev/input/wacom for kernel 2.6.18-1.2849.fc6is broken. Work around: Remove * NAME="input/%k", * from the contents of /etc/udev/rules.d/60-wacom.rules. (Thanks go to Johannes Fabian for reporting the solution). Do I have to do that? One things I found to help out Debian users was an old doc from there
http://linuxwacom.sourceforge.net/index.php/howto/debwcmdrv The only parts you really need to worry about is: Prepare for the /dev/input/wacom link In /etc/udev/rules.d/10-wacom.rules, add the following line: KERNEL="event*", SYSFS{idVendor}="056a", NAME="input/%k", SYMLINK="input/wacom%e" Thus the drivers will find the Wacom tablet, whatever its /dev/input/eventX address is. I would change that to: Prepare for the /dev/input/wacom link: Create a new file "/etc/udev/wacom.rules" put the following line in that file: KERNEL="event*", SYSFS{idVendor}="056a", NAME="input/%k", SYMLINK="input/wacom%e" Then in the directory "/etc/udev/rules.d" perform the following: ln -s ../wacom.rules 010_wacom.rules Thus the drivers will find the Wacom tablet, whatever the /dev/input/eventX attached is. I'd just setup your stuff accordingly to with the exceptions noted: http://linuxwacom.sourceforge.net/index.php/howto/x11 So, let us hope this works.
I will try this one in case the first workaround fails. Thanks a lot!
