Kernel Bug Tracker – Bug 3951
Wacom Intuos 3 tablet is missing on blacklist of hid-core.c
Last modified: 2005-08-18 21:41:30 UTC
Distribution: Fedore Core 3, but is independent.
Hardware Environment: AMD Athlon +2800
In the blacklist of hid-core.c of kernel 2.6.10 and previous, there are several
Wacom devices available. The Wacom Intuos 3 is missing.
When connecting the Wacom Intuos 3 with USB, it is recognized as an other
tablet, preventing the use of the Wacom driver, and not making all features
The Linux Wacom project on http://sourceforge.net/projects/linuxwacom/ has made
this device available in the hid-core.c and wacom.c modules but needs kernel
rebuild by the end user.
As there are already wacom.c and hid-core.c modules availble in the 2.6.10
kernel, it makes sence to add the latest once into the standard linux kernel.
Steps to reproduce:
Put the Wacom Intuos 3 into the USB connector. The /var/log/message shows:
Dec 27 09:56:28 localhost kernel: ohci_hcd 0000:00:02.0: wakeup
Dec 27 09:56:29 localhost kernel: usb 2-2: new full speed USB device using
Dec 27 09:56:34 localhost kernel: usb 2-2: control timeout on ep0in
Dec 27 09:56:39 localhost kernel: drivers/usb/input/hid-core.c: timeout
Dec 27 09:56:39 localhost kernel:
Dec 27 09:56:39 localhost hal.hotplug: DEVPATH is not set
Dec 27 09:56:39 localhost kernel: input,hiddev96: USB HID v1.00 Mouse [Tablet
PTZ-630] on usb-0000:00:02.0-2
Great, send a patch for the device then.
Also, the latest -mm releases have a wacom driver update in them, see if
that fixes the problem for you.
In hid-core.c the current blacklist is:
#define USB_VENDOR_ID_WACOM 0x056a
#define USB_DEVICE_ID_WACOM_PENPARTNER 0x0000
#define USB_DEVICE_ID_WACOM_GRAPHIRE 0x0010
#define USB_DEVICE_ID_WACOM_INTUOS 0x0020
#define USB_DEVICE_ID_WACOM_PL 0x0030
#define USB_DEVICE_ID_WACOM_INTUOS2 0x0040
#define USB_DEVICE_ID_WACOM_VOLITO 0x0060
It should be extended with the INTUOS3
#define USB_DEVICE_ID_WACOM_INTUOS3 0x00B0
Just a new wacom driver file, as it exists in the -mm patch is not sufficient.
This is fixed now.