LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-14-2009, 10:13 AM   #1
Ravendark
Member
 
Registered: Feb 2003
Distribution: Slackware 10.2
Posts: 61

Rep: Reputation: 15
Slackware -current Synaptics touchpad problem


Hi,

After upgrading to slackware -current (06/13/2009) the touchpad is not working (X v1.6.1).

Below I have my xorg.conf:

Code:
# File generated by xorgconfig

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

#    RgbPath	"/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/OTF"
    FontPath   "/usr/share/fonts/Type1"
    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/local/"
    FontPath   "/usr/lib/X11/fonts/misc/"
    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
    FontPath   "/usr/lib/X11/fonts/Speedo/"
    FontPath   "/usr/lib/X11/fonts/Type1/"
    FontPath   "/usr/lib/X11/fonts/TTF/"
    FontPath   "/usr/lib/X11/fonts/OTF/"
    FontPath   "/usr/lib/X11/fonts/cyrillic/"
    FontPath   "/usr/lib/X11/fonts/75dpi/"
    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/lib/xorg/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option	"Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"	"xorg"
    Option "XkbModel"	"pc105"
    Option "XkbLayout"	"gb"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"

# Identifier and driver

#    Identifier  "Touchpad"
#    Driver      "synaptics"
#    Option "SendCoreEvents"  "true"
#    Option "Protocol"    "auto-dev"       # IntelliMouse PS/2
#    Option "Device"      "/dev/psaux"
#    Option "HorizScrollDelta" "0"
#    Option "SHMConfig" "true"

Driver       "synaptics"
  Identifier   "Mouse1"
  Option       "Device"        "/dev/mouse"
  Option       "Protocol"      "auto-dev"
#  Option      "LeftEdge"      "1700"
#  Option      "RightEdge"     "5300"
#  Option      "TopEdge"       "1700"
#  Option      "BottomEdge"    "4200"
  Option       "FingerLow"     "25"
  Option       "FingerHigh"    "30"
  Option       "MaxTapTime"    "180"
  Option       "MaxTapMove"    "220"
  Option       "VertScrollDelta" "100"
  Option       "MinSpeed"      "0.09"
  Option       "MaxSpeed"      "0.18"
  Option       "AccelFactor"   "0.0015"
  Option       "SHMConfig"     "true"
  Option       "TapButton1"    "1"



EndSection

#Section "InputDevice"

# Identifier and driver

#    Identifier	"Mouse1"
#    Driver	"mouse"
#    Option "Protocol"    "IMPS/2"	# IntelliMouse PS/2
#    Option "Device"      "/dev/input/mice"
#    #Option "Device"      "/dev/input/mouse0"
#    Option "ZAxisMapping" "4 5"
#EndSection

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"	"9600"
#    Option "SampleRate"	"150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

 #   Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

#EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 48.5

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-70

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"Standard VGA"
    VendorName	"Unknown"
    BoardName	"Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset	"generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "** ATI (generic)                      [ati]"
    Driver      "radeon"
    #VideoRam    131072
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "** ATI (generic)                      [ati]"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x800" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

Code:
~$ synclient -l
Couldn't find synaptics properties. No synaptics driver loaded?
I have tried many different xorg.confs with no luck.
The thing is that the touchpad is working in terminal but not in X.

Thanks!
 
Old 06-14-2009, 10:50 AM   #2
jmacloue
LQ Newbie
 
Registered: Apr 2009
Posts: 12

Rep: Reputation: 1
Check /etc/modprobe.d/psmouse - it is as follows by default:

Code:
options psmouse proto=imps
This prevents synaptics driver to recognize the touchpad properly so you should comment this line out.
 
Old 06-14-2009, 11:18 AM   #3
Ravendark
Member
 
Registered: Feb 2003
Distribution: Slackware 10.2
Posts: 61

Original Poster
Rep: Reputation: 15
Did it, nothing happened.

It works with the default (huge) kernel but not with the recompiled 2.6.30 kernel. That where the problem lies...
But I haven't spotted the problem yet.
 
Old 06-14-2009, 02:21 PM   #4
Ravendark
Member
 
Registered: Feb 2003
Distribution: Slackware 10.2
Posts: 61

Original Poster
Rep: Reputation: 15
thanks for relies, problem fixed.
 
Old 06-15-2009, 07:20 AM   #5
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,778
Blog Entries: 1

Rep: Reputation: 412Reputation: 412Reputation: 412Reputation: 412Reputation: 412
Quote:
Originally Posted by Ravendark View Post
thanks for relies, problem fixed.

Care to enlighten us as to the fix?
 
Old 06-15-2009, 10:54 AM   #6
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,906

Rep: Reputation: Disabled
I'd bet it was the psmouse issue - after rebooting (regardless of which kernel he booted), the module was loaded with the correct options. Unfortunately, he credited the different kernel for the fix instead of what actually fixed it.
 
Old 06-15-2009, 06:38 PM   #7
Daehtop
LQ Newbie
 
Registered: Jun 2009
Location: southeast Missouri
Distribution: Slackware 12.2
Posts: 4

Rep: Reputation: 1
For the curious

I had the same problem with both -12.2 and -current but if I remember correctly the solution was the same.

changed "imps" to "any"
psmouse
Code:
options psmouse proto=any
added this section under "mouse0"
left mouse0 section alone (so a usb mouse will still work)
xorg.conf
Code:
Section "InputDevice"
    Identifier     "Mouse1"
    Driver         "synaptics"
    Option         "SendCoreEvents" "true"
    Option         "Device" "/dev/psaux"
    Option         "Protocal" "auto-dev"
    Option         "Sensitivity" "0.8"
    Option         "HorizScrollDelta" "0"
    Option         "LeftEdge" "1700"
    Option         "RightEdge" "5300"
    Option         "TopEdge" "1700"
    Option         "BottomEdge" "4200"
    Option         "FingerLow" "25"
    Option         "FingerHigh" "30"
    Option         "MaxTapTime" "180"
    Option         "MaxTapMove" "220"
    Option         "VertScrollDelta" "100"
    Option         "MinSpeed" "0.09"
    Option         "MaxSpeed" "0.18"
    Option         "AccelFactor" "0.0015"
    Option         "SHMConfig" "on"
EndSection
This information was rather difficult to find, I saw this post and thought I would save some others some searching.
 
Old 06-15-2009, 10:59 PM   #8
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 793

Rep: Reputation: 245Reputation: 245Reputation: 245
I had problems with the Synaptics Touchpad as well. It had to do with the order that modules are loaded and which drivers are built into the kernel. I added this to my "rc.local" script.

Code:
if [[ -n "$(lsmod | cut -f 1 -d " " | grep psmouse)" ]] ; then
        echo "Found psmouse module"
        echo "Reloading psmouse module so that Synaptics Tourchpad will work"
        /sbin/rmmod psmouse
        /sbin/insmod /lib/modules/`uname -r`/kernel/drivers/input/mouse/psmouse.ko
fi
 
Old 06-15-2009, 11:19 PM   #9
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,906

Rep: Reputation: Disabled
From CHANGES_AND_HINTS.TXT in 12.2
(I'm actually pasting from my working copy for -current, so the wording might be a bit different, but the concept is the same):

Code:
On many systems, the xf86-input-synaptics driver requires the psmouse kernel
kernel module be loaded without any special options.  This poses a problem on a
default Slackware installation, as /etc/modprobe.d/psmouse causes the psmouse
module to load with the imps protocol.  This is easily fixed though :-)
  First, edit /etc/modprobe.d/psmouse so that it looks like this (note
  that we're simply commenting out the last line):
    # PS/2 mouse support:
    # The default options when the psmouse module is loaded will completely
    # break the mouse if you change consoles with several models of KVM
    # switches.  Therefore, we'll have it use the imps protocol here, which
    # is a more basic protocol that is less likely to cause problems with
    # the mouse.  If you'd rather use the kernel default options, just
    # comment out the line below.  If you'd rather choose your own options,
    # then edit the line below as desired.
    #options psmouse proto=imps
  Next, unload and reload the psmouse module (do this as root):
    modprobe -r psmouse
    modprobe psmouse
 
Old 06-24-2009, 09:10 AM   #10
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,377

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
I have just completed the latest updates to -current (2.6.29.4 to 2.6.29.5) on my laptop with an older ALPS Glidepoint touchpad and had a problem. The symptoms were that I could boot to run level 3 and startx, but the touchpad did not work. If I booted directly to run level 4, the nVidia graphics startup screen would appear then the screen went black and the system would hang.
I traced the problem to /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi, which has entries to enable features (circular scrolling and two finger scrolling) that are not available with the ALPS Glidepoint. At the moment I have simply deleted these entries and continue to use the entries in my xorg.conf file to set up the touchpad.
All is now working, but I am wondering whether I should create a custom 11-x11-synaptics.fdi as a better option than using xorg.conf. Would such a file be liable to be overwritten in any future upgrades?
 
Old 06-24-2009, 02:58 PM   #11
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,906

Rep: Reputation: Disabled
Quote:
Originally Posted by allend View Post
I have just completed the latest updates to -current (2.6.29.4 to 2.6.29.5) on my laptop with an older ALPS Glidepoint touchpad and had a problem. The symptoms were that I could boot to run level 3 and startx, but the touchpad did not work. If I booted directly to run level 4, the nVidia graphics startup screen would appear then the screen went black and the system would hang.
I traced the problem to /usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi, which has entries to enable features (circular scrolling and two finger scrolling) that are not available with the ALPS Glidepoint. At the moment I have simply deleted these entries and continue to use the entries in my xorg.conf file to set up the touchpad.
All is now working, but I am wondering whether I should create a custom 11-x11-synaptics.fdi as a better option than using xorg.conf. Would such a file be liable to be overwritten in any future upgrades?
Those entries in the fdi file are commented out (or they *should* be), so they shouldn't make a difference...

Code:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input.touchpad">
        <merge key="input.x11_driver" type="string">synaptics</merge>
        <!-- Arbitrary options can be passed to the driver using
             the input.x11_options property since xorg-server-1.5. -->
        <!-- EXAMPLES:
        Switch on shared memory, enables the driver to be configured at runtime
	<merge key="input.x11_options.SHMConfig" type="string">true</merge>

	Maximum movement of the finger for detecting a tap
	<merge key="input.x11_options.MaxTapMove" type="string">2000</merge>

	Enable vertical scrolling when dragging along the right edge
	<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>

	Enable vertical scrolling when dragging with two fingers anywhere on the touchpad
	<merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>

	Enable horizontal scrolling when dragging with two fingers anywhere on the touchpad
	<merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>

	If on, circular scrolling is used
	<merge key="input.x11_options.CircularScrolling" type="string">true</merge>

	For other possible options, check CONFIGURATION DETAILS in synaptics man page
        -->
    </match>
  </device>
</deviceinfo>
 
Old 06-25-2009, 08:34 AM   #12
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,377

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
Quote:
Those entries in the fdi file are commented out (or they *should* be), so they shouldn't make a difference...
I thought that they were just comments, yet removing them did fix my problem! I have copied back the original file and now all is OK. I have no explanation for the original glitch, apart from some transient disk error.

Update in case any body looks at this.
It turns out that my problem was due to the ServerTimeout time in the [X-:*-Core] section of my /etc/kde/kdm/kdmrc being too short for my aged hardware to complete initialising the Xserver. A very easy fix, but difficult to find when sometimes it worked and sometimes it didn't. Finally got on the right track when I found Xerver timeout errors recorded in /var/log/syslog.

Last edited by allend; 07-07-2009 at 09:13 PM. Reason: Update in case any body looks at this
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Synaptics touchpad in Slackware 12.2 on HP G60 Mig21 Slackware 9 06-13-2009 11:08 PM
Again with Synaptics Touchpad problem. brokencog Linux - Hardware 8 09-04-2008 09:02 PM
Synaptics Touchpad on Acer Aspire 5050 - Slackware Erik_FL Linux - Hardware 3 12-03-2007 07:19 AM
Synaptics TouchPad Problem Toniee Linux - Laptop and Netbook 6 07-02-2005 12:14 PM
[MOUSE] Synaptics touchpad problem Ferllings Linux - Hardware 0 06-06-2004 11:57 AM


All times are GMT -5. The time now is 07:17 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration