| View previous topic :: View next topic |
| Author |
Message |
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
 Posted: Fri May 16, 2008 4:09 am Post subject: How do you calibrate the evtouch driver? |
 |
|
After emerging "xf86-input-evtouch" it tells me to run calibrate.sh with X stopped to calibrate the touchscreen. But when I try to run it I get some output then it dies. Here is what I get:
| Code: |
localhost ~ # calibrate.sh
/usr/bin/ev_calibrate
evalibrate located at /usr/bin/ev_calibrate
xinit located at /usr/bin/xinit
xserver located at /usr/bin/X
Creating FIFO...
Starting calibration program...
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux localhost 2.6.24-tuxonice-r3 #2 PREEMPT Sun Mar 9 04:31:47 Local time zone must be set--see z i686
Build Date: 29 February 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 15 20:45:08 2008
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "vesa" (module does not exist, 0)
(**) RADEON(0): RADEONPreInit
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(**) RADEON(0): RADEONScreenInit e0000000 0
(**) RADEON(0): Map: 0xe0000000, 0x01000000
(**) RADEON(0): RADEONSave
(**) RADEON(0): RADEONSaveMode(0x8217118)
(**) RADEON(0): Read: 0x00000006 0x00040048 0x00000000
(**) RADEON(0): Read: rd=6, fd=72, pd=4
(**) RADEON(0): Read: 0x00000000 0x00000000 0x00000000
(**) RADEON(0): Read: rd=0, fd=0, pd=0
(**) RADEON(0): RADEONSaveMode returns 0x8217118
(**) RADEON(0): DRI New memory map param
(**) RADEON(0): RADEONInitMemoryMap() :
(**) RADEON(0): mem_size : 0x04000000
(**) RADEON(0): MC_FB_LOCATION : 0xe3ffe000
(**) RADEON(0): MC_AGP_LOCATION : 0xffffffc0
(**) RADEON(0): RADEONModeInit()
800x600 443299.98 800 34208 34320 1688 600 1050 1053 1063 (24,32)
800x600 443299.98 800 34208 34320 1688 600 1050 1053 1063 (24,32)
(**) RADEON(0): Pitch = 6815848 bytes (virtualX = 800, displayWidth = 832)
(**) RADEON(0): Pitch = 6815848 bytes (virtualX = 800, displayWidth = 832)
(**) RADEON(0): dc=4000, of=16000, fd=71, pd=4
(**) RADEON(0): RADEONInit returns 0x8217ac8
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x8217ac8)
(**) RADEON(0): RADEONRestoreMemMapRegisters() :
(**) RADEON(0): MC_FB_LOCATION : 0xe3ffe000
(**) RADEON(0): MC_AGP_LOCATION : 0xffffffc0
(**) RADEON(0): Map Changed ! Applying ...
(**) RADEON(0): Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC2, offset: 0x00000000
(**) RADEON(0): Wrote: 0x0000000c 0x00020047 0x00000000 (0x0000a400)
(**) RADEON(0): Wrote: rd=12, fd=71, pd=2
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): GRPH_BUFFER_CNTL from 20155c5c to 20105c5c
(**) RADEON(0): GRPH2_BUFFER_CNTL from 20205c5c to 200d5c5c
(**) RADEON(0): RADEONSaveScreen(0)
(**) RADEON(0): Setting up initial surfaces
(**) RADEON(0): Initializing fb layer
(**) RADEON(0): Setting up accel memmap
(**) RADEON(0): Initializing backing store
(**) RADEON(0): DRI Finishing init !
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): GRPH_BUFFER_CNTL from 20155c5c to 20105c5c
(**) RADEON(0): GRPH2_BUFFER_CNTL from 20205c5c to 200d5c5c
(**) RADEON(0): Setting up final surfaces
(**) RADEON(0): Initializing Acceleration
(**) RADEON(0): EngineInit (32/32)
(**) RADEON(0): Pitch for acceleration = 104
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): Initializing Page Flipping
(**) RADEON(0): Initializing DPMS
(**) RADEON(0): Initializing Cursor
(**) RADEON(0): Initializing color map
(**) RADEON(0): Initializing DGA
(**) RADEON(0): Initializing Xv
(**) RADEON(0): RADEONScreenInit finished
Synaptics DeviceInit called
SynapticsCtrl called.
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
Synaptics DeviceOn called
(**) RADEON(0): RADEONSaveScreen(2)
XReadBitmapFile - could not open file '/empty_cursor.xbm'.
X Error of failed request: BadPixmap (invalid Pixmap parameter)
Major opcode of failed request: 93 (X_CreateCursor)
Resource id in failed request: 0xb7e5fff4
Serial number of failed request: 20
Current serial number in output stream: 22
waiting for X server to shut down Synaptics DeviceOff called
(**) RADEON(0): RADEONCloseScreen
(**) RADEON(0): RADEONDRIStop
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)
(**) RADEON(0): RADEONRestore
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x8217118)
(**) RADEON(0): RADEONRestoreMemMapRegisters() :
(**) RADEON(0): MC_FB_LOCATION : 0x1fff0000
(**) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
(**) RADEON(0): Map Changed ! Applying ...
(**) RADEON(0): Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC2, offset: 0x40000000
(**) RADEON(0): Wrote: 0x00000000 0x00000000 0x00000000 (0x0000a400)
(**) RADEON(0): Wrote: rd=0, fd=0, pd=0
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): Disposing accel...
(**) RADEON(0): Disposing cusor info
(**) RADEON(0): Disposing DGA
(**) RADEON(0): Unmapping memory
(**) RADEON(0): RADEONDRICloseScreen
FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
|
Does this thing just not work? Any ideas of how to calibrate this thing? |
|
| Back to top |
|
 |
xw_max
n00b
Joined: 25 Feb 2008
Posts: 4
|
| Posted: Fri May 16, 2008 11:59 am Post subject: Re: How do you calibrate the evtouch driver? |
|
|
| Xamindar wrote: |
| Code: |
(EE) Failed to load module "vesa" (module does not exist, 0)
|
|
Have you emerged vesa driver? |
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Sat May 17, 2008 2:38 am Post subject: Re: How do you calibrate the evtouch driver? |
|
|
| xw_max wrote: | | Xamindar wrote: |
| Code: |
(EE) Failed to load module "vesa" (module does not exist, 0)
|
|
Have you emerged vesa driver? |
yes, after I saw that I emerged vesa and got the same problem minus the vesa error. I had edited my xorg.conf to use vesa instead of radeon thinking it was the driver but forgot to emerge vesa. Even with it set to use vesa I still got all those radeon errors and it still bombed out on me. |
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Sat May 17, 2008 3:25 am Post subject: |
|
|
Here is a cleaner error report - this time using the vesa driver.
X WILL start just fine if I just run startx. But that calibrate.sh script doesn'r seem to want to run.
| Code: | localhost X11 # calibrate.sh
/usr/bin/ev_calibrate
evalibrate located at /usr/bin/ev_calibrate
xinit located at /usr/bin/xinit
xserver located at /usr/bin/X
Creating FIFO...
Starting calibration program...
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux localhost 2.6.24-tuxonice-r3 #2 PREEMPT Sun Mar 9 04:31:47 Local time zone must be set--see z i686
Build Date: 29 February 2008
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri May 16 20:03:06 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
Synaptics DeviceInit called
SynapticsCtrl called.
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
Synaptics DeviceOn called
XReadBitmapFile - could not open file '/empty_cursor.xbm'.
X Error of failed request: BadPixmap (invalid Pixmap parameter)
Major opcode of failed request: 93 (X_CreateCursor)
Resource id in failed request: 0xb7dbcff4
Serial number of failed request: 20
Current serial number in output stream: 22
waiting for X server to shut down Synaptics DeviceOff called
....FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
localhost X11 #
|
|
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Sat May 17, 2008 4:55 am Post subject: |
|
|
| GAH, this is crap. And the evtouch driver is a terrible driver anyway it seems. If the touchscreen gets turned off and back on again then X loses it completely until X is restarted. If I have the normal mouse driver run it then that doesn't happen....but it seems there is no way to define calibration with the normal mouse driver. |
|
| Back to top |
|
|
xw_max
n00b
Joined: 25 Feb 2008
Posts: 4
|
| Posted: Sun May 18, 2008 3:41 am Post subject: |
|
|
| Xamindar wrote: | | GAH, this is crap. And the evtouch driver is a terrible driver anyway it seems. If the touchscreen gets turned off and back on again then X loses it completely until X is restarted. If I have the normal mouse driver run it then that doesn't happen....but it seems there is no way to define calibration with the normal mouse driver. |
 X with touchscreen, I have never done that.
Any way, best wishes! |
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Sun May 18, 2008 3:49 am Post subject: |
|
|
Ok, I finally got it calibrated perfectly. Works.....until it is turned off and back on again. Last problem left but how to solve it? Is it really the fault of the evtouch driver?
HAH! when it loses the touchscreen...if I switch to a console and back to X again it will be back....weird.
Maybe I can make a little hack that can somehow detect when X has lost the touchscreen and then switch to the console and back again. Anyone know how to switch from the X console to another terminal and back again using only console comands? |
|
| Back to top |
|
|
thagame
Apprentice
Joined: 07 Mar 2004
Posts: 210
Location: Windsor, Ontario, Canada
|
| Posted: Mon May 19, 2008 12:40 am Post subject: |
|
|
| Xamindar wrote: | Ok, I finally got it calibrated perfectly. Works.....until it is turned off and back on again. Last problem left but how to solve it? Is it really the fault of the evtouch driver?
HAH! when it loses the touchscreen...if I switch to a console and back to X again it will be back....weird.
Maybe I can make a little hack that can somehow detect when X has lost the touchscreen and then switch to the console and back again. Anyone know how to switch from the X console to another terminal and back again using only console comands? |
What kind of touchscreen are you running? mine never uses focus and has never once stopped working. |
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Mon May 19, 2008 8:54 pm Post subject: |
|
|
| lilliput |
|
| Back to top |
|
|
Xamindar
Veteran
Joined: 03 Oct 2004
Posts: 1155
Location: California
|
| Posted: Wed May 21, 2008 8:48 am Post subject: |
|
|
tried the egalax driver from here:
http://210.64.17.162/web20/TouchKitDriver/linuxDriver.htm
and it works PERFECT! Even has a calibration tool that you can run while the driver is running (unlike the evtouch driver). Took me like 10 minutes to set up with the wonderful guide that comes with it. AMAZING!!! Touchscreen now works EVERY time and is reliable. |
|
| Back to top |
|
|
JCDenton
n00b
Joined: 25 Jan 2005
Posts: 8
|
| Posted: Sun Nov 23, 2008 11:43 am Post subject: Touchscreen does not work |
|
|
Hi,
I also tried this beta version of the eGalax driver. Most things worked out but when I start TouchKit the touchscreen does not react at all.
with:
# grep EE /var/log/Xorg.0.log
I get:
No HID Touch Controller Found!
What does this mean? Is it the usbhid?
# lsmod
usbcore usbhid, ... , usbtouchscreen
Can anybody help?
JC |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
