Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-17 Thread Fabrizio Romano Genovese
Well, I blacklisted the relevant module and recompiled the driver as the guide 
said. The hid-core.c file hasn't the line described in the guide tho: It has a 
definition by cases that collapses  the wacom driver to the standard one if 
wacom specific driver is not loaded. In doubt, I eliminated any reference to 
Wacom in the hid-core.c, and replaced the old drivers with the new one. Still, 
no effect whatsoever. 

Interestingly enough, giving 
cat /sys/kernel/debug/usb/devices
tells me that 
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  4 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs=  1
P:  Vendor=056a ProdID=00dd Rev= 1.02
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=CTL-470
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr= 98mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=  10 Ivl=2ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=82(I) Atr=03(Int.) MxPS=  64 Ivl=2ms

So the driver used is the right one. Only, usbhid doesn't recognize my tablet 
as a mouse. I feel like I'm out of options :/

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/27e9182d-6bb7-4271-83e8-1d81eee6bede%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-16 Thread 'Tom Zander' via qubes-users
I think I know why you get that error.

any part of the kernel (and drivers are part of the kernel) are off-limits to 
change for any Qube VM.

To avoid loading a module you don't have to remove it, you can just blacklist a 
module.
Your distro may have a specific way of doing it, but a little googling showed 
me this and that looks about right to me;

https://linux-audit.com/kernel-hardening-disable-and-blacklist-linux-modules/


On Tuesday, 16 January 2018 14:28:41 CET Fabrizio Romano Genovese wrote:
> when I tried to remove
> /lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/waco
> m_serial4.ko
> 
> I get the error
> 
> rm: cannot remove
> '/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wa
> com_serial4.ko': Read-only file system


-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2100592.U4tyHCJJMU%40mail.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-16 Thread Fabrizio Romano Genovese
Sorry, when I tried to remove 
/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
 

I get the error

rm: cannot remove 
'/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko':
 Read-only file system

(Not always I get ctrl+shift+v right :P)

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/30ce8576-e378-4a93-9cd9-3cf05d7ee3a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-16 Thread Fabrizio Romano Genovese
I saw this reply only yesterday, unfortunately.

So, I followed your suggestion and looked around. I found this, that should do 
exactly what you say:
https://cwcode.wordpress.com/2014/01/14/compiling-a-new-kernel-module-to-use-hid-core-for-a-wacom-bamboo-pad/

Now, since this guide is not for fedora, I wanted to try something easier 
before. In the comments someone says

"I found it easier to add usbhid.quirks=0x056a:0x0318:0x4000 to the kernel 
commandline in /etc/default/grub.
0x4000 is HID_QUIRK_NO_IGNORE. The first two numbers is the device’s ID."

So I tried to do the same. I clone the template-vm on which sys-usb is based 
and I added in /etc/default/grub
usbhid.quirks=0x056a:0x00dd:0x4000

where 056a identifies wacom as producer and 00dd is my product number, found in
/sys/kernel/debug/usb/devices.

When I rebooted nothing happened. I also tried to put this line in grub.qubes, 
with no success whatsoever. Then I tried following the guide, but I fail pretty 
quicly: Trying to remove 

/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
 

Gives me the error

/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/tablet/wacom_serial4.ko
 

Then I tried at least to monitor usb with usbmon. I gave

modprobe usbmon 

and then started monitoring my wacom tablet, that is on 2u, with:

sudo cat /sys/kernel/debug/usb/usbmon/2u

usbmon doesn't sense anything when I move the pen on the tablet, it only senses 
something when I connect/disconnect it. When I connect the tablet I get:

8cefcce66540 3453394997 C Ii:2:001:1 0:2048 2 = 0200
8cefcce66540 3453395017 S Ii:2:001:1 -115:2048 4 <
8cefca1b00c0 3453395039 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453395053 C Ci:2:001:0 0 4 = 01010100
8cefca1b00c0 3453395057 S Co:2:001:0 s 23 01 0010 0001  0
8cefca1b00c0 3453395067 C Co:2:001:0 0 0
8cefca1b00c0 3453395072 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453395086 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453422046 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453422064 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453449146 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453449166 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453476120 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453476138 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453503126 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453503155 C Ci:2:001:0 0 4 = 0101
8cefca1b00c0 3453503256 S Co:2:001:0 s 23 03 0004 0001  0
8cefca1b00c0 3453503279 C Co:2:001:0 0 0
8cefca1b00c0 3453555111 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453555135 C Ci:2:001:0 0 4 = 1101
8cefca1b00c0 3453607116 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453607141 C Ci:2:001:0 0 4 = 03011000
8cefca1b00c0 3453607152 S Co:2:001:0 s 23 01 0014 0001  0
8cefca1b00c0 3453607162 C Co:2:001:0 0 0
8cefca1b00c0 3453659185 S Ci:2:000:0 s 80 06 0100  0040 64 <
8cefca1b00c0 3453659601 C Ci:2:000:0 0 18 = 12010002 0020 6a05dd00 
02010102 0001
8cefca1b00c0 3453659620 S Co:2:001:0 s 23 03 0004 0001  0
8cefca1b00c0 3453659633 C Co:2:001:0 0 0
8cefca1b00c0 3453711790 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453711808 C Ci:2:001:0 0 4 = 1101
8cefca1b00c0 3453763103 S Ci:2:001:0 s a3 00  0001 0004 4 <
8cefca1b00c0 3453763128 C Ci:2:001:0 0 4 = 03011000
8cefca1b00c0 3453763133 S Co:2:001:0 s 23 01 0014 0001  0
8cefca1b00c0 3453763143 C Co:2:001:0 0 0
8cefca1b00c0 3453827084 S Ci:2:006:0 s 80 06 0100  0012 18 <
8cefca1b00c0 3453827583 C Ci:2:006:0 0 18 = 12010002 0020 6a05dd00 
02010102 0001
8cefca1b00c0 3453827613 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453827726 C Ci:2:006:0 -32 0
8cefca1b00c0 3453827741 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453827856 C Ci:2:006:0 -32 0
8cefca1b00c0 3453827871 S Ci:2:006:0 s 80 06 0600  000a 10 <
8cefca1b00c0 3453828010 C Ci:2:006:0 -32 0
8cefca1b00c0 3453828038 S Ci:2:006:0 s 80 06 0200  0009 9 <
8cefca1b00c0 3453828359 C Ci:2:006:0 0 9 = 09023b00 02010080 31
8cefca1b00c0 3453828384 S Ci:2:006:0 s 80 06 0200  003b 59 <
8cefca1b00c0 3453829398 C Ci:2:006:0 0 59 = 09023b00 02010080 31090400 
00010301 02000921 10010001 22b80007 0581030a
8cefca1b00c0 3453829420 S Ci:2:006:0 s 80 06 0300  00ff 255 <
8cefca1b00c0 3453829624 C Ci:2:006:0 0 4 = 04030904
8cefca1b00c0 3453829642 S Ci:2:006:0 s 80 06 0302 0409 00ff 255 <
8cefca1b00c0 3453830002 C Ci:2:006:0 0 16 = 10034300 54004c00 2d003400 
37003000
8cefca1b00c0 3453830023 S Ci:2:006:0 s 80 06 0301 0409 00ff 255 <
8cefca1b00c0 3453830594 C Ci:2:006:0 0 30 = 1e035700 61006300 6f006d00 
20004300 6f002e00 2c004c00 74006400 2e00
8cefca1b0cc0 3453831094 S Co:2:006:0 s 00 09 0001   0

Re: [qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-09 Thread 'Tom Zander' via qubes-users
On Tuesday, 9 January 2018 01:54:40 GMT Fabrizio Romano Genovese wrote:
> Hello all,
> This looks like an old issue:
> https://github.com/QubesOS/qubes-issues/issues/2715
> 
> I'd be interested in using only the basic tablet features (essentially
> moving the mouse and clicking around using the tablet would be enough).
> In the issue linked above it is said that
> 
> "this in theory should be easy (a matter adding proper metadata - min/max
> - to the protocol handshake, and filtering events based on this info)"
> 
> I'd like to help with this, but I am no coder. I just know a bit of bash
> scripting and trying to check the code in
> 
> https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/src/pro
> tocol.h#L17-L28
> 
> didn't really help. I understand that developers are quite busy with much
> more hardcore problems to solve, but if someone could at least point me
> to the right research direction I could try to investigate this by
> myself.

From;
http://linuxwacom.sourceforge.net/index_old.php/howto/theory

> Initially at least, the USB Wacom tablet is an HID compliant device, and
> when first connected to the computer, will identify itself as such.
> Unfortunately, this is not what you want because in this mode, you will
> not get any of the fancy features. The hid-core.c, mousedev.c, and
> usbmouse.c kernel drivers contain exceptions for the wacom; when the
> device is detected, they ignore the tablet.

So maybe you can use that website to find out how to configure your wacom to 
just be a HID (human interface device) and make it send those mouse clicks.

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3164963.Ui2e7s9DGh%40mail.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Graphic Tablet Compatibility (basic features)

2018-01-08 Thread Fabrizio Romano Genovese
Hello all,

I'd like to use a wacom bamboo graphic tablet as an alternative pointing 
device, mainly to draw on virtual whiteboards to do maths in conference calls. 
At the moment, this is not possible: Connecting the graphic tablet and passing 
it to the relevant VM produces no effect whatsoever. The tablet is listed among 
the usb devices but, if for instance one is using the standard fedora template, 
nothing is shown clicking on the "wacom tablet" application that can be found 
in /urs/share/applications, nor is it possible to use it to draw stuff.

This looks like an old issue:
https://github.com/QubesOS/qubes-issues/issues/2715

I'd be interested in using only the basic tablet features (essentially moving 
the mouse and clicking around using the tablet would be enough). In the issue 
linked above it is said that 

"this in theory should be easy (a matter adding proper metadata - min/max - to 
the protocol handshake, and filtering events based on this info)"

I'd like to help with this, but I am no coder. I just know a bit of bash 
scripting and trying to check the code in 

https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/src/protocol.h#L17-L28

didn't really help. I understand that developers are quite busy with much more 
hardcore problems to solve, but if someone could at least point me to the right 
research direction I could try to investigate this by myself.

Cheers,
Fab

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c5aeb07c-25ad-4d71-913d-369f08980fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.