tablet kernel driver problem?

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

 



i suddenly realized yesterday that my aiptek HP-12000U tablet is
supported under FC3.  gads! i never would have guessed.

so i plugged it in and it sort of works.  but, not quite right.  the
cursor disappears frequently and it seems to move around randomly when i
start the pen on the tablet.  i'm trying to say that i can't judge WHERE
it's going to start it's stroke when i press the pen to the tablet.
this is all in gaim, BTW.

i looked at the log and i see these errors:

Dec 22 21:14:29 junior kernel: usb 1-2.4: new low speed USB device using
address 6
Dec 22 21:14:29 junior kernel: usbhid: probe of 1-2.4:1.0 failed with
error -5
Dec 22 21:14:31 junior hal.hotplug[22831]: DEVPATH is not set
Dec 22 21:14:31 junior kernel: drivers/usb/input/aiptek.c: input: Aiptek
on usb-0000:00:02.2-2.4 (event3)
Dec 22 21:14:31 junior kernel:
Dec 22 21:14:33 junior kernel: drivers/usb/input/aiptek.c: input: Aiptek
using 400 ms programming speed
Dec 22 21:14:33 junior kernel:
Dec 22 21:14:33 junior kernel: drivers/usb/input/aiptek.c: aiptek: error
loading 'evdev' module
Dec 22 21:14:33 junior kernel: usbcore: registered new driver aiptek
Dec 22 21:14:33 junior kernel: drivers/usb/input/aiptek.c: v1.5
(May-15-2004): Bryan W. Headley/Chris Atenasio
Dec 22 21:14:33 junior kernel: drivers/usb/input/aiptek.c: Aiptek
HyperPen USB Tablet Driver (Linux 2.6.x)

sure enough there is an evdev.h file, so i presume it's in the kernel:

/lib/modules/2.6.9-1.681_FC3/build/include/config/input/evdev.h

i get this with a lsusb, so i think that the hid probe fail might be
related:

[root@junior input]# lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro
500
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 08ca:0010 Aiptek International, Inc. Tablet
Bus 001 Device 004: ID 046d:c281 Logitech, Inc. WingMan Force
Bus 001 Device 003: ID 0409:0059 NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 0000:0000


i'm sort of at a loss as to how to approach this problem, and i'm not
quite sure what the log messages imply.

sure would appreciate your collective wisdom, my friends!

john




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux