Gt80 touchpad problem

I just bought a gt80 and finished all driver setup with the attached CD, and now my computer doesn't function well. I'd really appreciate it if anyone could help me solve them.
The 1st one is about the touchpad. When it's activated, cursor on the screen starts to keep pressed for several seconds and then release, and just keeps doing that until I deactivate the touchpad. I unistalled Synaptics Pointer driver and reinstalled it but still the same.
The 2nd problem is about battery plan. I was so excited that I can play most games with highest graphics setting and clicked all the "download" I could find in Steam before I went to bed. About 2 a.m., I woke up and went to check how everything goes, and to my surprise I find my GT80 automatically slept somehow. I started it up and double checked the battery plan, it was set to highest performence with "don't do anything when close screen". Then I closed my screen and waited for about 10 min, and it still went to sleep. It was too late so I had to give up. Why the battery plan doesn't work? And most surprisingly, I can't find a way to turn off the screen. I can't find fn buttons to do that, could anybody help?  Thank you very much in advance!

Hi paintothemax,
These MSI forums are organized a bit strange and you've posted your message in the wrong place. The GT80 Titan is a gaming notebook so you're in the right general area but you should have posted the questions in the "GAMING Notebooks" forum. It is accessed by clicking on the red "GAMING Notebooks" title at the top of the section.
The "GAMING Notebooks" forum also has some subforums under it such as the "Steelseries Engine" forum where you posted your message. Don't use these subforums unless your post relates directly to them. Your post is not a "Steelseries Engine" post.
When you enter the main "GAMING Notebooks" forum, you'll see its five subforums listed first. Scroll down the page below them and you'll see a large red section. These are the "Sticky Topics" for the "GAMING Notebooks" forum. Keep scrolling down and you'll finally see the "Normal Topics" section with the most recent posts. Hopefully one of the moderators will move your post there so it will have a better chance of receiving replies.
Personally, I think the forum organization is kinda screwball here. I had some trouble with it at first, too. So don't feel bad.
My company recently purchased a GT80 Titan-001 so I may be able to offer some help. But we downgraded ours to Windows 7 Ultimate so the details will vary somewhat.
Quote from: paintothemax on 29-May-15, 15:44:56
I just bought a gt80 and finished all driver setup with the attached CD, and now my computer doesn't function well. I'd really appreciate it if anyone could help me solve them.
This doesn't make sense. Why did you have to "finish all driver setup with the attached CD"? I would have expected your Titan to arrive with all factory-provided drivers pre-installed. It would be helpful if you list the individual steps that you took.
One possible concern is if you or your computer vendor updated the system BIOS. MSI recommends that users never do this unless instructed to by MSI or your computer's vendor. If you, personally, updated the system BIOS, it is probably out of sync with the EC (embedded controller) and this can create all kinds of weird behavior. If your vendor updated the BIOS and they are not expert with MSI gaming notebooks, they may not have known about the EC quirks, either.
MSI says the EC must be reset every time that the BIOS is changed. The procedure varies, depending on the notebook model. To reset the EC of your Titan, begin by turning your Titan off. Then, while it is off, press and hold the power button for 12 seconds.
Another way to reset the EC is to disconnect the battery---but this is a very advanced procedure that is not intended for users because the Titan has a non-removable Li-ion battery.
Once the EC is reset, it will resync with the BIOS and many problems should simply "go away".
Quote
The 1st one is about the touchpad. When it's activated, cursor on the screen starts to keep pressed for several seconds and then release, and just keeps doing that until I deactivate the touchpad. I unistalled Synaptics Pointer driver and reinstalled it but still the same.
It sounds like the Tap settings are not configured the way you want. They are controlled from the Synaptics Device Settings which is nested under the Windows Mouse Properties. In Windows 7 you'd open the Windows Control Panel and go to Hardware and Sound > Devices and Printers > Mouse. The last tab labelled "Device Settings" should be the Synaptics settings. Select "Synaptics TouchPad ..." in the list of devices and click on the "Settings" button.
You should see a tree list on the left. Expand the "Tapping" section. There are three main sections: (1) the "Tapping" section, itself, (2) the "Tap and Drag" section, and (3) the "Tap Zones" section.
"Enable Tapping" must be on or you won't be able to invoke or use the numeric touchpad. Some new Titan owners have turned this off and then wondered why the numeric touchpad won't appear any more. But most of the other Tapping settings (in the "Tap and Drag" and "Tap Zones" sections) can be turned off. You may be able to get the touchpad working the way you want with these settings.
Quote
The 2nd problem is about battery plan. I was so excited that I can play most games with highest graphics setting and clicked all the "download" I could find in Steam before I went to bed. About 2 a.m., I woke up and went to check how everything goes, and to my surprise I find my GT80 automatically slept somehow. I started it up and double checked the battery plan, it was set to highest performence with "don't do anything when close screen". Then I closed my screen and waited for about 10 min, and it still went to sleep. It was too late so I had to give up. Why the battery plan doesn't work? And most surprisingly, I can't find a way to turn off the screen. I can't find fn buttons to do that, could anybody help?  Thank you very much in advance!
We had a similar problem and we tracked it down to MSI's SCM (System Control Manager) software. It can undo your custom power plan. We didn't want to uninstall the SCM because we rely on it to quickly turn the WiFi and bluetooth radios on and off as needed. Fortunately we found a workaround.
Our solution was to manually configure every one of the default Windows power plans (in Windows 7 they are: Balanced, High performance, and Power saver) so they do what we want. That way, regardless which power plan the SCM chooses, it will do what we want.
You will need to drill down into the details of each power plan in order to configure it fully---most of the settings are only available when you click the "Change advanced power settings" link. When you do, you should see something like this:
Hard disk
---Turn off hard disk after
------On battery: ______
------Plugged in: ______
Internet Explorer
---JavaScript Timer frequency
------On battery: ______
------Plugged in: ______
Desktop background settings
---Slide show
------On battery: ______
------Plugged in: ______
Wireless Adapter Settings
---Power Saving Mode
------On battery: ______
------Plugged in: ______
Sleep
---Sleep after
------On battery: ______
------Plugged in: ______
---Allow wake timers
------On battery: ______
------Plugged in: ______
USB settings
---USB selective suspend settings
------On battery: ______
------Plugged in: ______
Intel(R) Graphics Settings
---Intel(R) Graphics Power Plan
------On battery: ______
------Plugged in: ______
Power buttons and lid
---Lid close action
------On battery: ______
------Plugged in: ______
---Power button action
------On battery: ______
------Plugged in: ______
---Sleep button action
------On battery: ______
------Plugged in: ______
PCI Express
---Link State Power Management
------On battery: ______
------Plugged in: ______
Processor power management
---Minimum processor state
------On battery: ______
------Plugged in: ______
---System cooling policy
------On battery: ______
------Plugged in: ______
---Maximum processor state
------On battery: ______
------Plugged in: ______
Display
---Dim display after
------On battery: ______
------Plugged in: ______
---Turn off display after
------On battery: ______
------Plugged in: ______
---Display brightness
------On battery: ______
------Plugged in: ______
---Adaptive backlight
------On battery: ______
------Plugged in: ______
---Dimmed display brightness
------On battery: ______
------Plugged in: ______
Multimedia settings
---When sharing media
------On battery: ______
------Plugged in: ______
---When playing video
------On battery: ______
------Plugged in: ______
Battery
---Critical battery action
------On battery: ______
------Plugged in: ______
---Low battery level
------On battery: ______
------Plugged in: ______
---Critical battery level
------On battery: ______
------Plugged in: ______
---Low battery notification
------On battery: ______
------Plugged in: ______
---Low battery action
------On battery: ______
------Plugged in: ______
---Reserve battery level
------On battery: ______
------Plugged in: ______
The above settings should enable you to achieve what you want. But we found that a "custom" power plan was useless because the SCM overrides it. The trick here is that the SCM always chooses from one of the built-in plans that come with Windows. And, since Windows allows the user to edit each of the built-in plans, you can achieve what you want by changing them.
Kind regards, David

Similar Messages

  • [SOLVED] Synaptics touchpad problem eeepc 1000HE

    I installed Arch on my eeepc 1000HE yesterday and configured / used it happily for most of the day - but then it developed a touchpad problem which I'm struggling to fix.
    If you lift your finger from the touchpad the mouse cursors 'forgets' / 'resets' its position.
    eg When you put your finger back on the touchpad the cursor jumps to a different position. For one thing, this means you can't tap to click, because when you lift your finger to tap, the cursor jumps somewhere else (usually a slight move, but usually away from the item one wants to click).
    Also, when needing a few swipes (eg to move the cursor left to right across the screen), the cursor jumps away from its current position (to the left - sort of back to its original starting position) each time I lift my finger to make the extra swipe.
    The problem seems to have started when I had a tv plugged in via the vga and was managing screen switching with xrandr and the screen-switch function key (I'm trying to set up the eeepc as a mythtv frontend) but this could be coincidence.
    Some settings etc -
    Relevant parts of /var/log/Xorg.0.log seem to be -
    [    19.547] (**) Asus EeePC extra buttons: Applying InputClass "touchpad"
    [    19.547] (II) LoadModule: "synaptics"
    [    19.548] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [    19.561] (II) Module synaptics: vendor="X.Org Foundation"
    [    19.561]     compiled for 1.10.0, module version = 1.4.0
    [    19.561]     Module class: X.Org XInput Driver
    [    19.561]     ABI class: X.Org XInput driver, version 12.2
    [    19.561] (II) Using input driver 'synaptics' for 'Asus EeePC extra buttons'
    [    19.561] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [    19.561] (**) Asus EeePC extra buttons: always reports core events
    [    19.561] (**) Option "Device" "/dev/input/event8"
    [    19.713] (--) Asus EeePC extra buttons: invalid x-axis range.  defaulting to 1615 - 5685
    [    19.713] (--) Asus EeePC extra buttons: invalid y-axis range.  defaulting to 1729 - 4171
    [    19.713] (--) Asus EeePC extra buttons: invalid pressure range.  defaulting to 0 - 256
    [    19.713] (--) Asus EeePC extra buttons: invalid finger width range.  defaulting to 0 - 16
    [    19.714] (**) Option "EmulateTwoFingerMinZ" "0"
    [    19.714] (**) Option "VertEdgeScroll" "on"
    [    19.714] (**) Option "HorizEdgeScroll" "on"
    [    19.714] (**) Option "VertTwoFingerScroll" "on"
    [    19.714] (**) Option "HorizTwoFingerScroll" "on"
    [    19.714] (**) Option "TapButton1" "1"
    [    19.714] (**) Option "TapButton2" "2"
    [    19.714] (**) Option "TapButton3" "3"
    [    19.714] (**) Option "CircularScrolling" "on"
    [    19.714] (**) Option "CircScrollTrigger" "2"
    [    19.820] (--) Asus EeePC extra buttons: no supported touchpad found
    [    19.820] (EE) Asus EeePC extra buttons Unable to query/initialize Synaptics hardware.
    [    19.886] (EE) PreInit returned 11 for "Asus EeePC extra buttons"
    [    19.887] (II) UnloadModule: "synaptics"
    [    19.887] (II) Unloading synaptics
    and
    [    19.964] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event7)
    [    19.964] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev keyboard catchall"
    [    19.964] (II) Using input driver 'evdev' for 'ETPS/2 Elantech Touchpad'
    [    19.964] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [    19.965] (**) ETPS/2 Elantech Touchpad: always reports core events
    [    19.965] (**) ETPS/2 Elantech Touchpad: Device: "/dev/input/event7"
    [    19.980] (--) ETPS/2 Elantech Touchpad: Found 3 mouse buttons
    [    19.980] (--) ETPS/2 Elantech Touchpad: Found absolute axes
    [    19.980] (--) ETPS/2 Elantech Touchpad: Found x and y absolute axes
    [    19.980] (--) ETPS/2 Elantech Touchpad: Found absolute touchpad.
    [    19.980] (II) ETPS/2 Elantech Touchpad: Configuring as touchpad
    [    19.980] (**) ETPS/2 Elantech Touchpad: YAxisMapping: buttons 4 and 5
    [    19.980] (**) ETPS/2 Elantech Touchpad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [    19.980] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event7"
    [    19.980] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD)
    [    19.981] (II) ETPS/2 Elantech Touchpad: initialized for absolute axes.
    [    19.981] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
    [    19.981] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 0
    [    19.981] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
    [    19.981] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
    [    19.992] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse0)
    [    19.992] (II) No input driver/identifier specified (ignoring)
    I have commented out the touchpad section in /etc/X11/xorg.conf.d/10-evdev.conf  (un-commenting made no difference) -
    #Section "InputClass"
    #        Identifier "evdev touchpad catchall"
    #        MatchIsTouchpad "on"
    #        MatchDevicePath "/dev/input/event*"
    #        Driver "evdev"
    #EndSection
    /etc/X11/xorg.conf.d/10-synaptics.conf looks like this -
    Section "InputClass"
          Identifier "touchpad"
          Driver "synaptics"
          MatchIsTouchpad "on"
                 Option "TapButton1" "1"
                 Option "TapButton2" "2"
                 Option "TapButton3" "3"
                 Option "VertEdgeScroll" "on"
                 Option "VertTwoFingerScroll" "on"
                 Option "HorizEdgeScroll" "on"
                 Option "HorizTwoFingerScroll" "on"
                 Option "CircularScrolling" "on"
                 Option "CircScrollTrigger" "2"
                 Option "EmulateTwoFingerMinZ" "0"
    EndSection
    I thought the issue might be related to this https://bugs.archlinux.org/task/20830 , but adding MatchDevicePath "/dev/input/event*" to /etc/X11/xorg.conf.d/10-synaptics.conf didn't make a difference.
    My Daemons array looks like this -
    DAEMONS=(syslog-ng dbus !network wicd netfs crond lircd samba alsa !hal sshd gdm)
    Removing the ! before hal made no difference.
    I am using gnome. Changing the settings in  the /desktop/gnome/peripherals/touchpad/ folder with gconf-editor makes no difference to the problem.
    I am using kernel 2.6.38-ARCH. Using the fallback kernel didn't help.
    Any help would be much appreciated.
    Thanks
    Last edited by belbo (2011-04-26 12:58:17)

    Update. After some more searching the forum I thought downgrading udev may help. Since I had a fresh install I needed to install the AUR downgrade package. I did a yaourt -Suy before doing so which, amongst other things, installed a new kernel (4-1) and upgraded yajl. When I tried yaourt -S downgrade I got an error re yajl - error while loading shared libraries libyajl.so.1, canot open shared object file, no such file or directory, and then "error: target not found: dowgrade".
    Any help really appreciated.

  • B5400 Synaptics Touchpad Problem

    Leider musste ich jetzt nach ein paar Tagen bereits feststellen, dass das Touchpad sehr oft zicken macht. Das Problem ist, dass es in diesen Momenten irgendwelche Multitouchgesten erkennt, die aber nicht ausgeführt worden sind, so zB: - Plötzliches zoomen in Dokumente, Browser (musste ich jetzt ausstellen, sonst wärs unmöglich..)- Keine Reaktion, meist mittig des Touchpads. Am Rand ging es dann manchmal. Praktisch Arbeitsverweigerung.- Wenn keine Reaktion kommt, aber man trotzdem auf dem Touchpad rumwischt, dann fängt es oft an zu scrollen. Ebenfalls nicht tragbar beim Arbeiten. Die Treiber habe ich jetzt wie oft runter- und wieder neuinstalliert.. Dabei habe ich sowohl die Synaptics Treiber der Synaptic Homepage probiert (lässt sich nicht installieren, da Fehlermeldung) als auch die Lenovo Treiber, die angeblich zum B5400 passen. Mit sauberem Hoch und Runterfahren nach jeder Installationsaktion. Keine Besserung. Das komische ist, dass es eine Zeit lang mal sehr ordentlich funktioniert und plötzlich anfängt sich zu verweigern, weshalb ich glaube, dass die Hardware soweit funktioniert. Konkret habe ich das B5400 MB82AGE.//e: Mit Windows 8.1

    Nachtrag.... Nachtem ich mit dem Lenovo Support geredet habe ist denen das Problem nicht bekannt. Steh ich nun im Wald ??? Ich soll mein Lappi einschicken und es wird getestet. Wenn nichts gefunden wurde liegt es nicht am Laptop . Wenn ich danach weiterhin das Problem habe  ist dies dann kein Lenovo Problem und soll mich an den Händler wenden. Der Händler verweist auf Lenovo. Das ist doch ein Katz und Maus spiel. In diesem Forum wird genauso diskutiert da es probleme mit der M Serie und B serie gibt unter win7 und win8.1 http://forums.lenovo.com/t5/Lenovo-3000-and-Essential/B5400-Touchpad-problems-win8-1/m-p/1471722#M53914  Herr Marcel_Lenovo Spezialist wie kommt dies zu stande das diese Problem nicht im technical Support NICHT bekannt ist????  

  • HP Pavilion dv3500t Touchpad Problem - Need Help

    I'm running into touchpad problems with my HP Pavilion dv3500t whenever I have the battery charger plugged into the laptop.  When plugged in, the cursor starts drifting uncontrollably and automatically clicks the screen without me lifting my finger from the touchpad.  If I unplug the power plug and run on battery, the touchpad works perfectly.  Is anyone else experiencing this same issue?  Anyone know how I can solve this annoying issue with the touchpad? Basically the touchpad is useless when power is plugged in. I'm running Vista 64-bit with all the latest touchpad drivers and firmware.  The touchpad is an Alps touchpad.  Any help is appreciated.
    Thanks

    try downloading and installing this driver for a start,
    http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-65035-1&lc=en&dlc=en&cc=us&...
    All of my posts reflect my opinion only and not of HP.

  • GT80 Titan Touchpad Problems

    Greetings,
    There have been a number of posts here and in other forums about the dual-function Synaptics touchpad of the GT80 Titans. It can function as a traditional pointing device or it can function as a numpad. It's a brilliant idea but it has a few "gotchas".
    MSI recently posted a FAQ to address one of the problems here: www.msi.com/faq/nb-1654.html. The problem addressed in this FAQ is the numpad function no longer working.
    Unfortunately, the FAQ misses the most common cause of the problem that I've seen: Disabling "Tapping" in the Synaptics touchpad settings. Some users will turn off the "Tapping" setting because they don't want a tap to be interpreted as a mouse click when they use the touchpad as a pointing device. Why? Because it is too easy to accidentally "click" when you don't want to. Many users prefer to use the mechanical buttons of the touchpad for clicking. The problem is that disabling the "Tapping" feature also disables the Numpad function because it relies on tapping. After the user have disabled "Tapping" they discover that the numpad no longer works and become frustrated.
    In my opinion, the dual-functions of the touchpad in the GT80 Titan have been poorly implemented for a variety of reasons such as:
    1 - There should be separate Synaptics touchpad settings for the two modes. One set for use as a pointing device and another set for use as a touchpad. The most obvious reason is because many users do not like "Tapping" enabled for a pointing device but they need "Tapping" to be enabled for the numpad function.
    2 - The touchpad's mechanical buttons are only active when the touchpad is used as a pointing device. However, they are illuminated only when they are inactive and the touchpad is used as a numpad. This is backwards. The illumination should be turned on when they are active and it should follow the keyboard backlight setting controlled by Fn+Pgup and Fn+Pgdn. The illumination should be turned off when they are inactive during numpad use. As it is now, the touchpad buttons are impossible to see in the dark, making it easy to click the wrong one. I hope this can be fixed in a future BIOS update.
    3 - There is no way to make the numpad mode the default. For example, I use an external mouse most of the time and would like the touchpad to function as a numpad by default when I turn on the Titan each morning.
    Kind regards, David

    4 - The numpad illumination cannot be dimmed and it needs to be. In the dark, it is way, way, way too bright! It needs to follow the dimming of the keyboard backlight with Fn+Pgup and Fn+Pgdn.

  • GT80 Touchpad synaptics num button not working

    Hello, I made no changes to the synaptics adjustments, everything at default values, now num button for enabling number pad at gt80 not working any more. other functions (touchpad) are working. even reinstall of synaptics driver not working. Any suggestions? Thanks in advance 

    Greetings from Australia,
    I recently obtained this laptop and by design installed windows 7 x64.
    after a number of years working in call centres, I'm used to working blind and talking to people who have only recently been inducted into the realm of technology 
    (I admit sometimes it is like trying to give someone instructions in another language to help them fix their car engines via the muffler while using a braille workshop manual)
    As a matter of course, I encountered the same problem you guys did.
    Robert_Tirak thanks for your post, you gave me enough information to get started on finding a solution to this, however, I've taken the tact of writing this as if it's for someone who happened to get their hands on one of these amazing machines but isn't in any way whatsoever computer literate, as that caters for every/anyone.
    Quote from: robert_tirak on 25-March-15, 23:18:48
    The person with the "knocking zone" had the answer but it's called "tapping zones".  Just go in pointing device properties > device settings > settings. From there go to tapping and enable tapping. Then go to tap zones and enable tap zones. Fixed my numpad instantly.
    a little more detail:
    *right click on the synaptic touch pad icon in bottom right near time
    *pointing device properties
    *device settings tab up top
    *click device settings button near middle on the right hand side
    *on the new screen there's a menu on the left, in that menu
    *open 'Tapping'
    *then click tap zones and enable it
    *then you can change the zones if you like, however, what I've done is disabled top right, bottom left and *right and just enabled top left (the region that covers the num lock lit up section)
    my only problem now is, the literal command/app/function to go between numlock with keys vs mouse is missing from the list of available options.. pretty sure it'll just end up being some kind of executable or command line to initiate something in the driver,
    I'd be most grateful for any further assistance from anyone who has actually got this working.
    Sincerely
    X.

  • Scrolling Synaptic Touchpad Problem (Arch Wiki didn't solve it)

    Good to the whole Arch's community.
    First of all to appear, I am codebuster and am new in this community and in this magnificent distro that I have been charmed with for his simplicity and performance. Always I had begun for behind the topic of the configuration of Arch's installation, but consulting his magnificent tips and coming to the official information it me has been possible. I have everything working of correct form except the function of scroll of my touchpad Synaptic (function that I use always and that really I throw enough in lack). I have followed the steps indicated so much in the Wiki (http://wiki.archlinux.org/index.php/Touchpad_Synaptics) as in numerous forums of linux in inet but I have not managed to make it work, for what I resort to you to seeing if someone can throw something of light.
    Let's begin.
    PC: Acer Aspire 5610
    Distribution: ArchLinux updated a today.
    Desktop: XFCE
    Graphics: NVIDIA Geforce GO 7300 (proprietary Drivers: NVIDIA Driver Version:256.35)
    Driver: xf86-input-synaptics-1.2.2-2
    hardinfo
    Name PS/2 Synaptics TouchPad
    Type Mouse
    Bus 0x11
    Vendor 2
    Product 0x1
    Version 0x0
    Connected to isa0060/serio/input0
    cat /proc/bus/input/devices
    I: Bus=0011 Vendor=0002 Product=0001 Version=0000
    N: Name="PS/2 Synaptics TouchPad"
    P: Phys=isa0060/serio4/input0
    S: Sysfs=/devices/platform/i8042/serio4/input/input5
    U: Uniq=
    H: Handlers=mouse0 event5
    B: EV=7
    B: KEY=70000 0 0 0 0 0 0 0 0
    B: REL=3
    xorg.conf
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 256.35 (buildmeister@builder101) Wed Jun 16 19:25:59 PDT 2010
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc/"
    FontPath "/usr/share/fonts/TTF/"
    FontPath "/usr/share/fonts/OTF/"
    FontPath "/usr/share/fonts/Type1/"
    FontPath "/usr/share/fonts/100dpi/"
    FontPath "/usr/share/fonts/75dpi/"
    EndSection
    Section "Module"
    Load "dri2"
    Load "dbe"
    Load "record"
    Load "glx"
    Load "extmod"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mouse0"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G72M [Quadro NVS 110M/GeForce Go 7300]"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Xorg.0.log
    [ 18.827]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 18.828]
    X.Org X Server 1.8.1.902 (1.8.2 RC 2)
    Release Date: 2010-06-21
    [ 18.828] X Protocol Version 11, Revision 0
    [ 18.828] Build Operating System: Linux 2.6.34-ARCH i686
    [ 18.828] Current Operating System: Linux arch-live 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 21:03:38 UTC 2010 i686
    [ 18.828] Kernel command line: root=/dev/disk/by-uuid/2cf26781-3ca3-4654-8b83-37ea60864aab ro
    [ 18.828] Build Date: 21 June 2010 11:54:27AM
    [ 18.828]
    [ 18.829] Current version of pixman: 0.18.2
    [ 18.830] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 18.830] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 18.830] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 26 15:21:50 2010
    [ 18.909] (==) Using config file: "/etc/X11/xorg.conf"
    [ 18.909] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 18.962] (==) ServerLayout "X.org Configured"
    [ 18.962] (**) |-->Screen "Screen0" (0)
    [ 18.962] (**) | |-->Monitor "Monitor0"
    [ 18.963] (**) | |-->Device "Card0"
    [ 18.963] (**) |-->Input Device "Mouse0"
    [ 18.963] (**) |-->Input Device "Keyboard0"
    [ 18.963] (==) Automatically adding devices
    [ 18.963] (==) Automatically enabling devices
    [ 19.052] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 19.052] Entry deleted from font path.
    [ 19.063] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 19.063] Entry deleted from font path.
    [ 19.063] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 19.064] Entry deleted from font path.
    [ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 19.064] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 19.064] Entry deleted from font path.
    [ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 19.064] Entry deleted from font path.
    [ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 19.064] Entry deleted from font path.
    [ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 19.064] (**) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 19.064] (**) ModulePath set to "/usr/lib/xorg/modules"
    [ 19.064] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 19.064] (WW) Disabling Mouse0
    [ 19.064] (WW) Disabling Keyboard0
    [ 19.064] (II) Loader magic: 0x81e9d00
    [ 19.064] (II) Module ABI versions:
    [ 19.064] X.Org ANSI C Emulation: 0.4
    [ 19.064] X.Org Video Driver: 7.0
    [ 19.064] X.Org XInput driver : 9.0
    [ 19.064] X.Org Server Extension : 3.0
    [ 19.088] (--) PCI:*(0:1:0:0) 10de:01d7:1025:0090 nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] rev 161, Mem @ 0xd1000000/16777216, 0xc0000000/268435456, 0xd0000000/16777216
    [ 19.088] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 19.088] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    [ 19.088] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    [ 19.088] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    [ 19.088] (II) "record" will be loaded. This was enabled by default and also specified in the config file.
    [ 19.088] (II) "dri" will be loaded by default.
    [ 19.088] (II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
    [ 19.088] (II) LoadModule: "dri2"
    [ 19.141] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 19.175] (II) Module dri2: vendor="X.Org Foundation"
    [ 19.175] compiled for 1.8.1.902, module version = 1.2.0
    [ 19.175] ABI class: X.Org Server Extension, version 3.0
    [ 19.176] (II) Loading extension DRI2
    [ 19.176] (II) LoadModule: "dbe"
    [ 19.176] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 19.187] (II) Module dbe: vendor="X.Org Foundation"
    [ 19.187] compiled for 1.8.1.902, module version = 1.0.0
    [ 19.187] Module class: X.Org Server Extension
    [ 19.187] ABI class: X.Org Server Extension, version 3.0
    [ 19.187] (II) Loading extension DOUBLE-BUFFER
    [ 19.187] (II) LoadModule: "record"
    [ 19.187] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 19.188] (II) Module record: vendor="X.Org Foundation"
    [ 19.188] compiled for 1.8.1.902, module version = 1.13.0
    [ 19.188] Module class: X.Org Server Extension
    [ 19.188] ABI class: X.Org Server Extension, version 3.0
    [ 19.188] (II) Loading extension RECORD
    [ 19.188] (II) LoadModule: "glx"
    [ 19.189] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 20.431] (II) Module glx: vendor="NVIDIA Corporation"
    [ 20.431] compiled for 4.0.2, module version = 1.0.0
    [ 20.431] Module class: X.Org Server Extension
    [ 20.431] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:21:24 PDT 2010
    [ 20.431] (II) Loading extension GLX
    [ 20.431] (II) LoadModule: "extmod"
    [ 20.432] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 20.441] (II) Module extmod: vendor="X.Org Foundation"
    [ 20.441] compiled for 1.8.1.902, module version = 1.0.0
    [ 20.441] Module class: X.Org Server Extension
    [ 20.441] ABI class: X.Org Server Extension, version 3.0
    [ 20.441] (II) Loading extension MIT-SCREEN-SAVER
    [ 20.441] (II) Loading extension XFree86-VidModeExtension
    [ 20.441] (II) Loading extension XFree86-DGA
    [ 20.441] (II) Loading extension DPMS
    [ 20.441] (II) Loading extension XVideo
    [ 20.441] (II) Loading extension XVideo-MotionCompensation
    [ 20.441] (II) Loading extension X-Resource
    [ 20.441] (II) LoadModule: "dri"
    [ 20.442] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 20.451] (II) Module dri: vendor="X.Org Foundation"
    [ 20.451] compiled for 1.8.1.902, module version = 1.0.0
    [ 20.451] ABI class: X.Org Server Extension, version 3.0
    [ 20.451] (II) Loading extension XFree86-DRI
    [ 20.451] (II) LoadModule: "nvidia"
    [ 20.452] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 20.560] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 20.560] compiled for 4.0.2, module version = 1.0.0
    [ 20.560] Module class: X.Org Video Driver
    [ 20.620] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:59:34 PDT 2010
    [ 20.625] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 20.625] (++) using VT number 7
    [ 20.629] (II) Primary Device is: PCI 01@00:00:0
    [ 20.645] (II) Loading sub module "fb"
    [ 20.646] (II) LoadModule: "fb"
    [ 20.654] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 20.675] (II) Module fb: vendor="X.Org Foundation"
    [ 20.675] compiled for 1.8.1.902, module version = 1.0.0
    [ 20.675] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 20.675] (II) Loading sub module "wfb"
    [ 20.675] (II) LoadModule: "wfb"
    [ 20.676] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 20.694] (II) Module wfb: vendor="X.Org Foundation"
    [ 20.694] compiled for 1.8.1.902, module version = 1.0.0
    [ 20.694] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 20.694] (II) Loading sub module "ramdac"
    [ 20.694] (II) LoadModule: "ramdac"
    [ 20.694] (II) Module "ramdac" already built-in
    [ 20.744] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
    [ 20.744] (==) NVIDIA(0): RGB weight 888
    [ 20.744] (==) NVIDIA(0): Default visual is TrueColor
    [ 20.744] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 20.744] (**) NVIDIA(0): Enabling RENDER acceleration
    [ 20.744] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    [ 20.744] (II) NVIDIA(0): enabled.
    [ 22.341] (II) NVIDIA(0): NVIDIA GPU GeForce Go 7300 (G72) at PCI:1:0:0 (GPU-0)
    [ 22.341] (--) NVIDIA(0): Memory: 262144 kBytes
    [ 22.341] (--) NVIDIA(0): VideoBIOS: 05.72.22.58.30
    [ 22.341] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 22.341] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    [ 22.341] (--) NVIDIA(0): Connected display device(s) on GeForce Go 7300 at PCI:1:0:0:
    [ 22.341] (--) NVIDIA(0): LPL (DFP-0)
    [ 22.341] (--) NVIDIA(0): LPL (DFP-0): 330.0 MHz maximum pixel clock
    [ 22.341] (--) NVIDIA(0): LPL (DFP-0): Internal Dual Link LVDS
    [ 22.355] (II) NVIDIA(0): Assigned Display Device: DFP-0
    [ 22.355] (==) NVIDIA(0):
    [ 22.355] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
    [ 22.355] (==) NVIDIA(0): will be used as the requested mode.
    [ 22.355] (==) NVIDIA(0):
    [ 22.355] (II) NVIDIA(0): Validated modes:
    [ 22.355] (II) NVIDIA(0): "nvidia-auto-select"
    [ 22.356] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 800
    [ 22.356] (--) NVIDIA(0): DPI set to (98, 96); computed from "UseEdidDpi" X config
    [ 22.356] (--) NVIDIA(0): option
    [ 22.356] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    [ 22.356] (--) Depth 24 pixmap format is 32 bpp
    [ 22.358] (II) NVIDIA(0): Initialized GPU GART.
    [ 22.371] (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
    [ 22.371] (II) NVIDIA(0): enough to receive ACPI hotkey events.
    [ 22.371] (WW) NVIDIA(0): ACPI: Error: Unable to find the brightness file path under
    [ 22.372] (WW) NVIDIA(0): /proc/acpi/video. The NVIDIA X driver will not be able to
    [ 22.372] (WW) NVIDIA(0): respond to ACPI brightness change hotkey events.
    [ 22.372] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
    [ 23.783] (II) Loading extension NV-GLX
    [ 23.817] (II) NVIDIA(0): Initialized OpenGL Acceleration
    [ 23.831] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 23.831] (II) NVIDIA(0): Initialized X Rendering Acceleration
    [ 23.851] (==) NVIDIA(0): Backing store disabled
    [ 23.851] (==) NVIDIA(0): Silken mouse enabled
    [ 23.858] (==) NVIDIA(0): DPMS enabled
    [ 23.858] (II) Loading extension NV-CONTROL
    [ 23.859] (II) Loading extension XINERAMA
    [ 23.859] (II) Loading sub module "dri2"
    [ 23.859] (II) LoadModule: "dri2"
    [ 23.860] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 23.860] (II) NVIDIA(0): [DRI2] Setup complete
    [ 23.860] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 23.860] (==) RandR enabled
    [ 23.860] (II) Initializing built-in extension Generic Event Extension
    [ 23.860] (II) Initializing built-in extension SHAPE
    [ 23.860] (II) Initializing built-in extension MIT-SHM
    [ 23.860] (II) Initializing built-in extension XInputExtension
    [ 23.860] (II) Initializing built-in extension XTEST
    [ 23.860] (II) Initializing built-in extension BIG-REQUESTS
    [ 23.860] (II) Initializing built-in extension SYNC
    [ 23.860] (II) Initializing built-in extension XKEYBOARD
    [ 23.860] (II) Initializing built-in extension XC-MISC
    [ 23.860] (II) Initializing built-in extension SECURITY
    [ 23.860] (II) Initializing built-in extension XINERAMA
    [ 23.860] (II) Initializing built-in extension XFIXES
    [ 23.860] (II) Initializing built-in extension RENDER
    [ 23.860] (II) Initializing built-in extension RANDR
    [ 23.860] (II) Initializing built-in extension COMPOSITE
    [ 23.860] (II) Initializing built-in extension DAMAGE
    [ 23.864] (II) Initializing extension GLX
    [ 24.465] (II) config/udev: Adding input device Power Button (/dev/input/event4)
    [ 24.465] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 24.465] (II) LoadModule: "evdev"
    [ 24.466] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 24.483] (II) Module evdev: vendor="X.Org Foundation"
    [ 24.483] compiled for 1.8.0, module version = 2.4.0
    [ 24.483] Module class: X.Org XInput Driver
    [ 24.483] ABI class: X.Org XInput driver, version 9.0
    [ 24.483] (**) Power Button: always reports core events
    [ 24.483] (**) Power Button: Device: "/dev/input/event4"
    [ 24.491] (II) Power Button: Found keys
    [ 24.491] (II) Power Button: Configuring as keyboard
    [ 24.491] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 24.491] (**) Option "xkb_rules" "evdev"
    [ 24.491] (**) Option "xkb_model" "evdev"
    [ 24.491] (**) Option "xkb_layout" "us"
    [ 24.579] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
    [ 24.580] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 24.580] (**) Video Bus: always reports core events
    [ 24.580] (**) Video Bus: Device: "/dev/input/event5"
    [ 24.587] (II) Video Bus: Found keys
    [ 24.587] (II) Video Bus: Configuring as keyboard
    [ 24.587] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    [ 24.587] (**) Option "xkb_rules" "evdev"
    [ 24.587] (**) Option "xkb_model" "evdev"
    [ 24.587] (**) Option "xkb_layout" "us"
    [ 24.593] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 24.594] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 24.594] (**) Power Button: always reports core events
    [ 24.594] (**) Power Button: Device: "/dev/input/event3"
    [ 24.600] (II) Power Button: Found keys
    [ 24.600] (II) Power Button: Configuring as keyboard
    [ 24.600] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 24.600] (**) Option "xkb_rules" "evdev"
    [ 24.601] (**) Option "xkb_model" "evdev"
    [ 24.601] (**) Option "xkb_layout" "us"
    [ 24.602] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 24.602] (II) No input driver/identifier specified (ignoring)
    [ 24.602] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 24.602] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 24.602] (**) Sleep Button: always reports core events
    [ 24.602] (**) Sleep Button: Device: "/dev/input/event2"
    [ 24.611] (II) Sleep Button: Found keys
    [ 24.611] (II) Sleep Button: Configuring as keyboard
    [ 24.611] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
    [ 24.611] (**) Option "xkb_rules" "evdev"
    [ 24.611] (**) Option "xkb_model" "evdev"
    [ 24.611] (**) Option "xkb_layout" "us"
    [ 24.613] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
    [ 24.613] (II) No input driver/identifier specified (ignoring)
    [ 24.619] (II) config/udev: Adding input device MosArt Optical Mouse (/dev/input/event7)
    [ 24.619] (**) MosArt Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 24.619] (**) MosArt Optical Mouse: always reports core events
    [ 24.619] (**) MosArt Optical Mouse: Device: "/dev/input/event7"
    [ 24.631] (II) MosArt Optical Mouse: Found 3 mouse buttons
    [ 24.631] (II) MosArt Optical Mouse: Found scroll wheel(s)
    [ 24.631] (II) MosArt Optical Mouse: Found relative axes
    [ 24.631] (II) MosArt Optical Mouse: Found x and y relative axes
    [ 24.631] (II) MosArt Optical Mouse: Configuring as mouse
    [ 24.631] (**) MosArt Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 24.631] (**) MosArt Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 24.631] (II) XINPUT: Adding extended input device "MosArt Optical Mouse" (type: MOUSE)
    [ 24.631] (**) MosArt Optical Mouse: (accel) keeping acceleration scheme 1
    [ 24.631] (**) MosArt Optical Mouse: (accel) acceleration profile 0
    [ 24.631] (**) MosArt Optical Mouse: (accel) acceleration factor: 2.000
    [ 24.631] (**) MosArt Optical Mouse: (accel) acceleration threshold: 4
    [ 24.631] (II) MosArt Optical Mouse: initialized for relative axes.
    [ 24.632] (II) config/udev: Adding input device MosArt Optical Mouse (/dev/input/mouse1)
    [ 24.632] (II) No input driver/identifier specified (ignoring)
    [ 24.638] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 24.638] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 24.638] (**) AT Translated Set 2 keyboard: always reports core events
    [ 24.638] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 24.651] (II) AT Translated Set 2 keyboard: Found keys
    [ 24.651] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [ 24.651] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    [ 24.651] (**) Option "xkb_rules" "evdev"
    [ 24.651] (**) Option "xkb_model" "evdev"
    [ 24.651] (**) Option "xkb_layout" "us"
    [ 24.652] (II) config/udev: Adding input device PS/2 Synaptics TouchPad (/dev/input/event6)
    [ 24.652] (**) PS/2 Synaptics TouchPad: Applying InputClass "evdev pointer catchall"
    [ 24.652] (**) PS/2 Synaptics TouchPad: always reports core events
    [ 24.652] (**) PS/2 Synaptics TouchPad: Device: "/dev/input/event6"
    [ 24.664] (II) PS/2 Synaptics TouchPad: Found 3 mouse buttons
    [ 24.664] (II) PS/2 Synaptics TouchPad: Found relative axes
    [ 24.664] (II) PS/2 Synaptics TouchPad: Found x and y relative axes
    [ 24.664] (II) PS/2 Synaptics TouchPad: Configuring as mouse
    [ 24.664] (**) PS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
    [ 24.664] (**) PS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 24.664] (II) XINPUT: Adding extended input device "PS/2 Synaptics TouchPad" (type: MOUSE)
    [ 24.664] (**) PS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration profile 0
    [ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 24.664] (II) PS/2 Synaptics TouchPad: initialized for relative axes.
    [ 24.665] (II) config/udev: Adding input device PS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 24.665] (II) No input driver/identifier specified (ignoring)
    10-evdev.conf
    # Catchall classes for input devices
    # We don't simply match on any device since that also adds accelerometers
    # and other devices that we don't really want to use. The list below
    # matches everything but joysticks.
    Section "InputClass"
    Identifier "evdev pointer catchall"
    MatchIsPointer "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    Section "InputClass"
    Identifier "evdev keyboard catchall"
    MatchIsKeyboard "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    Section "InputClass"
    Identifier "evdev touchpad catchall"
    MatchIsTouchpad "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    Option "VertEdgeScroll" "true"
    Option "VertScrollDelta" "100"
    EndSection
    Section "InputClass"
    Identifier "evdev tablet catchall"
    MatchIsTablet "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    Section "InputClass"
    Identifier "evdev touchscreen catchall"
    MatchIsTouchscreen "on"
    MatchDevicePath "/dev/input/event*"
    Driver "evdev"
    EndSection
    10-synaptics.conf
    Section "InputClass"
    Identifier "touchpad catchall"
    Driver "synaptics"
    MatchIsTouchpad "on"
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    Option "VertEdgeScroll" "true"
    Option "VertScrollDelta" "100"
    EndSection
    Good, I believe that this is quite, if you need more information tell to me and it will make it come near.
    Excuse me for my poor english,Thanks in advance and best regards.
    codebuster.
    Last edited by codebuster (2010-07-26 14:44:07)

    kgas wrote:
    there is no need to include the synaptics option. here is mine and works fine (Acer Aspire 5738G)
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "dbe"
    Load "glx"
    Load "dri"
    Load "dri2"
    Load "extmod"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "G98M [GeForce G 105M]"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    ¡¡¡¡ Thanks a lot for the info !!! 
    I remove all the Synaptics entries in the xorg.conf and worked fine with the /dev/input/mice option (in the Arch Wiki was # commented, the device, was /dev/psaux, and my mouse in hardinfo was recognized as PS/2 Synaptic for that I thought that it was the correct  option ).
    Only one question, now I have set the scrolling mode with two fingers, ¿do you know how to activate one finger scrolling? I tried with these options in Mouse section but doesn't work for me:
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "false" # enable horizontal scroll zone
    Option "VertTwoFingerScroll" "false" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "false" # horizontal scroll anywhere with two fingers
    ¡ Many, many thanks and my best regards !
    codebuster.
    Last edited by codebuster (2010-07-26 08:26:55)

  • Probook 470 G1 touchpad problem - NOT SOLVED with SP64284

    Hello,
    my touchpad is problematic.
    It registers movement but often misses a click, also hangs from time to time.
    I have installed SP64284 but the problem remains.
    Please help,
    Miljan
    (HP Probook 470 G1)

    Hi,
    have the same problem :/
    i took my laptop to the store and they replace the touch pad...no improvements at all. Its interesting that if you put your hand on right side of the touch pad ( low pressure on plastic) its even worst...
    Have the same hp probook 470 g1
    Anže

  • G-580 touchpad problem when scrolling

    sir,
      my lenovo G-580 which is windows 8 besed laptop has a problem with its tuoch pad. 
    when i scroll over it's mouse pad it automatically selectes the items, and some times it takes comands automatically
    specially when internet is open and doing something on internet , it troubling me much. i have purchesed it from local retailer in the month of february 2014. sir plz provide me help as early as possible so that i can take a relif from it disturb...
                                                                      thank you...

    Hi,
    Welcome to Lenovo Community!
    I’m sorry to hear that your new G580 Laptops touchpad scroll feature is not working as expected, I suggest you to re-install the Touchpad driver in the computer and check the issue. While installing the driver right click on the downloaded file and select “Run as administrator” option to get it installed without any error.
    Do post us back if the issue persists.
    Best Regards
    Shiva Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Mousepad/touchpad problem control button activates

    Hi,
    Just bought a pavilion g6 and i have a problem with the touch pad. when moving the cursor around the screen the control button seems to suddenly activate.
    for example the "find your cursor when pressing control" function kicks in and a circle highlights the location of the cursor on the screen
    or even worse the webpage will zoom in and out as if I held the control button and swiped up or down with the touchpad page scroll option.
    I am not using the mouse pad in any weird way. eg just using one (slender) finger. I cant find any reference to this being a known problem but i am checking here before leaving my laptop back.
    is there meant to be some in built touchpad function that causes the control button to be able to be activated from the touchpad? If so can i disactivate it?
    regards,
    d500b
    This question was solved.
    View Solution.

    Hi
    Please find the link givenbelow might help you to resolve your issue.
    Using and Configuring the Touch Pad
    Let us know how it goes!
    "I work for HP."
    ****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
    ****Please mark Accept As Solution if it solves your problem****
    Regards
    Manjunath

  • Gnome 3::Touchpad problem

    Hi,
    I have a problem with gnome3. I have a new laptop Lenovo Thinkpad L420 (Intel Core
    i5-2410M + Intel HD 3000) with OS Archlinux 64-bit + Gnome3.
    When I disable touchpad, touchpad is off and I enable touchpad, touchpad is
    still disable::touchpad toggle (Fn+F8). When I switch to some tty (Ctrl + Alt + F1-F6) and
    back to Xserver (Ctrl + Alt + F7), so touchpad works.
    And touchpad in gnome 2 works normally.
    What can I do with this problem? Sorry for my bad english. Thanks for your help!

    You should post some logs. Give us an output of "dmesg | tail" when this happen.
    I have done bellow to get a working switch for my touchpad in X environment. This is a WORKAROUND not a solution to your problem. First of all type:
    xinput list
    You will see your touchpad. My touchpad is:
    ETPS/2 Elantech Touchpad
    I will use my touchpad as an example.
    Now copy this text to blank file and make it executable:
    #!/bin/bash
    if
    xinput --list-props "ETPS/2 Elantech Touchpad" | grep "Synaptics Off" | grep 1
    then
    xinput --set-prop 'ETPS/2 Elantech Touchpad' 'Synaptics Off' 0
    else
    xinput --set-prop 'ETPS/2 Elantech Touchpad' 'Synaptics Off' 1
    fi
    Again, my touchpad is examplary you have too put yours in.
    Now you can use this script through gnome keyboard shortcut application and assign key combination.
    Last edited by Shark (2011-08-23 13:35:06)

  • Touchpad problem after waking from Sleep

    When I wake my Macbook Pro (Snow Leopard 10.6.1) from sleep the touchpad soft clicking doesn't work however The phsyical click does.
    It rectifies itself after about 5 minutes of use however it is quite frustrating. Any possible solutions? This problem occured in with Leopard (10.5.x) as well.

    I have exact same problem, in that in waking from sleep, cursor cannot be moved by touchpad for 1-2 minutes but moves instantly and normally via a mouse. Has been happening ever since got machine in March, regardless of OS / firmware upgrades. Any suggestions out there?

  • [SOLVED] Touchpad problems with Kernel-2.6.28

    I just updated my kernel to 2.6.28. Everythink is working fine (including my Atheros AGN wireless ). The only problem I have now is the Touchpad. After update the double click on the touchpad and the scroll function is not working any more.
    Anyone knows why or is having the same problem?
    Last edited by falke (2009-01-26 16:32:31)

    Thanks a lot!!! It works! I cant live without touchpad scrolling.
    I also needed to create /etc/hal/fdi/policy/shmconfig.fdi with this content:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <deviceinfo version="0.2">
    <device>
    <match key="input.x11_driver" string="synaptics">
    <merge key="input.x11_options.SHMConfig" type="string">True</merge>
    </match>
    </device>
    </deviceinfo>

  • Zen Sleek Touchpad problem - scrolling down acts like a scroll

    Yes, a strange problem I ran into today. Everytime I try to scroll down using the touchpad on my Zen Sleek, the cursor moves up instead. It's like the whole touchpad can only move the cursor in one-direction, up. Even if I try to use the rapid-scroll, the cursor just moves up rapidly
    This happened yesterday, when on one bar of battery, my Sleek, around the afternoon froze while starting up and I could not restart it because I did not have a paperclip on me. After I get home hours later, I charge my Sleek since the battery died. And, now, today... I am at this rather strange problem.
    And, my Sleek hasn't given me problems since I bought it a year ago besides the occasional lockups on one-bar of battery.

    Creative Zen Sleek Photo and Zen Sleek
    . Detach the Zen player from your PC , and ensure that the Zen Sleek is turned off.
    2. Connect the power supply to the player.
    3. Hold down the Play/Pause button while inserting a paper clip into the Reset hole
    underneath your player, beside the data/power connector. Keep on holding the
    Play/Pause button while you release the Reset button. The Rescue Mode screen will
    then appear.
    4. After the recovery mode has started, release the Play/Pause button
    It will display the following options.
    Clean Up
    Scans the player and removes invalid links from its music library.
    Does not affect music files themselves.
    Format (All)
    Caution! Erases all content!
    Save a copy of your player's content before formatting.
    Reload OS/ Firmware
    Caution! Erases your player's firmware.
    DO NOT select the Reload Firmware option unless you have access to a PC and you have downloaded the necessary firmware to install.
    Reboot Reboots the device.

  • Ideapad U510 Touchpad problem

    I have bought a lenovo ideapad u510 a week before. From the very begining I am facing toucpad problem, The cursor jumps everywhere in the screen and make automatic selection all by itself. I am totally unable to control the cursor.
    I have tried installing Synaptics driver after unistalling default Elan driver, but it wasn't solved a bit. I have tried by changing various options from the  Elan menu, also disabled 'Multi-finger' option.
    I have bought it from Canada but now I'm far away from there. So if anyone knows the solution please help me.

    Please reinstall your default touchpad driver (ELAN). According to Elan: The main cause of unexpected cursor moving or click is the accidental palm contact with the touch pad. You can adjust your Palm Tracking setting to maximum to make your touch pad insensitive to "palm contacts"

Maybe you are looking for

  • What is the difference between wi-fi and wi-fi cellular in purchasing an i-pad?

    I am confused about the difference, and want to make a purchase, but don't know if I actually need the cellular or 3G, or what they would be for on an i-pad.  Thanks.

  • Capturing elements value in the selection screen for LDB during run time

    Hi, I have a program where LDB is used. Could anyone please suggest how to capture the values of the elements present in the LDB's default selection screen. Specially, the company code and the period values. Please reply . Its too urgent. Regards, Bi

  • Issue with printing program Z_RVADIN01

    Hello Experts, I am facing a funny issue and ask your help/ opinion on this: I created a new window/ element "payer" within the form for billing-docs (output type RD00). In this new window "payer"  the address of an alternative payer should be shown.

  • Air port extreme not working with 10.5

    ok so hear is one of the many problems i am having my airport extreme is working and functions fine i can screen share and see all 3 of my macs. now to the problem when i use the network diagnostics it get all green lights up till internet and server

  • Live snapshots not working in 3.0.3

    Please help. I have read that live snapshots are possible in Oracle VM 3.0.3. Simply do a clone of a running VM. But everytime I try this I get an error saying that it can't clone a live running VM. Please let me know what i am doing wrong. Thanks, V