You are not logged in.

#26 2012-02-01 13:53:05

gjasso
Member
From: Bonn, Germany
Registered: 2011-09-08
Posts: 21

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

How did you determine you dont have multitouch? By default, as far as I know, there is no program or anything which takes advantage of multitouch input just because it is there. You probably need to install something to use it.

Anyway, the driver also installs a utility called eGalaxCalib, you can run it from the command line just like that. It has a "multitouch drawing demo" where you can see if multitouch is working of not. Just try to draw with two fingers and you should see to lines on the screen.

Offline

#27 2012-02-02 06:27:52

Padfoot
Member
Registered: 2010-09-03
Posts: 381

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

The eGalax Calibration program should be in your system menu. As gjasso says, if the driver is loading, you can access the drawing test in that program. If the driver is not loading, the program will present an error dialog In which case, provide the details I previously asked for so we can help you trouble shoot the issue.

Currently the gtk toolkit does not have multitouch support, neither do the big desktops (Gnome, KDE, Xfce). I'm guessing it won't be long before multitouch is in KDE, as QT already has limited support. So to play with multitouch, look at something like Kivy which is a cython module for python2. Kivy implements a multitouch toolkit for writing aps. Also have a look at Plasma Active. This is KDE's touch form factor environment. There are also attempts to port Ubuntu's multitouch framework to Arch. Packages are in AUR.

Other than these the only other option I am currently aware of is the port of Android to x86 architecture.

On a side note, if anyone is aware of other linux multitouch projects, I am all ears.

Cheers.

Offline

#28 2012-02-13 02:20:23

Rage24
Member
Registered: 2012-01-22
Posts: 8

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

I was a little busy lately. Here's what I got. I could not find the log anywhere.

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:810c Suyin Corp. 
Bus 004 Device 002: ID 0eef:725e D-WAV Scientific Co., Ltd 
Bus 004 Device 005: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=12	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ Integrated Webcam                       	id=10	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=11	[slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        	id=13	[slave  keyboard (3)]

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# See 'man 5 rc.conf' for more details
#

# LOCALIZATION
# ------------
HARDWARECLOCK="UTC"
TIMEZONE="America/Phoenix"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
USECOLOR="yes"

# HARDWARE
# --------
MODULES=(hid-multitouch snd-hda-intel acpi-cpufreq)
USEDMRAID="no"
USEBTRFS="no"
USELVM="no"

# NETWORKING
# ----------
HOSTNAME="rage"

interface=eth0
address=
netmask=
broadcast=
gateway=

NETWORK_PERSIST="no"

# DAEMONS
# -------
#
DAEMONS=(hwclock syslog-ng dbus networkmanager bluetooth cpufreq crond gdm)

rc.local

#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#
/usr/bin/eGTouchD

It seems xinput does not recognize the touch. Not sure what happened. Thank you again.

Rage

Last edited by ewaller (2012-02-15 06:32:54)

Offline

#29 2012-02-13 05:45:06

Padfoot
Member
Registered: 2010-09-03
Posts: 381

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

Ok. Firstly, you should place all output and scripts inside code tags. it makes it easier for others to determine what is in a file and what isn't.

Now, it appears you are not passing your device details to the hid-multitouch module.

Change your rc.local as follows:

#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#
echo 3 0eef 725e 259 > /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id
/usr/bin/eGTouchD

Reboot and confirm if you have virtual multi and virtual single when you exec:

$ xinput list

Cheers.

Last edited by Padfoot (2012-02-13 05:46:02)

Offline

#30 2012-02-15 05:57:05

Rage24
Member
Registered: 2012-01-22
Posts: 8

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

Padfoot,

Everything works fine after I added it to the rc.local. How do you use code tag in the forum?


Thank you for your help.

Rage

Offline

#31 2012-02-15 06:34:54

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,406

Re: [SOLVED] Kernel 3.2.1 and USB Touchscreen Failure

Rage24 wrote:

Padfoot,

Everything works fine after I added it to the rc.local. How do you use code tag in the forum?


Thank you for your help.

Rage

Hi, and welcome to the forums.  see this link, or the BBCode link under the message box

I took the liberty of adding code tags to your former post.  You can edit that post to see what I did.

ewaller


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

Board footer

Powered by FluxBB