Quantcast

Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

Hello,


I'm a bit of a novice when it comes to linux so pardon me if I sound like a newbe.


Here's my setup:


I work for a small production company that uses numerous OSs (Window, Mac, RHEL 6.5) on machines for video production.  Most of our machine are connected to a Avocent HMX KVM system and has been working flawlessly with wacom tablets for a number of years with all the OSs I mentioned.


Recently, we purchased a new machine to run the latest version of Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5 ... again, wacom works with the Avocent and this workstation)  The new workstation is loaded with CentOS 7.2.  The integrator tested the wacom with the machine locally and it functioned normally.  When the new machine arrived, we integrated it into our Avocent KVM system and the wacom doesn't work through the KVM.  However, it shows up and identifies itself and loads it's driver. (I think)


With my limited knowledge, I put together some command line queries that might help in troubleshooting.  Any ideas or help would be much appreciated.  See the list below:

more /proc/bus/input/devices (wacom plugged into workstation)

I: Bus=0003 Vendor=056a Product=00b2 Version=0102
N: Name="Wacom Intuos3 9x12"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
U: Uniq=
H: Handlers=mouse2 event22
B: PROP=1
B: EV=1f
B: KEY=1cdf 1f00ff 0 0 0 0
B: REL=100
B: ABS=1000f00017f
B: MSC=1

xsetwacom --list devices (wacom plugged into workstation)

Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
Wacom Intuos3 9x12 eraser           id: 13    type: ERASER    
Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR    
Wacom Intuos3 9x12 pad              id: 15    type: PAD


lsusb (wacom plugged into workstation)

Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 005 Device 002: ID 8087:800a Intel Corp.
Bus 006 Device 002: ID 8087:8002 Intel Corp.
Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0624:0410 Avocent Corp.




more /proc/bus/input/devices (wacom through the Avocent KVM)

I: Bus=0003 Vendor=056a Product=00b2 Version=0102
N: Name="Wacom Intuos3 9x12"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
U: Uniq=
H: Handlers=mouse1 event5
B: PROP=1
B: EV=1f
B: KEY=1cdf 1f00ff 0 0 0 0
B: REL=100
B: ABS=1000f00017f
B: MSC=1


xsetwacom --list devices (wacom through the Avocent KVM)

Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
Wacom Intuos3 9x12 eraser           id: 12    type: ERASER    
Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR    
Wacom Intuos3 9x12 pad              id: 14    type: PAD


lsusb (wacom through the Avocent KVM)

Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 005 Device 002: ID 8087:800a Intel Corp.
Bus 006 Device 002: ID 8087:8002 Intel Corp.
Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0624:0410 Avocent Corp.
Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12


Thanks!


Joey

 

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Jason Gerecke
On 11/01/2016 09:03 AM, Joey Tucker wrote:

> Hello,
>
>
> I'm a bit of a novice when it comes to linux so pardon me if I sound
> like a newbe.
>
>
> Here's my setup:
>
>
> I work for a small production company that uses numerous OSs (Window,
> Mac, RHEL 6.5) on machines for video production.  Most of our machine
> are connected to a Avocent HMX KVM system and has been working
> flawlessly with wacom tablets for a number of years with all the OSs I
> mentioned.
>
>
> Recently, we purchased a new machine to run the latest version of
> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
> ... again, wacom works with the Avocent and this workstation)  The new
> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
> with the machine locally and it functioned normally.  When the new
> machine arrived, we integrated it into our Avocent KVM system and the
> wacom doesn't work through the KVM.  However, it shows up and identifies
> itself and loads it's driver. (I think)
>
>
> With my limited knowledge, I put together some command line queries that
> might help in troubleshooting.  Any ideas or help would be much
> appreciated.  See the list below:
>
> more /proc/bus/input/devices (wacom plugged into workstation)
>
> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
> N: Name="Wacom Intuos3 9x12"
> P: Phys=
> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
> U: Uniq=
> H: Handlers=mouse2 event22
> B: PROP=1
> B: EV=1f
> B: KEY=1cdf 1f00ff 0 0 0 0
> B: REL=100
> B: ABS=1000f00017f
> B: MSC=1
>
> xsetwacom --list devices (wacom plugged into workstation)
>
> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER    
> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR    
> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>
>
> lsusb (wacom plugged into workstation)
>
> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
> SuperSpeed hub
> Bus 005 Device 002: ID 8087:800a Intel Corp.
> Bus 006 Device 002: ID 8087:8002 Intel Corp.
> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
> High-Speed hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>
>
>
>
> more /proc/bus/input/devices (wacom through the Avocent KVM)
>
> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
> N: Name="Wacom Intuos3 9x12"
> P: Phys=
> S:
> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
> U: Uniq=
> H: Handlers=mouse1 event5
> B: PROP=1
> B: EV=1f
> B: KEY=1cdf 1f00ff 0 0 0 0
> B: REL=100
> B: ABS=1000f00017f
> B: MSC=1
>
>
> xsetwacom --list devices (wacom through the Avocent KVM)
>
> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER    
> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR    
> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>
>
> lsusb (wacom through the Avocent KVM)
>
> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
> SuperSpeed hub
> Bus 005 Device 002: ID 8087:800a Intel Corp.
> Bus 006 Device 002: ID 8087:8002 Intel Corp.
> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
> High-Speed hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>
>
> Thanks!
>
>
> Joey
>

Joey,

It does indeed appear that the device is being forwarded over the KVM
link, so could you please describe in a bit more detail what is not working?

Could you please provide the output of `dmesg | grep -iC3 wacom` for review?

Additionally, please try installing the evemu[1] package and then
running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
over the KVM. After selecting the Intuos3 from the list of devices
detected by evemu-record (let us know if the tablet is not detected),
draw a few strokes with the pen and then hit CTRL+C. Attach the
generated log file for review.

[1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826

--
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker
In reply to this post by Joey Tucker

Thank you so much, Jason for writing back!

 

I've added a CC to Jason Starne of Cinesys, Inc.  His company is the integrator of the CentOS 7 system we purchased.

 

It does indeed appear that the device is being forwarded over the KVM
link, so could you please describe in a bit more detail what is not working?

 

No feedback from the tablet at all ... pen nor mouse.  However, power is there.  Status LED responds to input.  Also a keyboard and mouse are connected to the same KVM and they function.


Could you please provide the output of `dmesg | grep -iC3 wacom` for review?

 

dmesg | grep -iC3 wacom
[   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
[   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model ARC-1883
[   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   12.880731] input: Wacom Intuos3 9x12 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
[   12.881334] AES CTR mode by8 optimization enabled
[   12.883240] [drm] Initialized drm 1.1.0 20060810
[   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
--
[   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
[   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
[   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
[   13.481560] usbcore: registered new interface driver wacom
[   13.927161] XFS (sda1): Ending clean mount
[   14.332635] device-mapper: uevent: version 1.0.3
[   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18) initialised: [hidden email]
--
[16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16015.787635] usb 1-1.3: Product: PTZ-930
[16015.787636] usb 1-1.3: Manufacturer: Tablet
[16015.789094] input: Wacom Intuos3 9x12 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
[16177.178260] usb 1-1.3: USB disconnect, device number 8
[16216.576711] usb 1-1.3: new full-speed USB device number 9 using xhci_hcd
[16216.780255] usb 1-1.3: New USB device found, idVendor=056a, idProduct=00b2
[16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16216.780258] usb 1-1.3: Product: PTZ-930
[16216.780259] usb 1-1.3: Manufacturer: Tablet
[16216.781286] input: Wacom Intuos3 9x12 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
[16247.216417] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[16247.216424] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error status/mask=00000080/00002000

 

Additionally, please try installing the evemu[1] package and then
running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
over the KVM. After selecting the Intuos3 from the list of devices
detected by evemu-record (let us know if the tablet is not detected),
draw a few strokes with the pen and then hit CTRL+C. Attach the
generated log file for review.

 

Log attached.  I added additional input from the wheel mouse on the tablet as well.  If I over-did it, let me know and I’ll do a shorter test.

 

Thanks Jason for your help!

 

Joey

 

 

 

From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 1, 2016 3:40 PM
To: Joey Tucker; [hidden email]
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

 

On 11/01/2016 09:03 AM, Joey Tucker wrote:
> Hello,
>
>
> I'm a bit of a novice when it comes to linux so pardon me if I sound
> like a newbe.
>
>
> Here's my setup:
>
>
> I work for a small production company that uses numerous OSs (Window,
> Mac, RHEL 6.5) on machines for video production.  Most of our machine
> are connected to a Avocent HMX KVM system and has been working
> flawlessly with wacom tablets for a number of years with all the OSs I
> mentioned.
>
>
> Recently, we purchased a new machine to run the latest version of
> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
> ... again, wacom works with the Avocent and this workstation)  The new
> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
> with the machine locally and it functioned normally.  When the new
> machine arrived, we integrated it into our Avocent KVM system and the
> wacom doesn't work through the KVM.  However, it shows up and identifies
> itself and loads it's driver. (I think)
>
>
> With my limited knowledge, I put together some command line queries that
> might help in troubleshooting.  Any ideas or help would be much
> appreciated.  See the list below:
>
> more /proc/bus/input/devices (wacom plugged into workstation)
>
> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
> N: Name="Wacom Intuos3 9x12"
> P: Phys=
> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
> U: Uniq=
> H: Handlers=mouse2 event22
> B: PROP=1
> B: EV=1f
> B: KEY=1cdf 1f00ff 0 0 0 0
> B: REL=100
> B: ABS=1000f00017f
> B: MSC=1
>
> xsetwacom --list devices (wacom plugged into workstation)
>
> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS   
> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER   
> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR   
> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>
>
> lsusb (wacom plugged into workstation)
>
> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
> SuperSpeed hub
> Bus 005 Device 002: ID 8087:800a Intel Corp.
> Bus 006 Device 002: ID 8087:8002 Intel Corp.
> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
> High-Speed hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>
>
>
>
> more /proc/bus/input/devices (wacom through the Avocent KVM)
>
> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
> N: Name="Wacom Intuos3 9x12"
> P: Phys=
> S:
> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
> U: Uniq=
> H: Handlers=mouse1 event5
> B: PROP=1
> B: EV=1f
> B: KEY=1cdf 1f00ff 0 0 0 0
> B: REL=100
> B: ABS=1000f00017f
> B: MSC=1
>
>
> xsetwacom --list devices (wacom through the Avocent KVM)
>
> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS   
> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER   
> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR   
> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>
>
> lsusb (wacom through the Avocent KVM)
>
> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
> SuperSpeed hub
> Bus 005 Device 002: ID 8087:800a Intel Corp.
> Bus 006 Device 002: ID 8087:8002 Intel Corp.
> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
> High-Speed hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>
>
> Thanks!
>
>
> Joey
>

Joey,

It does indeed appear that the device is being forwarded over the KVM
link, so could you please describe in a bit more detail what is not working?

Could you please provide the output of `dmesg | grep -iC3 wacom` for review?

Additionally, please try installing the evemu[1] package and then
running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
over the KVM. After selecting the Intuos3 from the list of devices
detected by evemu-record (let us know if the tablet is not detected),
draw a few strokes with the pen and then hit CTRL+C. Attach the
generated log file for review.

[1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826

--
Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

intuos3-kvm.log (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Jason Gerecke
Thanks for running those tests for me, Joey. Looking through the
attached log, I see that it is missing the events that should be sent by
the tablet in response to input from the pen/mouse. In the past we've
seen issues like this caused by KVMs that attempt to treat the tablet
like a mouse (which it boots up emulating, and is unusable by our driver
until we send it a command to switch modes) rather than a generic USB
device.

If your Avocent KVM works with CentOS 6 systems, it would seem that you
are experiencing a different issue. It must be KVM-related somehow since
the Intuos3 works when locally connected, but we will need to do some
additional debugging to locate the cause.

The kernel driver does not contain debug messages along the codepaths
that I suspect are affected, so I will need to provide you with some
patches to our input-wacom kernel driver that should provide more
illumination. It will take some time to write these patches; expect a
follow-up in a day or so. In the meantime, I would suggest familiarizing
yourself with the process of building and installing[1] the driver. Feel
free to ask questions if the instructions are unclear.

[1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 11/01/2016 01:22 PM, Joey Tucker wrote:

> Thank you so much, Jason for writing back!
>
>  
>
> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
> integrator of the CentOS 7 system we purchased.
>
>  
>
> *It does indeed appear that the device is being forwarded over the KVM
> link, so could you please describe in a bit more detail what is not
> working?*
>
>  
>
> No feedback from the tablet at all ... pen nor mouse.  However, power is
> there.  Status LED responds to input.  Also a keyboard and mouse are
> connected to the same KVM and they function.
>
>
> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
> review?*
>
>  
>
> dmesg | grep -iC3 wacom
> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model ARC-1883
> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   12.880731] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
> [   12.881334] AES CTR mode by8 optimization enabled
> [   12.883240] [drm] Initialized drm 1.1.0 20060810
> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
> --
> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
> [   13.481560] usbcore: registered new interface driver wacom
> [   13.927161] XFS (sda1): Ending clean mount
> [   14.332635] device-mapper: uevent: version 1.0.3
> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
> initialised: [hidden email] <mailto:[hidden email]>
> --
> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [16015.787635] usb 1-1.3: Product: PTZ-930
> [16015.787636] usb 1-1.3: Manufacturer: Tablet
> [16015.789094] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
> [16177.178260] usb 1-1.3: USB disconnect, device number 8
> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using xhci_hcd
> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
> idProduct=00b2
> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [16216.780258] usb 1-1.3: Product: PTZ-930
> [16216.780259] usb 1-1.3: Manufacturer: Tablet
> [16216.781286] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
> status/mask=00000080/00002000
>
>  
>
> *Additionally, please try installing the evemu[1] package and then*
> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
> *over the KVM. After selecting the Intuos3 from the list of devices*
> *detected by evemu-record (let us know if the tablet is not detected),*
> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
> *generated log file for revie*w.
>
>  
>
> Log attached.  I added additional input from the wheel mouse on the
> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>
>  
>
> Thanks Jason for your help!
>
>  
>
> Joey
>
>  
>
>  
>
>  
>
> *From:*Jason Gerecke <[hidden email] <mailto:[hidden email]>>
> *Sent:* Tuesday, November 1, 2016 3:40 PM
> *To:* Joey Tucker; [hidden email]
> <mailto:[hidden email]>
> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
> CentOS 7.2
>
>  
>
> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>> Hello,
>>
>>
>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>> like a newbe.
>>
>>
>> Here's my setup:
>>
>>
>> I work for a small production company that uses numerous OSs (Window,
>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>> are connected to a Avocent HMX KVM system and has been working
>> flawlessly with wacom tablets for a number of years with all the OSs I
>> mentioned.
>>
>>
>> Recently, we purchased a new machine to run the latest version of
>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>> ... again, wacom works with the Avocent and this workstation)  The new
>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>> with the machine locally and it functioned normally.  When the new
>> machine arrived, we integrated it into our Avocent KVM system and the
>> wacom doesn't work through the KVM.  However, it shows up and identifies
>> itself and loads it's driver. (I think)
>>
>>
>> With my limited knowledge, I put together some command line queries that
>> might help in troubleshooting.  Any ideas or help would be much
>> appreciated.  See the list below:
>>
>> more /proc/bus/input/devices (wacom plugged into workstation)
>>
>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>> N: Name="Wacom Intuos3 9x12"
>> P: Phys=
>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>> U: Uniq=
>> H: Handlers=mouse2 event22
>> B: PROP=1
>> B: EV=1f
>> B: KEY=1cdf 1f00ff 0 0 0 0
>> B: REL=100
>> B: ABS=1000f00017f
>> B: MSC=1
>>
>> xsetwacom --list devices (wacom plugged into workstation)
>>
>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER    
>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR    
>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>
>>
>> lsusb (wacom plugged into workstation)
>>
>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>> SuperSpeed hub
>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>> High-Speed hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>
>>
>>
>>
>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>
>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>> N: Name="Wacom Intuos3 9x12"
>> P: Phys=
>> S:
>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>> U: Uniq=
>> H: Handlers=mouse1 event5
>> B: PROP=1
>> B: EV=1f
>> B: KEY=1cdf 1f00ff 0 0 0 0
>> B: REL=100
>> B: ABS=1000f00017f
>> B: MSC=1
>>
>>
>> xsetwacom --list devices (wacom through the Avocent KVM)
>>
>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS    
>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER    
>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR    
>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>
>>
>> lsusb (wacom through the Avocent KVM)
>>
>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>> SuperSpeed hub
>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>> High-Speed hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>
>>
>> Thanks!
>>
>>
>> Joey
>>
>
> Joey,
>
> It does indeed appear that the device is being forwarded over the KVM
> link, so could you please describe in a bit more detail what is not working?
>
> Could you please provide the output of `dmesg | grep -iC3 wacom` for review?
>
> Additionally, please try installing the evemu[1] package and then
> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
> over the KVM. After selecting the Intuos3 from the list of devices
> detected by evemu-record (let us know if the tablet is not detected),
> draw a few strokes with the pen and then hit CTRL+C. Attach the
> generated log file for review.
>
> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>
> --
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

No problem, Jason.  You're help is greatly appreciated!


I had suspected a driver issue but really wasn't sure because of my limited knowledge. 


In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS versions of the following distros and had success with the wacom through the KVM:


Ubuntu 16.10

Linux Mint 17

Fedora 24


Just for giggles, I loaded a live version of CentOS 7.2 and had the same failure.


If needed, I can pull logs from the functioning RHEL 6.5 system so you can compare.


Let me know how I can help.


Thanks!


Joey Tucker
 



From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 1, 2016 5:07 PM
To: Joey Tucker; [hidden email]
Cc: Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 
Thanks for running those tests for me, Joey. Looking through the
attached log, I see that it is missing the events that should be sent by
the tablet in response to input from the pen/mouse. In the past we've
seen issues like this caused by KVMs that attempt to treat the tablet
like a mouse (which it boots up emulating, and is unusable by our driver
until we send it a command to switch modes) rather than a generic USB
device.

If your Avocent KVM works with CentOS 6 systems, it would seem that you
are experiencing a different issue. It must be KVM-related somehow since
the Intuos3 works when locally connected, but we will need to do some
additional debugging to locate the cause.

The kernel driver does not contain debug messages along the codepaths
that I suspect are affected, so I will need to provide you with some
patches to our input-wacom kernel driver that should provide more
illumination. It will take some time to write these patches; expect a
follow-up in a day or so. In the meantime, I would suggest familiarizing
yourself with the process of building and installing[1] the driver. Feel
free to ask questions if the instructions are unclear.

[1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 11/01/2016 01:22 PM, Joey Tucker wrote:
> Thank you so much, Jason for writing back!
>

>
> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
> integrator of the CentOS 7 system we purchased.
>

>
> *It does indeed appear that the device is being forwarded over the KVM
> link, so could you please describe in a bit more detail what is not
> working?*
>

>
> No feedback from the tablet at all ... pen nor mouse.  However, power is
> there.  Status LED responds to input.  Also a keyboard and mouse are
> connected to the same KVM and they function.
>
>
> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
> review?*
>

>
> dmesg | grep -iC3 wacom
> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model ARC-1883
> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   12.880731] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
> [   12.881334] AES CTR mode by8 optimization enabled
> [   12.883240] [drm] Initialized drm 1.1.0 20060810
> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
> --
> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
> [   13.481560] usbcore: registered new interface driver wacom
> [   13.927161] XFS (sda1): Ending clean mount
> [   14.332635] device-mapper: uevent: version 1.0.3
> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
> initialised: [hidden email] <[hidden email]>
> --
> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [16015.787635] usb 1-1.3: Product: PTZ-930
> [16015.787636] usb 1-1.3: Manufacturer: Tablet
> [16015.789094] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
> [16177.178260] usb 1-1.3: USB disconnect, device number 8
> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using xhci_hcd
> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
> idProduct=00b2
> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [16216.780258] usb 1-1.3: Product: PTZ-930
> [16216.780259] usb 1-1.3: Manufacturer: Tablet
> [16216.781286] input: Wacom Intuos3 9x12 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
> status/mask=00000080/00002000
>

>
> *Additionally, please try installing the evemu[1] package and then*
> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
> *over the KVM. After selecting the Intuos3 from the list of devices*
> *detected by evemu-record (let us know if the tablet is not detected),*
> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
> *generated log file for revie*w.
>

>
> Log attached.  I added additional input from the wheel mouse on the
> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>

>
> Thanks Jason for your help!
>

>
> Joey
>

>

>

>
> *From:*Jason Gerecke <[hidden email] <[hidden email]>>
> *Sent:* Tuesday, November 1, 2016 3:40 PM
> *To:* Joey Tucker; [hidden email]
> <[hidden email]>
> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
> CentOS 7.2
>

>
> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>> Hello,
>>
>>
>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>> like a newbe.
>>
>>
>> Here's my setup:
>>
>>
>> I work for a small production company that uses numerous OSs (Window,
>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>> are connected to a Avocent HMX KVM system and has been working
>> flawlessly with wacom tablets for a number of years with all the OSs I
>> mentioned.
>>
>>
>> Recently, we purchased a new machine to run the latest version of
>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>> ... again, wacom works with the Avocent and this workstation)  The new
>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>> with the machine locally and it functioned normally.  When the new
>> machine arrived, we integrated it into our Avocent KVM system and the
>> wacom doesn't work through the KVM.  However, it shows up and identifies
>> itself and loads it's driver. (I think)
>>
>>
>> With my limited knowledge, I put together some command line queries that
>> might help in troubleshooting.  Any ideas or help would be much
>> appreciated.  See the list below:
>>
>> more /proc/bus/input/devices (wacom plugged into workstation)
>>
>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>> N: Name="Wacom Intuos3 9x12"
>> P: Phys=
>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>> U: Uniq=
>> H: Handlers=mouse2 event22
>> B: PROP=1
>> B: EV=1f
>> B: KEY=1cdf 1f00ff 0 0 0 0
>> B: REL=100
>> B: ABS=1000f00017f
>> B: MSC=1
>>
>> xsetwacom --list devices (wacom plugged into workstation)
>>
>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS   
>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER   
>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR   
>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>
>>
>> lsusb (wacom plugged into workstation)
>>
>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>> SuperSpeed hub
>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>> High-Speed hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>
>>
>>
>>
>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>
>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>> N: Name="Wacom Intuos3 9x12"
>> P: Phys=
>> S:
>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>> U: Uniq=
>> H: Handlers=mouse1 event5
>> B: PROP=1
>> B: EV=1f
>> B: KEY=1cdf 1f00ff 0 0 0 0
>> B: REL=100
>> B: ABS=1000f00017f
>> B: MSC=1
>>
>>
>> xsetwacom --list devices (wacom through the Avocent KVM)
>>
>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS   
>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER   
>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR   
>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>
>>
>> lsusb (wacom through the Avocent KVM)
>>
>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>> SuperSpeed hub
>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>> High-Speed hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>
>>
>> Thanks!
>>
>>
>> Joey
>>
>
> Joey,
>
> It does indeed appear that the device is being forwarded over the KVM
> link, so could you please describe in a bit more detail what is not working?
>
> Could you please provide the output of `dmesg | grep -iC3 wacom` for review?
>
> Additionally, please try installing the evemu[1] package and then
> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
> over the KVM. After selecting the Intuos3 from the list of devices
> detected by evemu-record (let us know if the tablet is not detected),
> draw a few strokes with the pen and then hit CTRL+C. Attach the
> generated log file for review.
>
> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>
> --
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Jason Gerecke
Apologies for the longer-than-expected delay...

Please download the input-wacom 0.32.0 tarball and install any build
pre-requisites as outlined at
http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Before building, apply the attached patch by running `patch -p1 <
path/to/debug_0.32.0_v1.patch` from within the extracted
input-wacom-0.32.0 directory. This will add a number of debug
statements that should help me trace what is going on with your
system. You can then build and manually load the module by using `sudo
modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
install` step since this is a temporary debug build).

Once the module has been loaded, run `sudo tail -f /var/log/messages |
tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
should see some log output about the tablet being attached. Touch the
pen to the tablet surface and you should see lines prefixed with
"wacom_sys_irq" scroll by. After a second or so, remove the pen,
disconnect the tablet through the KVM, and press CTRL+C to stop the
log. Attach the generated debug_v1.log file for me to review.

The output should contain information about the status of the tablet
and the complete contents of any packets that it sends. This should
give me an idea of if the tablet is not being initialized properly, if
the data is incorrect, or if the functions are misbehaving.



Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:

> No problem, Jason.  You're help is greatly appreciated!
>
>
> I had suspected a driver issue but really wasn't sure because of my limited
> knowledge.
>
>
> In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS
> versions of the following distros and had success with the wacom through the
> KVM:
>
>
> Ubuntu 16.10
>
> Linux Mint 17
>
> Fedora 24
>
>
> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
> failure.
>
>
> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
> compare.
>
>
> Let me know how I can help.
>
>
> Thanks!
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 1, 2016 5:07 PM
> To: Joey Tucker; [hidden email]
> Cc: Jason Starne
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Thanks for running those tests for me, Joey. Looking through the
> attached log, I see that it is missing the events that should be sent by
> the tablet in response to input from the pen/mouse. In the past we've
> seen issues like this caused by KVMs that attempt to treat the tablet
> like a mouse (which it boots up emulating, and is unusable by our driver
> until we send it a command to switch modes) rather than a generic USB
> device.
>
> If your Avocent KVM works with CentOS 6 systems, it would seem that you
> are experiencing a different issue. It must be KVM-related somehow since
> the Intuos3 works when locally connected, but we will need to do some
> additional debugging to locate the cause.
>
> The kernel driver does not contain debug messages along the codepaths
> that I suspect are affected, so I will need to provide you with some
> patches to our input-wacom kernel driver that should provide more
> illumination. It will take some time to write these patches; expect a
> follow-up in a day or so. In the meantime, I would suggest familiarizing
> yourself with the process of building and installing[1] the driver. Feel
> free to ask questions if the instructions are unclear.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>> Thank you so much, Jason for writing back!
>>
>>
>>
>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>> integrator of the CentOS 7 system we purchased.
>>
>>
>>
>> *It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?*
>>
>>
>>
>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>> there.  Status LED responds to input.  Also a keyboard and mouse are
>> connected to the same KVM and they function.
>>
>>
>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?*
>>
>>
>>
>> dmesg | grep -iC3 wacom
>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>> ARC-1883
>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   12.880731] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>> [   12.881334] AES CTR mode by8 optimization enabled
>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>> --
>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>> [   13.481560] usbcore: registered new interface driver wacom
>> [   13.927161] XFS (sda1): Ending clean mount
>> [   14.332635] device-mapper: uevent: version 1.0.3
>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>> initialised: [hidden email] <mailto:[hidden email]>
>> --
>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16015.787635] usb 1-1.3: Product: PTZ-930
>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>> [16015.789094] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>> xhci_hcd
>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>> idProduct=00b2
>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16216.780258] usb 1-1.3: Product: PTZ-930
>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>> [16216.781286] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>> id=0010
>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>> status/mask=00000080/00002000
>>
>>
>>
>> *Additionally, please try installing the evemu[1] package and then*
>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
>> *over the KVM. After selecting the Intuos3 from the list of devices*
>> *detected by evemu-record (let us know if the tablet is not detected),*
>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>> *generated log file for revie*w.
>>
>>
>>
>> Log attached.  I added additional input from the wheel mouse on the
>> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>>
>>
>>
>> Thanks Jason for your help!
>>
>>
>>
>> Joey
>>
>>
>>
>>
>>
>>
>>
>> *From:*Jason Gerecke <[hidden email] <mailto:[hidden email]>>
>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>> *To:* Joey Tucker; [hidden email]
>> <mailto:[hidden email]>
>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS 7.2
>>
>>
>>
>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>> Hello,
>>>
>>>
>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>> like a newbe.
>>>
>>>
>>> Here's my setup:
>>>
>>>
>>> I work for a small production company that uses numerous OSs (Window,
>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>> are connected to a Avocent HMX KVM system and has been working
>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>> mentioned.
>>>
>>>
>>> Recently, we purchased a new machine to run the latest version of
>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>> ... again, wacom works with the Avocent and this workstation)  The new
>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>> with the machine locally and it functioned normally.  When the new
>>> machine arrived, we integrated it into our Avocent KVM system and the
>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>> itself and loads it's driver. (I think)
>>>
>>>
>>> With my limited knowledge, I put together some command line queries that
>>> might help in troubleshooting.  Any ideas or help would be much
>>> appreciated.  See the list below:
>>>
>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>> U: Uniq=
>>> H: Handlers=mouse2 event22
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>> xsetwacom --list devices (wacom plugged into workstation)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>
>>>
>>> lsusb (wacom plugged into workstation)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>
>>>
>>>
>>>
>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S:
>>>
>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>> U: Uniq=
>>> H: Handlers=mouse1 event5
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>>
>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>
>>>
>>> lsusb (wacom through the Avocent KVM)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Joey
>>>
>>
>> Joey,
>>
>> It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?
>>
>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?
>>
>> Additionally, please try installing the evemu[1] package and then
>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>> over the KVM. After selecting the Intuos3 from the list of devices
>> detected by evemu-record (let us know if the tablet is not detected),
>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>> generated log file for review.
>>
>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>
>> --
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>

------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

debug_0.32.0_v1.patch (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

Hi Jason and thanks for your efforts!


First .... I downloaded the tarball, extracted it to a folder then dropped the patch in the folder one layer up the folder tree.  I'm applying the patch as root and the command seems to be hung.  Any ideas?


Thanks!


Joey Tucker
 



From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 15, 2016 2:37 PM
To: Joey Tucker
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 
Apologies for the longer-than-expected delay...

Please download the input-wacom 0.32.0 tarball and install any build
pre-requisites as outlined at
http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Before building, apply the attached patch by running `patch -p1 <
path/to/debug_0.32.0_v1.patch` from within the extracted
input-wacom-0.32.0 directory. This will add a number of debug
statements that should help me trace what is going on with your
system. You can then build and manually load the module by using `sudo
modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
install` step since this is a temporary debug build).

Once the module has been loaded, run `sudo tail -f /var/log/messages |
tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
should see some log output about the tablet being attached. Touch the
pen to the tablet surface and you should see lines prefixed with
"wacom_sys_irq" scroll by. After a second or so, remove the pen,
disconnect the tablet through the KVM, and press CTRL+C to stop the
log. Attach the generated debug_v1.log file for me to review.

The output should contain information about the status of the tablet
and the complete contents of any packets that it sends. This should
give me an idea of if the tablet is not being initialized properly, if
the data is incorrect, or if the functions are misbehaving.



Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:
> No problem, Jason.  You're help is greatly appreciated!
>
>
> I had suspected a driver issue but really wasn't sure because of my limited
> knowledge.
>
>
> In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS
> versions of the following distros and had success with the wacom through the
> KVM:
>
>
> Ubuntu 16.10
>
> Linux Mint 17
>
> Fedora 24
>
>
> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
> failure.
>
>
> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
> compare.
>
>
> Let me know how I can help.
>
>
> Thanks!
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 1, 2016 5:07 PM
> To: Joey Tucker; [hidden email]
> Cc: Jason Starne
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Thanks for running those tests for me, Joey. Looking through the
> attached log, I see that it is missing the events that should be sent by
> the tablet in response to input from the pen/mouse. In the past we've
> seen issues like this caused by KVMs that attempt to treat the tablet
> like a mouse (which it boots up emulating, and is unusable by our driver
> until we send it a command to switch modes) rather than a generic USB
> device.
>
> If your Avocent KVM works with CentOS 6 systems, it would seem that you
> are experiencing a different issue. It must be KVM-related somehow since
> the Intuos3 works when locally connected, but we will need to do some
> additional debugging to locate the cause.
>
> The kernel driver does not contain debug messages along the codepaths
> that I suspect are affected, so I will need to provide you with some
> patches to our input-wacom kernel driver that should provide more
> illumination. It will take some time to write these patches; expect a
> follow-up in a day or so. In the meantime, I would suggest familiarizing
> yourself with the process of building and installing[1] the driver. Feel
> free to ask questions if the instructions are unclear.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>> Thank you so much, Jason for writing back!
>>
>>
>>
>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>> integrator of the CentOS 7 system we purchased.
>>
>>
>>
>> *It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?*
>>
>>
>>
>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>> there.  Status LED responds to input.  Also a keyboard and mouse are
>> connected to the same KVM and they function.
>>
>>
>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?*
>>
>>
>>
>> dmesg | grep -iC3 wacom
>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>> ARC-1883
>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   12.880731] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>> [   12.881334] AES CTR mode by8 optimization enabled
>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>> --
>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>> [   13.481560] usbcore: registered new interface driver wacom
>> [   13.927161] XFS (sda1): Ending clean mount
>> [   14.332635] device-mapper: uevent: version 1.0.3
>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>> initialised: [hidden email] <[hidden email]>
>> --
>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16015.787635] usb 1-1.3: Product: PTZ-930
>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>> [16015.789094] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>> xhci_hcd
>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>> idProduct=00b2
>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16216.780258] usb 1-1.3: Product: PTZ-930
>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>> [16216.781286] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>> id=0010
>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>> status/mask=00000080/00002000
>>
>>
>>
>> *Additionally, please try installing the evemu[1] package and then*
>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
>> *over the KVM. After selecting the Intuos3 from the list of devices*
>> *detected by evemu-record (let us know if the tablet is not detected),*
>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>> *generated log file for revie*w.
>>
>>
>>
>> Log attached.  I added additional input from the wheel mouse on the
>> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>>
>>
>>
>> Thanks Jason for your help!
>>
>>
>>
>> Joey
>>
>>
>>
>>
>>
>>
>>
>> *From:*Jason Gerecke <[hidden email] <[hidden email]>>
>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>> *To:* Joey Tucker; [hidden email]
>> <[hidden email]>
>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS 7.2
>>
>>
>>
>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>> Hello,
>>>
>>>
>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>> like a newbe.
>>>
>>>
>>> Here's my setup:
>>>
>>>
>>> I work for a small production company that uses numerous OSs (Window,
>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>> are connected to a Avocent HMX KVM system and has been working
>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>> mentioned.
>>>
>>>
>>> Recently, we purchased a new machine to run the latest version of
>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>> ... again, wacom works with the Avocent and this workstation)  The new
>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>> with the machine locally and it functioned normally.  When the new
>>> machine arrived, we integrated it into our Avocent KVM system and the
>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>> itself and loads it's driver. (I think)
>>>
>>>
>>> With my limited knowledge, I put together some command line queries that
>>> might help in troubleshooting.  Any ideas or help would be much
>>> appreciated.  See the list below:
>>>
>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>> U: Uniq=
>>> H: Handlers=mouse2 event22
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>> xsetwacom --list devices (wacom plugged into workstation)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>
>>>
>>> lsusb (wacom plugged into workstation)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>
>>>
>>>
>>>
>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S:
>>>
>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>> U: Uniq=
>>> H: Handlers=mouse1 event5
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>>
>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>
>>>
>>> lsusb (wacom through the Avocent KVM)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Joey
>>>
>>
>> Joey,
>>
>> It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?
>>
>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?
>>
>> Additionally, please try installing the evemu[1] package and then
>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>> over the KVM. After selecting the Intuos3 from the list of devices
>> detected by evemu-record (let us know if the tablet is not detected),
>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>> generated log file for review.
>>
>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>
>> --
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>

------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

Never mind on the patch install.  Syntax error.  Results of test coming later.


Thanks.


Joey Tucker
 



From: Joey Tucker <[hidden email]>
Sent: Tuesday, November 15, 2016 3:29 PM
To: Jason Gerecke
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 

Hi Jason and thanks for your efforts!


First .... I downloaded the tarball, extracted it to a folder then dropped the patch in the folder one layer up the folder tree.  I'm applying the patch as root and the command seems to be hung.  Any ideas?


Thanks!


Joey Tucker
 



From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 15, 2016 2:37 PM
To: Joey Tucker
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 
Apologies for the longer-than-expected delay...

Please download the input-wacom 0.32.0 tarball and install any build
pre-requisites as outlined at
http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Before building, apply the attached patch by running `patch -p1 <
path/to/debug_0.32.0_v1.patch` from within the extracted
input-wacom-0.32.0 directory. This will add a number of debug
statements that should help me trace what is going on with your
system. You can then build and manually load the module by using `sudo
modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
install` step since this is a temporary debug build).

Once the module has been loaded, run `sudo tail -f /var/log/messages |
tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
should see some log output about the tablet being attached. Touch the
pen to the tablet surface and you should see lines prefixed with
"wacom_sys_irq" scroll by. After a second or so, remove the pen,
disconnect the tablet through the KVM, and press CTRL+C to stop the
log. Attach the generated debug_v1.log file for me to review.

The output should contain information about the status of the tablet
and the complete contents of any packets that it sends. This should
give me an idea of if the tablet is not being initialized properly, if
the data is incorrect, or if the functions are misbehaving.



Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:
> No problem, Jason.  You're help is greatly appreciated!
>
>
> I had suspected a driver issue but really wasn't sure because of my limited
> knowledge.
>
>
> In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS
> versions of the following distros and had success with the wacom through the
> KVM:
>
>
> Ubuntu 16.10
>
> Linux Mint 17
>
> Fedora 24
>
>
> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
> failure.
>
>
> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
> compare.
>
>
> Let me know how I can help.
>
>
> Thanks!
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 1, 2016 5:07 PM
> To: Joey Tucker; [hidden email]
> Cc: Jason Starne
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Thanks for running those tests for me, Joey. Looking through the
> attached log, I see that it is missing the events that should be sent by
> the tablet in response to input from the pen/mouse. In the past we've
> seen issues like this caused by KVMs that attempt to treat the tablet
> like a mouse (which it boots up emulating, and is unusable by our driver
> until we send it a command to switch modes) rather than a generic USB
> device.
>
> If your Avocent KVM works with CentOS 6 systems, it would seem that you
> are experiencing a different issue. It must be KVM-related somehow since
> the Intuos3 works when locally connected, but we will need to do some
> additional debugging to locate the cause.
>
> The kernel driver does not contain debug messages along the codepaths
> that I suspect are affected, so I will need to provide you with some
> patches to our input-wacom kernel driver that should provide more
> illumination. It will take some time to write these patches; expect a
> follow-up in a day or so. In the meantime, I would suggest familiarizing
> yourself with the process of building and installing[1] the driver. Feel
> free to ask questions if the instructions are unclear.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>> Thank you so much, Jason for writing back!
>>
>>
>>
>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>> integrator of the CentOS 7 system we purchased.
>>
>>
>>
>> *It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?*
>>
>>
>>
>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>> there.  Status LED responds to input.  Also a keyboard and mouse are
>> connected to the same KVM and they function.
>>
>>
>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?*
>>
>>
>>
>> dmesg | grep -iC3 wacom
>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>> ARC-1883
>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   12.880731] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>> [   12.881334] AES CTR mode by8 optimization enabled
>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>> --
>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>> [   13.481560] usbcore: registered new interface driver wacom
>> [   13.927161] XFS (sda1): Ending clean mount
>> [   14.332635] device-mapper: uevent: version 1.0.3
>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>> initialised: [hidden email] <[hidden email]>
>> --
>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16015.787635] usb 1-1.3: Product: PTZ-930
>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>> [16015.789094] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>> xhci_hcd
>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>> idProduct=00b2
>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16216.780258] usb 1-1.3: Product: PTZ-930
>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>> [16216.781286] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>> id=0010
>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>> status/mask=00000080/00002000
>>
>>
>>
>> *Additionally, please try installing the evemu[1] package and then*
>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
>> *over the KVM. After selecting the Intuos3 from the list of devices*
>> *detected by evemu-record (let us know if the tablet is not detected),*
>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>> *generated log file for revie*w.
>>
>>
>>
>> Log attached.  I added additional input from the wheel mouse on the
>> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>>
>>
>>
>> Thanks Jason for your help!
>>
>>
>>
>> Joey
>>
>>
>>
>>
>>
>>
>>
>> *From:*Jason Gerecke <[hidden email] <[hidden email]>>
>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>> *To:* Joey Tucker; [hidden email]
>> <[hidden email]>
>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS 7.2
>>
>>
>>
>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>> Hello,
>>>
>>>
>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>> like a newbe.
>>>
>>>
>>> Here's my setup:
>>>
>>>
>>> I work for a small production company that uses numerous OSs (Window,
>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>> are connected to a Avocent HMX KVM system and has been working
>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>> mentioned.
>>>
>>>
>>> Recently, we purchased a new machine to run the latest version of
>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>> ... again, wacom works with the Avocent and this workstation)  The new
>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>> with the machine locally and it functioned normally.  When the new
>>> machine arrived, we integrated it into our Avocent KVM system and the
>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>> itself and loads it's driver. (I think)
>>>
>>>
>>> With my limited knowledge, I put together some command line queries that
>>> might help in troubleshooting.  Any ideas or help would be much
>>> appreciated.  See the list below:
>>>
>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>> U: Uniq=
>>> H: Handlers=mouse2 event22
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>> xsetwacom --list devices (wacom plugged into workstation)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>
>>>
>>> lsusb (wacom plugged into workstation)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>
>>>
>>>
>>>
>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S:
>>>
>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>> U: Uniq=
>>> H: Handlers=mouse1 event5
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>>
>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>
>>>
>>> lsusb (wacom through the Avocent KVM)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Joey
>>>
>>
>> Joey,
>>
>> It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?
>>
>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?
>>
>> Additionally, please try installing the evemu[1] package and then
>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>> over the KVM. After selecting the Intuos3 from the list of devices
>> detected by evemu-record (let us know if the tablet is not detected),
>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>> generated log file for review.
>>
>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>
>> --
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>

------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

Actually I'm stuck at "insmod 3.7/wacom.ko"  File is missing.


Joey Tucker
 



From: Joey Tucker <[hidden email]>
Sent: Tuesday, November 15, 2016 3:57 PM
To: Jason Gerecke
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 

Never mind on the patch install.  Syntax error.  Results of test coming later.


Thanks.


Joey Tucker
 



From: Joey Tucker <[hidden email]>
Sent: Tuesday, November 15, 2016 3:29 PM
To: Jason Gerecke
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 

Hi Jason and thanks for your efforts!


First .... I downloaded the tarball, extracted it to a folder then dropped the patch in the folder one layer up the folder tree.  I'm applying the patch as root and the command seems to be hung.  Any ideas?


Thanks!


Joey Tucker
 



From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 15, 2016 2:37 PM
To: Joey Tucker
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 
Apologies for the longer-than-expected delay...

Please download the input-wacom 0.32.0 tarball and install any build
pre-requisites as outlined at
http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Before building, apply the attached patch by running `patch -p1 <
path/to/debug_0.32.0_v1.patch` from within the extracted
input-wacom-0.32.0 directory. This will add a number of debug
statements that should help me trace what is going on with your
system. You can then build and manually load the module by using `sudo
modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
install` step since this is a temporary debug build).

Once the module has been loaded, run `sudo tail -f /var/log/messages |
tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
should see some log output about the tablet being attached. Touch the
pen to the tablet surface and you should see lines prefixed with
"wacom_sys_irq" scroll by. After a second or so, remove the pen,
disconnect the tablet through the KVM, and press CTRL+C to stop the
log. Attach the generated debug_v1.log file for me to review.

The output should contain information about the status of the tablet
and the complete contents of any packets that it sends. This should
give me an idea of if the tablet is not being initialized properly, if
the data is incorrect, or if the functions are misbehaving.



Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:
> No problem, Jason.  You're help is greatly appreciated!
>
>
> I had suspected a driver issue but really wasn't sure because of my limited
> knowledge.
>
>
> In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS
> versions of the following distros and had success with the wacom through the
> KVM:
>
>
> Ubuntu 16.10
>
> Linux Mint 17
>
> Fedora 24
>
>
> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
> failure.
>
>
> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
> compare.
>
>
> Let me know how I can help.
>
>
> Thanks!
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 1, 2016 5:07 PM
> To: Joey Tucker; [hidden email]
> Cc: Jason Starne
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Thanks for running those tests for me, Joey. Looking through the
> attached log, I see that it is missing the events that should be sent by
> the tablet in response to input from the pen/mouse. In the past we've
> seen issues like this caused by KVMs that attempt to treat the tablet
> like a mouse (which it boots up emulating, and is unusable by our driver
> until we send it a command to switch modes) rather than a generic USB
> device.
>
> If your Avocent KVM works with CentOS 6 systems, it would seem that you
> are experiencing a different issue. It must be KVM-related somehow since
> the Intuos3 works when locally connected, but we will need to do some
> additional debugging to locate the cause.
>
> The kernel driver does not contain debug messages along the codepaths
> that I suspect are affected, so I will need to provide you with some
> patches to our input-wacom kernel driver that should provide more
> illumination. It will take some time to write these patches; expect a
> follow-up in a day or so. In the meantime, I would suggest familiarizing
> yourself with the process of building and installing[1] the driver. Feel
> free to ask questions if the instructions are unclear.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>> Thank you so much, Jason for writing back!
>>
>>
>>
>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>> integrator of the CentOS 7 system we purchased.
>>
>>
>>
>> *It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?*
>>
>>
>>
>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>> there.  Status LED responds to input.  Also a keyboard and mouse are
>> connected to the same KVM and they function.
>>
>>
>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?*
>>
>>
>>
>> dmesg | grep -iC3 wacom
>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>> ARC-1883
>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   12.880731] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>> [   12.881334] AES CTR mode by8 optimization enabled
>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>> --
>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>> [   13.481560] usbcore: registered new interface driver wacom
>> [   13.927161] XFS (sda1): Ending clean mount
>> [   14.332635] device-mapper: uevent: version 1.0.3
>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>> initialised: [hidden email] <[hidden email]>
>> --
>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16015.787635] usb 1-1.3: Product: PTZ-930
>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>> [16015.789094] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>> xhci_hcd
>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>> idProduct=00b2
>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16216.780258] usb 1-1.3: Product: PTZ-930
>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>> [16216.781286] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>> id=0010
>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>> status/mask=00000080/00002000
>>
>>
>>
>> *Additionally, please try installing the evemu[1] package and then*
>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
>> *over the KVM. After selecting the Intuos3 from the list of devices*
>> *detected by evemu-record (let us know if the tablet is not detected),*
>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>> *generated log file for revie*w.
>>
>>
>>
>> Log attached.  I added additional input from the wheel mouse on the
>> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>>
>>
>>
>> Thanks Jason for your help!
>>
>>
>>
>> Joey
>>
>>
>>
>>
>>
>>
>>
>> *From:*Jason Gerecke <[hidden email] <[hidden email]>>
>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>> *To:* Joey Tucker; [hidden email]
>> <[hidden email]>
>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS 7.2
>>
>>
>>
>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>> Hello,
>>>
>>>
>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>> like a newbe.
>>>
>>>
>>> Here's my setup:
>>>
>>>
>>> I work for a small production company that uses numerous OSs (Window,
>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>> are connected to a Avocent HMX KVM system and has been working
>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>> mentioned.
>>>
>>>
>>> Recently, we purchased a new machine to run the latest version of
>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>> ... again, wacom works with the Avocent and this workstation)  The new
>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>> with the machine locally and it functioned normally.  When the new
>>> machine arrived, we integrated it into our Avocent KVM system and the
>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>> itself and loads it's driver. (I think)
>>>
>>>
>>> With my limited knowledge, I put together some command line queries that
>>> might help in troubleshooting.  Any ideas or help would be much
>>> appreciated.  See the list below:
>>>
>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>> U: Uniq=
>>> H: Handlers=mouse2 event22
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>> xsetwacom --list devices (wacom plugged into workstation)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>
>>>
>>> lsusb (wacom plugged into workstation)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>
>>>
>>>
>>>
>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S:
>>>
>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>> U: Uniq=
>>> H: Handlers=mouse1 event5
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>>
>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>
>>>
>>> lsusb (wacom through the Avocent KVM)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Joey
>>>
>>
>> Joey,
>>
>> It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?
>>
>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?
>>
>> Additionally, please try installing the evemu[1] package and then
>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>> over the KVM. After selecting the Intuos3 from the list of devices
>> detected by evemu-record (let us know if the tablet is not detected),
>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>> generated log file for review.
>>
>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>
>> --
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>

------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker
In reply to this post by Jason Gerecke

Jason,


Please ignore the previous messages.  I failed to read through all the prerequisites for building the patched driver.  After I followed instructions, It worked flawlessly and I was able to use the wacom tablet on the Avocent.  Attached is the debug log.


Thank you, Jason.


Joey Tucker
 



From: Jason Gerecke <[hidden email]>
Sent: Tuesday, November 15, 2016 2:37 PM
To: Joey Tucker
Cc: [hidden email]; Jason Starne
Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2
 
Apologies for the longer-than-expected delay...

Please download the input-wacom 0.32.0 tarball and install any build
pre-requisites as outlined at
http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

Before building, apply the attached patch by running `patch -p1 <
path/to/debug_0.32.0_v1.patch` from within the extracted
input-wacom-0.32.0 directory. This will add a number of debug
statements that should help me trace what is going on with your
system. You can then build and manually load the module by using `sudo
modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
install` step since this is a temporary debug build).

Once the module has been loaded, run `sudo tail -f /var/log/messages |
tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
should see some log output about the tablet being attached. Touch the
pen to the tablet surface and you should see lines prefixed with
"wacom_sys_irq" scroll by. After a second or so, remove the pen,
disconnect the tablet through the KVM, and press CTRL+C to stop the
log. Attach the generated debug_v1.log file for me to review.

The output should contain information about the status of the tablet
and the complete contents of any packets that it sends. This should
give me an idea of if the tablet is not being initialized properly, if
the data is incorrect, or if the functions are misbehaving.



Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:
> No problem, Jason.  You're help is greatly appreciated!
>
>
> I had suspected a driver issue but really wasn't sure because of my limited
> knowledge.
>
>
> In my attempt to try and isolate the problem to CentOS 7.2, I loaded liveOS
> versions of the following distros and had success with the wacom through the
> KVM:
>
>
> Ubuntu 16.10
>
> Linux Mint 17
>
> Fedora 24
>
>
> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
> failure.
>
>
> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
> compare.
>
>
> Let me know how I can help.
>
>
> Thanks!
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 1, 2016 5:07 PM
> To: Joey Tucker; [hidden email]
> Cc: Jason Starne
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Thanks for running those tests for me, Joey. Looking through the
> attached log, I see that it is missing the events that should be sent by
> the tablet in response to input from the pen/mouse. In the past we've
> seen issues like this caused by KVMs that attempt to treat the tablet
> like a mouse (which it boots up emulating, and is unusable by our driver
> until we send it a command to switch modes) rather than a generic USB
> device.
>
> If your Avocent KVM works with CentOS 6 systems, it would seem that you
> are experiencing a different issue. It must be KVM-related somehow since
> the Intuos3 works when locally connected, but we will need to do some
> additional debugging to locate the cause.
>
> The kernel driver does not contain debug messages along the codepaths
> that I suspect are affected, so I will need to provide you with some
> patches to our input-wacom kernel driver that should provide more
> illumination. It will take some time to write these patches; expect a
> follow-up in a day or so. In the meantime, I would suggest familiarizing
> yourself with the process of building and installing[1] the driver. Feel
> free to ask questions if the instructions are unclear.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>> Thank you so much, Jason for writing back!
>>
>>
>>
>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>> integrator of the CentOS 7 system we purchased.
>>
>>
>>
>> *It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?*
>>
>>
>>
>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>> there.  Status LED responds to input.  Also a keyboard and mouse are
>> connected to the same KVM and they function.
>>
>>
>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?*
>>
>>
>>
>> dmesg | grep -iC3 wacom
>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>> ARC-1883
>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   12.880731] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>> [   12.881334] AES CTR mode by8 optimization enabled
>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>> --
>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>
>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>> [   13.481560] usbcore: registered new interface driver wacom
>> [   13.927161] XFS (sda1): Ending clean mount
>> [   14.332635] device-mapper: uevent: version 1.0.3
>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>> initialised: [hidden email] <[hidden email]>
>> --
>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16015.787635] usb 1-1.3: Product: PTZ-930
>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>> [16015.789094] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>> xhci_hcd
>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>> idProduct=00b2
>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=0
>> [16216.780258] usb 1-1.3: Product: PTZ-930
>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>> [16216.781286] input: Wacom Intuos3 9x12 as
>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>> id=0010
>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>> status/mask=00000080/00002000
>>
>>
>>
>> *Additionally, please try installing the evemu[1] package and then*
>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected*
>> *over the KVM. After selecting the Intuos3 from the list of devices*
>> *detected by evemu-record (let us know if the tablet is not detected),*
>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>> *generated log file for revie*w.
>>
>>
>>
>> Log attached.  I added additional input from the wheel mouse on the
>> tablet as well.  If I over-did it, let me know and I’ll do a shorter test.
>>
>>
>>
>> Thanks Jason for your help!
>>
>>
>>
>> Joey
>>
>>
>>
>>
>>
>>
>>
>> *From:*Jason Gerecke <[hidden email] <[hidden email]>>
>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>> *To:* Joey Tucker; [hidden email]
>> <[hidden email]>
>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS 7.2
>>
>>
>>
>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>> Hello,
>>>
>>>
>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>> like a newbe.
>>>
>>>
>>> Here's my setup:
>>>
>>>
>>> I work for a small production company that uses numerous OSs (Window,
>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>> are connected to a Avocent HMX KVM system and has been working
>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>> mentioned.
>>>
>>>
>>> Recently, we purchased a new machine to run the latest version of
>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>> ... again, wacom works with the Avocent and this workstation)  The new
>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>> with the machine locally and it functioned normally.  When the new
>>> machine arrived, we integrated it into our Avocent KVM system and the
>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>> itself and loads it's driver. (I think)
>>>
>>>
>>> With my limited knowledge, I put together some command line queries that
>>> might help in troubleshooting.  Any ideas or help would be much
>>> appreciated.  See the list below:
>>>
>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>> U: Uniq=
>>> H: Handlers=mouse2 event22
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>> xsetwacom --list devices (wacom plugged into workstation)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>
>>>
>>> lsusb (wacom plugged into workstation)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>
>>>
>>>
>>>
>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>
>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>> N: Name="Wacom Intuos3 9x12"
>>> P: Phys=
>>> S:
>>>
>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>> U: Uniq=
>>> H: Handlers=mouse1 event5
>>> B: PROP=1
>>> B: EV=1f
>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>> B: REL=100
>>> B: ABS=1000f00017f
>>> B: MSC=1
>>>
>>>
>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>
>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>
>>>
>>> lsusb (wacom through the Avocent KVM)
>>>
>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>> SuperSpeed hub
>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>> High-Speed hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Joey
>>>
>>
>> Joey,
>>
>> It does indeed appear that the device is being forwarded over the KVM
>> link, so could you please describe in a bit more detail what is not
>> working?
>>
>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>> review?
>>
>> Additionally, please try installing the evemu[1] package and then
>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>> over the KVM. After selecting the Intuos3 from the list of devices
>> detected by evemu-record (let us know if the tablet is not detected),
>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>> generated log file for review.
>>
>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>
>> --
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>

------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

debug_v1.log (912K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Jason Gerecke
Glad you finally got it working :) The log looks good, very nearly
matching what I see when connecting an Intuos3 to a CentOS 7 VM.
Unfortunately, I don't see anything that would indicate why you aren't
seeing events. The tablet is clearly being initialized properly and
sending a valid stream of pen events to the kernel. The kernel,
furthermore, should be sending the right signal to flush the input
event buffer after each event. The only odd thing I notice in the log
are two "pad" events events received immediately after the tablet
finishes connecting; in addition to the suspicious timing, both events
indicate "no buttons pressed", which I would never expect to see
back-to-back or without a "buttons pressed" packet preceeding them.
Even so, nothing in the "pad" event processing should prevent the pen
from working.

The testing you did with Ubuntu, Mint, and Fedora is interesting to
know. The versions you tested have a quite-different version of our
kernel driver so its not entirely apples-to-apples, but interesting
nonetheless. A more direct comparison would be to Debian Jessie whose
kernel driver is much more similar to what you're testing.

I'll poke around a little more with my system and see if I can think
of anything else...

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Nov 15, 2016 at 2:15 PM, Joey Tucker <[hidden email]> wrote:

> Jason,
>
>
> Please ignore the previous messages.  I failed to read through all the
> prerequisites for building the patched driver.  After I followed
> instructions, It worked flawlessly and I was able to use the wacom tablet on
> the Avocent.  Attached is the debug log.
>
>
> Thank you, Jason.
>
>
> Joey Tucker
>
>
>
> ________________________________
> From: Jason Gerecke <[hidden email]>
> Sent: Tuesday, November 15, 2016 2:37 PM
> To: Joey Tucker
> Cc: [hidden email]; Jason Starne
>
> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS
> 7.2
>
> Apologies for the longer-than-expected delay...
>
> Please download the input-wacom 0.32.0 tarball and install any build
> pre-requisites as outlined at
> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> Before building, apply the attached patch by running `patch -p1 <
> path/to/debug_0.32.0_v1.patch` from within the extracted
> input-wacom-0.32.0 directory. This will add a number of debug
> statements that should help me trace what is going on with your
> system. You can then build and manually load the module by using `sudo
> modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make
> install` step since this is a temporary debug build).
>
> Once the module has been loaded, run `sudo tail -f /var/log/messages |
> tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You
> should see some log output about the tablet being attached. Touch the
> pen to the tablet surface and you should see lines prefixed with
> "wacom_sys_irq" scroll by. After a second or so, remove the pen,
> disconnect the tablet through the KVM, and press CTRL+C to stop the
> log. Attach the generated debug_v1.log file for me to review.
>
> The output should contain information about the status of the tablet
> and the complete contents of any packets that it sends. This should
> give me an idea of if the tablet is not being initialized properly, if
> the data is incorrect, or if the functions are misbehaving.
>
>
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
>
>
>
> On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:
>> No problem, Jason.  You're help is greatly appreciated!
>>
>>
>> I had suspected a driver issue but really wasn't sure because of my
>> limited
>> knowledge.
>>
>>
>> In my attempt to try and isolate the problem to CentOS 7.2, I loaded
>> liveOS
>> versions of the following distros and had success with the wacom through
>> the
>> KVM:
>>
>>
>> Ubuntu 16.10
>>
>> Linux Mint 17
>>
>> Fedora 24
>>
>>
>> Just for giggles, I loaded a live version of CentOS 7.2 and had the same
>> failure.
>>
>>
>> If needed, I can pull logs from the functioning RHEL 6.5 system so you can
>> compare.
>>
>>
>> Let me know how I can help.
>>
>>
>> Thanks!
>>
>>
>> Joey Tucker
>>
>>
>>
>> ________________________________
>> From: Jason Gerecke <[hidden email]>
>> Sent: Tuesday, November 1, 2016 5:07 PM
>> To: Joey Tucker; [hidden email]
>> Cc: Jason Starne
>> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>> CentOS
>> 7.2
>>
>> Thanks for running those tests for me, Joey. Looking through the
>> attached log, I see that it is missing the events that should be sent by
>> the tablet in response to input from the pen/mouse. In the past we've
>> seen issues like this caused by KVMs that attempt to treat the tablet
>> like a mouse (which it boots up emulating, and is unusable by our driver
>> until we send it a command to switch modes) rather than a generic USB
>> device.
>>
>> If your Avocent KVM works with CentOS 6 systems, it would seem that you
>> are experiencing a different issue. It must be KVM-related somehow since
>> the Intuos3 works when locally connected, but we will need to do some
>> additional debugging to locate the cause.
>>
>> The kernel driver does not contain debug messages along the codepaths
>> that I suspect are affected, so I will need to provide you with some
>> patches to our input-wacom kernel driver that should provide more
>> illumination. It will take some time to write these patches; expect a
>> follow-up in a day or so. In the meantime, I would suggest familiarizing
>> yourself with the process of building and installing[1] the driver. Feel
>> free to ask questions if the instructions are unclear.
>>
>> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one /
>> (That is to say, eight) to the two, /
>> But you can’t take seven from three, /
>> So you look at the sixty-fours....
>>
>> On 11/01/2016 01:22 PM, Joey Tucker wrote:
>>> Thank you so much, Jason for writing back!
>>>
>>>
>>>
>>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the
>>> integrator of the CentOS 7 system we purchased.
>>>
>>>
>>>
>>> *It does indeed appear that the device is being forwarded over the KVM
>>> link, so could you please describe in a bit more detail what is not
>>> working?*
>>>
>>>
>>>
>>> No feedback from the tablet at all ... pen nor mouse.  However, power is
>>> there.  Status LED responds to input.  Also a keyboard and mouse are
>>> connected to the same KVM and they function.
>>>
>>>
>>> *Could you please provide the output of `dmesg | grep -iC3 wacom` for
>>> review?*
>>>
>>>
>>>
>>> dmesg | grep -iC3 wacom
>>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X
>>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model
>>> ARC-1883
>>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0
>>> [   12.880731] input: Wacom Intuos3 9x12 as
>>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5
>>> [   12.881334] AES CTR mode by8 optimization enabled
>>> [   12.883240] [drm] Initialized drm 1.1.0 20060810
>>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
>>> --
>>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as
>>>
>>>
>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19
>>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as
>>>
>>>
>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20
>>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as
>>>
>>>
>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21
>>> [   13.481560] usbcore: registered new interface driver wacom
>>> [   13.927161] XFS (sda1): Ending clean mount
>>> [   14.332635] device-mapper: uevent: version 1.0.3
>>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)
>>> initialised: [hidden email] <mailto:[hidden email]>
>>> --
>>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=0
>>> [16015.787635] usb 1-1.3: Product: PTZ-930
>>> [16015.787636] usb 1-1.3: Manufacturer: Tablet
>>> [16015.789094] input: Wacom Intuos3 9x12 as
>>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input25
>>> [16177.178260] usb 1-1.3: USB disconnect, device number 8
>>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using
>>> xhci_hcd
>>> [16216.780255] usb 1-1.3: New USB device found, idVendor=056a,
>>> idProduct=00b2
>>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=0
>>> [16216.780258] usb 1-1.3: Product: PTZ-930
>>> [16216.780259] usb 1-1.3: Manufacturer: Tablet
>>> [16216.781286] input: Wacom Intuos3 9x12 as
>>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input26
>>> [16247.216417] pcieport 0000:00:02.0: AER: Corrected error received:
>>> id=0010
>>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:
>>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
>>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error
>>> status/mask=00000080/00002000
>>>
>>>
>>>
>>> *Additionally, please try installing the evemu[1] package and then*
>>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3
>>> connected*
>>> *over the KVM. After selecting the Intuos3 from the list of devices*
>>> *detected by evemu-record (let us know if the tablet is not detected),*
>>> *draw a few strokes with the pen and then hit CTRL+C. Attach the*
>>> *generated log file for revie*w.
>>>
>>>
>>>
>>> Log attached.  I added additional input from the wheel mouse on the
>>> tablet as well.  If I over-did it, let me know and I’ll do a shorter
>>> test.
>>>
>>>
>>>
>>> Thanks Jason for your help!
>>>
>>>
>>>
>>> Joey
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:*Jason Gerecke <[hidden email] <mailto:[hidden email]>>
>>> *Sent:* Tuesday, November 1, 2016 3:40 PM
>>> *To:* Joey Tucker; [hidden email]
>>> <mailto:[hidden email]>
>>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +
>>> CentOS 7.2
>>>
>>>
>>>
>>> On 11/01/2016 09:03 AM, Joey Tucker wrote:
>>>> Hello,
>>>>
>>>>
>>>> I'm a bit of a novice when it comes to linux so pardon me if I sound
>>>> like a newbe.
>>>>
>>>>
>>>> Here's my setup:
>>>>
>>>>
>>>> I work for a small production company that uses numerous OSs (Window,
>>>> Mac, RHEL 6.5) on machines for video production.  Most of our machine
>>>> are connected to a Avocent HMX KVM system and has been working
>>>> flawlessly with wacom tablets for a number of years with all the OSs I
>>>> mentioned.
>>>>
>>>>
>>>> Recently, we purchased a new machine to run the latest version of
>>>> Autodesk Flame.  (we already have a Flame workstation running RHEL 6.5
>>>> ... again, wacom works with the Avocent and this workstation)  The new
>>>> workstation is loaded with CentOS 7.2.  The integrator tested the wacom
>>>> with the machine locally and it functioned normally.  When the new
>>>> machine arrived, we integrated it into our Avocent KVM system and the
>>>> wacom doesn't work through the KVM.  However, it shows up and identifies
>>>> itself and loads it's driver. (I think)
>>>>
>>>>
>>>> With my limited knowledge, I put together some command line queries that
>>>> might help in troubleshooting.  Any ideas or help would be much
>>>> appreciated.  See the list below:
>>>>
>>>> more /proc/bus/input/devices (wacom plugged into workstation)
>>>>
>>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>>> N: Name="Wacom Intuos3 9x12"
>>>> P: Phys=
>>>> S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input30
>>>> U: Uniq=
>>>> H: Handlers=mouse2 event22
>>>> B: PROP=1
>>>> B: EV=1f
>>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>>> B: REL=100
>>>> B: ABS=1000f00017f
>>>> B: MSC=1
>>>>
>>>> xsetwacom --list devices (wacom plugged into workstation)
>>>>
>>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER
>>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR
>>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD
>>>>
>>>>
>>>> lsusb (wacom plugged into workstation)
>>>>
>>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>>> Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>>> SuperSpeed hub
>>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>>> High-Speed hub
>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>>
>>>>
>>>>
>>>>
>>>> more /proc/bus/input/devices (wacom through the Avocent KVM)
>>>>
>>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102
>>>> N: Name="Wacom Intuos3 9x12"
>>>> P: Phys=
>>>> S:
>>>>
>>>>
>>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input27
>>>> U: Uniq=
>>>> H: Handlers=mouse1 event5
>>>> B: PROP=1
>>>> B: EV=1f
>>>> B: KEY=1cdf 1f00ff 0 0 0 0
>>>> B: REL=100
>>>> B: ABS=1000f00017f
>>>> B: MSC=1
>>>>
>>>>
>>>> xsetwacom --list devices (wacom through the Avocent KVM)
>>>>
>>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS
>>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER
>>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR
>>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD
>>>>
>>>>
>>>> lsusb (wacom through the Avocent KVM)
>>>>
>>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB 2.0 Hub
>>>> Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074
>>>> SuperSpeed hub
>>>> Bus 005 Device 002: ID 8087:800a Intel Corp.
>>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.
>>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074
>>>> High-Speed hub
>>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>> Bus 001 Device 004: ID 0624:0410 Avocent Corp.
>>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
>>>>
>>>>
>>>> Thanks!
>>>>
>>>>
>>>> Joey
>>>>
>>>
>>> Joey,
>>>
>>> It does indeed appear that the device is being forwarded over the KVM
>>> link, so could you please describe in a bit more detail what is not
>>> working?
>>>
>>> Could you please provide the output of `dmesg | grep -iC3 wacom` for
>>> review?
>>>
>>> Additionally, please try installing the evemu[1] package and then
>>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3 connected
>>> over the KVM. After selecting the Intuos3 from the list of devices
>>> detected by evemu-record (let us know if the tablet is not detected),
>>> draw a few strokes with the pen and then hit CTRL+C. Attach the
>>> generated log file for review.
>>>
>>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826
>>>
>>> --
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one /
>>> (That is to say, eight) to the two, /
>>> But you can’t take seven from three, /
>>> So you look at the sixty-fours....
>>>

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

Joey Tucker

Hi Jason,

 

Again, thanks for your continued help!

 

You mentioned a comparison to Debian for Wacom functionality.  I loaded both Jesse KDE and Jesse Gnome on my test platform and the Wacom tablet worked through the KVM for both OS versions.  BTW … I noticed there are “Wacom” tablet “settings” in all the Gnome versions and no settings in all the KDE versions.  Is this unique to KDE in general?

 

Thanks!

 

Joey Tucker

 

 

-----Original Message-----

From: Jason Gerecke [mailto:[hidden email]]

Sent: Wednesday, November 16, 2016 12:21 PM

To: Joey Tucker

Cc: [hidden email]; Jason Starne

Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM + CentOS 7.2

 

Glad you finally got it working :) The log looks good, very nearly matching what I see when connecting an Intuos3 to a CentOS 7 VM.

Unfortunately, I don't see anything that would indicate why you aren't seeing events. The tablet is clearly being initialized properly and sending a valid stream of pen events to the kernel. The kernel, furthermore, should be sending the right signal to flush the input event buffer after each event. The only odd thing I notice in the log are two "pad" events events received immediately after the tablet finishes connecting; in addition to the suspicious timing, both events indicate "no buttons pressed", which I would never expect to see back-to-back or without a "buttons pressed" packet preceeding them.

Even so, nothing in the "pad" event processing should prevent the pen from working.

 

The testing you did with Ubuntu, Mint, and Fedora is interesting to know. The versions you tested have a quite-different version of our kernel driver so its not entirely apples-to-apples, but interesting nonetheless. A more direct comparison would be to Debian Jessie whose kernel driver is much more similar to what you're testing.

 

I'll poke around a little more with my system and see if I can think of anything else...

 

Jason

---

Now instead of four in the eights place / you’ve got three, ‘Cause you added one  /

(That is to say, eight) to the two,     /

But you can’t take seven from three,    /

So you look at the sixty-fours....

 

 

 

On Tue, Nov 15, 2016 at 2:15 PM, Joey Tucker <[hidden email]> wrote:

> Jason,

> 

> 

> Please ignore the previous messages.  I failed to read through all the

> prerequisites for building the patched driver.  After I followed

> instructions, It worked flawlessly and I was able to use the wacom

> tablet on the Avocent.  Attached is the debug log.

> 

> 

> Thank you, Jason.

> 

> 

> Joey Tucker

> 

> 

> 

> ________________________________

> From: Jason Gerecke <[hidden email]>

> Sent: Tuesday, November 15, 2016 2:37 PM

> To: Joey Tucker

> Cc: [hidden email]; Jason Starne

> 

> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +

> CentOS

> 7.2

> 

> Apologies for the longer-than-expected delay...

> 

> Please download the input-wacom 0.32.0 tarball and install any build

> pre-requisites as outlined at

> http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

> 

> Before building, apply the attached patch by running `patch -p1 <

> path/to/debug_0.32.0_v1.patch` from within the extracted

> input-wacom-0.32.0 directory. This will add a number of debug

> statements that should help me trace what is going on with your

> system. You can then build and manually load the module by using `sudo

> modprobe -r wacom && sudo insmod 3.7/wacom.ko` (please skip the `make

> install` step since this is a temporary debug build).

> 

> Once the module has been loaded, run `sudo tail -f /var/log/messages |

> tee debug_v1.log`. Next, connect the Intuos3 through your KVM. You

> should see some log output about the tablet being attached. Touch the

> pen to the tablet surface and you should see lines prefixed with

> "wacom_sys_irq" scroll by. After a second or so, remove the pen,

> disconnect the tablet through the KVM, and press CTRL+C to stop the

> log. Attach the generated debug_v1.log file for me to review.

> 

> The output should contain information about the status of the tablet

> and the complete contents of any packets that it sends. This should

> give me an idea of if the tablet is not being initialized properly, if

> the data is incorrect, or if the functions are misbehaving.

> 

> 

> 

> Jason

> ---

> Now instead of four in the eights place / you’ve got three, ‘Cause you

> added one  /

> (That is to say, eight) to the two,     /

> But you can’t take seven from three,    /

> So you look at the sixty-fours....

> 

> 

> 

> On Tue, Nov 1, 2016 at 2:25 PM, Joey Tucker <[hidden email]> wrote:

>> No problem, Jason.  You're help is greatly appreciated!

>> 

>> 

>> I had suspected a driver issue but really wasn't sure because of my

>> limited knowledge.

>> 

>> 

>> In my attempt to try and isolate the problem to CentOS 7.2, I loaded

>> liveOS versions of the following distros and had success with the

>> wacom through the

>> KVM:

>> 

>> 

>> Ubuntu 16.10

>> 

>> Linux Mint 17

>> 

>> Fedora 24

>> 

>> 

>> Just for giggles, I loaded a live version of CentOS 7.2 and had the

>> same failure.

>> 

>> 

>> If needed, I can pull logs from the functioning RHEL 6.5 system so

>> you can compare.

>> 

>> 

>> Let me know how I can help.

>> 

>> 

>> Thanks!

>> 

>> 

>> Joey Tucker

>> 

>> 

>> 

>> ________________________________

>> From: Jason Gerecke <[hidden email]>

>> Sent: Tuesday, November 1, 2016 5:07 PM

>> To: Joey Tucker; [hidden email]

>> Cc: Jason Starne

>> Subject: Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX KVM +

>> CentOS

>> 7.2

>> 

>> Thanks for running those tests for me, Joey. Looking through the

>> attached log, I see that it is missing the events that should be sent

>> by the tablet in response to input from the pen/mouse. In the past

>> we've seen issues like this caused by KVMs that attempt to treat the

>> tablet like a mouse (which it boots up emulating, and is unusable by

>> our driver until we send it a command to switch modes) rather than a

>> generic USB device.

>> 

>> If your Avocent KVM works with CentOS 6 systems, it would seem that

>> you are experiencing a different issue. It must be KVM-related

>> somehow since the Intuos3 works when locally connected, but we will

>> need to do some additional debugging to locate the cause.

>> 

>> The kernel driver does not contain debug messages along the codepaths

>> that I suspect are affected, so I will need to provide you with some

>> patches to our input-wacom kernel driver that should provide more

>> illumination. It will take some time to write these patches; expect a

>> follow-up in a day or so. In the meantime, I would suggest

>> familiarizing yourself with the process of building and installing[1]

>> the driver. Feel free to ask questions if the instructions are unclear.

>> 

>> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

>> 

>> Jason

>> ---

>> Now instead of four in the eights place / you’ve got three, ‘Cause

>> you added one / (That is to say, eight) to the two, / But you can’t

>> take seven from three, / So you look at the sixty-fours....

>> 

>> On 11/01/2016 01:22 PM, Joey Tucker wrote:

>>> Thank you so much, Jason for writing back!

>>> 

>>> 

>>> 

>>> I've added a CC to Jason Starne of Cinesys, Inc.  His company is the

>>> integrator of the CentOS 7 system we purchased.

>>> 

>>> 

>>> 

>>> *It does indeed appear that the device is being forwarded over the

>>> KVM link, so could you please describe in a bit more detail what is

>>> not

>>> working?*

>>> 

>>> 

>>> 

>>> No feedback from the tablet at all ... pen nor mouse.  However,

>>> power is there.  Status LED responds to input.  Also a keyboard and

>>> mouse are connected to the same KVM and they function.

>>> 

>>> 

>>> *Could you please provide the output of `dmesg | grep -iC3 wacom`

>>> for

>>> review?*

>>> 

>>> 

>>> 

>>> dmesg | grep -iC3 wacom

>>> [   12.850406] mei_me 0000:00:16.0: irq 94 for MSI/MSI-X

>>> [   12.879027] Areca RAID Controller1: F/W V1.53 2016-02-16 & Model

>>> ARC-1883

>>> [   12.879853] sd 0:0:0:0: Attached scsi generic sg0 type 0

>>> [   12.880731] input: Wacom Intuos3 9x12 as

>>> /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input5

>>> [   12.881334] AES CTR mode by8 optimization enabled

>>> [   12.883240] [drm] Initialized drm 1.1.0 20060810

>>> [   12.883967] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)

>>> --

>>> [   13.274613] input: HDA NVidia HDMI/DP,pcm=7 as

>>> 

>>> 

>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input19

>>> [   13.275253] input: HDA NVidia HDMI/DP,pcm=8 as

>>> 

>>> 

>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input20

>>> [   13.275759] input: HDA NVidia HDMI/DP,pcm=9 as

>>> 

>>> 

>>> /devices/pci0000:00/0000:00:03.0/0000:03:00.0/0000:04:08.0/0000:06:00.1/sound/card1/input21

>>> [   13.481560] usbcore: registered new interface driver wacom

>>> [   13.927161] XFS (sda1): Ending clean mount

>>> [   14.332635] device-mapper: uevent: version 1.0.3

>>> [   14.332930] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18)

>>> initialised: [hidden email] <mailto:[hidden email]>

>>> --

>>> [16015.787634] usb 1-1.3: New USB device strings: Mfr=1, Product=2,

>>> SerialNumber=0

>>> [16015.787635] usb 1-1.3: Product: PTZ-930 [16015.787636] usb 1-1.3:

>>> Manufacturer: Tablet [16015.789094] input: Wacom Intuos3 9x12 as

>>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/inpu

>>> t25 [16177.178260] usb 1-1.3: USB disconnect, device number 8

>>> [16216.576711] usb 1-1.3: new full-speed USB device number 9 using

>>> xhci_hcd [16216.780255] usb 1-1.3: New USB device found,

>>> idVendor=056a,

>>> idProduct=00b2

>>> [16216.780257] usb 1-1.3: New USB device strings: Mfr=1, Product=2,

>>> SerialNumber=0

>>> [16216.780258] usb 1-1.3: Product: PTZ-930 [16216.780259] usb 1-1.3:

>>> Manufacturer: Tablet [16216.781286] input: Wacom Intuos3 9x12 as

>>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/input/inpu

>>> t26 [16247.216417] pcieport 0000:00:02.0: AER: Corrected error

>>> received:

>>> id=0010

>>> [16247.216424] pcieport 0000:00:02.0: PCIe Bus Error:

>>> severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)

>>> [16247.216426] pcieport 0000:00:02.0:   device [8086:6f04] error

>>> status/mask=00000080/00002000

>>> 

>>> 

>>> 

>>> *Additionally, please try installing the evemu[1] package and then*

>>> *running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3

>>> connected*

>>> *over the KVM. After selecting the Intuos3 from the list of devices*

>>> *detected by evemu-record (let us know if the tablet is not

>>> detected),* *draw a few strokes with the pen and then hit CTRL+C.

>>> Attach the* *generated log file for revie*w.

>>> 

>>> 

>>> 

>>> Log attached.  I added additional input from the wheel mouse on the

>>> tablet as well.  If I over-did it, let me know and I’ll do a shorter

>>> test.

>>> 

>>> 

>>> 

>>> Thanks Jason for your help!

>>> 

>>> 

>>> 

>>> Joey

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> *From:*Jason Gerecke <[hidden email]

>>> <mailto:[hidden email]>>

>>> *Sent:* Tuesday, November 1, 2016 3:40 PM

>>> *To:* Joey Tucker; [hidden email]

>>> <mailto:[hidden email]>

>>> *Subject:* Re: [Linuxwacom-discuss] Wacom Intuous 3 + Avocent HMX

>>> KVM + CentOS 7.2

>>> 

>>> 

>>> 

>>> On 11/01/2016 09:03 AM, Joey Tucker wrote:

>>>> Hello,

>>>> 

>>>> 

>>>> I'm a bit of a novice when it comes to linux so pardon me if I

>>>> sound like a newbe.

>>>> 

>>>> 

>>>> Here's my setup:

>>>> 

>>>> 

>>>> I work for a small production company that uses numerous OSs

>>>> (Window, Mac, RHEL 6.5) on machines for video production.  Most of

>>>> our machine are connected to a Avocent HMX KVM system and has been

>>>> working flawlessly with wacom tablets for a number of years with

>>>> all the OSs I mentioned.

>>>> 

>>>> 

>>>> Recently, we purchased a new machine to run the latest version of

>>>> Autodesk Flame.  (we already have a Flame workstation running RHEL

>>>> 6.5 ... again, wacom works with the Avocent and this workstation) 

>>>> The new workstation is loaded with CentOS 7.2.  The integrator

>>>> tested the wacom with the machine locally and it functioned

>>>> normally.  When the new machine arrived, we integrated it into our

>>>> Avocent KVM system and the wacom doesn't work through the KVM. 

>>>> However, it shows up and identifies itself and loads it's driver.

>>>> (I think)

>>>> 

>>>> 

>>>> With my limited knowledge, I put together some command line queries

>>>> that might help in troubleshooting.  Any ideas or help would be

>>>> much appreciated.  See the list below:

>>>> 

>>>> more /proc/bus/input/devices (wacom plugged into workstation)

>>>> 

>>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102

>>>> N: Name="Wacom Intuos3 9x12"

>>>> P: Phys=

>>>> S:

>>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input

>>>> 30

>>>> U: Uniq=

>>>> H: Handlers=mouse2 event22

>>>> B: PROP=1

>>>> B: EV=1f

>>>> B: KEY=1cdf 1f00ff 0 0 0 0

>>>> B: REL=100

>>>> B: ABS=1000f00017f

>>>> B: MSC=1

>>>> 

>>>> xsetwacom --list devices (wacom plugged into workstation)

>>>> 

>>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS

>>>> Wacom Intuos3 9x12 eraser           id: 13    type: ERASER

>>>> Wacom Intuos3 9x12 cursor           id: 14    type: CURSOR

>>>> Wacom Intuos3 9x12 pad              id: 15    type: PAD

>>>> 

>>>> 

>>>> lsusb (wacom plugged into workstation)

>>>> 

>>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB

>>>> 2.0 Hub Bus 001 Device 003: ID 056a:00b2 Wacom Co., Ltd Intuos3

>>>> 9x12 Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc.

>>>> ASM1074 SuperSpeed hub Bus 005 Device 002: ID 8087:800a Intel Corp.

>>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.

>>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074

>>>> High-Speed hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation

>>>> 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0

>>>> root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root

>>>> hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

>>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus

>>>> 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001

>>>> Device 004: ID 0624:0410 Avocent Corp.

>>>> 

>>>> 

>>>> 

>>>> 

>>>> more /proc/bus/input/devices (wacom through the Avocent KVM)

>>>> 

>>>> I: Bus=0003 Vendor=056a Product=00b2 Version=0102

>>>> N: Name="Wacom Intuos3 9x12"

>>>> P: Phys=

>>>> S:

>>>> 

>>>> 

>>>> Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/inp

>>>> ut/input27

>>>> U: Uniq=

>>>> H: Handlers=mouse1 event5

>>>> B: PROP=1

>>>> B: EV=1f

>>>> B: KEY=1cdf 1f00ff 0 0 0 0

>>>> B: REL=100

>>>> B: ABS=1000f00017f

>>>> B: MSC=1

>>>> 

>>>> 

>>>> xsetwacom --list devices (wacom through the Avocent KVM)

>>>> 

>>>> Wacom Intuos3 9x12 stylus           id: 10    type: STYLUS

>>>> Wacom Intuos3 9x12 eraser           id: 12    type: ERASER

>>>> Wacom Intuos3 9x12 cursor           id: 13    type: CURSOR

>>>> Wacom Intuos3 9x12 pad              id: 14    type: PAD

>>>> 

>>>> 

>>>> lsusb (wacom through the Avocent KVM)

>>>> 

>>>> Bus 001 Device 002: ID 0424:2503 Standard Microsystems Corp. USB

>>>> 2.0 Hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc.

>>>> ASM1074 SuperSpeed hub Bus 005 Device 002: ID 8087:800a Intel Corp.

>>>> Bus 006 Device 002: ID 8087:8002 Intel Corp.

>>>> Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074

>>>> High-Speed hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation

>>>> 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0

>>>> root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root

>>>> hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

>>>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus

>>>> 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001

>>>> Device 004: ID 0624:0410 Avocent Corp.

>>>> Bus 001 Device 008: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12

>>>> 

>>>> 

>>>> Thanks!

>>>> 

>>>> 

>>>> Joey

>>>> 

>>> 

>>> Joey,

>>> 

>>> It does indeed appear that the device is being forwarded over the

>>> KVM link, so could you please describe in a bit more detail what is

>>> not working?

>>> 

>>> Could you please provide the output of `dmesg | grep -iC3 wacom` for

>>> review?

>>> 

>>> Additionally, please try installing the evemu[1] package and then

>>> running `evemu-record > /tmp/intuos3-kvm.log` with the Intuos3

>>> connected over the KVM. After selecting the Intuos3 from the list of

>>> devices detected by evemu-record (let us know if the tablet is not

>>> detected), draw a few strokes with the pen and then hit CTRL+C.

>>> Attach the generated log file for review.

>>> 

>>> [1]: http://koji.fedoraproject.org/koji/buildinfo?buildID=809826

>>> 

>>> --

>>> Jason

>>> ---

>>> Now instead of four in the eights place / you’ve got three, ‘Cause

>>> you added one / (That is to say, eight) to the two, / But you can’t

>>> take seven from three, / So you look at the sixty-fours....

>>> 


------------------------------------------------------------------------------

_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Loading...