New IT forum
29 June 2022, 06:34:42 am *
Welcome, %1$s. Please login or register.

: MiraBox now in stock.
 
Pages: [1] 2 3

Author Topic: GuiPlug does not see touch screen?  (Read 29513 times)

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
GuiPlug does not see touch screen?
« 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
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuiPlug does not see touch screen?
« Reply #1 on: 11 September 2011, 06:49:33 pm »

Logged
NewITJames

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #2 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
« Last Edit: 14 September 2011, 03:16:04 am by Stephane_Varin »
Logged

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #3 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

Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuiPlug does not see touch screen?
« Reply #4 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
Logged
NewITJames

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #5 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
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuiPlug does not see touch screen?
« Reply #6 on: 18 September 2011, 08:14:56 am »

Stephane,

could you post the output from 'lsusb' please.

NewITJames
Logged
NewITJames

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #7 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
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuiPlug does not see touch screen?
« Reply #8 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
Logged
NewITJames

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #9 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
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuiPlug does not see touch screen?
« Reply #10 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

« Last Edit: 18 September 2011, 10:13:08 pm by NewIT_James »
Logged
NewITJames

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #11 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
Logged

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #12 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...
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: GuiPlug does not see touch screen?
« Reply #13 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
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Stephane_Varin

  • Newbie
  • *
  • Posts: 24
Re: GuiPlug does not see touch screen?
« Reply #14 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...
Logged
Pages: [1] 2 3
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!