Touchscreen HOWTO

How to do things, solutions, recipes, tutorials
Message
Author
mcelmeel
Posts: 33
Joined: Mon 27 Dec 2010, 13:10

#61 Post by mcelmeel »

Hi Guys,

This is getting more stranger for me and so fustrating. I tried the install again and once again it was unable to start X and i had to run xorgwizard. When the wizard has finished and the computer loaded, the touchscreen mouse works perfectly. the pointer goes exactly where ever i press it. I thought that i finally had it. After a short time using it, the pointer was slightly off calibration. then as i continued to use the computer, the calibration changed and got worse. after running xorgwizard again, the mouse was working perfectly and continued to do so until the first program that i opened. this caused the calibration to go off. then when i started another program, the calibration changed bringing me to the conclusion that starting a program changes the calibration. This has me completely stumped. Has anyone any idea what may be causing this or has anyone expericenced it before. Also, the config settings are not in the xorg.conf file.

mcelmeel
Posts: 33
Joined: Mon 27 Dec 2010, 13:10

#62 Post by mcelmeel »

Hi Guys,

Still no joy getting the touchscreen to work. I have tried everything i can think of, changed to puppy 4.3.1, followed instructions on the elo website. sometime i can get the cursor working but always off calibration and can never get it calibrated.

Is there anyone there that may be able to help me at all, please?

mcelmeel
Posts: 33
Joined: Mon 27 Dec 2010, 13:10

#63 Post by mcelmeel »

Hi Guys,

I got the touchscreen working but have stumbled across another problem that I'm hoping someone may know the solution to.

The touchscreen is being used as a kiosk which is coin operated. When the system first loads and a coin is put it to activate the USB conection to the touchscreen, it works fine. But when the timer runs out and another coin has to be inserted, the touchscreen moves way off calibration. Does anyone know if there is any setting i could use in xorg.conf to prevent the calibration changing when the usb connection is cut and then connected again.

I can paste my xorg.conf setting here is needed, just that i'm using my vista computer at the minute.

Thanks,

Anthony

mcelmeel
Posts: 33
Joined: Mon 27 Dec 2010, 13:10

#64 Post by mcelmeel »

Here is the code from my xorg.conf file.

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "touchscreen" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "gb" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/input/evtouch_event"
Option "DeviceName" "touchscreen"
Option "MinX" "0"
Option "MinY" "0"
Option "MaxX" "4095"
Option "MaxY" "4095"
Option "ReportingMode" "Raw"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection

mcelmeel
Posts: 33
Joined: Mon 27 Dec 2010, 13:10

#65 Post by mcelmeel »

Hi,

does anyone have any idea how to manually calibrate an elo serial touchscreen. My calibration is slightly off and when i run the elova calibration tool, it only gives me two targets on the right of the screen but none on the left and calibration is away off.

I need to manually change the NVRAM or something like that i think or is there a file with the settings that i could change. I've tried changing Xorg.conf but it makes no difference.

Fractal
Posts: 8
Joined: Wed 08 Dec 2010, 11:54

HID touchscreen working incorrectly.

#66 Post by Fractal »

***** SOLVED *****
***** See Below *****

Please help - I cannot get my Data Modul EasyTouch Max USB touchscreen to work.

It is a modern HID touchscreen. I have tried masses of things found mostly on this site, all to no avail. Out of interest, when I plug it into my WinXP machine it works just fine with no drivers and no calibration. It's ace.

Plugging the touchscreen into Puppy works, but the cursor does not align with my finger. The cursor moves more than my finger when I move my finger.
If I move my finger to the edge of the screen, the cursor moves faster than my finger and hits the edge first. If I continue to move my finger to the edge, then return my finger to the original position, the cursor does not return to it's original position.

The screen is definitely sending its info correctly to Puppy - I am pretty sure Puppy isn't using the positioning information properly. If so, how can I fix it?
I have contacted the manufacturer, who are very helpful, but can only say that their product works with big distros and Windoze. they have told me that the HID touchscreen declares itself as an absolute positioning device and sends absolute position information.

Using "cat /proc/bus/input/devices", I can see that it is registered as "mouse0" on "event0", but what should I do? Should I be editing xorg.conf? It's an HID screen so it does not require drivers.

Does Puppy support absolute pointing devices? If so, how can I calibrate it?

So, can anyone help me with my USB HID touchscreen problem? Thanks in advance.

***** SOLVED *****
The touchscreen required the "evdev" input driver. it's an HID-compliant device and it is the CorePointer pointing device "mouse0" / "event0".
Below is my Xorg.conf snippet, I have commented-out the lines which have no effect. The thing doesn't need to be calibrated.
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
#Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/input/event0"
#Option "Device" "/dev/input/mice"
#Option "MinX" "0"
#Option "MinY" "0"
#Option "MaxX" "800"
#Option "MaxY" "600"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
#Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
It's a nice touchscreen.

prralex1
Posts: 2
Joined: Mon 26 Sep 2011, 21:11

fujitsu stylistic st5032

#67 Post by prralex1 »

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio3/input0
S: Sysfs=/devices/platform/i8042/serio3/input/input1
U: Uniq=
H: Handlers=mouse0 event1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=13ba Product=0017 Version=0110
N: Name="Generic USB K/B"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=13ba Product=0017 Version=0110
N: Name="Generic USB K/B"
P: Phys=usb-0000:00:1d.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse1 event3
B: EV=17
B: KEY=7001f 0 0 0 c000 100000 0 0 0
B: REL=103
B: MSC=10

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Fujitsu FUJ02B1"
P: Phys=FUJ02B1/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:05/FUJ02B1:00/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=10003 0 0 0 0 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7
U: Uniq=
H: Handlers=kbd event7
B: EV=3
B: KEY=3f000b 0 0 0 0 0 0 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input8
U: Uniq=
H: Handlers=kbd event8
B: EV=40001
B: SND=6

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Fujitsu Application Panel buttons"
P: Phys=apanel/input0
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/i2c-0/0-0019/input/input9
U: Uniq=
H: Handlers=kbd event9
B: EV=3
B: KEY=8700000 0 0 0 0
====
ok, i think the touchscreen shows up as this thing:

I: Bus=0003 Vendor=13ba Product=0017 Version=0110
N: Name="Generic USB K/B"
P: Phys=usb-0000:00:1d.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse1 event3
B: EV=17
B: KEY=7001f 0 0 0 c000 100000 0 0 0
B: REL=103
B: MSC=10

i tied the handlers to mouse1 and event 3 as indicated in xorg.conf
but i'm using macpup528, and there is no server layout.

any help? :roll:

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#68 Post by tempestuous »

Google tells me your Fujitsu ST5032 has a wacom input device.
Puppy 5.1/5.2.x already contains the necessary wacom kernel module and Xorg plugin, the only thing missing is the wacom udev rule. Install it from here -
http://www.murga-linux.com/puppy/viewto ... 457#467457

Then follow the wacom configuration instructions provided by forum member don570 later in the same thread -
http://www.murga-linux.com/puppy/viewto ... 649#506649
You will see that a critical step is the creation of a new xorg.conf file, by running the xorgwizard ... this is how a "ServerLayout" section is created.

You can compare don570's xorg.conf settings to those from the official HOWTO, here -
http://linuxwacom.sourceforge.net/index ... o/inputdev
http://linuxwacom.sourceforge.net/index ... /srvlayout

and also the settings successfully used on a Fujitsu ST5022D -
http://www.alfonsomartone.itb.it/zswdjp.html

Fractal
Posts: 8
Joined: Wed 08 Dec 2010, 11:54

#69 Post by Fractal »

The final problem to solve is that the USB-touchscreen can be allocated a different event by the kernel every time it boots.

To fix this, you configure the udev subsystem to create a new device at boot-time, which is bound to the event ID which has been allocated to the touchscreen.

If you follow the links, you can get the information below, but I thought I'd condense it for you:

***How-To***

Create a file in:
/etc/udev/rules.d
called:
10-local.rules

Which contains the following:

KERNEL=="event[0-4]*", SUBSYSTEM=="input", ATTRS{idVendor}=="7374", ATTRS{idProduct}=="1100", SYMLINK+="input/touchscreen"

The {idvendor} and {idProduct} numbers are particular to the touchscreen I used - a very nice and clear HID DataModul touchscreen.

This creates a dev point for a new device called "touchscreen", only for the DataModul touchscreen, regardless of it's actual event number.
This is needed because the event number may change at boot-time.

Then, in xorg.conf, change the relevant sections to:

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "gb" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Device" "/dev/input/touchscreen
EndSection

der-schutzhund
Posts: 1045
Joined: Mon 26 Nov 2007, 22:07
Location: Blomberg / Germany

#70 Post by der-schutzhund »

Recently I am a proud owner of a TabletPC Viewsonic Viewpad 10. There is him at the moment for 299 euros. He owns Intel atom. Win7 and Android are preloaded. Now I would like to pursue this Tablet with Puppy 431. I can boot the tablet from stick, Wlan runs, sound runs. The only problem is the touchscreen. On the Internet I have read HSD101PFW3D and suppose sometimes that the touchscreen of type Hanvon 10.1 is. I have found the Pet 431 and instal, however, with it nothing does itself. Can somebody help me to get the touchscreen under 431 to the running?

many greetings

wolfgang

der-schutzhund
Posts: 1045
Joined: Mon 26 Nov 2007, 22:07
Location: Blomberg / Germany

#71 Post by der-schutzhund »

still no answer to my inquiry has presumably come up to now because not enough infos exist.
Has worked through, in the meantime, the whole Thread. However, I have not found a solution from it. I instal touchscree-puppy41.pet then modprobe usbtouchscreen and evdev.
the order: cat/proc/bus/input/device brings the following announcement and the Tocuscreen is absent.

cat /proc/bus/input/devices

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=04d9 Product=2519 Version=0110
N: Name="2.4G Wireless Touchpad Keyboard"
P: Phys=usb-0000:00:1d.0-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=04d9 Product=2519 Version=0110
N: Name="2.4G Wireless Touchpad Keyboard"
P: Phys=usb-0000:00:1d.0-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.1/input/input2
U: Uniq=
H: Handlers=kbd mouse0 event2
B: EV=1f
B: KEY=837fff 2c3027 bf004444 0 0 1f0001 f84 8a27c000 667bfa d941dfed 9e0000 0 0 0
B: REL=1c3
B: ABS=1 0
B: MSC=10

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=1700 Product=013a Version=0000
N: Name="Gotek"
P: Phys=usb-0000:00:1d.7-1/button
S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1:1.0/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=3
B: KEY=100000 0 0 0 0 0 0
-------------------------------------------------------------------------------------
the order: cat/proc/bus/usb/devices shows the Tocuscreen as an USB device (Hanvon)
sh-3.00# cat /proc/bus/usb/devices

T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.30.5 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=05 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs= 1
P: Vendor=20b3 ProdID=0a18 Rev=38.91
S: Manufacturer=Hanvon
S: Product=10.1
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=5ms

T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.30.5 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.30.5 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=3000 Rev= 2.00
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 29/900 us ( 3%), #Int= 2, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.30.5 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=04d9 ProdID=2519 Rev= 1.00
S: Product=2.4G Wireless Touchpad Keyboard
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms
I:* If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.30.5 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(unk. ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1700 ProdID=013a Rev= 0.00
S: Manufacturer=Gotek
S: Product=Gotek
S: SerialNumber=FT-1316-R5801-OV03-R08.05.00.L
C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
A: FirstIf#= 0 IfCount= 2 Cls=0e(video) Sub=03 Prot=00
I:* If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
E: Ad=83(I) Atr=03(Int.) MxPS= 16 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
I: If#= 1 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS= 128 Ivl=125us
I: If#= 1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS= 512 Ivl=125us
I: If#= 1 Alt= 3 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS=1024 Ivl=125us
I: If#= 1 Alt= 4 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS=1536 Ivl=125us
I: If#= 1 Alt= 5 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS=2048 Ivl=125us
I: If#= 1 Alt= 6 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS=2688 Ivl=125us
I: If#= 1 Alt= 7 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
E: Ad=81(I) Atr=05(Isoc) MxPS=3072 Ivl=125us

how should I go on working now?
Yours sincerely

Wolfgang

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#72 Post by Aitch »

Hi Wolfgang
I try to offer help
ViewSonic Viewpad 10

Key specifications:

10' tablet at 1024x600
Intel Atom
Hanvon touchscreen
Approximate price: 470€ (dutch brick n mortar store)

openSUSE 11.4

openSUSE 11.4 runs fine on this machine, graphics seem reasonably fast but the Blur effect in KWin's Dektop Effects has to be disabled
Problem with Hanvon touchpad, sending too many click events, makes touchscreen almost unusable. Update to 2.6.38 from openSUSE:Tumbleweed fixes this problem and makes it fully functional.
The system comes with windows 7 and Android 1.6 initially. One can keep the dualboot option, Android takes by default 2 GB of the internal storage, win7 gets the rest. The system boots with a standard grub, when installing openSUSE 11.4, make sure you note the grub config for Android so you can add this back to grub later on. oS 11.4 doesn't add Android automatically to grub's config.
Network via wifi works out of the box
Suspend works and is reasonably fast
Battery life 4 - 5 hours with web-browsing
From this I read that later kernel, 2.6.38, is needed, probably has a kernel driver, which helps send correct event messages?

tempestuous is the guy to ask with this

Aitch :)

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#73 Post by tempestuous »

der-schutzhund wrote:Recently I am a proud owner of a TabletPC Viewsonic Viewpad 10.
...
the touchscreen of type Hanvon
Apparently you need the "hid-multitouch" kernel module, available from kernel version 2.6.38 onwards.
Thus, Puppy 4.31 is not possible, neither Lucid Puppy, neither Slacko 5.3.x.

Your best chance would be Dpup Exprimo -
http://www.murga-linux.com/puppy/viewtopic.php?t=71755

And you may need to ask in that forum thread whether the hid-multitouch driver is included.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#74 Post by nooby »

A bit offtopic.

1. One tech they use is capacitive then we have resistive but
2. There is also IR light from the sides of the screen.
Would that not allow one to do some kind of DIY touch screen?

3. Another late comer is to use the microphone in the smartphone or
tablet to listen to the sound when one tap on the screen and know where one are and that way get a primitive form of touch screen. Seems odd.

But the IR light is used on Amazon Kindle their latest with E-Ink so that
seems a workable solution. Not without problem though.
Depending on how one hold it one can accidently turn pages and have to
try to get back to from where it too off :)

But IR diodes is not so expensive so as a add on to an old screen
If some firm made an inexpensive kit?
I use Google Search on Puppy Forum
not an ideal solution though

der-schutzhund
Posts: 1045
Joined: Mon 26 Nov 2007, 22:07
Location: Blomberg / Germany

#75 Post by der-schutzhund »

if 431 does not go, is a great pity because there is a German version and I have already inserted approx. 20 programmes for my lessons in it. 431 is also the version with the best hardware support I has tested up to now. Up to now everything ran with it. Is there no possibility to insert the missing module?

Yours sincerely

Wolfgang
tempestuous wrote:
der-schutzhund wrote:Recently I am a proud owner of a TabletPC Viewsonic Viewpad 10.
...
the touchscreen of type Hanvon
Apparently you need the "hid-multitouch" kernel module, available from kernel version 2.6.38 onwards.
Thus, Puppy 4.31 is not possible, neither Lucid Puppy, neither Slacko 5.3.x.

Your best chance would be Dpup Exprimo -
http://www.murga-linux.com/puppy/viewtopic.php?t=71755

And you may need to ask in that forum thread whether the hid-multitouch driver is included.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#76 Post by Aitch »

Wolfgang
There is a retro version of Lucid 525 which uses the same kernel as 431, which you could try, and might be able to upgrade kernel
Also see if a kernel upgrade can be applied to 431?
Polarpup/Icepup and Lupen also use 2.6.38, Slacko 531 has 2.6.39, and I'm using it now
see also
http://www.murga-linux.com/puppy/viewtopic.php?t=66528

Perhaps MU could help with a German version?
However I thought Internationalisation was now functional in later puppies?

Aitch :)

User avatar
J_Rey
Posts: 273
Joined: Wed 04 May 2005, 20:08
Location: Northwest Florida, U.S.A.
Contact:

#77 Post by J_Rey »

Hey, need some help figuring out what driver type to use with a Fujitsu Point 1600. Tried a bunch of the things mentioned in this but no go. Googling this machine doesn't pull up anything for what driver or even connection type it uses (USB, serial, etc.). lspci & lsusb & cat the device input & TTY & events don't seem to show up much. Any commands to definitively try?

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#78 Post by Aitch »

Don't know if this is any use?

http://www.retrevo.com/search/v2/jsp/my ... p?page=man

http://www.youtube.com/watch?v=VT7k32NkGoQ

maybe a driver from a different model?

http://tuxmobil.org/touch_laptops.html

Info's a bit sparse for that one...

Aitch :)

longobedience
Posts: 1
Joined: Sat 01 Dec 2012, 23:28

compaq tc1000 touchscreen

#79 Post by longobedience »

Hello guys. I'm an eager but very basic user of puppy and linux, and at the moment I'm trying to bring a Compaq TC1000 back to life.
Puppy (4.3.1) works fine as usual, but the touchscreen doesn't work. I installed the pet from the beginning of this thread, but I can't understand most of what comes after. Could someone please help with some 'idiot-proof' guidelines?
Cheers.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#80 Post by tempestuous »

longobedience, at the outset, you need to do some research to learn exactly what type of touchscreen device is in your laptop, and what interface it's connected to (USB, serial, or PS/2).
Then the instructions I provided on page 1 will make more sense, because you will know which section is relevant.

Fortunately for you, I just did this research for you: your touchscreen device is the Fujitsu Finepoint Stylus, which is connected to an internal serial port.

So the relevant instructions for you are - "HOWTO - serial touchscreens" -
http://www.murga-linux.com/puppy/viewto ... 651#295651
Work your way through that information carefully.
Your kernel module will be "fujitsu_ts"
and your Xorg driver will be "fujitsu" (in more recent versions of Linux this is now "fpit").

Your serial address will probably (?) be /dev/ttyS0

And just in case someone with a Compaq TC1100 stumbles upon this information - don't assume your touchscreen is the same!
It's not.

Post Reply