Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x210 IdVendor 0x0eef D-WAV Scientific Co., LtdīInterfaceSubClass 1 Boot Interface Subclass Classic New Touch Keyboardīus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreenīDeviceClass 0 (Defined at Interface level) (usbtouchscreen does exist but is not loaded)īus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.īus 001 Device 004: ID 046d:c315 Logitech, Inc. Note that at present I do not have anything specific in nf or related to the touchscreen this did not seem to be necessary with the older hardware. Is this a known issue, or something that can be fixed, or just a configuration error? I've included some diagnostic output from various tools below in the hope that it may be useful to identify and/or fix the issue please let me know if you need more information. (I'm ok with it behaving like a single-touch mouse - I just want it to actually do something when touched.) However it does not perform any "click" action when the screen is touched. I've found the ARM-specific vendor drivers but I haven't installed them yet as I remember this working without them on an older model of eGalax touchscreen.Įven without those, it still seems to autodetect the touchscreen and it loads the hid_multitouch driver, and within X the pointer moves according to touches as expected.
I'm trying to use it from a Raspberry Pi, so I can't use the prebuilt drivers on that CD. I have a new eGalax touchscreen (came with driver cd 5.1.0, if that helps).
0 kommentar(er)
