Home » forums » Debian Help Forums: Users Helping Users » Hardware

graphics tablet

Tags:

hi

I borrowed a "Genius G-Pen 450" graphics tablet from a friend of mine, but I am having trouble getting it to behave as a tablet.

I cannot seem to get the wacom drivers to detect it, although I admit I have not tried very hard. It does not appear as a "supported device" on the linuxwacom website.

it is detected by the HID drivers, although these are fairly useless for a tablet - there is no pressure sensitivity, and it seems to use some warped absolute resolution:

example, if i move the pen to the top left corner of the tablet, the cursor will move to the top left corner of the screen. If i then move diagonally across the screen to the center of the tablet, the cursor will move diagonally across to the bottom of my screen .
if i continue to the bottom right corner, then i can use the bottom right quadrant of the tablet. It is like the resolution of the tablet is twice that of the screen.

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Propeller
  • Reddit
  • Magnoliacom
  • Newsvine
  • Furl
  • Google
  • Yahoo
  • Technorati
No votes yet
‹ No sound, and no error messages! minor problem with message about error activating XKB configuration when booting ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

graphics tablet

Submitted by pinniped on Fri, 2007-03-16 02:12.

At least you're getting messages - that's a start. You then need to find out what driver to report and set the options (X resolution, Y resolution, etc). I don't know if a "relative" mode is available or if the mapping from tablet to screen is 1:1 absolute.

Just to check that other things are working - the pen pressure, change of virtual pen type, switch to eraser, etc are all reported as 'events'. You can try something like:

less -f /dev/input/event0

then play with the pen and see how it responds. Try the same for other events (until you're told "no such device"). This will give you an idea what event channels are being used - you'll still have to figure out what they actually are and how to map them to your graphics software, but at least you'll know that everything is actually working.

»

graphics tablet

Submitted by jamei on Fri, 2007-03-16 08:10.

the pen is currently using the HID driver, which does not seem to have any of the advanced options like pressure.

this command worked better for me.
cat /dev/input/event1

even so, this just blurts out lines of garbage binary whenever the pen is near the tablet. nothing human-readable there. I can sort of see some patterns in the binary codes (just like John Nash in "A Beautiful Mind"), but they don't make any sense to me.

will the wacom driver (if it is appropriate) detect automatically, or is there some way to force the device to use it?

Cheers

»

graphics tablet

Submitted by jamei on Fri, 2007-03-16 08:24.

the pen is currently using the HID driver, which does not seem to have any of the advanced options like pressure.

this command worked better for me.
cat /dev/input/event1

even so, this just blurts out lines of garbage binary whenever the pen is near the tablet. nothing human-readable there. I can sort of see some patterns in the binary codes (just like John Nash in "A Beautiful Mind"), but they don't make any sense to me.

will the wacom driver (if it is appropriate) detect automatically, or is there some way to force the device to use it?

Cheers

»

graphics tablet

Submitted by pinniped on Fri, 2007-03-16 17:36.

Since events are being properly reported (at least some are), you can try to follow the instructions for setting up your X configuration file and see what success you have (although some operations such as setting operating parameters may fail unless the 'wacom.ko' driver is running).

What kernel are you running?
Run 'lsusb' to list your USB devices along with VendorID:ProductID - it is possible that your tablet has exactly the same controllers as some previous models and will work fine with the existing driver (with a few modifications to make the driver load).

»
Syndicate content