| 1 |
Sebastian Kromp wrote: |
| 2 |
> I´ve choosed this bug for beginning |
| 3 |
> http://bugs.gentoo.org/show_bug.cgi?id=205261 , and after searching the |
| 4 |
> web I´ve found this |
| 5 |
> http://linuxwacom.sourceforge.net/index.php/howto/inputdev , and I |
| 6 |
> think, that could solve the problem. But because I don´t want to do |
| 7 |
> something wrong, I want to ask first, what I exactly should do now, |
| 8 |
> cause it´s a little bit unclear for me. |
| 9 |
|
| 10 |
You've found a document detailing how to match up the kernel side driver |
| 11 |
part (wacom) with the userspace configuration for the tablet. |
| 12 |
|
| 13 |
The problem in this case is that the kernel driver is not recognizing |
| 14 |
the device, and hence is not creating the /dev/input/eventX interface |
| 15 |
that the document is talking about. So, the document is not entirely |
| 16 |
relevant because the problem occurs at a lower layer. |
| 17 |
|
| 18 |
The next thing to do on that bug is to research the issue. Try and find |
| 19 |
other Linux users who have the same hardware, and see whether they are |
| 20 |
reporting it as working or broken. If it appears broken for everyone, |
| 21 |
has it been reported to the wacom developers, perhaps on a mailing list? |
| 22 |
Are there any patches available? Google around a bit, and let us know |
| 23 |
what you find (if you're confident you can just put your findings |
| 24 |
directly on the bug). |
| 25 |
|
| 26 |
Also, you'll see that I asked for "lsusb -v" output. I asked for this |
| 27 |
because all USB devices have unique ID numbers (vendor and product ID) |
| 28 |
which can be useful when searching. In this case the vendor ID is 056a |
| 29 |
and the product ID is 0090 (see if you can find where I read those |
| 30 |
numbers from in his attachment). |
| 31 |
Just putting the phrase "056a 0090" into google seems to bring up some |
| 32 |
relevant results. |
| 33 |
|
| 34 |
Thanks, |
| 35 |
Daniel |
| 36 |
-- |
| 37 |
gentoo-kernel@l.g.o mailing list |
Archives