Giter Club home page Giter Club logo

input-wacom's Introduction

What is input-wacom?

The Linux Wacom Project manages the drivers, libraries, and documentation for configuring and running Wacom tablets under the Linux operating system. The project consist of this driver (input-wacom), xf86-input-wacom and libwacom. Our drivers are included in most major Linux distributions and provide out-of-the box support for a wide variety of Wacom tablets and component devices.

Given this, you will only need this driver if you have a newer Wacom device, are running an older operating system, or need a bugfix. If one of these situations applies to you, install input-wacom from source by following the instructions in our wiki.

Developers:

For developers and others needing additional information please see the wiki.

input-wacom's People

Contributors

aristeu avatar arvindyadavcs avatar axellin avatar bentiss avatar caihuoqing1990 avatar cbagwell avatar chggr avatar dcghub avatar dmlambea avatar dtor avatar elfring avatar flying-elephant avatar geertu avatar gregkh avatar grundlerchromium avatar gustavoarsilva avatar hadess avatar jigpu avatar joshua-dickens avatar kees avatar lyude avatar mmagnaudet avatar paulgortmaker avatar pinglinux avatar pyma1 avatar rikardfalkeborn avatar seesturm avatar skomra avatar tititiou36 avatar whot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

input-wacom's Issues

wacom_set_report: ran out of retries (EREMOTEIO)

I'm using the latest version of the driver (0.39.0) on a 4.15.15 kernel (Arch Linux) on my Lenovo Yoga 920. I'm getting the following message when I load the module:

[ 1042.530504] input: Wacom HID 5110 Pen as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM5110:00/0018:056A:5110.0001/input/input27
[ 1042.530863] input: Wacom HID 5110 Finger as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM5110:00/0018:056A:5110.0001/input/input28
[ 1042.531119] wacom 0018:056A:5110.0001: hidraw1: I2C HID v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
[ 1043.745527] i2c_hid i2c-WCOM5110:00: failed to set a report to device.
[ 1043.745543] wacom 0018:056A:5110.0001: wacom_set_report: ran out of retries (last error = -121)
[ 1043.745704] i2c_hid i2c-WCOM5110:00: failed to set a report to device.

-121 seems to be a EREMOTEIO error. However, the touchscreen works just fine. Any idea why this is happening?

P.S. This seems to be related:
https://patchwork.kernel.org/patch/10105647/

Wacom PTH-660 not starting on boot Centos 7.4

I'm seeing a strange issue with the newer tablets not working when plugged into a machine at boot. unplugging and plugging the tablet in when it's in the state does not start the tablet. Disconnecting the tablet and turning it off, then restarting the machine and connecting it when the machine has fully booted in the os causes it work as intended.

input wacom issues with intous4 wacoms on hardware vs vm

Hi guys,

We have some issues with the newest drivers. We use multiple wacoms, PTH-660(Pro 2), PTK-640 (Intuos4) and PTH-651(Intuso 5).The intuos 5 and Pro2 work fine with 0.37.1 release but the Intuos4 pen doesn't want to produce any input unless i manually remove the kernel module and reinsert it back using modprobe -r/i wacom.When i connect the tablet it gets detected by the kernel and the wacom module get loaded automatically. Even the kcmwacomtabled kde module will find it and display a message on the screen that's its been detected but the pen doesn't move and only the express buttons would work. I tested on a clean centos 7 latest install and its reproducible on large hardware range but not on a VM. If I test with a VM in virtual box there are no driver issues at all, Intuos4 would work properly every time.I also tried to downgrade a few versions and the only way I got to get the intuos4 tables was with 0.35.0 but then the the Pro 2 wacoms don't work anymore :(

Any help would be very much appreciated. 

Thanks!

wacom_set_report: ran out of retries (ETIMEDOUT)

When using the stylus after a brief period of inactivity there is a 30-60-second delay before input events register, with the message wacom_set_report: ran out of retries (last error = -110) in dmesg. Touch is unaffected and works fine. Occasionally, but not reliably, the driver stops recognizing the stylus at all (generally after several dozen messages).

I am opening a second issue because the errno is different from the one reported in #25. The behavior persists regardless of which client or desktop environment is in use. The bug persists when I build the driver from @jigpu's fix-issue-25 branch.

This is a Thinkpad Yoga 370 with up-to-date Fedora 28 running XFCE and kernel 4.16.8-300.fc28.x86_64. While the behavior exists in other kernel versions and distros, I'm reporting this from a Fedora installation in hopes it's easier for someone to reproduce the problem.

sysinfo output is attached. Please let me know what I can do to help.

BASH error script XUBUNTU 17.04?

mtcs@mccreary-HP-Compaq-dc7100-CMT-PC927A:~/Downloads/input-wacom-0.42.0$ $ if test -x ./autogen.sh; then ./autogen.sh; else ./configure; fi && make && sudo make install || echo "Build Failed"
bash: syntax error near unexpected token `then'
mtcs@mccreary-HP-Compaq-dc7100-CMT-PC927A:~/Downloads/input-wacom-0.42.0$ 

Build Failed

I cannot figure out why the build is failing, I have the correct kernel and headers. I cannot find a resource that says what config file the build is looking for or how to get it. Please help.

ben@archlabs ~/Downloads/input-wacom-0.41.0 % if test -x ./autogen.sh; then ./autogen.sh; else ./configure; fi && make && sudo make install || echo "Build Failed"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for kernel type... Linux
checking for linux-based kernel... yes
checking for kernel source/headers... not found
configure: WARNING: Unable to find build config in any of:
[/lib/modules/4.14.52-1-lts/source],
[/lib/modules/4.14.52-1-lts/build],
[/usr/src/linux],
[/usr/src/linux-4.14.52-1-lts],
[/usr/src/linux-2.6]

configure: WARNING: Kernel directory does not appear to have needed config files
checking kernel version...
configure: WARNING: Spcified '4.14.52-1-lts' kernel, but found '' instead
configure: error: We could not find the development environment to build modules for the '4.14.52-1-lts' kernel within the '' directory. Please install the kernel source or the kernel development package and try again.
Build Failed
ben@archlabs ~/Downloads/input-wacom-0.41.0 % uname -or
4.14.52-1-lts GNU/Linux
ben@archlabs ~/Downloads/input-wacom-0.41.0 %

Intuos BT S works via Bluetooth

I recently bought an Intuos BT S (CTL-4100WL) and connected to it via a Bluetooth 4.0 adapter. Pointing, buttons and pressure sensitivity worked for me. The „Device IDs“ wiki page states that it only works (or is tested?) via USB. Should that be added there?

Linux: 4.18.9
libwacom: 0.30
modinfo wacom yields version V2.00 and srcversion 52EA4FCCDDA2584FF8C195E
(xf86-input-wacom is not installed)

Intuos4 LEDs don't support luminance under 2.6.30

The luminance information is available (wacom->led.llv and wacom->led.hlv) but the luminance store function and sysfs code are missing. I don't see any reason it shouldn't be as simple as copy/paste.

One by Wacom medium doesn't work on Ubuntu 18.04

It was working before update, after xorg package was updated it wasn't working. I did rollback via Timeshift and disabled system updates, but now it's broken again. I tried to recompile input-wacom, but compilation was failed
config.log

Also, # modprobe wacom message is:
modprobe: ERROR: could not insert 'wacom': Exec format error

failed to link up the device via "Wireless Accessory Kit" - "unknown PID"

device: wacom cth-690 art
kernel: 3.10.0-862.14.4.el7.x86_64

system log as below:

Nov 10 07:01:34 localhost kernel: usb 4-2: new full-speed USB device number 2 using uhci_hcd
Nov 10 07:01:34 localhost kernel: usb 4-2: string descriptor 0 read error: -71
Nov 10 07:01:34 localhost kernel: usb 4-2: New USB device found, idVendor=056a, idProduct=0084
Nov 10 07:01:34 localhost kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 10 07:01:34 localhost kernel: usb 4-2: can't set config #1, error -71
Nov 10 07:01:34 localhost mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-2"
Nov 10 07:01:34 localhost mtp-probe: bus: 4, device: 2 was not an MTP device
Nov 10 07:01:34 localhost kernel: usb 4-2: USB disconnect, device number 2
Nov 10 07:01:38 localhost kernel: usb 4-2: new full-speed USB device number 3 using uhci_hcd
Nov 10 07:01:38 localhost kernel: usb 4-2: New USB device found, idVendor=056a, idProduct=0084
Nov 10 07:01:38 localhost kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 10 07:01:38 localhost kernel: usb 4-2: Product: Wacom Wireless Receiver
Nov 10 07:01:38 localhost kernel: usb 4-2: Manufacturer: Wacom Co.,Ltd.
Nov 10 07:01:38 localhost mtp-probe: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-2"
Nov 10 07:01:38 localhost mtp-probe: bus: 4, device: 3 was not an MTP device
Nov 10 07:02:02 localhost kernel: wacom 4-2:1.0: wireless tablet connected with PID 33e
Nov 10 07:02:02 localhost kernel: wacom 4-2:1.0: ignoring unknown PID.
Nov 10 07:02:02 localhost journal: g_array_unref: assertion 'array' failed

Intuos4 LEDs not properly handled

The LEDs on Intuos4 aren't initialized/destroyed for all models. Each version of the driver gets it wrong in a different way. Additionally, 2.6.30 and 2.6.36 don't appear to handle the resume and disconnect cases like 2.6.38 does.

HP Elite x2 1013 G3: i2c_hid errors on boot

Hello!

On HP Elite x2 1013 G3 I see error messages on related to loading driver for Wacom 4870 input device:

[    2.519741] i2c_hid i2c-WCOM4870:00: i2c-WCOM4870:00 supply vdd not found, using dummy regulator
[    2.519755] i2c_hid i2c-WCOM4870:00: Linked as a consumer to regulator.0
[    2.519757] i2c_hid i2c-WCOM4870:00: i2c-WCOM4870:00 supply vddl not found, using dummy regulator
[    2.860577] input: WCOM4870:00 056A:4870 Touchscreen as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input12
[    2.860937] input: WCOM4870:00 056A:4870 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input13
[    2.861120] input: WCOM4870:00 056A:4870 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input14
[    2.861437] input: WCOM4870:00 056A:4870 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input15
[    2.861636] input: WCOM4870:00 056A:4870 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input16
[    2.861717] hid-generic 0018:056A:4870.0001: input,hidraw0: I2C HID v1.00 Mouse [WCOM4870:00 056A:4870] on i2c-WCOM4870:00
[    3.149446] input: Wacom HID 4870 Pen as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input20
[    3.149837] input: Wacom HID 4870 Finger as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-WCOM4870:00/0018:056A:4870.0001/input/input21
[    3.150314] wacom 0018:056A:4870.0001: hidraw0: I2C HID v1.00 Mouse [WCOM4870:00 056A:4870] on i2c-WCOM4870:00
[    4.283793] i2c_hid i2c-WCOM4870:00: failed to set a report to device.
[    4.285058] i2c_hid i2c-WCOM4870:00: failed to set a report to device.

Sysinfo and complete dmesg is here: linuxwacom/wacom-hid-descriptors#42

Can't map wacom device.

When i use my wacom (Intuos CTL-6100WL) tablet on linux. It just maps to all of my screens.
The problem is, when i open the tablet settings, it says "no tablet detected".
xsetwacom --list devices return nothing.
xinput list:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:17                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:17            	id=7	[slave  pointer  (2)]
⎜   ↳ xwayland-stylus:17                      	id=9	[slave  pointer  (2)]
⎜   ↳ xwayland-eraser:17                      	id=10	[slave  pointer  (2)]
⎜   ↳ xwayland-cursor:17                      	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:17   

lsusb:

Bus 002 Device 003: ID 08bb:2902 Texas Instruments PCM2902 Audio Codec
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c07d Logitech, Inc. 
Bus 001 Device 003: ID 1532:0221 Razer USA, Ltd 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0781:5583 SanDisk Corp. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046d:0a66 Logitech, Inc. 
Bus 003 Device 002: ID 056a:0378 Wacom Co., Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I'm using ubuntu studio, with gnome-desktop.
If any other information is needed please tell me.
^^

hard cpu lockup on starting Wacom Intuos S 2

Imported from Sourceforge Bug #293


Trying first time to make an intuos s 2 work. It doesn't.

Tried under 4.4.0-rc2 (internal driver), 4.2.0 and wacom-input 0.30.1, xorg 1.17.3 and debian xorg-wacom 0.30.0.

4 clicky buttons seem to work.

As soon as I create any pen event the system locks up. Every time, both kernels. It turned out that one CPU core gets locked up hard, and once I was lucky to have the report generated on the other core:

kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 3 PID: 0 at /build/linux-CrHvZ_/linux-4.2.6/kernel/watchdog.c:311 watchdog_overflow_callback+0x84/0xb0()
kernel: Watchdog detected hard LOCKUP on cpu 3
kernel: Modules linked in:
kernel:  wacom(O) ipt_REJECT nf_reject_ipv4 xt_multiport nfnetlink_queue nfnetlink_log nfnetlink bluetooth rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace 
kernel:  mfd_core lm85 acpi_cpufreq video hwmon_vid button 8250_fintek processor shpchp mei_me mei xt_conntrack nf_conntrack thermal_sys nf_log_ipv4 nf_log_common eeprom i2c_i801 p
kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P           O    4.2.0-1-amd64 #1 Debian 4.2.6-1
kernel: Hardware name:                  /DH55HC, BIOS TCIBX10H.86A.0037.2010.0614.1712 06/14/2010
kernel:  0000000000000000 ffffffff817f4f50 ffffffff8154e2f6 ffff88043fc65b60
kernel:  ffffffff8106e5b1 ffff88042d19b800 0000000000000000 ffff88043fc65c40
kernel:  ffff88043fc65ef8 0000000000000000 ffffffff8106e62a ffffffff817f4f28
kernel: Call Trace:
kernel:  <NMI>  [<ffffffff8154e2f6>] ? dump_stack+0x40/0x50
kernel:  [<ffffffff8106e5b1>] ? warn_slowpath_common+0x81/0xb0
kernel:  [<ffffffff8106e62a>] ? warn_slowpath_fmt+0x4a/0x50
kernel:  [<ffffffff81108f64>] ? watchdog_overflow_callback+0x84/0xb0
kernel:  [<ffffffff811482a2>] ? __perf_event_overflow+0x82/0x1c0
kernel:  [<ffffffff81030ed4>] ? intel_pmu_handle_irq+0x1d4/0x440
kernel:  [<ffffffff81028055>] ? perf_event_nmi_handler+0x25/0x40
kernel:  [<ffffffff8101c814>] ? native_sched_clock+0x24/0x80
kernel:  [<ffffffff810176c2>] ? nmi_handle+0x82/0x110
kernel:  [<ffffffff81017c32>] ? default_do_nmi+0xc2/0x110
kernel:  [<ffffffff81017d5b>] ? do_nmi+0xdb/0x130
kernel:  [<ffffffff81555d11>] ? end_repeat_nmi+0x1a/0x1e
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  <<EOE>>  <IRQ>  [<ffffffff815537f2>] ? _raw_spin_lock_irqsave+0x32/0x40
kernel:  [<ffffffffa0112dd2>] ? usbhid_submit_report+0x32/0x3c0 [usbhid]
kernel:  [<ffffffffa15042d3>] ? wacom_intuos_irq+0x17c3/0x1eb0 [wacom]
kernel:  [<ffffffffa150560a>] ? wacom_wac_irq+0xaa/0x2380 [wacom]
kernel:  [<ffffffff81093f40>] ? check_preempt_curr+0x50/0x90
kernel:  [<ffffffff81093f94>] ? ttwu_do_wakeup+0x14/0xd0
kernel:  [<ffffffffa1508995>] ? wacom_raw_event+0x55/0xc0 [wacom]
kernel:  [<ffffffffa0204ded>] ? hid_input_report+0x14d/0x180 [hid]
kernel:  [<ffffffffa011332e>] ? hid_ctrl+0x14e/0x160 [usbhid]
kernel:  [<ffffffffa0067af2>] ? __usb_hcd_giveback_urb+0x82/0x130 [usbcore]
kernel:  [<ffffffffa00688ea>] ? usb_giveback_urb_bh+0x8a/0xd0 [usbcore]
kernel:  [<ffffffff81072216>] ? tasklet_action+0xe6/0xf0
kernel:  [<ffffffff8107258e>] ? __do_softirq+0xfe/0x250
kernel:  [<ffffffff81072852>] ? irq_exit+0x92/0xa0
kernel:  [<ffffffff815565ff>] ? do_IRQ+0x4f/0xd0
kernel:  [<ffffffff815545ab>] ? common_interrupt+0x6b/0x6b
kernel:  <EOI>  [<ffffffff8142aa05>] ? cpuidle_enter_state+0xe5/0x220
kernel:  [<ffffffff8142a9e3>] ? cpuidle_enter_state+0xc3/0x220
kernel:  [<ffffffff810aa146>] ? cpu_startup_entry+0x256/0x310
kernel:  [<ffffffff81047d78>] ? start_secondary+0x178/0x1a0
kernel: ---[ end trace f5e4dda74ca3a31e ]---
kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 3 PID: 0 at /build/linux-CrHvZ_/linux-4.2.6/kernel/watchdog.c:311 watchdog_overflow_callback+0x84/0xb0()
kernel: Watchdog detected hard LOCKUP on cpu 3
kernel: Modules linked in:
kernel:  wacom(O) ipt_REJECT nf_reject_ipv4 xt_multiport nfnetlink_queue nfnetlink_log nfnetlink bluetooth rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace 
kernel:  mfd_core lm85 acpi_cpufreq video hwmon_vid button 8250_fintek processor shpchp mei_me mei xt_conntrack nf_conntrack thermal_sys nf_log_ipv4 nf_log_common eeprom i2c_i801 p
kernel: CPU: 3 PID: 0 Comm: swapper/3 Tainted: P           O    4.2.0-1-amd64 #1 Debian 4.2.6-1
kernel: Hardware name:                  /DH55HC, BIOS TCIBX10H.86A.0037.2010.0614.1712 06/14/2010
kernel:  0000000000000000 ffffffff817f4f50 ffffffff8154e2f6 ffff88043fc65b60
kernel:  ffffffff8106e5b1 ffff88042d19b800 0000000000000000 ffff88043fc65c40
kernel:  ffff88043fc65ef8 0000000000000000 ffffffff8106e62a ffffffff817f4f28
kernel: Call Trace:
kernel:  <NMI>  [<ffffffff8154e2f6>] ? dump_stack+0x40/0x50
kernel:  [<ffffffff8106e5b1>] ? warn_slowpath_common+0x81/0xb0
kernel:  [<ffffffff8106e62a>] ? warn_slowpath_fmt+0x4a/0x50
kernel:  [<ffffffff81108f64>] ? watchdog_overflow_callback+0x84/0xb0
kernel:  [<ffffffff811482a2>] ? __perf_event_overflow+0x82/0x1c0
kernel:  [<ffffffff81030ed4>] ? intel_pmu_handle_irq+0x1d4/0x440
kernel:  [<ffffffff81028055>] ? perf_event_nmi_handler+0x25/0x40
kernel:  [<ffffffff8101c814>] ? native_sched_clock+0x24/0x80
kernel:  [<ffffffff810176c2>] ? nmi_handle+0x82/0x110
kernel:  [<ffffffff81017c32>] ? default_do_nmi+0xc2/0x110
kernel:  [<ffffffff81017d5b>] ? do_nmi+0xdb/0x130
kernel:  [<ffffffff81555d11>] ? end_repeat_nmi+0x1a/0x1e
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  [<ffffffff810aee34>] ? native_queued_spin_lock_slowpath+0x154/0x170
kernel:  <<EOE>>  <IRQ>  [<ffffffff815537f2>] ? _raw_spin_lock_irqsave+0x32/0x40
kernel:  [<ffffffffa0112dd2>] ? usbhid_submit_report+0x32/0x3c0 [usbhid]
kernel:  [<ffffffffa15042d3>] ? wacom_intuos_irq+0x17c3/0x1eb0 [wacom]
kernel:  [<ffffffffa150560a>] ? wacom_wac_irq+0xaa/0x2380 [wacom]
kernel:  [<ffffffff81093f40>] ? check_preempt_curr+0x50/0x90
kernel:  [<ffffffff81093f94>] ? ttwu_do_wakeup+0x14/0xd0
kernel:  [<ffffffffa1508995>] ? wacom_raw_event+0x55/0xc0 [wacom]
kernel:  [<ffffffffa0204ded>] ? hid_input_report+0x14d/0x180 [hid]
kernel:  [<ffffffffa011332e>] ? hid_ctrl+0x14e/0x160 [usbhid]
kernel:  [<ffffffffa0067af2>] ? __usb_hcd_giveback_urb+0x82/0x130 [usbcore]
kernel:  [<ffffffffa00688ea>] ? usb_giveback_urb_bh+0x8a/0xd0 [usbcore]
kernel:  [<ffffffff81072216>] ? tasklet_action+0xe6/0xf0
kernel:  [<ffffffff8107258e>] ? __do_softirq+0xfe/0x250
kernel:  [<ffffffff81072852>] ? irq_exit+0x92/0xa0
kernel:  [<ffffffff815565ff>] ? do_IRQ+0x4f/0xd0
kernel:  [<ffffffff815545ab>] ? common_interrupt+0x6b/0x6b
kernel:  <EOI>  [<ffffffff8142aa05>] ? cpuidle_enter_state+0xe5/0x220
kernel:  [<ffffffff8142a9e3>] ? cpuidle_enter_state+0xc3/0x220
kernel:  [<ffffffff810aa146>] ? cpu_startup_entry+0x256/0x310
kernel:  [<ffffffff81047d78>] ? start_secondary+0x178/0x1a0
kernel: ---[ end trace f5e4dda74ca3a31e ]---

'sticky' stylus, won't click or drag

I have installed the input-wacom and xf86-input-wacom drivers from both source and the repositories, however, my stylus would not click and not move when pressed down. I'm running Ubuntu 18.04.1 LTS. It has been this way since the beginning.

These are the files produced when I ran sysinfo.sh:
sysinfo.7oadtDMbOF.tar.gz

Any hints?

Jumpy cursor with Relative mode on CTH-670 and CTH-470

Hi. I am used to Relative mode with the tablet but starting from input-wacom-0.41.0 cursor jumps randomly. It looks like if Absolute and Relative modes would work at the same time. For solid behavior I am using input-wacom-0.40.0 for now. Please let me know if I can provide debug information or help somehow.

P.S. On any other wacom tablet without touch the issue does not appear with input-wacom-0.41.0 and later.

I can't change settings on my Wacom CTL-672

I couldn't change it with Manjaro's built-in GUI settings.

xsetwacom doesn't seem to recognize my tablet.

 $ xsetwacom --list devices
 $ 

xinput sees it as a generic mouse, because I can't change the mode of it to "absolute".

$ xinput --set-mode 9 ABSOLUTE
X Error of failed request:  XI_BadMode (invalid Mode parameter)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  5 (X_SetDeviceMode)
  Mode id in failed request: 0x17
  Serial number of failed request:  18
  Current serial number in output stream:  18

Wacom one medium no more recognized

Hello,
(Moved from libwacom where i posted it first by mistake)
My Wacom one medium tablet was not recognized on both of my computers under Ubuntu 16.04.
Although I'm not a developer and very afraid of doing mistakes, I tried to fix that by building the drivers from the sources you are providing because i can't wait any longer a built-in version in Ubuntu. Your explanations were very helpful for a non professional like me, thank you so much for that.
Unfortunately, on both computers, my tablet is still not recognized. BUT more than that, on my old Packard Bell EasyNote, it actually DID work for a while yesterday at night, just after the upgrading of the drivers, but it is not working anymore this morning. I've done nothing in the meantime, except to shutdown the computer.
I'm attaching the logs you asked for on another similar topic.
Regards
sysinfo.LKtj9xwr3T.tar.gz

How to remove input-wacom from Ubuntu 18.04?

I wanted to buy a wacom tablet and installed input-wacom driver to my Ubuntu 18.04
But then I changed my mind and don't want to buy it now.

I found that every time I use
sudo apt-get update
I get the following error from wacom driver.
Err:16 http://ppa.launchpad.net/doctormo/wacom-plus/ubuntu bionic Release 404 Not Found [IP: 91.189.95.83 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/doctormo/wacom-plus/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
Please tell me how to remove this driver. Do I just reverse the installation process? I am not sure I know how to do this, please help, thanks!

input-wacom does not compile on Linux 2.6.38

Imported from Sourceforge Bug #295


The current input-wacom-0.30.1 driver fails to compile for the Linux 2.6.38 kernel. This is because the code within the 2.6.38 folder makes use of the kstrtouint function that was introduced in Linux 2.6.39. It should be replaced with an equivalent such as strict_strtoul.

Wacom STU-530 not supported

[ 2632.678391] usb 3-1: new full-speed USB device number 5 using xhci_hcd
[ 2632.860539] usb 3-1: New USB device found, idVendor=056a, idProduct=00a5
[ 2632.860544] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2632.860548] usb 3-1: Product: STU-530
[ 2632.860551] usb 3-1: Manufacturer: Wacom Co.,Ltd.
[ 2632.860553] usb 3-1: SerialNumber: 7DZQ008370
[ 2632.949532] input input30: Absolute device without dev->absinfo, refusing to register
[ 2632.949560] wacom: probe of 0003:056A:00A5.0007 failed with error -22

how to update packages?

(I am not sure this is the correct place to post this question.)

I am running Ubuntu 17.10.

I have the Wacom Intuos tablet. At first it did not work. Then, following the instructions at https://linuxwacom.github.io/ , I installed the three packages. Now the tablet works great!

Here are my questions:

If there are updates to any of these packages, how will I know about them? And, what is the process to update them? Will the updates for these packages be part of the the update process that the Ubuntu OS on my computer always notifies me about?

Hope can drive Wacom DTI-520

From @SenlinOS on April 12, 2017 1:24

I have a Wacom DTI-520, the old LCD tablet.
Cannot drive in Ubuntu 16.04.

[   528.461] (II) config/udev: Adding input device WACOM DTI-520-U Pen (/dev/input/event7)
[   528.461] (  ) WACOM DTI-520-U Pen: Applying InputClass "Wacom USB device class"
[   528.461] (  ) WACOM DTI-520-U Pen: Applying InputClass "Wacom class"
[   528.461] (II) Using input driver 'wacom' for 'WACOM DTI-520-U Pen'
[   528.461] (  ) WACOM DTI-520-U Pen: always reports core events
[   528.461] (  ) Option "Device" "/dev/input/event7"
[   528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'stylus' for this device.
[   528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'eraser' for this device.
[   528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'cursor' for this device.
[   528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'touch' for this device.
[   528.528] (EE) WACOM DTI-520-U Pen: Invalid type 'pad' for this device.
[   528.528] (EE) WACOM DTI-520-U Pen: No type specified
[   528.560] (EE) PreInit returned 8 for "WACOM DTI-520-U Pen"
[   528.560] (II) UnloadModule: "wacom"

A device, actually has two ID.

$ lsusb
Bus 001 Device 010: ID 056a:003a Wacom Co., Ltd 
Bus 001 Device 009: ID 056a:003b Wacom Co., Ltd 

Thank you.

Copied from original issue: linuxwacom/xf86-input-wacom#7

are these directories needed?

(I am not sure this is the correct place to post this question.)

I am running Ubuntu 17.10.

I have the Wacom Intuos tablet. At first it did not work. Then, following the instructions at https://linuxwacom.github.io/ , I installed the three packages. Now the tablet works great!

Here is my question:

By following those instructions, I see that two directories were created in my "home" directory:

input-wacom-0.40.0 , and, libwacom

Do I need to keep those directories and their contents in order for the wacom packages to work?

Touch input disabled if a pen enters/leaves range without entering prox

Imported from Sourceforge Bug #300


The 2nd-generation consumer "Intuos" tablets (e.g Intuos Draw) don't seem to send an "out-of-prox" packet like earlier tablets (e.g. Intuos Pro) when its pen enters range and then immediately exits range without ever entering prox. This causes problems for wacom_intuos_inout which assumes that such a packet will be recieved to clear the stylus_in_proximity flag.

Bad LED string->int conversion

Upstream uses kstrtouint to translate the string passed in through sysfs. Backports prior to 2.6.38 instead use a hand-rolled algorithm which treats all characters as valid digits. Specifically, even doing something as simple as echo 1 > status_led0_select will not behave as expected since echo adds a newline (which is treated in as a digit in its own right).

Touch input behaves oddly with pen in range / disabled when leaving range

Imported from Sourceforge Bug #301


With an Intuos Pro, if a touch is present on the touchpad and a pen is brough into range the touchpad will continue to operate, albeit very slowly. Additionally, if the pen is then removed from range without entering prox, there is a chance that the touchpad will become disabled until the pen is brought fully into and out of prox.

This seems to be related to wacom_intuos_schedule_prox_event requesting the tablet to provide a tool ID while a tool is in-range. In some cases the tablet returns an out-of-prox packet in reply which causes stylus_in_proximity to be reset and allow touch_down to be re-asserted. After the out-of-prox response is recieved, however, the tablet sends another in-range packet, once again setting stylus_in_proximity. If touch_down is set before the tablet sends a final out-of-range packet, the if (wacom->shared->touch_down) check will cause us to return early without ever realizing it is an out-of-range packet and un-asserting stylus_in_proximity.

Note that I'm not 100% sure when "in some cases" is. Sometimes (e.g. without the changes introduced in "Fix deadlock on proximity in") will always send out-of-prox packets. Other times (e.g. with those changes in place) it instead seems to send in-range packets.

Version mismatch in dmesg and tablet not working?

Hi there,

My wacom one, stopped working this morning. After a little troubleshooting from my side and attempt to recompile/reinstall drivers, I get the following message when connecting it to my laptop.

[   42.627349] hid-generic 0003:045E:07A5.000D: input,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® Nano Transceiver v2.1] on usb-0000:00:14.0-2/input2
[   54.805701] usb 1-1: new full-speed USB device number 10 using xhci_hcd
[   54.957705] usb 1-1: New USB device found, idVendor=056a, idProduct=037a
[   54.957712] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   54.957717] usb 1-1: Product: CTL-472
[   54.957721] usb 1-1: Manufacturer: Wacom Co.,Ltd.
[   54.957725] usb 1-1: SerialNumber: 7HE00L1009789
[   55.010715] wacom: version magic '4.15.0-32-generic SMP mod_unload ' should be '4.15.0-33-generic SMP mod_unload '
[   55.010937] wacom: version magic '4.15.0-32-generic SMP mod_unload ' should be '4.15.0-33-generic SMP mod_unload '
[   55.011495] wacom: version magic '4.15.0-32-generic SMP mod_unload ' should be '4.15.0-33-generic SMP mod_unload '
[   55.011696] wacom: version magic '4.15.0-32-generic SMP mod_unload ' should be '4.15.0-33-generic SMP mod_unload '

I am working on ubuntu 18.04 LTS.

Any hint appreciated.

Thanks,
Peri

problem installing Wacom One Medium

Hello

I am pretty stuck with my tablet since several weeks already. I have been following the instructions from this Wiki (actually http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom, but the instructions seem to be the same), and at the end I get:

$ cat /sys/module/wacom*/version
v2.00-0.37.1

But the tablet pointer won't move, even after reboot. How can I fix it/troubleshoot it?

I have this tablet: https://www.amazon.de/gp/product/B076H8RVXR/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1.

My Ubuntu version:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial

But I have already tried 16.04 with new Kernel, 17.04 and 17.10, with the same result.

The full output:

monik@monik:~/Downloads/input-wacom-0.37.1$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for kernel type... Linux
checking for linux-based kernel... yes
checking for kernel source/headers... /lib/modules/4.4.0-104-generic/build
checking kernel version... 4.4.0-104-generic
checking RHEL7 minor release... 0

checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating 2.6.30/Makefile
config.status: creating 2.6.36/Makefile
config.status: creating 2.6.38/Makefile
config.status: creating 3.7/Makefile
config.status: creating 3.17/Makefile
config.status: creating 4.5/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure:
----------------------------------------
  BUILD ENVIRONMENT:
       linux kernel - yes 3.17
      kernel source - yes /lib/modules/4.4.0-104-generic/build

NOTE: The kernel drivers included in this package are only tested with the
X Wacom driver built from xf86-input-wacom. If you are running an X server
version older than 1.7, please use the drivers provided by the linuxwacom
package.

Please run 'make && make install'.
monik@monik:~/Downloads/input-wacom-0.37.1$ make
make  all-recursive
make[1]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1'
Making all in 3.17
make[2]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1/3.17'
    Building input-wacom drivers for 3.17 kernel.
make -C /lib/modules/4.4.0-104-generic/build M=/home/monik/Downloads/input-wacom-0.37.1/3.17
make[3]: Entering directory '/usr/src/linux-headers-4.4.0-104-generic'
  LD      /home/monik/Downloads/input-wacom-0.37.1/3.17/built-in.o
  CC [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_wac.o
  CC [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_sys.o
  LD [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom.o
  CC [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_w8001.o
  Building modules, stage 2.
  MODPOST 2 modules
  CC      /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom.mod.o
  LD [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom.ko
  CC      /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_w8001.mod.o
  LD [M]  /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_w8001.ko
make[3]: Leaving directory '/usr/src/linux-headers-4.4.0-104-generic'
make[2]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1/3.17'
make[2]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1'
make[2]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1'
make[1]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1'
monik@monik:~/Downloads/input-wacom-0.37.1$ sudo make install
Making install in 3.17
make[1]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1/3.17'
make -C /lib/modules/4.4.0-104-generic/build M=/home/monik/Downloads/input-wacom-0.37.1/3.17 modules_install
make[2]: Entering directory '/usr/src/linux-headers-4.4.0-104-generic'
  INSTALL /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom.ko
At main.c:222:
- SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/monik/Downloads/input-wacom-0.37.1/3.17/wacom_w8001.ko
At main.c:222:
- SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  DEPMOD  4.4.0-104-generic
make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-104-generic'
mkdir -p /etc/depmod.d
echo "override wacom * extra" > /etc/depmod.d/input-wacom.conf
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/bin:/sbin" depmod -a 4.4.0-104-generic
/usr/sbin/update-initramfs -u -k 4.4.0-104-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-104-generic
make[1]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1/3.17'
make[1]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1'
make[2]: Entering directory '/home/monik/Downloads/input-wacom-0.37.1'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1'
make[1]: Leaving directory '/home/monik/Downloads/input-wacom-0.37.1'

M.

input-wacom compiling errors

Hey guys.

I'm installing latest input-wacom drivers on CentOS 7 machines with Wacom Intuos PTH-860 tablet connected. Got all dependencies, but when compiling I'm getting:

/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c: In function ‘__wacom_notify_battery’:
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c:65:7: error: used struct type value where scalar is required
   if (battery->battery.dev)
       ^
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c: In function ‘wacom_status_irq’:
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c:1767:7: error: wrong type argument to unary exclamation mark
   if (!wacom->battery.battery.dev &&
       ^
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c:1773:52: error: invalid operands to binary && (have ‘int’ and ‘struct device’)
  else if ((features->quirks & WACOM_QUIRK_BATTERY) &&
                                                    ^
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c: In function ‘wacom_mspro_device_irq’:
/root/Downloads/input-wacom-input-wacom-0.37.0/3.7/wacom_wac.c:1793:6: error: wrong type argument to unary exclamation mark
  if (!w->battery.battery.dev &&
      ^

This happens with all new drivers down to 0.36.0 which compiles and works for me. So I'm forced to use it.

wacom tablet unresponsive after xhci controller crash

Maybe this should be filed against the usb subsystem in the linux kernel, but this only happens when using the wacom tablet so I thought I'd file here. Lenovo X1 Carbon Yoga 3rd generation experiencing loss of wacom tablet functionality when optimal power management settings are used. Using stock wacom driver in Fedora (v. 2.00)

What happens:

  1. Using powertop configure system for optimal power management (all settings are set to "Good" under powertop tunables, including wacom usb entries)
  2. Reboot and notice that things look good in dmesg:
    [    0.000000] Linux version 4.16.7-300.fc28.x86_64 ([email protected]) (gcc version 8.0.1 20180324 (Red Hat 8.0.1-0.20) (GCC)) #1 SMP Wed May 2 20:09:13 UTC 2018
    [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.16.7-300.fc28.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet resume=/dev/mapper/fedora-swap acpi.ec_no_wakeup=1 psmouse.synaptics_intertouch=1 
    
    and the relevant parts for wacom:
    [    2.555509] usb 1-10: New USB device found, idVendor=056a, idProduct=5146
    [    2.555511] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [    2.555513] usb 1-10: Product: Pen and multitouch sensor
    [    2.555514] usb 1-10: Manufacturer: Wacom Co.,Ltd.
    [    2.558357] input: Wacom Co.,Ltd. Pen and multitouch sensor as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5146.0001/input/input7
    [    2.558719] hid-generic 0003:056A:5146.0001: input,hiddev96,hidraw0: USB HID v1.11 Device [Wacom Co.,Ltd. Pen and multitouch sensor] on usb-0000:00:14.0-10/input0
    [    2.560531] input: Wacom Co.,Ltd. Pen and multitouch sensor as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5146.0002/input/input8
    [    2.560640] hid-generic 0003:056A:5146.0002: input,hiddev97,hidraw1: USB HID v1.11 Mouse [Wacom Co.,Ltd. Pen and multitouch sensor] on usb-0000:00:14.0-10/input1
    [    2.607775] input: Wacom Pen and multitouch sensor Finger as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:056A:5146.0001/input/input10
    [    2.607959] wacom 0003:056A:5146.0001: hidraw0: USB HID v1.11 Device [Wacom Co.,Ltd. Pen and multitouch sensor] on usb-0000:00:14.0-10/input0
    [    2.608304] input: Wacom Pen and multitouch sensor Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:056A:5146.0002/input/input12
    [    2.608710] wacom 0003:056A:5146.0002: hidraw1: USB HID v1.11 Mouse [Wacom Co.,Ltd. Pen and multitouch sensor] on usb-0000:00:14.0-10/input1   
    
  3. After approximately 5 minutes of using the tablet, it becomes unresponsive and the system becomes noticeably hotter with power use spiking to 16W. This is what I see in dmesg:
    [   51.010836] xhci_hcd 0000:3c:00.0: remove, state 4
    [   51.010845] usb usb4: USB disconnect, device number 1
    [   51.011269] xhci_hcd 0000:3c:00.0: USB bus 4 deregistered
    [   51.011363] xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead
    [   51.011368] xhci_hcd 0000:3c:00.0: remove, state 4
    [   51.011375] usb usb3: USB disconnect, device number 1
    [   51.011589] xhci_hcd 0000:3c:00.0: Host halt failed, -19
    [   51.011592] xhci_hcd 0000:3c:00.0: Host not accessible, reset failed.
    [   51.011821] xhci_hcd 0000:3c:00.0: USB bus 3 deregistered
    [   51.719358] thunderbolt 0000:08:00.0: stopping RX ring 0
    [   51.719364] thunderbolt 0000:08:00.0: disabling interrupt at register 0x38200 bit 12 (0xffffffff -> 0xffffefff)
    [   51.719371] thunderbolt 0000:08:00.0: stopping TX ring 0
    [   51.719375] thunderbolt 0000:08:00.0: disabling interrupt at register 0x38200 bit 0 (0xffffffff -> 0xfffffffe)
    [   51.719378] thunderbolt 0000:08:00.0: control channel stopped
    [   51.719459] thunderbolt 0000:08:00.0: freeing RX ring 0
    [   51.719466] thunderbolt 0000:08:00.0: freeing TX ring 0
    [   51.719474] thunderbolt 0000:08:00.0: shutdown
    [   51.743396] pci_bus 0000:07: Allocating resources
    [   51.743429] pcieport 0000:07:01.0: bridge window [io  0x1000-0x0fff] to [bus 09-3b] add_size 1000
    [   51.743439] pcieport 0000:07:02.0: bridge window [io  0x1000-0x0fff] to [bus 3c] add_size 1000
    [   51.743441] pcieport 0000:07:02.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 3c] add_size 200000 add_align 100000
    [   51.743450] pcieport 0000:07:04.0: bridge window [io  0x1000-0x0fff] to [bus 3d-70] add_size 1000
    [   51.743459] pcieport 0000:06:00.0: bridge window [io  0x1000-0x0fff] to [bus 07-70] add_size 3000
    [   51.743463] pcieport 0000:06:00.0: BAR 13: no space for [io  size 0x3000]
    [   51.743464] pcieport 0000:06:00.0: BAR 13: failed to assign [io  size 0x3000]
    [   51.743466] pcieport 0000:06:00.0: BAR 13: no space for [io  size 0x3000]
    [   51.743467] pcieport 0000:06:00.0: BAR 13: failed to assign [io  size 0x3000]
    [   51.743473] pcieport 0000:07:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
    [   51.743474] pcieport 0000:07:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
    [   51.743475] pcieport 0000:07:01.0: BAR 13: no space for [io  size 0x1000]
    [   51.743476] pcieport 0000:07:01.0: BAR 13: failed to assign [io  size 0x1000]
    [   51.743477] pcieport 0000:07:02.0: BAR 13: no space for [io  size 0x1000]
    [   51.743479] pcieport 0000:07:02.0: BAR 13: failed to assign [io  size 0x1000]
    [   51.743480] pcieport 0000:07:04.0: BAR 13: no space for [io  size 0x1000]
    [   51.743482] pcieport 0000:07:04.0: BAR 13: failed to assign [io  size 0x1000]
    [   51.743484] pcieport 0000:07:04.0: BAR 13: no space for [io  size 0x1000]
    [   51.743485] pcieport 0000:07:04.0: BAR 13: failed to assign [io  size 0x1000]
    [   51.743487] pcieport 0000:07:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
    [   51.743488] pcieport 0000:07:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
    [   51.743490] pcieport 0000:07:02.0: BAR 13: no space for [io  size 0x1000]
    [   51.743491] pcieport 0000:07:02.0: BAR 13: failed to assign [io  size 0x1000]
    [   51.743492] pcieport 0000:07:01.0: BAR 13: no space for [io  size 0x1000]
    [   51.743493] pcieport 0000:07:01.0: BAR 13: failed to assign [io  size 0x1000]
    [   56.038973] pcieport 0000:07:00.0: Refused to change power state, currently in D3
    [   56.040866] pci_bus 0000:08: busn_res: [bus 08] is released
    [   56.040931] pci_bus 0000:09: busn_res: [bus 09-3b] is released
    [   56.040977] pci_bus 0000:3c: busn_res: [bus 3c] is released
    [   56.041076] pci_bus 0000:3d: busn_res: [bus 3d-70] is released
    [   56.041144] pci_bus 0000:07: busn_res: [bus 07-70] is released
    [  633.322847] xhci_hcd 0000:00:14.0: xHC is not running.
    [  701.099735] xhci_hcd 0000:00:14.0: xHC is not running.
    [  722.939901] xhci_hcd 0000:00:14.0: xHC is not running.
    [  732.892947] xhci_hcd 0000:00:14.0: xHC is not running.
    [  819.554547] xhci_hcd 0000:00:14.0: xHC is not running.
    [  863.556178] xhci_hcd 0000:00:14.0: xHC is not running.
    [  901.909278] xhci_hcd 0000:00:14.0: xHC is not running.
    [  944.272820] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1032.719054] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1045.293000] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1069.748934] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1077.114486] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1088.723426] xhci_hcd 0000:00:14.0: xHC is not running.
    [ 1088.726020] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
    [ 1088.726036] xhci_hcd 0000:00:14.0: HC died; cleaning up
    [ 1088.801794] usb 1-5: USB disconnect, device number 2
    [ 1088.803044] usb 1-8: USB disconnect, device number 4
    [   1088.803668] usb 1-10: USB disconnect, device number 5 
    
  4. The other usb devices and the xhci appears to come back online but not the tablet. Unloading/reloading wacom kernel module fails to bring the tablet back. Have to restart at this point to recover functionality.

I can avoid the problem 2 ways:

  1. Use computer in notebook mode and avoid the touchscreen, or
  2. Turn off power management on the xHCI controller:
# Runtime PM for PCI Device Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller 
/sys/bus/pci/devices/0000:00:14.0/power/control=on

with the downside to this second approach being that system power usage goes up quite a bit (about 1Whr), which is a concern because the machine is already not the most battery efficient.

How to uninstall?

I have been getting the following error after installing input-wacom on my Ubuntu 18.04

Err:16 http://ppa.launchpad.net/doctormo/wacom-plus/ubuntu bionic Release
  404  Not Found [IP: 91.189.95.83 80]
Reading package lists... Done                      
E: The repository 'http://ppa.launchpad.net/doctormo/wacom-plus/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Error executing command, exiting

So now, I would like to remove everything related, but I cannot find relevant instructions. Do I just reverse my installation process by replacing 'install' with 'uninstall'? Please help, thanks!

Wacom Cintiq 24HD Pen stopped working

My Wacom Cintiq 24HD Pen stopped working when I upgraded the kernel to 4.16.x. Booting fc26 (X Server 1.19.6) with kernel 4.15.17 (from fc25) makes it work again.

"Working" in this case means that the cursor does no longer follow the pen movements. Actually, nothing that I do with the pen has any effect. The X server log files don't show any problems. The device is detected and registered.

Any hints?

Tablet PC pen and touch input is disabled after booting into Windows

Based on Sourceforge Bug #307 and Sourceforge Bug #310


Based on the hid-recorder output from the Lenovo Thinkpad Yoga 260 (056a:5048) and the Lenovo Thinkpad X1 Yoga (056a:503e), it looks like the device is sending events with an unexpected report ID. Instead of having the ID specified for the generic HID packets, the ID is of the "vendor defined" HID packets that the driver can't automatically decode. That's really odd since since most devices use the former automatically.

This can apparently be worked around by using the device's reset switch, but the pen and touch stops working again once the system is booted into Windows. This likely indicates the sensor is persisting the mode change that is done by the Wacom driver for Windows. To fix this bug, we need to manually change the mode so it sends standard HID reports again.

Touchscreen shows 1% battery

I've got a Dell Inspiron 5379 with an active touchscreen. I'm not sure the details of the device but if you tell me how I'd be happy to get it.

As soon as I use the stylus for the first time, I notice there's a keyboard in battery settings with 0% battery and I think it's related to the touchscreen/stylus. A message pops up saying the battery is low.

The real problem is after that the screen starts dimming after just a few seconds, presumably to conserve battery power. I need to reboot to fix it so consequently I never bother using the stylus.

If you need help debugging this just let me know what you want me to do.

Thanks.

Wacom One CTL-672 is not detected anymore in Ubuntu 18.04

Hello.
I have Wacom CTL-672 and Ubuntu 18.04.1 LTS.
I installed the driver following the instruction here: https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source
And it worked fine just one day, but then (apparently after sleep-mode or turning off) it stopped working.
In system settings there's message "No tablet detected", but it is detected as a usb device when I type "lsusb" I get "Bus 004 Device 004: ID 056a:037b Wacom Co., Ltd".
I tried to reinstall driver by using the same instruction, but still no result.
When I type command "grep "" /sys/module/wacom*/version" I get the message "/sys/module/wacom*/version: No such file or directory".
Please, help.

Here is the installation log with a couple of errors:

if test -x ./autogen.sh; then ./autogen.sh; else ./configure; fi && make && sudo make install || echo "Build Failed"
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for kernel type... Linux
checking for linux-based kernel... yes
checking for kernel source/headers... /lib/modules/4.15.0-36-generic/build
checking kernel version... 4.15.0-36-generic
checking RHEL7 minor release... 0
checking power supply version... v4.1+
checking abs accessor version... v2.6.36+

checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating 2.6.32/Makefile
config.status: creating 2.6.38/Makefile
config.status: creating 3.7/Makefile
config.status: creating 3.17/Makefile
config.status: creating 4.5/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure:
----------------------------------------
  BUILD ENVIRONMENT:
       linux kernel - yes 4.5
      kernel source - yes /lib/modules/4.15.0-36-generic/build

NOTE: The kernel drivers included in this package are only tested with the
X Wacom driver built from xf86-input-wacom. If you are running an X server
version older than 1.7, please use the drivers provided by the linuxwacom
package.

Please run 'make && make install'.
make  all-recursive
make[1]: Entering directory '/home/user/Downloads/input-wacom-0.41.0'
Making all in 4.5
make[2]: Entering directory '/home/user/Downloads/input-wacom-0.41.0/4.5'
    Building input-wacom drivers for 4.5 kernel.
make -C /lib/modules/4.15.0-36-generic/build M=/home/user/Downloads/input-wacom-0.41.0/4.5
make[3]: Entering directory '/usr/src/linux-headers-4.15.0-36-generic'
Makefile:975: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
  CC [M]  /home/user/Downloads/input-wacom-0.41.0/4.5/wacom_wac.o
/home/user/Downloads/input-wacom-0.41.0/4.5/wacom_wac.c: In function ‘wacom_setup_pen_input_capabilities’:
/home/user/Downloads/input-wacom-0.41.0/4.5/wacom_wac.c:3517:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
   __clear_bit(ABS_MISC, input_dev->absbit);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/user/Downloads/input-wacom-0.41.0/4.5/wacom_wac.c:3519:2: note: here
  case WACOM_MO:
  ^~~~
  CC [M]  /home/user/Downloads/input-wacom-0.41.0/4.5/wacom_sys.o
  LD [M]  /home/user/Downloads/input-wacom-0.41.0/4.5/wacom.o
  Building modules, stage 2.
  MODPOST 2 modules
  LD [M]  /home/user/Downloads/input-wacom-0.41.0/4.5/wacom.ko
make[3]: Leaving directory '/usr/src/linux-headers-4.15.0-36-generic'
make[2]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0/4.5'
make[2]: Entering directory '/home/user/Downloads/input-wacom-0.41.0'
make[2]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0'
make[1]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0'
Making install in 4.5
make[1]: Entering directory '/home/user/Downloads/input-wacom-0.41.0/4.5'
make -C /lib/modules/4.15.0-36-generic/build M=/home/user/Downloads/input-wacom-0.41.0/4.5 modules_install
make[2]: Entering directory '/usr/src/linux-headers-4.15.0-36-generic'
Makefile:975: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
  INSTALL /home/user/Downloads/input-wacom-0.41.0/4.5/wacom.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
  INSTALL /home/user/Downloads/input-wacom-0.41.0/4.5/wacom_w8001.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:74
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:81
sign-file: certs/signing_key.pem: No such file or directory
  DEPMOD  4.15.0-36-generic
make[2]: Leaving directory '/usr/src/linux-headers-4.15.0-36-generic'
mkdir -p /etc/depmod.d
echo "override wacom * extra" > /etc/depmod.d/input-wacom.conf
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/bin:/sbin" depmod -a 4.15.0-36-generic
/usr/sbin/update-initramfs -u -k 4.15.0-36-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-36-generic
make[1]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0/4.5'
make[1]: Entering directory '/home/user/Downloads/input-wacom-0.41.0'
make[2]: Entering directory '/home/user/Downloads/input-wacom-0.41.0'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0'
make[1]: Leaving directory '/home/user/Downloads/input-wacom-0.41.0'

Unknown device_type for 'Wacom Co.,Ltd. CTL-472'.

I just bought a One tablet today and it doesnt work with this driver.
I thought support for this tablet was added by #18.

Here is what cat /sys/module/wacom*/version says:

❯❯ cat /sys/module/wacom*/version
v2.00-0.37.1

Here is what journalctl says:

Nov 30 22:25:56 arch kernel: usb 5-4.3: new full-speed USB device number 10 using xhci_hcd
Nov 30 22:26:02 arch kernel: input input59: Absolute device without dev->absinfo, refusing to register
Nov 30 22:26:02 arch kernel: wacom: probe of 0003:056A:037A.000F failed with error -22
Nov 30 22:26:02 arch kernel: wacom 0003:056A:037A.0010: Unknown device_type for 'Wacom Co.,Ltd. CTL-472'. Ignoring.

Release script should error out if `jq` program is not found

The input-wacom release.sh script relies on the jq program being installed to work with the JSON API that Github provides. If this program isn't installed, the script does not work correctly. Since this is a non-standard tool, we should add a check early on (e.g. in the --github option parsing case) and exit with a warning if the program is unavailable.

Usable for macs?

The latest version of macos, Mojave,
10.14, broke compatability for the intuos 3 series. Is there any chance that I could use this driver as a replacement for the now defunct original driver on a Mac?

Minor inconsistencies between kernel versions

There are some minor inconsistencies between the kernel versions that cause patches that "should" apply cleanly to not do so. For the most part these are a matter of slightly different style (e.g. line breaks at different spots) that trip things up. The different versions should be brought back in line with each other to make backporting patches easier.

Waltop tablet not detected in LM 18.2 (Kernel 4.13) but detected in LM17.3 (Kernel 4.4)

Hi guys in linux Mint 17.3 I successfully managed to recognise my tablet by installing the two files libwacom-common_0.11+dfsg-0ubuntu1_all.deb and libwacom2_0.11+dfsg-0ubuntu1_amd64.deb
Files were downloaded at that time from these links which are now dead
[(http://packages.ubuntu.com/vivid/amd64/libwacom2/download]
[http://packages.ubuntu.com/vivid/all/libwacom-common/download)]

Recently I did a clean install to 18.2 and I had no success making the same tablet working.

I started by running the command sudo dpkg -i libwacom2_0.11+dfsg-0ubuntu1_amd64.deb libwacom-common_0.11+dfsg-0ubuntu1_all.deb with the existing files I had...
which probably was a mistake as these packages were compiled for LM17. I didn't get any error though.
The tablet didn't work. I went to Synaptic and there these two packages were reported as broken. I fixed them, did an update and then they were upgraded to versions 0.22
Still the tablet is not working...

At that point I was confused: either my initial mistake to install the old debian packages is the cause or LM 18 is responsible for not making it work.
I tried to uninstall the packages manually but the dependencies do not allow me because thousand other packages (including cinnamon) will be removed. So I never uninstalled them completely! (HOW CAN I DO IT?? IS IT EVEN POSSIBLE??)

Then I found your page and I followed all the steps described here, compiling all the necessary files from scratch. Still no luck!!!

I ran out of ideas! I still have my old LM17.3 installed in the same computer so it's really annoying knowing that it is there working and not here in 18.2...

My LM17.3 had kernel 4.4 and my LM 18.2 has kernel 4.13.
The tablet has a USB ID: 172f:0047 Waltop International Corp.

Command xsetwacom --list devices returns nothing in LM18.2

Command grep "Using input driver" /var/log/Xorg.0.log returns

[     6.475] (II) Using input driver 'libinput' for 'Power Button'
[     6.521] (II) Using input driver 'libinput' for 'Power Button'
[     6.544] (II) Using input driver 'libinput' for 'Sleep Button'
[     6.561] (II) Using input driver 'libinput' for 'Logitech USB-PS/2 Optical Mouse'
[     6.714] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    28.586] (II) Using input driver 'libinput' for 'WALTOP International Corp. Mars Tablet'
[    93.451] (II) Using input driver 'libinput' for 'WALTOP International Corp. Mars Tablet'
[   530.555] (II) Using input driver 'libinput' for 'WALTOP International Corp. Mars Tablet'
[   742.623] (II) Using input driver 'libinput' for 'WALTOP International Corp. Mars Tablet'

Command dmesg|tail returns

[  739.799344] usb 1-5: USB disconnect, device number 7
[  742.329912] usb 1-5: new full-speed USB device number 8 using xhci_hcd
[  742.474277] usb 1-5: New USB device found, idVendor=172f, idProduct=0047
[  742.474280] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  742.474281] usb 1-5: Product: Mars Tablet
[  742.474283] usb 1-5: Manufacturer: WALTOP International Corp.
[  742.481369] input: WALTOP International Corp. Mars Tablet as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:172F:0047.0005/input/input21
[  742.538481] hid-generic 0003:172F:0047.0005: input,hidraw1: USB HID v1.10 Mouse [WALTOP International Corp. Mars Tablet] on usb-0000:00:14.0-5/input0

Any help please?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.