New IT forum

GuiPlug => GuiPlug General Discussion => Topic started by: Stephane_Varin on 11 September 2011, 06:02:28 pm

Title: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 11 September 2011, 06:02:28 pm
Hi there,

I had already bought a GuruPlug and a Mimo Touch Screen but was never able to make it work well, so I recently bought a GuiPlug, without buying a screen since I had already one.

At first, everything seem to work, the GuiPlug booted on the screen, but unfortunately, impossible to interact through the touch screen, as if the touch interface was not properly configured.

I decided to reboot the plug, and since then it seems to always boot in "vnc mode". I manage to vnc to the plug and everything is working fine, but I would really need to make the screen work.

Any advice how to proceed? A configuration file I should update/delete?

Many thanks in advance.

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 11 September 2011, 06:49:33 pm
Stephane,

Try with v2.6

http://www.newit.co.uk/forum/index.php/topic,2246.msg6342.html#msg6342 (http://www.newit.co.uk/forum/index.php/topic,2246.msg6342.html#msg6342)

NewITJames
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 13 September 2011, 04:24:10 am
Edit: Nevermind that post, tested on another laptop and the SD card mounts just fine...Back to burning the image to the card now...

Hi James,

Thanks for the quick reply. I downloaded the v2.6 image and extracted it, but I am facing a new problem: I am not able to mount the SD card. I have tried both my laptop's internal SD card reader, and an external USB card reader, but impossible to see the card...
I have checked on the GuiPlug, it is still working fine, but it doesn't show up on my laptop.

How do I copy the image on the card then? I assume I need to use the command 'dd' for that, but I don't know what to put for destination...

Sorry if this is an obvious question.

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 16 September 2011, 09:02:10 am
Finally had the time to burn the v2.6 image on the SD card and boot up the GuiPlug.

Unfortunately, it still doesn't work. Exact same behavior.

Plug boots fine, screen comes up fine, things are moving around as they should at boot time, little thingy rotating and all, but once everything is ready, I cannot interact through the touch screen, nothing moves, no way to 'click' the menu or move the cursor...If I don't plug in the monitor, I can VNC to the plug with no problem, so I believe it has something to do with the "touch" part of the touch screen?

Could it be that a config file got created with wrong parameters and is still hanging around and causes the touch interface to not work?
Anything i should check, any log file or config file I could submit to check with you?

Stephane

Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 16 September 2011, 09:16:17 am
Stephane,

Could you  plug the monitor into the booted plug and post a dmesg log please.

NewITJames
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 17 September 2011, 02:28:03 pm
Hi James,

Here are the output of dmesg from the GuiPlug. Noob as I am, I cannot make much of it, but it looks like the screen was identified successfully, to a certain point...

Code: [Select]
Initializing cgroup subsys cpu
Linux version 2.6.38.8 ([email protected]) (gcc version 4.5.3 (PlugComputer G++ 20110530) ) #2 PREEMPT Tue Jun 14 01:44:32 MDT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c0581564, node_mem_map c0651000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 513288k/513288k available, 11000k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xe0800000 - 0xfe800000   ( 480 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc002f000   ( 156 kB)
      .text : 0xc002f000 - 0xc054e288   (5245 kB)
      .data : 0xc0550000 - 0xc0583898   ( 207 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
  final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
FS-Cache: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
FS-Cache: Netfs 'nfs' registered for caching
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32080
msgmni has been set to 1002
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 2152 at 0x000010d00000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:9a:52
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Registering the dns_resolver key type
Gating clock of unused units
before: 0x00c701dd
 after: 0x00c701d9
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2011-09-17 14:08:23 UTC (1316268503)
Waiting 5sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 61a6
mmcblk0: mmc0:61a6 SD08G 7.68 GiB
 mmcblk0: p1 p2
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 156K
fuse init (API version 7.16)
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 100 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
sshd (1279): /proc/1279/oom_adj is deprecated, please use /proc/1279/oom_score_adj instead.
eth0: no IPv6 routers present
usb 1-1: new high speed USB device using orion-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
hub 1-1.1:1.0: USB hub found
hub 1-1.1:1.0: 4 ports detected
usb 1-1.1.2: new high speed USB device using orion-ehci and address 4
usb 1-1.1.3: new full speed USB device using orion-ehci and address 5
udlfb: DisplayLink AT-7 - serial #200528
udlfb: vid_17e9&pid_02fc&rev_0104 driver's dlfb_data struct at de452000
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01
udlfb: DL chip limited to 1500000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
udlfb: DisplayLink USB device /dev/fb0 attached. 800x480 resolution. Using 1504K framebuffer memory
usbcore: registered new interface driver udlfb
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/input/input0
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/input/input1
generic-usb 0003:0EEF:0001.0001: input: USB HID v2.10 Pointer [eGalax I USB Touc] on usb-orion-ehci.0-1.1.3/input0
usbcore: registered new interface driver usbtouchscreen

Thanks for the help.

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 18 September 2011, 08:14:56 am
Stephane,

could you post the output from 'lsusb' please.

NewITJames
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 18 September 2011, 02:23:32 pm
Hi James,

Here is the result of lsusb:

Code: [Select]
Bus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 001 Device 004: ID 17e9:02fc Newnham Research
Bus 001 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 18 September 2011, 05:24:22 pm
An iMo pivot is detected

Quote
Bus 001 Device 004: ID 17e9:02fc Newnham Research

The GuiPlugInit should have run and done the following
Code: [Select]
cp /usr/share/X11/xorg.conf.pivot /usr/share/X11/xorg.conf.d/xorg.conf
So does your  /usr/share/X11/xorg.conf.d/xorg.conf look like below?
Code: [Select]
# xorg.conf (X.Org X Window System server configuration file) 
 ################################################# 
 Section     "ServerLayout" 
     Identifier   "Server Layout" 
     Screen 0    "MimoScreen" 0 0 
 EndSection 
 ################################################# 
 Section     "Device" 
     Identifier   "MimoDevice" 
     driver     "fbdev" 
     Option     "fbdev" "/dev/fb0" 
 EndSection 
 
Section     "Monitor" 
     Identifier   "MimoMonitor" 
EndSection 

Section     "Screen" 
     Identifier "MimoScreen" 
     Device     "MimoDevice" 
     Monitor    "MimoMonitor" 
EndSection 

Section "InputClass"
        Identifier "iMo Pivot"
        MatchProduct "eGalax Inc. USB TouchController"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons" "false"
        Option "SendCoreEvents" "On"
        Option "InvertX" "false"
        Option "InvertY" "true"
        Option "Calibration" "4014 98 3965 149"
EndSection


NewITJames
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 18 September 2011, 08:22:15 pm
Hi James,

Yes, it looks exactly identical (here is the copy from my Plug):

Code: [Select]
# xorg.conf (X.Org X Window System server configuration file) 
 ################################################# 
 Section     "ServerLayout" 
     Identifier   "Server Layout" 
     Screen 0    "MimoScreen" 0 0 
 EndSection 
 ################################################# 
 Section     "Device" 
     Identifier   "MimoDevice" 
     driver     "fbdev" 
     Option     "fbdev" "/dev/fb0" 
 EndSection 
 
Section     "Monitor" 
     Identifier   "MimoMonitor" 
EndSection 

Section     "Screen" 
     Identifier "MimoScreen" 
     Device     "MimoDevice" 
     Monitor    "MimoMonitor" 
EndSection 

Section "InputClass"
        Identifier "iMo Pivot"
        MatchProduct "eGalax Inc. USB TouchController"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons" "false"
        Option "SendCoreEvents" "On"
        Option "InvertX" "false"
        Option "InvertY" "true"
        Option "Calibration" "4014 98 3965 149"
EndSection

 

Somehow, I feel that it is not going to help  :-\

Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 18 September 2011, 09:31:02 pm
Stephane,

Could you post the output from 'ls /dev/input -l'

You should have event 0-2 in that listing so try 'cat /dev/input/event2' then touch the screen, do you see output? (CTRL-C to quit)

Have you tried the monitor on a Desktop PC to confirm that it's not actually a hardware fault?

If you plug in a Usb mouse does the Cursor move normally?

NewITJames

Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 19 September 2011, 08:51:56 pm
Hi James,

Code: [Select]
[email protected]:~# ls /dev/input -l
total 0
drwxr-xr-x 2 root root     80 Sep 19 20:41 by-id
drwxr-xr-x 2 root root     80 Sep 19 20:41 by-path
crw------- 1 root root 13, 64 Sep 19 20:41 event0
crw------- 1 root root 13, 65 Sep 19 20:41 event1
crw------- 1 root root 13, 63 Sep 19 20:41 mice
crw------- 1 root root 13, 32 Sep 19 20:41 mouse0
crw------- 1 root root 13, 33 Sep 19 20:41 mouse1

I have only event0 and event1, no event2. Could this be the problem?

I have tested with a usb mouse plugged on the 4 port usb hub, the cursor does move normally.

I have not been able to test on another pc, my ubuntu laptop does not seem to support the monitor, I only get a green screen. But I can confirm it was working with the GuruPlug I had bought previously (with GuiPlug on a usb stick...)

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 22 September 2011, 07:14:54 pm
Anything else I should try? Is this result completely unbelievable? I could have made a mistake in the previous steps...
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 22 September 2011, 07:33:06 pm
Quote
try 'cat /dev/input/event2' then touch the screen
Try James's suggestion with 'event1', the system thinks you have two mice, chances are the second is the touch screen.

If that fails, post the results of

Code: [Select]
grep -C3 'No input driver/identifier' /var/log/Xorg.0.log
and

Code: [Select]
grep -C3 'XINPUT'  /var/log/Xorg.0.log
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 25 September 2011, 01:54:02 pm
Hi Confusticated,

Thanks for the help.

Unfortunately, cat /dev/input/event1 does nothing (neither does event0)

Code: [Select]
grep -C3 'No input driver/identifier' /var/log/Xorg.0.log

(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: MOUSE)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/event1)
(**) eGalax I USB Touc: Applying InputClass "evdev tablet catchall"
(**) eGalax I USB Touc: always reports core events
--
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: TABLET)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)

Code: [Select]
grep -C3 'XINPUT'  /var/log/Xorg.0.log

(II) eGalax I USB Touc: Configuring as mouse
(**) eGalax I USB Touc: YAxisMapping: buttons 4 and 5
(**) eGalax I USB Touc: EmulateWheelButton: 4, EmulateWheelInertia: 10, Emulate$
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: MOUSE)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
--
(II) eGalax I USB Touc: Configuring as tablet
(**) eGalax I USB Touc: YAxisMapping: buttons 4 and 5
(**) eGalax I USB Touc: EmulateWheelButton: 4, EmulateWheelInertia: 10, Emulate$
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: TABLET)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)

Looks like the touch screen is indeed identified as a mouse...I suppose it shouldn't ?

I am lost here guys, sorry to be such a pain, I have no clue what to do next...
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 25 September 2011, 04:45:08 pm
Stephane,

I think it's likely that you either have Usb Monitor that does not support touchscreen (some don't) or there is a problem with it.

The best thing to do is try the monitor on a Windows PC and see if your hardware is faulty or not.

NewITJames
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 25 September 2011, 05:22:46 pm
Quote
Applying InputClass "evdev tablet catchall"
This is what I was looking for (but didn't want to see).
It means the the configuration section in your xorg.conf file is not being applied.

Quote
MatchProduct "eGalax Inc. USB TouchController"
Is failing, your device is reported using the truncated string
"eGalax I USB Touc".

From the logs, your touchscreen is being set up as /dev/input/event1.
It is being identified as a TABLET device, not a touchscreen.
It is NOT sending core events, the opposite of what you require.
(Maybe a New IT staff member can confirm which is normal 'TABLET' or 'TOUCHSCREEN').

I suggest you replace the current 'MatchProduct' string with the reported one.

NB I have never seen a truncated string like this before.
Be absolutely certain that the monitor has an adequate power supply and good electrical connections.
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 28 September 2011, 07:45:45 pm
Stephane,

I think it's likely that you either have Usb Monitor that does not support touchscreen (some don't) or there is a problem with it.

The best thing to do is try the monitor on a Windows PC and see if your hardware is faulty or not.

NewITJames

Hi NewITJames,

I am positive this is a touchscreen monitor, iMo Pivot Touch to be specific.

I did manage to make it work once with your help with a GuruPlug and the system on a usb stick but the performance was not great (euphemism...) so I decided to buy the GuiPlug alone since I already had the same monitor you offer on your site. 

Unfortunately, on my work PC (windows XP) I do not have sufficient privileges to install the drivers...The world is a hard place for poor guys like me :-(

Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 28 September 2011, 08:17:28 pm
Hi Confusticated,

Quote
I suggest you replace the current 'MatchProduct' string with the reported one.

I tried to modify directly my xorg.conf file, but each time I reboot the changes were overwritten.

So I updated this file: /usr/share/X11/xorg.conf.pivot with the same changes you suggested, and this time the content of xorg.conf remains what you suggested after reboot, but unfortunately, touch is still not working.

Quote
Be absolutely certain that the monitor has an adequate power supply and good electrical connections.

I have tried different settings, because I wasn't sure how to do this. Currently, the monitor has a dual end usb cord, one end attached to the GuiPlug, the other attached to a powered usb hub...

At this point, I am happy to try anything you guys can think of...I am ready to buy an additional iMo Pivot Touch directly from NewIT if you think that will make a difference...

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 28 September 2011, 08:59:05 pm
Stephane,

For comparison this is the dmesg output below when I plug an iMo pivot AT-7 into a Dreamplug running GuiPlug v2.6

Code: [Select]
[email protected]:~# usb 1-1.3: new high speed USB device using orion-ehci and address 5
hub 1-1.3:1.0: USB hub found
hub 1-1.3:1.0: 4 ports detected
usb 1-1.3.2: new high speed USB device using orion-ehci and address 6
usb 1-1.3.3: new full speed USB device using orion-ehci and address 7
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/input/input1
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/input/input2
generic-usb 0003:0EEF:0001.0002: input: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-orion-ehci.0-1.3.3/input0
usbcore: registered new interface driver usbtouchscreen
udlfb: DisplayLink AT-7 - serial #200331
udlfb: vid_17e9&pid_02fc&rev_0104 driver's dlfb_data struct at de43b000
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01
udlfb: DL chip limited to 1500000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
udlfb: DisplayLink USB device /dev/fb0 attached. 800x480 resolution. Using 1504K framebuffer memory
usbcore: registered new interface driver udlfb

Another possible problem is usb power or lack of it, the Sheevaplug barely has the usb output to drive the Pivot whilst the Dreamplug can power it fine. We always recommend using one of our 7-port usb hubs with the Sheeva and Pivot which puts enough 5v back up the usb to power the plug and the monitor (most powered hubs don't do this).

http://www.newit.co.uk/shop/proddetail.php?prod=7_Port_Hub (http://www.newit.co.uk/shop/proddetail.php?prod=7_Port_Hub)
http://www.newit.co.uk/forum/index.php/topic,699.0.html (http://www.newit.co.uk/forum/index.php/topic,699.0.html)
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 28 September 2011, 09:26:06 pm

I have a D-Link 4 port usb hub...So I guess that could be the cause...ok, I can always have a need of another usb hub  ::) I'll get one from your site...

To be continued when I receive it...

Cheers,
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 28 September 2011, 10:57:05 pm
Quote
/usr/share/X11/xorg.conf.pivot
Don't forget to restore the original contents 'MatchProduct' string :)
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 09 October 2011, 03:45:53 pm
Hi guys,

I am really gratefull for all the help provided so far, I hope you can still help me further.

I received the usb hub yesterday, time for me to buy the french power adapter and I finally had the chance to test...
Unfortunately, still the same problem, no touch interface...

Here is a recap of the situation:

- GuiPlug v2.6
- iMo AT-7 touch monitor
- Pluscom 7port usb hub

Plug boots up fine, screen comes up fine, when mouse plugged, cursor moves fine, but touch interface not working.

dmesg gives this:

Code: [Select]
Initializing cgroup subsys cpu
Linux version 2.6.38.8 ([email protected]) (gcc version 4.5.3 (PlugComputer G++ 20110530) ) #2 PREEMPT Tue Jun 14 01:44:32 MDT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c0581564, node_mem_map c0651000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 513288k/513288k available, 11000k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xe0800000 - 0xfe800000   ( 480 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc002f000   ( 156 kB)
      .text : 0xc002f000 - 0xc054e288   (5245 kB)
      .data : 0xc0550000 - 0xc0583898   ( 207 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
  final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
FS-Cache: Loaded
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
FS-Cache: Netfs 'nfs' registered for caching
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4010, nTxLock = 32080
msgmni has been set to 1002
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 2152 at 0x000010d00000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:9a:52
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plug:green:health
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Registering the dns_resolver key type
Gating clock of unused units
before: 0x00c701dd
 after: 0x00c701d9
registered taskstats version 1
rtc-mv rtc-mv: setting system clock to 2011-10-09 14:59:31 UTC (1318172371)
Waiting 5sec before mounting root device...
usb 1-1: new high speed USB device using orion-ehci and address 2
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 61a6
mmcblk0: mmc0:61a6 SD08G 7.68 GiB
 mmcblk0: p1 p2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high speed USB device using orion-ehci and address 3
hub 1-1.1:1.0: USB hub found
hub 1-1.1:1.0: 4 ports detected
usb 1-1.1.4: new high speed USB device using orion-ehci and address 4
hub 1-1.1.4:1.0: USB hub found
hub 1-1.1.4:1.0: 4 ports detected
usb 1-1.1.4.2: new high speed USB device using orion-ehci and address 5
usb 1-1.1.4.3: new full speed USB device using orion-ehci and address 6
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input0
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input1
generic-usb 0003:0EEF:0001.0001: input: USB HID v2.10 Pointer [eGalax I USB Touc] on usb-orion-ehci.0-1.1.4.3/input0
EXT3-fs: barriers not enabled
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 156K
udlfb: DisplayLink AT-7 - serial #200528
udlfb: vid_17e9&pid_02fc&rev_0104 driver's dlfb_data struct at df126000
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01
udlfb: DL chip limited to 1500000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
udlfb: DisplayLink USB device /dev/fb0 attached. 800x480 resolution. Using 1504K framebuffer memory
usbcore: registered new interface driver udlfb
fuse init (API version 7.16)
udlfb: open /dev/fb0 user=1 fb_info=df170c00 count=1
udlfb: released /dev/fb0 user=1 count=0
udlfb: open /dev/fb0 user=1 fb_info=df170c00 count=1
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: link up, 100 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udlfb: released /dev/fb0 user=1 count=0
sshd (1312): /proc/1312/oom_adj is deprecated, please use /proc/1312/oom_score_adj instead.
udlfb: open /dev/fb0 user=1 fb_info=df170c00 count=1
udlfb: released /dev/fb0 user=1 count=0
udlfb: open /dev/fb0 user=1 fb_info=df170c00 count=1
eth0: no IPv6 routers present
EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended

I see a couple of things that seem weird:

Code: [Select]
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input0
input: eGalax I USB Touc as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input1
generic-usb 0003:0EEF:0001.0001: input: USB HID v2.10 Pointer [eGalax I USB Touc] on usb-orion-ehci.0-1.1.4.3/input0

compared to what NewIT_James has posted:

Code: [Select]
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/input/input1
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/input/input2
generic-usb 0003:0EEF:0001.0002: input: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-orion-ehci.0-1.3.3/input0

In my case, only input0 and input1 are mentionned, when it is input0, input1 and input2 for NewIT_James...Does that lead to something?

Also, is this a problem?
Code: [Select]
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
And In NewIT_James file, I see the following:

Code: [Select]
usbcore: registered new interface driver usbtouchscreen
but not in my dmesg.

I also post the various commands you suggested previously, ran with the new usb hub...
lsusb:

Code: [Select]
Bus 001 Device 005: ID 17e9:02fc Newnham Research
Bus 001 Device 006: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 001 Device 004: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 003: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

grep -C3 'No input driver/identifier' /var/log/Xorg.0.log:

Code: [Select]
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: MOUSE)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/event1)
(**) eGalax I USB Touc: Applying InputClass "evdev tablet catchall"
(**) eGalax I USB Touc: always reports core events
--
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: TABLET)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)

grep -C3 'XINPUT'  /var/log/Xorg.0.log:

Code: [Select]
(II) eGalax I USB Touc: Configuring as mouse
(**) eGalax I USB Touc: YAxisMapping: buttons 4 and 5
(**) eGalax I USB Touc: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: MOUSE)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
--
(II) eGalax I USB Touc: Configuring as tablet
(**) eGalax I USB Touc: YAxisMapping: buttons 4 and 5
(**) eGalax I USB Touc: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "eGalax I USB Touc" (type: TABLET)
(II) eGalax I USB Touc: initialized for absolute axes.
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)

It really looks like the touchscreen is configured as a mouse and not as a touchscreen, right?

Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 09 October 2011, 04:03:33 pm
Hi again,

I did another test, just to see, in the directory "/usr/share/X11/xorg.conf.d" I renamed the following files:

10-evdev.conf.bak
20-wacom.conf.bak
50-synaptics.conf.bak

and now here is what I get:

Code: [Select]
grep -C3 'No input driver/identifier' /var/log/Xorg.0.log
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/event0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/event1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)

So it really looks like xorg.conf is not used at all to configure the screen, but 10-evdev.conf was used in its stead, right? So the question is, why is it using this file and not xorg.conf?
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 09 October 2011, 07:40:40 pm
Xorg uses configuration files in a hierarchical structure.

It looks for a matching configuration section in
Code: [Select]
/etc/X11/xorg.conf
/etc/X11/xorg.conf.d/*.conf
/usr/share/X11/xorg.conf.d/*.conf
in that order, using the first match it finds.

User written system configuration files should be placed in /etc/X11/xorg.conf.d/
(I have the details of my three different monitors in three different files
I then refer to the monitor I want for a specific layout in /etc/X11/xorg.conf )

The config files in /usr/share/X11/xorg.conf.d/ are generic catchalls provided by
packages for your distro as a fallback, and usually contain no specific configuration
information (in the hope that the device is generic enough to 'just work' with the driver installed).

To answer your question, the touchscreen section in xorg.conf is failing to match the device found.
See the "MatchProduct" parameter below, it fails, Xorg ignores this and moves on to the next config file.
Quote
Section "InputClass"
        Identifier "iMo Pivot"
        MatchProduct "eGalax Inc. USB TouchController"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons" "false"
        Option "SendCoreEvents" "On"
        Option "InvertX" "false"
        Option "InvertY" "true"
        Option "Calibration" "4014 98 3965 149"
EndSection

I still do not understand why you are getting a corrupted identification.
Quote
eGalax I USB Touc
This begs the question, what else is being corrupted ?


Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 09 October 2011, 09:03:51 pm
There is one common system we have not looked at.
All of this is tied together by udev, it may be worth having a poke around there.

run
Code: [Select]
udevadm monitor

and then plug the monitor in, maybe James could do the same after you have posted the output.
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 09 October 2011, 09:18:06 pm
Hi Confusticated,

Thanks for your help, I really appreciate.

Here is the result of the execution of "udevadm monitor" when first un-plugging then re-plugging the monitor:

Code: [Select]
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1318194867.733392] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/graphics/fb1 (graphics)
UDEV  [1318194867.735328] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/graphics/fb1 (graphics)
KERNEL[1318194867.735741] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/1-1.1.4.2:1.0 (usb)
UDEV  [1318194867.736382] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/1-1.1.4.2:1.0 (usb)
KERNEL[1318194867.738628] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/usb_device/usbdev1.16 (usb_device)
UDEV  [1318194867.739631] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/usb_device/usbdev1.16 (usb_device)
KERNEL[1318194867.740336] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2 (usb)
UDEV  [1318194867.745874] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2 (usb)
KERNEL[1318194867.757642] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4/mouse0 (input)
UDEV  [1318194867.760655] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4/mouse0 (input)
KERNEL[1318194867.772699] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4/event0 (input)
UDEV  [1318194867.776416] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4/event0 (input)
KERNEL[1318194867.794468] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4 (input)
KERNEL[1318194867.794565] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5/mouse1 (input)
UDEV  [1318194867.796729] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5/mouse1 (input)
UDEV  [1318194867.798246] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input4 (input)
KERNEL[1318194867.812792] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5/event1 (input)
UDEV  [1318194867.815219] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5/event1 (input)
KERNEL[1318194867.836407] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5 (input)
KERNEL[1318194867.836531] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/0003:0EEF:0001.0003 (hid)
KERNEL[1318194867.836626] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0 (usb)
KERNEL[1318194867.836712] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/usb_device/usbdev1.17 (usb_device)
KERNEL[1318194867.836813] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3 (usb)
KERNEL[1318194867.836905] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0 (usb)
KERNEL[1318194867.836987] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/usb_device/usbdev1.15 (usb_device)
KERNEL[1318194867.837084] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4 (usb)
KERNEL[1318194867.837174] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0 (usb)
KERNEL[1318194867.837256] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/usb_device/usbdev1.14 (usb_device)
KERNEL[1318194867.837356] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1 (usb)
KERNEL[1318194867.837447] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[1318194867.837529] remove   /devices/platform/orion-ehci.0/usb1/1-1/usb_device/usbdev1.13 (usb_device)
KERNEL[1318194867.837639] remove   /devices/platform/orion-ehci.0/usb1/1-1 (usb)
UDEV  [1318194867.842906] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/0003:0EEF:0001.0003 (hid)
UDEV  [1318194867.845107] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/usb_device/usbdev1.14 (usb_device)
UDEV  [1318194867.846315] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0 (usb)
UDEV  [1318194867.848928] remove   /devices/platform/orion-ehci.0/usb1/1-1/usb_device/usbdev1.13 (usb_device)
UDEV  [1318194867.849971] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input5 (input)
UDEV  [1318194867.851266] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0 (usb)
UDEV  [1318194867.853865] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0 (usb)
UDEV  [1318194867.855823] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/usb_device/usbdev1.15 (usb_device)
UDEV  [1318194867.856548] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0 (usb)
UDEV  [1318194867.858296] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/usb_device/usbdev1.17 (usb_device)
UDEV  [1318194867.863561] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3 (usb)
UDEV  [1318194867.866682] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4 (usb)
UDEV  [1318194867.869829] remove   /devices/platform/orion-ehci.0/usb1/1-1/1-1.1 (usb)
UDEV  [1318194867.872994] remove   /devices/platform/orion-ehci.0/usb1/1-1 (usb)
KERNEL[1318194874.233466] add      /devices/platform/orion-ehci.0/usb1/1-1 (usb)
KERNEL[1318194874.237607] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[1318194874.247006] add      /devices/platform/orion-ehci.0/usb1/1-1/usb_device/usbdev1.18 (usb_device)
UDEV  [1318194874.252093] add      /devices/platform/orion-ehci.0/usb1/1-1 (usb)
UDEV  [1318194874.259392] add      /devices/platform/orion-ehci.0/usb1/1-1/usb_device/usbdev1.18 (usb_device)
UDEV  [1318194874.268080] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1:1.0 (usb)
KERNEL[1318194874.633475] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1 (usb)
KERNEL[1318194874.637947] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0 (usb)
KERNEL[1318194874.647647] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/usb_device/usbdev1.19 (usb_device)
UDEV  [1318194874.654293] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1 (usb)
UDEV  [1318194874.661759] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/usb_device/usbdev1.19 (usb_device)
UDEV  [1318194874.670706] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0 (usb)
KERNEL[1318194875.033237] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4 (usb)
KERNEL[1318194875.038036] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0 (usb)
KERNEL[1318194875.053926] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/usb_device/usbdev1.20 (usb_device)
UDEV  [1318194875.055076] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4 (usb)
UDEV  [1318194875.063330] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/usb_device/usbdev1.20 (usb_device)
UDEV  [1318194875.072644] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0 (usb)
KERNEL[1318194875.466714] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2 (usb)
KERNEL[1318194875.471566] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/1-1.1.4.2:1.0 (usb)
KERNEL[1318194875.610290] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/graphics/fb1 (graphics)
KERNEL[1318194875.620308] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/usb_device/usbdev1.21 (usb_device)
UDEV  [1318194875.628818] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2 (usb)
UDEV  [1318194875.635019] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/graphics/fb1 (graphics)
UDEV  [1318194875.649257] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/usb_device/usbdev1.21 (usb_device)
UDEV  [1318194875.666974] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.2/1-1.1.4.2:1.0 (usb)
KERNEL[1318194875.854486] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3 (usb)
KERNEL[1318194875.859302] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0 (usb)
KERNEL[1318194875.859691] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/0003:0EEF:0001.0004 (hid)
KERNEL[1318194880.855995] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6 (input)
KERNEL[1318194880.867585] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6/mouse0 (input)
KERNEL[1318194880.868040] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6/event0 (input)
KERNEL[1318194880.868579] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7 (input)
KERNEL[1318194880.879958] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7/mouse1 (input)
KERNEL[1318194880.880408] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7/event1 (input)
KERNEL[1318194880.891635] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/usb_device/usbdev1.22 (usb_device)
UDEV  [1318194880.900163] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3 (usb)
UDEV  [1318194880.909476] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/usb_device/usbdev1.22 (usb_device)
UDEV  [1318194880.919390] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0 (usb)
UDEV  [1318194880.938193] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7 (input)
UDEV  [1318194880.948141] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6 (input)
UDEV  [1318194880.975883] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/0003:0EEF:0001.0004 (hid)
UDEV  [1318194881.024259] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7/mouse1 (input)
UDEV  [1318194881.029289] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6/mouse0 (input)
UDEV  [1318194881.034990] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input7/event1 (input)
UDEV  [1318194881.041422] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4.3/1-1.1.4.3:1.0/input/input6/event0 (input)
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 09 October 2011, 10:00:32 pm
I forgot to mention
Quote
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/event1)
(**) eGalax I USB Touc: Applying InputClass "evdev tablet catchall"
(**) eGalax I USB Touc: always reports core events

Is where xorg is accepting
Quote
Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection
in '/usr/share/X11/xorg.conf.d/10-evdev.conf'

Unfortunately the 'evdev' driver can't handle the touchscreen correctly with this missing
Quote
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons" "false"
        Option "SendCoreEvents" "On"
        Option "InvertX" "false"
        Option "InvertY" "true"
        Option "Calibration" "4014 98 3965 149"
You could try pasting it in just to see what happens, but it is not the proper fix for your problem.

I can't see anything obviously wrong in the "udevadm monitor" output,
I have no idea where to go from here software wise.

How to debug the hardware ?
Got a PC with windoze that you can plug the monitor into, boot off a Live CD ?
Sorry Stephane, more questions, no answers.....



Title: Re: GuiPlug does not see touch screen?
Post by: NewITMalcolm on 09 October 2011, 10:32:40 pm
iMo touch being plugged into a Dreamplug with Gui v2.6


Quote
udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

KERNEL - the kernel uevent


usb 1-1.2: new high speed USB device using orion-ehci and address 9

KERNEL[1318199424.509624] add      /devices/platform/orion-ehci.hub 1-1.2:1.0: USB hub found
0/usb1/1-1/1-1.2 (usb)
KERNEL[1318199424.514476hub 1-1.2:1
.0: 4 ports detected
] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb)
UDEV  [1318199424.531711] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2 (usb)
KERNEL[1318199424.534667] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/usb_device/usbdev1.9 (usb_device)
UDEV  [1318199424.540755] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/usb_device/usbdev1.9 (usb_device)
UDEV  [1318199424.550076] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb)

usb 1-1.2.2: new high speed USB device using orion-ehci and address 10

KERNEL[1318199424.943022] add      /devices/platform/orion-ehci.udlfb: DisplayLink AT-7 - serial #200331
0/usb1/1-1/1-1
.2/1-1.2.2 (usb)
KERNEL[131819942udlfb: vid_17e9&pid_02fc&rev_0104 driver's dlfb_data struct at df244000
4.948079] add   udlfb: console enable=0
   /devices/platudlfb: fb_defio enable=1
form/orion-ehci.udlfb: vendor descriptor length:23 data:23 5f 01 0021 00 04 04 07 00 01
0/usb1/1-1/1-1.2udlfb: DL chip limited to 1500000 pixel modes
/1-1.2.2/1-1.2.2udlfb: allocated 4 65024 byte urbs
:1.0 (usb)

udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
KERNEL[131819942udlfb: DisplayLink USB device /dev/fb0 attached. 800x480 resolution. Using 1504K framebuffer memory
5.094793] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/graphics/fb0 (graphics)
KERNEL[1318199425.106057] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/usb_device/usbdev1.10 (usb_device)
UDEV  [1318199425.113851] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2 (usb)
UDEV  [1318199425.119802] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/graphics/fb0 (graphics)
UDEV  [1318199425.133405] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/usb_device/usbdev1.10 (usb_device)
UDEV  [1318199425.151800] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0 (usb)

usb 1-1.2.3: new full speed USB device using orion-ehci and address 11

KERNEL[1318199425.340926] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3 (usb)
KERNEL[131819942input: eGalax Inc. USB Touch
Controller as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5
5.346501] add      /devices/platform/orion-ehci.input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6
0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3generic-usb 0003:0EEF:0001.0005: input: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-orion-ehci.0-1.2.3/input0
:1.0 (usb)
KERNEL[1318199425.346985] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/0003:0EEF:0001.0005 (hid)
KERNEL[1318199425.350076] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5 (input)
KERNEL[1318199425.363990] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5/mouse0 (input)
KERNEL[1318199425.364513] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5/event0 (input)
KERNEL[1318199425.365066] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6 (input)
KERNEL[1318199425.376934] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6/mouse1 (input)
KERNEL[1318199425.377409] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6/event1 (input)
KERNEL[1318199425.391142] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/usb_device/usbdev1.11 (usb_device)
UDEV  [1318199425.398742] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3 (usb)
UDEV  [1318199425.407287] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/usb_device/usbdev1.11 (usb_device)
UDEV  [1318199425.417214] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0 (usb)
UDEV  [1318199425.434727] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6 (input)
UDEV  [1318199425.444811] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5 (input)
UDEV  [1318199425.472478] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/0003:0EEF:0001.0005 (hid)
UDEV  [1318199425.524776] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6/mouse1 (input)
UDEV  [1318199425.529243] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5/mouse0 (input)
UDEV  [1318199425.533198] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input6/event1 (input)
UDEV  [1318199425.538427] add      /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input5/event0 (input)
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 10 October 2011, 01:10:30 pm
Looking at that, and re-reading all the previous posts, I think that it is a hardware fault in the touchscreen (which is separate from the display) part of the monitor.
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 10 October 2011, 01:24:54 pm

I'll try to test the touchscreen with a windows computer to rule that out.

I will need to get access to a computer where I will be allowed to install the drivers.

Are you positive that the touchscreen should work out of the box with windows?

Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 11 October 2011, 04:03:45 am
Have not been able to test on windows yet, just an additional thought.

If it is a "hardware" problem, it doesn't explain why this:

Code: [Select]
(II) config/udev: Adding input device eGalax I USB Touc (/dev/input/mouse0)
I mean, if I folllow your reasoning correctly, it is because of the incorrect MatchProduct line that the xorg.conf file is not used, right? I don't know if a hardware problem would cause this, would it?

Now, looking at your web site, I see that the picture of the iMo Pivot Touch you are selling is slightly different from the one I have. So it is likely that my model is an earlier version from the model sold by NewIT, which would probably explain the different behaviour (and the MatchProduct problem)

If that is indeed the reason, I also understand it is not NewIT responsibility, I should have bought the screen together with the GuiPlug, but again, I already had the screen, I thought it was going to work.

The question in that case would be: what needs to be changed to get this screen to be "correctly" recognized and configured? Is it a driver version problem?
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 11 October 2011, 09:28:15 am
Here is my reasoning, please comment on anything you feel is wrong or anything I have ommitted:

However you look at it, this
Quote
eGalax I USB Touc
should be this
Quote
"eGalax Inc. USB TouchController"
the string is mangled, which to me implies a communication problem.
(OK it could possibly be 'eGalax Inc. USB TouchScreen'  or even just 'eGalax Inc. USB Touch' on a different model release, but no way are they going to truncate the 'Inc' part of the company name).

Software communication issues:
It is unlikely to be a kernel module (udlfb) problem, but it has not been ruled out, you would be the only reported user suffering it if it is.
The module in some form has been around since 2009 (tried & tested in the wild).
The rest of the USB infrastructure is well established, and would most probably affect other USB devices if it had issues.

Hardware communication issues:
There is little point in swapping USB ports on the plug, they are all on the same hub.

On a PC you will  (usually) be able to swap between USB 1 & USB 2 ports (worth trying).
If you get the same when plugged into a different computer running a different OS, the only component that has remained constant is the monitor itself.
You may not need to install widows drivers (if it's been around since 2009, is should be in Windows 7).
If you can get at 'device manager', look for the touchscreen identification string.

Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 15 October 2011, 03:54:56 pm
Halas, finally got a chance to test the monitor with a Windows Vista PC...and the touch does not work. The display works fine, but it looks like the screen presented itself as a tablet...

So Confusticated, James, you were right, looks like this is a hardware problem.

I am going send NewIT another pile of cash and get another touch screen  :-\

Anyway, this might sound crazy, but I am still really enjoying this tinkering around with the stuff, banging my head on a wall, having to investigate and eventually figuring it out. Hopefully, I will get a screen that works and in the end I will be able to share with you guys the final result (don't get too excited, it's rather lame...)

Thanks again very much for your help.

Until next time.

Cheers
Stephane
Title: Re: GuiPlug does not see touch screen?
Post by: Confusticated on 15 October 2011, 07:28:21 pm
It is a well recorded fact that 'you will learn more about computers using a broken one' than you will one that works :)
Title: Re: GuiPlug does not see touch screen?
Post by: Stephane_Varin on 29 December 2011, 11:39:49 am
Hi all,

Just wanted to "close" the thread by saying that everything is working just fine, I have finally found the time to complete my little pet project. A lame inventory manager, nothing extraordinary, but my wife thinks it's cool and my daughter thinks it's cool, so I feel cool  :D

Thanks a lot for the support, advice, help and assistance.

See you next year for the next project  ;)

Cheers,
Stephane