056a:0319 Wacom Bamboo Pad is not communicating with system

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1265714

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

I created a patch and built a test kernel using the mainline tree. Can you test the kernel found at the following link and see if it resolves this bug:

http://kernel.ubuntu.com/~jsalisbury/lp1265714/

-Please, with what packages/drivers would I use your edited kernel?
-What kernet files I would install? I'm sorry, Im not expert user. Im web-developer and graphic designer, but this is high level for me.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I was installed an edited kernel, but not change. My Bamboo wireless Pad still not working.

Can you run the following commands while running the test kernel:

dmesg
lspci -vvvnn
lsusb

And attach the output.

Or you could just run the apport-collect command while booted in the test kernel:

apport-collect 1265714

Okey, here is LSUSB:
Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 056a:0319 Wacom Co., Ltd
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
------------------------------------------
lspci -vvvnn:
00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a83] (rev b1)
 Subsystem: NVIDIA Corporation Device [10de:cb79]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0

00:00.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a88] (rev b1)
 Subsystem: NVIDIA Corporation Device [10de:cb79]
 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0

00:03.0 ISA bridge [0601]: NVIDIA Corporation MCP79 LPC Bridge [10de:0aae] (rev b3)
 Subsystem: ASUSTeK Computer Inc. Device [1043:1cf7]
 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Region 0: I/O ports at 4f00 [size=256]

00:03.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0aa4] (rev b1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:1cf7]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:03.2 SMBus [0c05]: NVIDIA Corporation MCP79 SMBus [10de:0aa2] (rev b1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:1cf7]
 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 14
 Region 0: I/O ports at 4900 [size=64]
 Region 4: I/O ports at 4d00 [size=64]
 Region 5: I/O ports at 4e00 [size=64]
 Capabilities: <access denied>
 Kernel driver in use: nForce2_smbus

00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a89] (rev b1)
 Subsystem: NVIDIA Corporation Device [10de:cb79]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:03.5 Co-processor [0b40]: NVIDIA Corporation MCP79 Co-processor [10de:0aa3] (rev b1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:1cf7]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin B routed to IRQ 21
 Region 0: Memory at fae80000 (32-bit, non-prefetchable) [size=512K]
 Kernel driver ...

Now the edited kernel was broken my laptop. I was must use older kernel 3.11.0-15-generic, but i found this: http://sourceforge.net/mailarchive/forum.php?thread_name=CAMTzk84L8CbQTtBLyAhj0-qOMEz%3DKS5tueRtRk-E1N1m%2BgMY4w%40mail.gmail.com&forum_name=linuxwacom-discuss

Is there some option, when you will edit 3.11 kernel?

I was tried to edited my kernel hidcore.c by the instructions, but i wasn't found that file.

Yes! I was tried to install new kernel again, and now it works!
I'm going to run apport collect now

Apport said me: "there is not new informations to collect"
what now?

Just to confirm, the test kernel I posted in comment #2 does in fact fix this bug and allow the Bamboo pad to work correctly?

I was must completely reinstall system. So, I was install Ubuntu 13.10, then i was install your edited kernel and then I was reboot my laptop. My Wacom bamboo pad still not working. Will I must install some another wacom driver? I'm was install your edited kernel to clear system installation.

Which kernel were you using when the Bamboo pad worked in comment #21?

I'm sorry, "your Kernel begin works on my laptop", Bamboo Pad never worked on my laptop. Only on brothers PC with Windows.

Can you run the following after booting with my test kernel:

uname -a

Also, capturing a full dmesg would help. You can redirect the output to a file with:

sudo dmesg > dmesg.out

Then attach the dmesg.out file.

psenik@psenik-K50IN:~$ uname -a
Linux psenik-K50IN 3.13.0-031300rc6-generic #201401031203 SMP Fri Jan 3 17:05:58 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Dmesg is in attachment.

Can you test the new kernel posted at:

http://kernel.ubuntu.com/~jsalisbury/lp1265714/

The kernel name is:
linux-image-3.13.0-1-generic_3.13.0-1.16~lp1265714v1_amd64.deb
and
linux-image-extra-3.13.0-1-generic_3.13.0-1.16~lp1265714v1_amd64.deb

Please install both of those .deb packages and reboot.

I'm followed your instructions, but tablet still not working:

psenik@psenik-K50IN:~$ uname -a
Linux psenik-K50IN 3.13.0-1-generic #16~lp1265714v1 SMP Thu Jan 9 19:30:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I built one more test kernel, but this time using the linux-next tree and adding the 0x0319 device id. Can you give this kernel a test to see if it resolves the bug:

http://kernel.ubuntu.com/~jsalisbury/lp1265714/

So, new kernel is installed, but still nothink. When im booting up system on kernel RC7, system starting services and out of classic services, it writing this:
[ 4.105692 ] unable to find transceiver
[ 4.119005 ] unable to find transceiver
and after this is starting classic services like CUPS, Apache etc...

Hi, i was compiled my first own kernel after minimally a million (I'm absolute n00b for thinks like this) attempts I compile it good.
I'm attaching a link to kernel 3.11.0-15 for Saucy Salamander with solution for Wacom Bamboo Pad "wireless".

You can download complete kernel here:
http://www.edisk.cz/stahni/21506/linux-headers-3.11.0-15_3.11.0-15.23_all.deb_12.13MB.html
http://www.edisk.cz/stahni/85780/linux-headers-3.11.0-15-generic_3.11.0-15.23_amd64.deb_1.1MB.html
http://www.edisk.cz/stahni/65837/linux-image-3.11.0-15-generic_3.11.0-15.23_amd64.deb_14.03MB.html
http://www.edisk.cz/stahni/62777/linux-tools-3.11.0-15-generic_3.11.0-15.23_amd64.deb_95.53KB.html
http://www.edisk.cz/stahni/14816/linux-image-extra-3.11.0-15-generic_3.11.0-15.23_amd64.deb_32.26MB.html

It doesn't appear that this specific device has been implemented in the kernel yet. The last test kernel, I tried to reuse the code for the INTUOS4 device. I built another test kernel, using the GRAPHIRE code and the linux-next tree.

Can you give this kernel a test to see if it resolves the bug:

http://kernel.ubuntu.com/~jsalisbury/lp1265714/

If that kernel does not work, we will have to wait until a proper implementation comes from upstream.

I'm sorry, but Bamboo Pad still not working.
It's working only with my "hard" edited kernel.

Can you clarify what you mean by "Hard" edited kernel? Do you have a patch that allows the Bamboo pad to work in Saucy? If so, can you attach it or the details to this bug?

The device 056a:0319 is the wireless version of 056a:0318, just an RF dongle that replaces the USB cable.

Just got one now and tried it, doesn't do anything:
uname -a: Linux <hostname> 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux
dmesg:
usb 4-1: new full-speed USB device number 6 using uhci_hcd
usb 4-1: New USB device found, idVendor=056a, idProduct=0319
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-1: Product: Bamboo Pad, wireless
usb 4-1: Manufacturer: Wacom Co.,Ltd.

Some people got it partially working, at least with the pen but not the (multi-)touch part:
http://article.gmane.org/gmane.linux.drivers.wacom/6945/match=

The previous threads mentioned in that message are these:
http://thread.gmane.org/gmane.linux.drivers.wacom/6853
http://thread.gmane.org/gmane.linux.drivers.wacom/6930

The second thread has the details of the communication between the tablet and the driver.
Essentially, what that person did is use it with hid-core, but the proper Wacom driver doesn't work yet.
From the last message of the second thread:
> Bamboo Pad and other recent Wacom tablets seem to both default to USB
> HID's Boot Protocol. That means they emulate a simple mouse so they
> can be used in your BIOS menus before real drivers can be loaded.
>
> For normal HID devices, there is a Set Protocol request to change from
> Boot protocol to None Protocol and then the device begins to work like
> their HID Report describes. I'm 99% sure thats what Linux HID driver
> sent to get your tablet working.
>
> HID devices also have a Set Feature request where you can change
> behavior of HW. Thats what the above 0202 is doing. For Wacom
> devices, that command both sets a HW feature *and* turn the Protocol
> from Boot to None in single call.

Got it perfectly running, now someone can help to get it fixed for all by default. So the steps are:
1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline(/etc/default/grub). Now the tablet is already working with wacom driver but automatically assigned wacom driver doesn't support touchpad and it's keyboard part

2. I have added to 50-wacom.conf (/usr/share/X11/xorg.conf.d/) the line
        MatchIsTablet "on"
in the first section after
 MatchProduct "Wacom|WACOM|Hanwang|PTK-540WL|ISD-V4"
This way "evdev" works for keyboard and pad parts of the device and "wacom" only for tablet

Everything works, including three-finger swipes(which are sent by keyboard driver as Alt-Left, Alt-Right, Super etc) and pressure sensitivity of pen!
There must be a better way to match Bamboo Pad without breaking the generic wacom file but I have no experience of doing that, still I will try later if no one else does it faster.
For the wired edition replace 0x0319 with 0x0318 in the grub cmdline
Hooray :)

Oh, and I'm on Trusty 14.04

Thank you for your effort. Works perfectly on Kubuntu 14.10, 3.16.0-24-generic x86_64.

Now I can use these devices in our exhibition hal (Teknikens Hus, Science Center, Luleå, Sweden). Every exhibit cant use touchscreen so this will be a great option.

Some clarification (maybe) for us less hackish :)

1.
In console/terminal do:

sudo nano /etc/default/grub

Edit GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x056a:0x0319:0x40000000"
for wireless or
to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbhid.quirks=0x056a:0x0318:0x40000000"
for wired.

sudo update-grub

sudo nano /usr/share/X11/xorg.conf.d/50-wacom.conf

Add new line with
MatchIsTablet "on"
in the first section after
MatchProduct "Wacom|WACOM|Hanwang|PTK-540WL|ISD-V4"

Just found this on Ubuntu 14.04 - followed the steps above and can confirm it's now working for me (System Settings>Wacom tablet still says 'No tablet detected', but it works fine).

Thanks very much!

I just tried these steps, Ubuntu 14.04.1, no luck. However, I've got a Wacom Bamboo CTH-300 tablet - so I'm not sure if the fix is different.

@aeves-nate you probably need to tweak the change in the grub config to the id of the CTH-300. You'll probably find the id using lsusb or some of the other commands mentioned here.

I've followed the steps on debian 8 and it is now usable with the pen, but not as a touchpad. Unfortunately though it is far too sensitive sensing the pen even 3 cm over the surface.

On elementary OS freya.
Everything just works after following the steps.

First I have left out the 0x40000000 from the end of the grub line. Maybe that was happened to others too.

For the lazy ones:

sudo sed -i s/splash/splash\ usbhid.quirks=0x056a:0x0319:0x40000000/g /etc/default/grub
sudo sed -i s/ISD-V4\"/ISD-V4\"\\\n\\\tMatchIsTablet\ \"on\"/g /usr/share/X11/xorg.conf.d/50-wacom.conf
sudo update-grub
sudo reboot

;-)

Tried all methods provided above as well as the ones suggested by this post: http://askubuntu.com/questions/530205/how-to-get-bamboo-pad-working-on-ubuntu-14-04 to no avail, has anyone have any other suggestions, currently running gnome ubuntu 15.04 but have had the same issues on previous versions such as 14.04, thanks in advance!

Kubuntu 15.04 Kernel 4.0.0-040000-generic here with a wired Bamboo.

After the two recommended changes only stylus is working. No response from touchpad or buttons.