Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

[Padfoot]

On 21/01/12 03:02, Greg KH wrote:
> On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
>> Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
>> no longer recognised.
>>
>> Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
>> is a pci device but is connected on boot as a usb input device.
>> Issue appears to be with either UDEV or USBINPUT boot hook failing
>> to recognise the device as can be seen in the dmesg.3.2.1
>> attachment.
>>
>> Downgrading to kernel 3.1.9 corrects the issue.
> Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
> commit here?
>
> Also, you might want to cc: the linux-input developers, they can help
> you out much better than the general list can.
>
> greg k-h
>
Hi Greg,

I am not a kernel dev, nor have I ever compiled a kernel, so I don't 
think I am able to help with a git bisect to locate the offending 
commit. I am just a regular user running pre-compiled packages on my 
Arch Linux distro. But, of course I am happy to assist wherever I can.

Cheers.
Lachlan

Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

[Greg KH]

On Sat, Jan 21, 2012 at 07:13:58AM +1100, Padfoot wrote:
> On 21/01/12 03:02, Greg KH wrote:
> >On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
> >>Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
> >>no longer recognised.
> >>
> >>Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
> >>is a pci device but is connected on boot as a usb input device.
> >>Issue appears to be with either UDEV or USBINPUT boot hook failing
> >>to recognise the device as can be seen in the dmesg.3.2.1
> >>attachment.
> >>
> >>Downgrading to kernel 3.1.9 corrects the issue.
> >Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
> >commit here?
> >
> >Also, you might want to cc: the linux-input developers, they can help
> >you out much better than the general list can.
> >
> >greg k-h
> >
> Hi Greg,
> 
> I am not a kernel dev, nor have I ever compiled a kernel, so I don't
> think I am able to help with a git bisect to locate the offending
> commit. I am just a regular user running pre-compiled packages on my
> Arch Linux distro. But, of course I am happy to assist wherever I
> can.

If you want to build your own kernel, there are lots of instructions on
how do this online (google for 'linux kernel in a nutshell' for a free
book about this.)

Otherwise, can you file a bug with the arch linux developers?  They
might be able to help you out here better as you are using a distro
kernel.

good luck,

greg k-h

Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

[Benjamin Tissoires]

Hi Lachlan,

Well, many eGalax devices are multitouch devices, and can not be
handled by the generic input hid layer without having strange issues.
We have a patch in 3.2 that auto detect such devices and release them
from the generic input stack.
Then, it's easier for people to handle the devices through
hid-multitouch as the recompilation of the kernel is not required
anymore.
I also submitted a patch to catch multitouch devices in
hid-multitouch, but it has not been accepted as it would require
everybody to load hid-multitouch for every hid device.

To enable your device, do (as root)
# modprobe hid-multitouch
# echo 3 VID PID 104 >
/sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id

where:
- 3 is the bus, usb here
- VID: vendor ID (must be 0eef in your case)
- PID: product ID
- 104 is the number of the right class of multitouch device to use
(see MT_CLS_* definitions in hid-multitouch)
VID/PID  can be retrieved from lsusb.

If it's working, then you should also give us your PID so that we can
add it in the source of hid-multitouch.

Cheers,
Benjamin


On Fri, Jan 20, 2012 at 21:13, Padfoot <padfoot@exemail.com.au> wrote:
> On 21/01/12 03:02, Greg KH wrote:
>>
>> On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
>>>
>>> Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
>>> no longer recognised.
>>>
>>> Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
>>> is a pci device but is connected on boot as a usb input device.
>>> Issue appears to be with either UDEV or USBINPUT boot hook failing
>>> to recognise the device as can be seen in the dmesg.3.2.1
>>> attachment.
>>>
>>> Downgrading to kernel 3.1.9 corrects the issue.
>>
>> Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
>> commit here?
>>
>> Also, you might want to cc: the linux-input developers, they can help
>> you out much better than the general list can.
>>
>> greg k-h
>>
> Hi Greg,
>
> I am not a kernel dev, nor have I ever compiled a kernel, so I don't think I
> am able to help with a git bisect to locate the offending commit. I am just
> a regular user running pre-compiled packages on my Arch Linux distro. But,
> of course I am happy to assist wherever I can.
>
> Cheers.
> Lachlan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

[Padfoot]

On 21/01/12 07:50, Benjamin Tissoires wrote:
> Hi Lachlan,
>
> Well, many eGalax devices are multitouch devices, and can not be
> handled by the generic input hid layer without having strange issues.
> We have a patch in 3.2 that auto detect such devices and release them
> from the generic input stack.
> Then, it's easier for people to handle the devices through
> hid-multitouch as the recompilation of the kernel is not required
> anymore.
> I also submitted a patch to catch multitouch devices in
> hid-multitouch, but it has not been accepted as it would require
> everybody to load hid-multitouch for every hid device.
>
> To enable your device, do (as root)
> # modprobe hid-multitouch
> # echo 3 VID PID 104>
> /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
>
> where:
> - 3 is the bus, usb here
> - VID: vendor ID (must be 0eef in your case)
> - PID: product ID
> - 104 is the number of the right class of multitouch device to use
> (see MT_CLS_* definitions in hid-multitouch)
> VID/PID  can be retrieved from lsusb.
>
> If it's working, then you should also give us your PID so that we can
> add it in the source of hid-multitouch.
>
> Cheers,
> Benjamin
>
>
> On Fri, Jan 20, 2012 at 21:13, Padfoot<padfoot@exemail.com.au>  wrote:
>> On 21/01/12 03:02, Greg KH wrote:
>>> On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
>>>> Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
>>>> no longer recognised.
>>>>
>>>> Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
>>>> is a pci device but is connected on boot as a usb input device.
>>>> Issue appears to be with either UDEV or USBINPUT boot hook failing
>>>> to recognise the device as can be seen in the dmesg.3.2.1
>>>> attachment.
>>>>
>>>> Downgrading to kernel 3.1.9 corrects the issue.
>>> Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
>>> commit here?
>>>
>>> Also, you might want to cc: the linux-input developers, they can help
>>> you out much better than the general list can.
>>>
>>> greg k-h
>>>
>> Hi Greg,
>>
>> I am not a kernel dev, nor have I ever compiled a kernel, so I don't think I
>> am able to help with a git bisect to locate the offending commit. I am just
>> a regular user running pre-compiled packages on my Arch Linux distro. But,
>> of course I am happy to assist wherever I can.
>>
>> Cheers.
>> Lachlan
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-input" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Hi Benjamin,

Thankyou very much. Your solution has worked brilliantly.

The device parameters I had to pass to hid-multitouch are as follows:

echo 3 0eef 7302 259 > /sys/mod........

I also have to use the binary daemon driver from eGalax for the device 
to work:
http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm

Cheers.
Lachlan.

Re: PROBLEM: Kernel version 3.2.1 usb touchscreen device not recognised [UDEV? USBINPUT? HOOK]

[Benjamin Tissoires]

Hi Lachlan,

thanks for the feedback.
The pid you provided is already included for 3.3, and has been
scheduled in stable too (3.2 and 3.0).
So this command won't be required soon.

Cheers,
Benjamin

On Fri, Jan 20, 2012 at 22:57, Padfoot <padfoot@exemail.com.au> wrote:
> On 21/01/12 07:50, Benjamin Tissoires wrote:
>>
>> Hi Lachlan,
>>
>> Well, many eGalax devices are multitouch devices, and can not be
>> handled by the generic input hid layer without having strange issues.
>> We have a patch in 3.2 that auto detect such devices and release them
>> from the generic input stack.
>> Then, it's easier for people to handle the devices through
>> hid-multitouch as the recompilation of the kernel is not required
>> anymore.
>> I also submitted a patch to catch multitouch devices in
>> hid-multitouch, but it has not been accepted as it would require
>> everybody to load hid-multitouch for every hid device.
>>
>> To enable your device, do (as root)
>> # modprobe hid-multitouch
>> # echo 3 VID PID 104>
>> /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
>>
>> where:
>> - 3 is the bus, usb here
>> - VID: vendor ID (must be 0eef in your case)
>> - PID: product ID
>> - 104 is the number of the right class of multitouch device to use
>> (see MT_CLS_* definitions in hid-multitouch)
>> VID/PID  can be retrieved from lsusb.
>>
>> If it's working, then you should also give us your PID so that we can
>> add it in the source of hid-multitouch.
>>
>> Cheers,
>> Benjamin
>>
>>
>> On Fri, Jan 20, 2012 at 21:13, Padfoot<padfoot@exemail.com.au>  wrote:
>>>
>>> On 21/01/12 03:02, Greg KH wrote:
>>>>
>>>> On Fri, Jan 20, 2012 at 07:13:54PM +1100, Padfoot wrote:
>>>>>
>>>>> Upgrade from kernel 3.1.9 to 3.2.1 eGalax usb touchscreen device is
>>>>> no longer recognised.
>>>>>
>>>>> Device is an Acer Iconia Tab w501 with inbuilt touchscreen. Screen
>>>>> is a pci device but is connected on boot as a usb input device.
>>>>> Issue appears to be with either UDEV or USBINPUT boot hook failing
>>>>> to recognise the device as can be seen in the dmesg.3.2.1
>>>>> attachment.
>>>>>
>>>>> Downgrading to kernel 3.1.9 corrects the issue.
>>>>
>>>> Can you run 'git bisect' between 3.1.0 and 3.2.0 to find the problem
>>>> commit here?
>>>>
>>>> Also, you might want to cc: the linux-input developers, they can help
>>>> you out much better than the general list can.
>>>>
>>>> greg k-h
>>>>
>>> Hi Greg,
>>>
>>> I am not a kernel dev, nor have I ever compiled a kernel, so I don't
>>> think I
>>> am able to help with a git bisect to locate the offending commit. I am
>>> just
>>> a regular user running pre-compiled packages on my Arch Linux distro.
>>> But,
>>> of course I am happy to assist wherever I can.
>>>
>>> Cheers.
>>> Lachlan
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-input" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> Hi Benjamin,
>
> Thankyou very much. Your solution has worked brilliantly.
>
> The device parameters I had to pass to hid-multitouch are as follows:
>
> echo 3 0eef 7302 259 > /sys/mod........
>
> I also have to use the binary daemon driver from eGalax for the device to
> work:
> http://home.eeti.com.tw/web20/eGalaxTouchDriver/linuxDriver.htm
>
> Cheers.
> Lachlan.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html