Wacom Graphire Bluetooth does not work (nothing listed in xsetwacom list)

Bug #483453 reported by Kirk Bridger
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
xf86-input-wacom (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: wacom-tools

Installing a fresh Karmic I am unable to get my Graphire Bluetooth tablet working. I installed wacom-tools and turned the tablet on. Reboots do not help.

syslog reports:
Nov 15 22:39:12 Creativity kernel: [ 305.477343] input: WACOM Pen Tablet as /devices/pci0000:00/0000:00:04.0/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input5
Nov 15 22:39:12 Creativity kernel: [ 305.477426] wacom 0005:056A:0081.0003: input,hidraw1: BLUETOOTH HID v1.00 Mouse [WACOM Pen Tablet] on 00:02:72:0F:5E:33
Nov 15 23:18:59 Creativity kernel: [ 2692.473714] wacom 0005:056A:0081.0004: parse failed
Nov 15 23:18:59 Creativity kernel: [ 2692.473724] wacom: probe of 0005:056A:0081.0004 failed with error -14
Nov 15 23:18:59 Creativity kernel: [ 2692.473743] wacom driver registered

I can see that a hid_wacom module loads, and I can pair with the tablet via Bluetooth without any problems. However the tablet is unresponsive to pen and mouse movement.

The community doc (https://help.ubuntu.com/community/WacomGraphireBluetooth) has not been updated with Karmic info - perhaps this won't work (I had it working in jaunty on the same hardware).

ProblemType: Bug
Architecture: amd64
Date: Sun Nov 15 23:21:44 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: BIOSTAR Group N68PA-M2T
NonfreeKernelModules: nvidia
Package: wacom-tools 1:0.8.4.1-0ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=14deceb2-1344-455e-896f-a5d6fe89d4d2 ro quiet splash
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: wacom-tools
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1853): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1853): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1952): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1992): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:1969): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
dmi.bios.date: 01/22/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: N68PA-M2T
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnBIOSTARGroup:pnN68PA-M2T:pvr5.0:rvnBIOSTARGroup:rnN68PA-M2T:rvr1.0:cvnBIOSTARGroup:ct3:cvr:
dmi.product.name: N68PA-M2T
dmi.product.version: 5.0
dmi.sys.vendor: BIOSTAR Group
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: BIOSTAR Group N68PA-M2T
Package: xf86-input-wacom (not installed)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid lucid
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/22/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: N68PA-M2T
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnBIOSTARGroup:pnN68PA-M2T:pvr5.0:rvnBIOSTARGroup:rnN68PA-M2T:rvr1.0:cvnBIOSTARGroup:ct3:cvr:
dmi.product.name: N68PA-M2T
dmi.product.version: 5.0
dmi.sys.vendor: BIOSTAR Group
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-21-generic

Revision history for this message
Kirk Bridger (kbridger) wrote :
Revision history for this message
Niels (niels-olson) wrote :

According to Mesilliac's post on the sourceforge project, [URL="http://sourceforge.net/tracker/?func=detail&aid=2781875&group_id=69596&atid=525126"]the bluetooth wacom has kernel support as of 2.6.31[/URL]. Kernelnewbies provides [URL="http://kernelnewbies.org/Linux_2_6_31"]a little amplification[/URL] and provides a [URL="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ca2dcd40f54c8928b3994712a6cadd2078a087fa"]link to the commit[/URL]. I have tried inserting the hid-wacom module, and touching the wacom pen to the tablet now seems to act like a mouse click, but that's all it does.

Revision history for this message
tommy (yobbobandana) wrote :

Hi, I'm not too sure why the kernel driver isn't working, but here's an updated version of the driver i was using in Jaunty which seems to work ok.

"make && sudo make install" to compile and install

Strangely it seems to break if I remove the part that renames the tablet from "WACOM Pen Tablet" to "Wacom Pen Tablet". Unfortunately I don't have much time right now to do more debugging :(.

Revision history for this message
Niels (niels-olson) wrote : Re: [Bug 483453] Re: Wacom Graphire Bluetooth does not work (nothing listed in xsetwacom list)

tommy, awesome! Pen moves and is in relative mode. Question: are you
getting pressure sensitivity also? I have pressure sensitivity in my
Intuos3, but not in my bluetooth tablet.

On Wed, Dec 9, 2009 at 5:59 AM, tommy <email address hidden> wrote:
> Hi, I'm not too sure why the kernel driver isn't working, but here's an
> updated version of the driver i was using in Jaunty which seems to work
> ok.
>
> "make && sudo make install" to compile and install
>
> Strangely it seems to break if I remove the part that renames the tablet
> from "WACOM Pen Tablet" to "Wacom Pen Tablet". Unfortunately I don't
> have much time right now to do more debugging :(.
>
>
> ** Attachment added: "hid-wacom-bt-2009-12-08.tar.gz"
>   http://launchpadlibrarian.net/36619391/hid-wacom-bt-2009-12-08.tar.gz
>
> --
> Wacom Graphire Bluetooth does not work (nothing listed in xsetwacom list)
> https://bugs.launchpad.net/bugs/483453
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
tommy (yobbobandana) wrote :

With that driver the tablet should have been fully functional, pressure and all... but I have a better solution now anyway.

It turns out there's a tweak to the bluez package that needs to be made to enable the new kernel driver to work. I've uploaded a modified package to my ppa at

https://launchpad.net/~yobbobandana/+archive/ppa

Could you try installing this and see if it works?
You should also uninstall the driver I uploaded previously with the command:

sudo aptitude reinstall linux-image-`uname -r`

(backticks important)
After this, the tablet should hotplug and work fully except perhaps for the two pad buttons. You might need to turn it off and on again once initially, due to an unrelated bug.

Revision history for this message
MvW (2nv2u) wrote :

Is your bluez fix included within the bluez project itself? I've installed blueman which installed version 4.61 of bluez and makes your ppa fix useless because it's much newer.

http://ubuntuforums.org/showthread.php?t=1401033

Revision history for this message
MvW (2nv2u) wrote :

Any progress on this issue? Still have a brand new tablet for more than a month now and still can't use it. :-S
Can anyone point me in the direction of fixing this issue myself?
So my question remains, what's the fix in bluez to make this thing working again?

Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Bryce Harrington (bryce) wrote :

Thank you for reporting this issue with wacom-tools, we are migrating it to the new xf86-input-wacom package which has replaced it in the development version of Ubuntu.

This would be a good point for you to re-test this issue against the new package to see if is still occurring. If not, you can mark it as Fix Released in Launchpad. If it is still an issue in the current development release and you're the original reporter, please reply and attach a fresh Xorg.0.log.

Changed in wacom-tools (Ubuntu):
status: New → Incomplete
affects: wacom-tools (Ubuntu) → xf86-input-wacom (Ubuntu)
Changed in xf86-input-wacom (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
MvW (2nv2u) wrote :

Well I suppose u mean lucid lynx (10.04) and if that's the case it's still broken.
It still results in the same behavior.

Bryce Harrington (bryce)
Changed in xf86-input-wacom (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Ben Tullis (tullis) wrote :

I am seeing a similar failure with my Graphire Bluetooth.

wacom 0005:056A:0081.0004: parse failed
wacom: probe of 0005:056A:0081.0004 failed with error -14
wacom driver registered

This is Ubuntu 10.4 on amd64.
I've got the PPA installed and the updated bluetooth packages.

I have removed blueman and reinstalled a stock kernel, to make sure that /lib/modules/2.6.32-22-generic/kernel/drivers/hid/hid-wacom.ko is original.

Bluetooth pairing works and the connection remains up, but no new devices appear in /dev/input/by-path/

I have got a /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi file in place, but I don't think that it's being used yet.

Any help to get it working would be appreciated.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Kirk,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 483453

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 483453 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/483453

Changed in xf86-input-wacom (Ubuntu):
status: Incomplete → New
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Kirk Bridger (kbridger) wrote :

I am writing this from a LiveCD of Lucid, with no additional PPAs installed or anything. I am running amd64.

The tablet still does not work. I am able to get it associated with relative ease (associating works, but syslog shows errors. Turning the tablet off then on again syslog shows no errors.)

I'll run the apport command.

Note that Ben in comment 10 had already tried this on Lucid, and in fact seems to have tried with some PPA software installed.

tags: added: apport-collected
description: updated
Revision history for this message
Kirk Bridger (kbridger) wrote : BootDmesg.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : GdmLog.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : Lspci.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : Lsusb.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : PciDisplay.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : ProcModules.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : UdevDb.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : UdevLog.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : XorgLog.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : Xrandr.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : setxkbmap.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : xdpyinfo.txt

apport information

Revision history for this message
Kirk Bridger (kbridger) wrote : xkbcomp.txt

apport information

tags: added: lucid
removed: needs-retested-on-lucid-by-june
Revision history for this message
MvW (2nv2u) wrote :

I've got i working now.
By using the PPA from this post.
It also includes the source for changing bluez accordingly.
It basically comes to tell the tablet to go in full functional mode.

http://ubuntuforums.org/showpost.php?p=9232133&postcount=134

Revision history for this message
MvW (2nv2u) wrote :

Any progress on including this fix?

Revision history for this message
Niels (niels-olson) wrote : rarely h--)

Hi, a very good business company, I suggest you go to see:
mobiles3gs.com, and now all of products enjoy great discount, saving
time and money. 6--)

Bryce Harrington (bryce)
Changed in xf86-input-wacom (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
MvW (2nv2u) wrote :

Everything seems fine in 12.04 (Except the buttons), there is some unrelated bug concerning this tablet, when the battery reports to be empty, the attached computer running Ubuntu will suspend as if it's laptop battery was empty.

Revision history for this message
MvW (2nv2u) wrote :

And it stopped again, just installed 12.04 from scratch (new HDD), completely updated it and now it doens't work anymore.
Does show up in xsetwacom list en xinput though.

Revision history for this message
MvW (2nv2u) wrote :
Download full text (6.7 KiB)

Seems to be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021069
I've got the same log entries, but do not experience any visual crash.

Jul 6 11:54:09 Laptop kernel: [ 51.018658] input: WACOM Pen Tablet as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.3/1-1.6.3:1.0/bluetooth/hci0/hci0:11/input17
Jul 6 11:54:09 Laptop kernel: [ 51.018841] wacom 0005:056A:0081.0005: input,hidraw1: BLUETOOTH HID v1.00 Mouse [WACOM Pen Tablet] on C4:46:19:E9:D5:A5
Jul 6 11:54:10 Laptop kernel: [ 51.708224] BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
Jul 6 11:54:10 Laptop kernel: [ 51.708228] IP: [<ffffffff811ee50c>] sysfs_do_create_link+0x3c/0x210
Jul 6 11:54:10 Laptop kernel: [ 51.708235] PGD 79dac7067 PUD 79daca067 PMD 0
Jul 6 11:54:10 Laptop kernel: [ 51.708238] Oops: 0000 [#1] SMP
Jul 6 11:54:10 Laptop kernel: [ 51.708240] CPU 0
Jul 6 11:54:10 Laptop kernel: [ 51.708241] Modules linked in: hid_wacom(+) hidp ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) bnep rfcomm parport_pc ppdev joydev vesafb btusb bluetooth nvidia(P) pcmcia snd_hda_codec_idt snd_hda_intel uvcvideo snd_hda_codec videodev snd_hwdep v4l2_compat_ioctl32 snd_pcm snd_seq_midi tifm_7xx1 lib80211_crypt_tkip snd_rawmidi snd_seq_midi_event snd_seq wl(P) tifm_core snd_timer snd_seq_device yenta_socket pcmcia_rsrc dell_laptop pcmcia_core i7core_edac psmouse dell_wmi dcdbas edac_core sparse_keymap serio_raw snd soundcore snd_page_alloc lib80211 video mac_hid wmi lp parport firewire_ohci sdhci_pci sdhci firewire_core crc_itu_t tg3 usbhid hid usb_storage
Jul 6 11:54:10 Laptop kernel: [ 51.708299]
Jul 6 11:54:10 Laptop udevd[745]: '/sbin/modprobe -bv hid:b0005v0000056Ap00000081' [2690] terminated by signal 9 (Killed)
Jul 6 11:54:10 Laptop kernel: [ 51.708301] Pid: 2690, comm: modprobe Tainted: P O 3.2.0-26-generic #41-Ubuntu Dell Inc. Precision M6500 /0R1203
Jul 6 11:54:10 Laptop kernel: [ 51.708304] RIP: 0010:[<ffffffff811ee50c>] [<ffffffff811ee50c>] sysfs_do_create_link+0x3c/0x210
Jul 6 11:54:10 Laptop kernel: [ 51.708307] RSP: 0018:ffff88079d9f1c38 EFLAGS: 00010202
Jul 6 11:54:10 Laptop kernel: [ 51.708308] RAX: 0000000000000002 RBX: ffffffff81a4d618 RCX: 0000000000000001
Jul 6 11:54:10 Laptop kernel: [ 51.708310] RDX: ffffffff81a4d618 RSI: ffff8807cb2df8b0 RDI: 0000000000000010
Jul 6 11:54:10 Laptop kernel: [ 51.708311] RBP: ffff88079d9f1c98 R08: ffff88079d9f0000 R09: 0000000000000001
Jul 6 11:54:10 Laptop kernel: [ 51.708313] R10: dead000000200200 R11: 0000000000000001 R12: ffff8807cadf7000
Jul 6 11:54:10 Laptop kernel: [ 51.708314] R13: ffff8807cb2df8a0 R14: ffff8807cb2df8b0 R15: 0000000000000001
Jul 6 11:54:10 Laptop kernel: [ 51.708316] FS: 00007f529931e700(0000) GS:ffff8807ffc00000(0000) knlGS:0000000000000000
Jul 6 11:54:10 Laptop kernel: [ 51.708317] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 6 11...

Read more...

To post a comment you must log in.