Re: Trying to get Wacom CTL-490 to work

[Frank Groeneveld]

On Mon, Jul 18, 2016 at 09:54:02AM +0200, Philip Guenther wrote:
> 
> The privilege separation code in xenocara has a compiled in list of
> devices that are permitted to be opened; of the uhid devices it only
> currently includes /dev/uhid0 through /dev/uhid3.  You can either
> a) update the list and recompile the X server
> b) symlink it to a different name that's already in the allowed list
> but that's not used by OpenBSD (e.g., "/dev/ttyJ0")
> c) ???

Great tip, thank you! The permission denied error is gone indeed.
Unfortunately it seems the drive cannot do anythin with the raw uhid
devices, it complains about missing X & Y directions.

Frank

Re: Trying to get Wacom CTL-490 to work

[Philip Guenther]

On Mon, Jul 18, 2016 at 8:03 AM, Frank Groeneveld
 wrote:
> On Sun, Jul 17, 2016 at 08:53:50PM +0200, Frank Groeneveld wrote:
>> [46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6
>> Operation not permitted.
>> [46.602] (EE) Error opening /dev/uhid6: Operation not permitted
>
> Forgot to mention: I had changed the file permissions on uhid6 to be
> worl readable and writable.

The privilege separation code in xenocara has a compiled in list of
devices that are permitted to be opened; of the uhid devices it only
currently includes /dev/uhid0 through /dev/uhid3.  You can either
a) update the list and recompile the X server
b) symlink it to a different name that's already in the allowed list
but that's not used by OpenBSD (e.g., "/dev/ttyJ0")
c) ???


Philip Guenther

Re: Trying to get Wacom CTL-490 to work

[Frank Groeneveld]

On Sun, Jul 17, 2016 at 08:53:50PM +0200, Frank Groeneveld wrote:
> [46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6
> Operation not permitted.
> [46.602] (EE) Error opening /dev/uhid6: Operation not permitted

Forgot to mention: I had changed the file permissions on uhid6 to be
worl readable and writable.

Frank

Trying to get Wacom CTL-490 to work

[Frank Groeneveld]

I'm trying to get my new Wacom tablet working with X11 in -current.
It's a Wacom Intuos Pen (CTL-490) and it shows up in dmesg like this:

uhidev0 at uhub3 port 1 configuration 1 interface 0 "Wacom Co.,Ltd.
Intuos PS" rev 2.00/1.00 addr 5
uhidev0: iclass 3/0, 192 report ids
uhid0 at uhidev0 reportid 2: input=0, output=0, feature=1
uhid1 at uhidev0 reportid 3: input=0, output=0, feature=1
uhid2 at uhidev0 reportid 4: input=0, output=0, feature=1
uhid3 at uhidev0 reportid 5: input=0, output=0, feature=1
uhid4 at uhidev0 reportid 7: input=0, output=0, feature=9
uhid5 at uhidev0 reportid 8: input=0, output=0, feature=9
uhid6 at uhidev0 reportid 16: input=9, output=0, feature=2
uhid7 at uhidev0 reportid 17: input=0, output=0, feature=16
uhid8 at uhidev0 reportid 19: input=0, output=0, feature=1
uhid9 at uhidev0 reportid 20: input=0, output=0, feature=31
uhid10 at uhidev0 reportid 32: input=0, output=0, feature=5
uhid11 at uhidev0 reportid 33: input=0, output=0, feature=1
uhid12 at uhidev0 reportid 34: input=0, output=0, feature=1
uhid13 at uhidev0 reportid 35: input=0, output=0, feature=14
uhid14 at uhidev0 reportid 36: input=0, output=0, feature=31
uhid15 at uhidev0 reportid 37: input=0, output=0, feature=4
uhid16 at uhidev0 reportid 48: input=0, output=0, feature=2
uhid17 at uhidev0 reportid 49: input=0, output=0, feature=33
uhid18 at uhidev0 reportid 50: input=0, output=0, feature=33
uhid19 at uhidev0 reportid 51: input=0, output=0, feature=1
uhid20 at uhidev0 reportid 64: input=0, output=0, feature=10
uhid21 at uhidev0 reportid 192: input=9, output=0, feature=0
uhidev1 at uhub3 port 1 configuration 1 interface 1 "Wacom Co.,Ltd.
Intuos PS" rev 2.00/1.00 addr 5
uhidev1: iclass 3/0, 3 report ids
uhid22 at uhidev1 reportid 2: input=63, output=0, feature=0
uhid23 at uhidev1 reportid 3: input=63, output=0, feature=0
uhidev2 at uhub3 port 1 configuration 1 interface 2 "Wacom Co.,Ltd.
Intuos PS" rev 2.00/1.00 addr 5
uhidev2: iclass 3/1, 1 report id
ums0 at uhidev2 reportid 1: 5 buttons
wsmouse1 at ums0 mux 0

When I run `cat /dev/uhid6` (after making that device) I get output that
seems to suggest it is related to the pen movement. When not moving the
pen there is less output etc.
However, `cat /dev/wsmouse1` doesn't give any output.

Searching the archives I found this suggested xorg.conf InputDevice
section, which I tried:

Section "InputDevice"
Identifier "pen"
Driver "usbtablet"
Option "Type" "stylus"
Option "Device" "/dev/uhid6"
Option "Mode" "Absolute"
EndSection

Running this gives me the following error in my Xorg log file though.
Maybe because it was old and only meant for serial-over-usb tablets?

[46.602] (II) Using input driver 'usbtablet' for 'pen'
[46.602] (**) Option "CorePointer"
[46.602] (**) pen: always reports core events
[46.602] (**) Stylus: always reports core events
[46.602] (**) Stylus device is /dev/uhid6
[46.602] (**) Stylus is in absolute mode
[46.602] (==) Stylus: threshold = 5
[46.602] (==) Stylus: suppress = 2
[46.602] (II) XINPUT: Adding extended input device "Stylus" (type:
TABLET, id 6)
[46.602] (**) Option "Device" "/dev/uhid6"
[46.602] (EE) xf86OpenSerial: Cannot open device /dev/uhid6
Operation not permitted.
[46.602] (EE) Error opening /dev/uhid6: Operation not permitted
[46.602] (EE) Couldn't init device "Stylus"
[46.602] (II) UnloadModule: "usbtablet"

Finally I've modified the kernel and called uhidev_set_report with the
same parameters as for the Graphire 3 & 4, because the Linux kernel
driver seems to suggest that without that call the device will run in a
more generic mouse mode. However, it did not change anything.

Does anybody know how to get X working with the uhid device? Or is that
not the suggested method? Based on my findings that uhid6 is for pen
movement, might ums attach to the wrong device?

Thanks for any help.

Frank