« Return to Thread: Graphire4 Pad Button freeze with 0.10.11.
Re: Graphire4 Pad Button freeze with 0.10.11.
by Jason G.
::
Rate this Message:
On Sat, May 28, 2011 at 5:53 PM, Chris Bagwell <chris@...> wrote:
> On Sat, May 28, 2011 at 3:54 PM, Jason Gerecke <killertofu@...> wrote:
>> On Fri, May 27, 2011 at 9:11 PM, Chris Bagwell <chris@...> wrote:
>>> Hi Favux,
>>>
>>> For first bug report, it does sound same issue as I looked into a
>>> while back. The kernel driver is mistakenly telling userland that the
>>> PAD device has gone out of proximity when you use pen. From that
>>> point, buttons don't work.
>>>
>>> Something has changed in xf86-input-wacom that we must l trust kernel
>>> information more then we used to. My personal preference is to fix
>>> the kernel to give us good info instead of reverting back to old
>>> xf86-input-wacom behavior.
>>>
>>> Maybe when Ping gets back next month we can have some progress. Or
>>> hopefully we can find a user that doesn't mind hacking kernel drivers.
>>> I can give tons of guidance on patch to implement (its like 3 lines
>>> for simple solution) but ultimately I can't push forward much more
>>> since I don't have the device.
>>>
>>> For second bug report (X server crash), I've no idea. It sounds like
>>> its own issue.
>>>
>>> Chris
>>>
>>
>> Chris, I just happen to have a Graphire4 at home. If you have an idea
>> of where the bug may lie, I'd be happy to try patching up the kernel
>> code :)
>>
>> Jason
>>
>
> Cool. I've attached the patch I think that is needed. This is
> against Linus' git that was rebased at some random time in last month
> or two.
>
> Originally, I was going to give you a patch against input-wacom but it
> looks like that is different compared to upstream for graphire.
> Specifically, it is correctly setting MSC_SERIAL when switching over
> to pen.
>
> That means input-wacom may be working with graphire4. input-wacom is
> not ever sending BTN_TOOL_FINGER for some reason so if its not working
> then thats probably only change needed (add it back in to match
> kernel).
>
> Chris
>
While I can confirm the bug under Ubuntu 11.04 64-bit
(2.6.38-8-generic), I can't under my 32-bit Arch Linux development
box. This was tested with the pre-installed "2.6.38-ARCH" kernel, as
well as the tarballs from kernel.org for 2.6.38.7 or 2.8.39 (with the
config from /proc/config used as the source). xf86-input-wacom was
from Git obviously :)
There is a similar bug under these kernels (multiple presses to the
same pad button don't work while pen is in prox -- you either have to
press another button before the first works again, or take the pen out
of prox to press buttons repeatedly).
I'll try setting up a build environment under my virtual Ubuntu box to
see what the official kernel sources do there.
Jason
---
Day xee-nee-svsh duu-'ushtlh-ts'it;
nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
Huu-chan xuu naa~-gha.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
> On Sat, May 28, 2011 at 3:54 PM, Jason Gerecke <killertofu@...> wrote:
>> On Fri, May 27, 2011 at 9:11 PM, Chris Bagwell <chris@...> wrote:
>>> Hi Favux,
>>>
>>> For first bug report, it does sound same issue as I looked into a
>>> while back. The kernel driver is mistakenly telling userland that the
>>> PAD device has gone out of proximity when you use pen. From that
>>> point, buttons don't work.
>>>
>>> Something has changed in xf86-input-wacom that we must l trust kernel
>>> information more then we used to. My personal preference is to fix
>>> the kernel to give us good info instead of reverting back to old
>>> xf86-input-wacom behavior.
>>>
>>> Maybe when Ping gets back next month we can have some progress. Or
>>> hopefully we can find a user that doesn't mind hacking kernel drivers.
>>> I can give tons of guidance on patch to implement (its like 3 lines
>>> for simple solution) but ultimately I can't push forward much more
>>> since I don't have the device.
>>>
>>> For second bug report (X server crash), I've no idea. It sounds like
>>> its own issue.
>>>
>>> Chris
>>>
>>
>> Chris, I just happen to have a Graphire4 at home. If you have an idea
>> of where the bug may lie, I'd be happy to try patching up the kernel
>> code :)
>>
>> Jason
>>
>
> Cool. I've attached the patch I think that is needed. This is
> against Linus' git that was rebased at some random time in last month
> or two.
>
> Originally, I was going to give you a patch against input-wacom but it
> looks like that is different compared to upstream for graphire.
> Specifically, it is correctly setting MSC_SERIAL when switching over
> to pen.
>
> That means input-wacom may be working with graphire4. input-wacom is
> not ever sending BTN_TOOL_FINGER for some reason so if its not working
> then thats probably only change needed (add it back in to match
> kernel).
>
> Chris
>
While I can confirm the bug under Ubuntu 11.04 64-bit
(2.6.38-8-generic), I can't under my 32-bit Arch Linux development
box. This was tested with the pre-installed "2.6.38-ARCH" kernel, as
well as the tarballs from kernel.org for 2.6.38.7 or 2.8.39 (with the
config from /proc/config used as the source). xf86-input-wacom was
from Git obviously :)
There is a similar bug under these kernels (multiple presses to the
same pad button don't work while pen is in prox -- you either have to
press another button before the first works again, or take the pen out
of prox to press buttons repeatedly).
I'll try setting up a build environment under my virtual Ubuntu box to
see what the official kernel sources do there.
Jason
---
Day xee-nee-svsh duu-'ushtlh-ts'it;
nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
Huu-chan xuu naa~-gha.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
« Return to Thread: Graphire4 Pad Button freeze with 0.10.11.
| Free embeddable forum powered by Nabble | Forum Help |
