General Touch input device drivers. Install drivers automatically. Are you tired of looking for drivers? DriverPack will automatically select and install the required drivers. Popular General Touch input devices. Digital Vision SAW USB Controller GeneralTouch Touchscreen USB Interface. N/a The package provides the installation files for Microsoft USB Input Device Driver version 10.0.4. If the driver is already installed on your system, updating (overwrite-installing). The package provides the installation files for Microsoft USB Input Device Driver version 10.0.4. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Aug 29, 2020 In troubleshoot tab, find Hardware Devices and Run the troubleshooter. After that, the troubleshooter system tool will start scan the hardware issue including touch screen missing problem and then fix it automatically. Solution 3: Update HID-Compliant Touch Screen Driver. Installing the missing driver for HID-Compliant touch screen can fix the.
(c) 2002-2006 by Christoph Baumann, cgb(at)debian.org
v3.4 -- Nov 7, 2006 -- the GNU FreeDocumentation License applies to this document
This document describes how to set up a touch screen input device under XFree86. As the author had only the opportunity to work with devicesfrom EloTouch(R) and MicroTouch(R) this HOWTO is rather specific for thesedevices. The examples given in this HOWTO concentrate on devicesconnected via the serial port i.e. /dev/ttyS0 or /dev/ttyS1.(Information about USB devices would be appreciated!)Touch screen devices are configured in the Xinput section in the XF86Configfile (mostly /etc/X11/XF86Config or /etc/XF86Config).At first verify that the device driver modules exist. They are located in/usr/X11R6/lib/modules/ (the modules for the above mentioned devices are xf86Elo.so and xf86MuTouch.so). Now have a look into XF86Config.There should be a section looking like this:
To get the module loaded by the X server there has to be a section like this:
Now the more tricky part. X needs to know some parameters about the device.The section for this looks like this (see 'man XF86Config' for more details):
The values for the entries MinimumXPosition etc. are of course specificfor the setup of the hardware (i.e. depend on the position of the touchscreen relative to the monitor). The values determine where the points (0,0)and (xmax,ymax) on your monitor (xmax and ymax depend on the resolutionchosen for the Xserver, such as 1024x768) are mapped on the touch screen.The device driver reads these values and interpolishes the other coordinates.For illustration:
This mapping can be done by trial and error or by reading the raw outputof the device (needs some serial port programming, see 'The Linux Serial Programming HOWTO'). For the types EloTouch and MicroTouch exists arudimentary calibration tool (written by the author of this document,it can be found at http://touchcal.sourceforge.net).
After starting X, type in an Xterminal the command
xsetpointer <devicename>
where<devicename> is the name defined in XF86Config with the lineDeviceName '.....', in this example it would be TouchScreen.
To get the device working on startup use the AlwaysCore option inthe touch screen section (see above)
To use the touch screen and a mouse in parallel you need to enter themouse specs in the Xinput-section. This definitions should be the sameas in the Pointer-section. The following example is for aPS/2-mouse:Several people pointed this out, especially the usage of theAlwaysCore option. Thanks to them all.
(from Lee Monamy)
Example XF86Config-4 for an ELO touch screen:
Noteable differences between this and the version 3 config are that youspecify a Device, *not* a Port, otherwise you get an error.Also, AlwaysCore from v3 has been replaced with SendCoreEvents.
You must also add to the ServerLayout section, despite that X mightsay:'(II) XINPUT: Adding extended input device 'TOUCHSCREEN' (type:Elographics Touch Screen)'
from Dirk Mueller (for Microtouch SMT3 Series):
Option 'Type' can be 'finger' or 'stylus'Since Microtouch was bought by 3M-Touch, the resources are onhttp://www.3M.com/3MTouchSystems/downloads/legacy.jhtml#Linux
According to Wong Yeow Sen the configuration option names have changedin XFree86 4.2 (at least with Red Hat 7.3). If it seems yourcalibration values aren't parsed try the following:
(from Joerg Hau)
Microsoft Usb Input Device Driver
Information about these devices can be found here:
'...
Harald Hoyer's Linux Touch Panel Drivers for the Fujitsu LifebooksB112/B142/B2130, http://parzelle.de/Linux/Lifebook/. Unfortunately,this is XFree 3.x only and it seems that this information is now'static' (dead?).
Kenan Esau's Lifebook Series B Touchscreen driver, which is theadaptation of Harald's driver to XFree 4.x.http://www.conan.de/lifebook/lifebook.html.
I [Joerg Hau] have used Kenan's driver on my Fujitsu LifeBook B142 (described athttp://www.mysunrise.ch/users/joerg.hau/linux/b142.htm), and it works like a charm.
...'
(from Kenan Bektas)
Example xorg.conf for an Elo TouchSystems 2216 AccuTouch® USB Touch-Monitor:
- Manpage for XF86Config
- http://www.hof-berlin.de/tablet/tablet.html (Thanks toChrister Olofsson for sending me this URL)
- http://freshmeat.net/projects/xf86elousb (Driver for iTouch USB)
- The manual shipped with your touch screen :-)
This article describes the setup of Bluetooth input devices, for example a bluetooth mouse, on a Linux system.
Installation
Kernel
Both Bluetooth and evdev support is necessary in the kernel. The following options are also required:
BlueZ settings
Change the value of UserspaceHID to true in /etc/bluetooth/input.conf to enable user-space HID support:
/etc/bluetooth/input.confUser-space HID support also requires the User-space I/O driver for HID input devices (CONFIG_UHID) to be enabled:
Configuration
To configure the input devices use the specialized desktop management tools:
- net-wireless/gnome-bluetooth for GNOME
- kde-plasma/bluedevil for KDE
- net-wireless/blueman is a generic GTK client (i.e. for use with Openbox/i3, etc)
Some Bluetooth input devices are initially not in HID mode, but in HCI mode. This is handled by udev in /lib/udev/rules.d/97-hid2hci.rules. Additional devices can be added in a custom rule file which needs to be placed in /etc/udev/rules.d. Refer to the udev article for more details.
See also
General Touch Input Devices Driver Updater
- Bluetooth — describes the configuration and usage of Bluetooth controllers and devices.
Output Devices
Comments are closed.