Find the answer to your Linux question:
Results 1 to 9 of 9
For the past few hours I have been reading forums, trying all sorts of xorg.conf settings and searching out drivers. Out of the box, Debian moves the cursor when I ...
  1. #1
    Linux Enthusiast flipjargendy's Avatar
    Join Date
    Aug 2004
    Location
    Xanadu, Titan, Saturn
    Posts
    610

    Touch Screen - Kind of Works - Any input?

    For the past few hours I have been reading forums, trying all sorts of xorg.conf settings and searching out drivers. Out of the box, Debian moves the cursor when I touch the screen and move my finger across it. The only problem is that it doesn't process it correctly. It is moving faster, so it doesn't stay under it. It also doesn't land under my finger when I touch the screen.

    I am running a Panasonic Toughbook CF-29.
    Driver I am trying: evtouch

    Has anyone had success with this laptop?

    Here is my current xorg.conf:
    Code:
    # xorg.conf (X.Org X Window System server configuration file)
    #
    # This file was generated by dexconf, the Debian X Configuration tool, using
    # values from the debconf database.
    #
    # Edit this file with caution, and see the xorg.conf manual page.
    # (Type "man xorg.conf" at the shell prompt.)
    #
    # This file is automatically updated on xserver-xorg package upgrades *only*
    # if it has not been modified since the last upgrade of the xserver-xorg
    # package.
    #
    # If you have edited this file but would like it to be automatically updated
    # again, run the following command:
    #   sudo dpkg-reconfigure -phigh xserver-xorg
    
    Section "InputDevice"
    	Identifier	"Generic Keyboard"
    	Driver		"kbd"
    	Option		"XkbRules"	"xorg"
    	Option		"XkbModel"	"pc104"
    	Option		"XkbLayout"	"us"
    EndSection
    
    Section "InputDevice"
    	Identifier	"Configured Mouse"
    	Driver		"mouse"
    EndSection
    
    Section "Device"
    	Identifier	"Configured Video Device"
    EndSection
    
    Section "Monitor"
    	Identifier	"Configured Monitor"
    EndSection
    
    Section "Screen"
    	Identifier	"Default Screen"
    	Monitor		"Configured Monitor"
    EndSection
    
    Section "InputDevice"
        Identifier "touchscreen"
        Driver "evtouch"
        Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"
        Option "DeviceName" "touchscreen"
        Option "MinX" "98"
        Option "MinY" "43"
        Option "MaxX" "940"
        Option "MaxY" "925"
        Option "ReportingMode" "Raw"
        Option "Emulate3Buttons"
        Option "Emulate3Timeout" "50"
        Option "SendCoreEvents" "On"
    EndSection
    Last edited by flipjargendy; 04-25-2010 at 03:15 AM. Reason: Xorg Drop
    Running Linux Since 2001®
    Registered Linux User #430868 - Since 9•12•06

  2. #2
    Just Joined!
    Join Date
    May 2010
    Posts
    5
    I have a CF-18 which is experiencing similar problems. This laptop's touchscreen worked with previous version of kernel/xorg. I am thinking it is my recent xorg upgrade that broke it (currently running X.Org X Server 1.7.5). This was with evtouch.

    I have never gotten evdev method to work. If your experience is like mine try evdev instead of evtouch and I think you may get same results.

    I have posted to xorg mailing list on this topic. It may help if you added your comments to the thread (assuming it is same issue).

    I am in process of trying some live CDs of various distributions to see if one of them works.

    Again, touchscreen worked great on my CF-18 at one point (with evtouch).

    John

  3. #3
    Just Joined!
    Join Date
    May 2010
    Posts
    5
    I was able to resolve this on my system. It may be same issue as original poster so I will add this here as I came across it when researching my issue.

    I made a few changes at once so am not sure what addressed it. I am running a Gentoo based CF-18. I upgraded xorg-server to version 1.8. Also, I let the X server detect my input device instead of having explicit entries in xorg.conf. I could have updated other X drivers to other more recent versions.

    After doing some/all of the above I noticed that with evdev the touchscreen was tracking differently then previous (although not accurate). I then ran x_input_calibrator and not only did the calibration values "take", they resulted in correct calibration.

    Here is snippet of what server generated on startup:

    Code:
    [  3674.040] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [  3674.040] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [  3674.040] (II) LoadModule: "evdev"
    [  3674.040] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [  3674.040] (II) Module evdev: vendor="X.Org Foundation"
    [  3674.041]    compiled for 1.8.0, module version = 2.4.0
    [  3674.041]    Module class: X.Org XInput Driver
    [  3674.041]    ABI class: X.Org XInput driver, version 9.0
    [  3674.041] (**) Power Button: always reports core events
    [  3674.041] (**) Power Button: Device: "/dev/input/event2"
    [  3674.041] (II) Power Button: Found keys
    [  3674.041] (II) Power Button: Configuring as keyboard
    [  3674.041] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [  3674.041] (**) Option "xkb_rules" "evdev"
    [  3674.041] (**) Option "xkb_model" "evdev"
    [  3674.041] (**) Option "xkb_layout" "us"
    [  3674.274] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
    [  3674.274] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [  3674.274] (**) Video Bus: always reports core events
    [  3674.274] (**) Video Bus: Device: "/dev/input/event3"
    [  3674.274] (II) Video Bus: Found keys
    [  3674.274] (II) Video Bus: Configuring as keyboard
    [  3674.274] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    [  3674.274] (**) Option "xkb_rules" "evdev"
    [  3674.274] (**) Option "xkb_model" "evdev"
    [  3674.274] (**) Option "xkb_layout" "us"
    [  3674.289] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [  3674.289] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [  3674.289] (**) Power Button: always reports core events
    [  3674.289] (**) Power Button: Device: "/dev/input/event1"
    [  3674.289] (II) Power Button: Found keys
    [  3674.289] (II) Power Button: Configuring as keyboard
    [  3674.289] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [  3674.289] (**) Option "xkb_rules" "evdev"
    [  3674.289] (**) Option "xkb_model" "evdev"
    [  3674.289] (**) Option "xkb_layout" "us"
    [  3674.290] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
    [  3674.290] (EE) No input driver/identifier specified (ignoring)
    [  3674.297] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
    [  3674.297] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [  3674.297] (**) AT Translated Set 2 keyboard: always reports core events
    [  3674.297] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
    [  3674.297] (II) AT Translated Set 2 keyboard: Found keys
    [  3674.297] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [  3674.297] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    [  3674.297] (**) Option "xkb_rules" "evdev"
    [  3674.297] (**) Option "xkb_model" "evdev"
    [  3674.297] (**) Option "xkb_layout" "us"
    [  3674.298] (II) config/udev: Adding input device LBPS/2 Fujitsu Lifebook TouchScreen (/dev/input/event6)
    [  3674.298] (**) LBPS/2 Fujitsu Lifebook TouchScreen: Applying InputClass "evdev touchscreen catchall"
    [  3674.298] (**) LBPS/2 Fujitsu Lifebook TouchScreen: always reports core events
    [  3674.298] (**) LBPS/2 Fujitsu Lifebook TouchScreen: Device: "/dev/input/event6"
    [  3674.298] (II) LBPS/2 Fujitsu Lifebook TouchScreen: Found absolute axes
    [  3674.298] (II) LBPS/2 Fujitsu Lifebook TouchScreen: Found x and y absolute axes
    [  3674.298] (II) LBPS/2 Fujitsu Lifebook TouchScreen: Found absolute touchscreen
    [  3674.298] (II) LBPS/2 Fujitsu Lifebook TouchScreen: Configuring as touchscreen
    [  3674.298] (**) LBPS/2 Fujitsu Lifebook TouchScreen: YAxisMapping: buttons 4 and 5
    [  3674.298] (**) LBPS/2 Fujitsu Lifebook TouchScreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  3674.298] (II) XINPUT: Adding extended input device "LBPS/2 Fujitsu Lifebook TouchScreen" (type: TOUCHSCREEN)
    [  3674.298] (II) LBPS/2 Fujitsu Lifebook TouchScreen: initialized for absolute axes.
    [  3674.299] (II) config/udev: Adding input device LBPS/2 Fujitsu Lifebook TouchScreen (/dev/input/mouse0)
    [  3674.299] (EE) No input driver/identifier specified (ignoring)
    [  3674.299] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event7)
    [  3674.299] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
    [  3674.299] (**) PS/2 Generic Mouse: always reports core events
    [  3674.299] (**) PS/2 Generic Mouse: Device: "/dev/input/event7"
    [  3674.299] (II) PS/2 Generic Mouse: Found 3 mouse buttons
    [  3674.299] (II) PS/2 Generic Mouse: Found relative axes
    [  3674.299] (II) PS/2 Generic Mouse: Found x and y relative axes
    [  3674.299] (II) PS/2 Generic Mouse: Configuring as mouse
    [  3674.299] (**) PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
    [  3674.299] (**) PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [  3674.300] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE)
    [  3674.300] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
    [  3674.300] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
    [  3674.300] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
    [  3674.300] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
    [  3674.300] (II) PS/2 Generic Mouse: initialized for relative axes.
    [  3674.300] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse1)
    [  3674.300] (EE) No input driver/identifier specified (ignoring)
    [  3674.302] (II) config/udev: Adding input device Panasonic Laptop Support (/dev/input/event5)
    [  3674.302] (**) Panasonic Laptop Support: Applying InputClass "evdev keyboard catchall"
    [  3674.302] (**) Panasonic Laptop Support: always reports core events
    [  3674.302] (**) Panasonic Laptop Support: Device: "/dev/input/event5"
    [  3674.302] (II) Panasonic Laptop Support: Found keys
    [  3674.302] (II) Panasonic Laptop Support: Configuring as keyboard
    [  3674.302] (II) XINPUT: Adding extended input device "Panasonic Laptop Support" (type: KEYBOARD)
    [  3674.302] (**) Option "xkb_rules" "evdev"
    [  3674.302] (**) Option "xkb_model" "evdev"
    [  3674.302] (**) Option "xkb_layout" "us"
    To be clear: I am not using evtouch.

    John

  4. #4
    Linux Enthusiast flipjargendy's Avatar
    Join Date
    Aug 2004
    Location
    Xanadu, Titan, Saturn
    Posts
    610
    An update... and response...

    UPDATE
    Touchscreen works and is pretty much calibrated due to the help of someone else on other forums providing an xorg.conf for their Toughbook.

    Everything works properly now except the touch pad. The buttons for the touchpad work. I can also tap the touchpad, for use as a button. There is definitely input from the touchpad when I scroll it but the mouse cursor does not move. Instead it switches mouse cursor images (ex. text cursor to arrow).

    I have commented certain things out of the xorg.conf and set some from true to false and what not. Nothing has effected the way the touchpad works. yet.

    RESPONSE
    Is x_input_calibrator something that comes with Gentoo? Thanks for the info!
    Running Linux Since 2001®
    Registered Linux User #430868 - Since 9•12•06

  5. #5
    Linux Enthusiast flipjargendy's Avatar
    Join Date
    Aug 2004
    Location
    Xanadu, Titan, Saturn
    Posts
    610
    I have narrowed it down to the "Server Layout" section.

    This probably seems obvious. After "touchscreen" or "Synaptics Touchpad" if you put "CorePointer" that will the device that will work. I have tried a few other configurations with no success in making them both work at the same time.
    Running Linux Since 2001®
    Registered Linux User #430868 - Since 9•12•06

  6. #6
    Just Joined!
    Join Date
    May 2010
    Posts
    5
    Quote Originally Posted by flipjargendy View Post
    An update... and response...


    RESPONSE
    Is x_input_calibrator something that comes with Gentoo? Thanks for the info!
    It is not Gentoo specific. I downloaded and compiled it. The forum won't let me include a url. Do a search for xinput calibrator.

  7. #7
    Just Joined!
    Join Date
    May 2010
    Posts
    5
    Quote Originally Posted by flipjargendy View Post
    I have narrowed it down to the "Server Layout" section.

    This probably seems obvious. After "touchscreen" or "Synaptics Touchpad" if you put "CorePointer" that will the device that will work. I have tried a few other configurations with no success in making them both work at the same time.
    Code:
    Section "ServerLayout"
            Identifier     "X.org Configured"
            Screen      0  "Screen0" 0 0
    EndSection
    In my case udev is finding all the input devices (X.Org X Server 1.8.0)

  8. #8
    Linux Enthusiast flipjargendy's Avatar
    Join Date
    Aug 2004
    Location
    Xanadu, Titan, Saturn
    Posts
    610
    I am tempted to try udev but have read that it doesn't work with Debian... or am I thinking of evdev?
    Last edited by flipjargendy; 06-06-2010 at 03:16 PM.
    Running Linux Since 2001®
    Registered Linux User #430868 - Since 9•12•06

  9. #9
    Just Joined!
    Join Date
    May 2010
    Posts
    5
    Quote Originally Posted by flipjargendy View Post
    I am tempted to try udev but have read that it doesn't work with Debian... or am I thinking of evdev?
    I am not familiar with Debian but I expect both should work. You may want to research both udev (part of kernel) and evdev (part of xserver). In order for me to get he touchscreen on my CF-18 to work with recent xserver I needed to use both together.

    Previously I used evtouch but that is not part of xserver and was problematic for me to get working with recent xserver.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •