Synaptics doesn't work at all

Corvin · 2008-11-18 21:20:29

Hi I'm archlinux user for several years. I am always uptodate but last time arch is somehow unstable.
Touchpad is not recognized at all, I've got HP nx 6110. All is working in Windows and a month ago or little more it was working in X. but it stopped. /proc/bus/input/devices shows that instead of touchpad I've got macintosh mouse emulation device? trying to start Xes causes stop and message that synaptics is not recognized. I don't get it at all Could you help me? thanks

kb3pev · 2008-11-19 03:11:03

I'm having the exact same problem. It came as soon as I updated from stable to testing. Not sure what the issue is yet.

bfc · 2008-11-19 10:00:20

Not sure if this will help, but it solved my synaptics issue....

add the following to your xorg.conf

Section "ServerFlags"
Option "AllowEmptyInput" "false"
EndSection

Also, make sure you've actually installed the xf86-input-synpatics package from testing repo.

schuay · 2008-11-19 10:31:23

Your problem is most probably caused by the new xorg hotplugging feature. Theres at least 5 threads open on this on the forums

You can disable it using the AllowEmptyInput/AutoAddDevices server flags, or fix it by commenting out the input sections in xorg.conf and using the hal xml files (for example /etc/hal/fdi/policy/11-x11-synaptics.fdi)

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.capabilities" contains="input.touchpad">
      <match key="info.product" contains="Synaptics TouchPad">
        <merge key="input.x11_driver" type="string">synaptics</merge>
    <merge key="input.x11_options.MinSpeed"     type="string">0.09</merge>
    <merge key="input.x11_options.MaxSpeed"     type="string">0.18</merge>
    <merge key="input.x11_options.Emulate3Buttons"  type="string">true</merge>
        <merge key="input.x11_options.SHMConfig"        type="string">true</merge>
        <merge key="input.x11_options.AccelFactor"      type="string">0.032</merge>
        <merge key="input.x11_options.LeftEdge"         type="string">1700</merge>
        <merge key="input.x11_options.RightEdge"        type="string">5300</merge>
        <merge key="input.x11_options.TopEdge"          type="string">1700</merge>
        <merge key="input.x11_options.BottomEdge"       type="string">4200</merge>
        <merge key="input.x11_options.FingerLow"        type="string">25</merge>
        <merge key="input.x11_options.FingerHigh"       type="string">30</merge>
        <merge key="input.x11_options.MaxTapTime"       type="string">180</merge>
        <merge key="input.x11_options.MaxTapMove"       type="string">220</merge>
        <merge key="input.x11_options.HorizEdgeScroll"  type="string">true</merge>
        <merge key="input.x11_options.HorizScrollDelta" type="string">100</merge>
        <merge key="input.x11_options.VertEdgeScroll"   type="string">true</merge>
        <merge key="input.x11_options.VertScrollDelta"  type="string">100</merge>
        <!-- Restore old synaptics driver defaults removed by Fedora/RH patch -->
        <merge key="input.x11_options.RTCornerButton"   type="string">2</merge>
        <merge key="input.x11_options.RBCornerButton"   type="string">3</merge>
        <merge key="input.x11_options.TapButton1"       type="string">1</merge>
        <merge key="input.x11_options.TapButton2"       type="string">2</merge>
        <merge key="input.x11_options.TapButton3"       type="string">3</merge>
      <!-- Arbitrary options can be passed to the driver using 
         the input.x11_options property since xorg-server-1.5. -->
    <!-- EXAMPLE:
    <merge key="input.x11_options.LeftEdge" type="string">120</merge>
    -->
      </match>
      <match key="info.product" contains="AlpsPS/2 ALPS">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
      <match key="info.product" contains="appletouch">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
      <match key="info.product" contains="bcm5974">
        <merge key="input.x11_driver" type="string">synaptics</merge>
      </match>
    </match>
  </device>
</deviceinfo>

edit: by the way... my /proc/bus/input/devices:

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=mouse0 event0 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

snip

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/class/input/input8
U: Uniq=
H: Handlers=mouse1 event8 
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003

Last edited by schuay (2008-11-19 10:38:41)

Corvin · 2008-11-19 22:20:13

I've aaded your xml file, but I don't have synaptics in my /proc/bus/input/devices

at all

schuay · 2008-11-20 08:32:54

Hm.. not sure if I can help you then

Do you have xf86-input-evdev installed? Have you commented out the input sections in xorg.conf?

Corvin · 2008-11-20 09:36:29

No I have not commented them out yet. But I don't know what is going on with system and I have xf86-input-evdev installed
and even evdev module loaded

thayer · 2008-11-21 05:39:17

Been struggling with this myself today...figured out what's going on. Assuming you do not want to deal with the evdev/hal/hotplugging crap, you can re-enable the old method of configuring devices by adding the following to the ServerFlags section:

"Option"    "AutoAddDevices"    "false"

If you find that your scrolling no longer works, you must now explicitly enable the scroll zones in the synaptics InputDevice section of xorg.conf:

    Option      "VertEdgeScroll"    "true"  # enable vertical scroll zone
    Option      "HorizEdgeScroll"   "true"  # enable horizontal scroll zone

As mentioned, this assumes you have disabled input hotplugging.

Last edited by thayer (2008-11-21 05:42:06)

tomk · 2008-11-21 07:22:38

I'm running it with no xorg.conf and the .fdi file, and it's working fine.

thayer · 2008-11-21 19:31:38

tomk wrote:

I'm running it with no xorg.conf and the .fdi file, and it's working fine.

This works for generic setups, but AFAIK if you add a single device to xorg.conf (such as enabling the fglrx driver) then you have to specify everything in xorg.conf.

Inkaine · 2008-11-21 19:45:29

For me it's working fine one two machines with xorg.conf for graphics and hal for input drivers. I commented out all lines related to keyboard, mice, and touchpad in xorg.conf's but still retain server flags, device sections for screen and vga etc. Only problems I've been having now were related to defines in fdi.

tomk · 2008-11-21 20:56:48

thayer - interesting. One of these days, I'll probably give fglrx another shot, so we'll see what happens if I do.

Corvin · 2008-11-22 21:42:27

This is mine /proc/bus/input/devices

I don't know why Archlinux is getting worse last time but 4 serious things don't work as expected.

1. synaptics stopped to work
2. alsa - my ICH6 device is recognized alsaconf properly, but running alsamixer gives error message that no sound card found, /proc/asound in my opinion looks ok
3. led on my laptop connected to IPW2200 doesn't lid any more but it is working
4. udev doesn't create device file /dev/sda6, this is NTFS logical disk on extended partition

so I as software developer think that arch is undertested, I'm using distro for more than 3 years but I it more and more disappointing in last few months.

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=mouse0 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=kbd 
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=kbd 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button (CM)"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/class/input/input3
U: Uniq=
H: Handlers=kbd 
B: EV=3
B: KEY=4000 0 0 0 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=
B: EV=21
B: SW=1

tomk · 2008-11-23 15:11:11

thayer wrote:

This works for generic setups, but AFAIK if you add a single device to xorg.conf (such as enabling the fglrx driver) then you have to specify everything in xorg.conf.

Just for interest's sake, I tried fglrx again, and in the context of this thread, it runs correctly with the xorg.conf generated by aticonfig and the .fdi file for the touchpad. I didn't comment or remove the input sections, or anything else, from xorg.conf.

Corvin - this thread is about synaptics and xorg. You are more likely to get help with your other issues if you start separate threads for them. If you believe Arch is undertested, you are more than welcome to participate in our ongoing testing activities by activating the testing repo, and reporting and/or fixing bugs.

ProgDan · 2008-11-24 09:13:06

I fixed Synaptics-driver problem with xorg-server from [testing] by installing xf86-input-synaptics from [testing].
The current stable libsynaptics is incompatible with new xorg-server

stonecrest · 2008-11-24 15:05:02

ProgDan wrote:

I fixed Synaptics-driver problem with xorg-server from [testing] by installing xf86-input-synaptics from [testing].
The current stable libsynaptics is incompatible with new xorg-server

If you're going to use the testing repo, you should already know that it should be placed first in your pacman.conf, so that the above situation won't happen. It is a really bad idea to pick and choose the testing packages that you want to use, you're asking for things to break.

Corvin · 2008-11-26 08:50:48

I've found a solution to the problem, I've noticed that although there is udev hook in mkinitcpio and some devices are created, but I had initscripts-genslpash, and they require /etc/start-udev! I've noticed the problem installed new initscripts from repos and everything comes back to normal (almost). I think that this is a bug and developers should make pacman to ask about upgrade to initscripts. Moreover there should be more info on webpages, wiki, forum that so important package is changed, and there is risk that udev won't start at all. I think that would greatly reduce traffic on forum.

Last edited by Corvin (2008-11-26 08:51:41)

tomk · 2008-11-26 20:13:29

Bugs and feature requests should be posted on the bugtracker, as there is no guarantee that the dev(s) concerned will read this thread.

Corvin · 2008-11-27 09:40:38

Ok I've entered a bug

denisfalqueto · 2008-11-28 00:49:55

Hi,

I just solved this exact problem and wanted to say something.

First, I'm using hal to configure the keyboard and the synaptics touchpad. The devil is on the details. I lost a lot of time trying to configure the touchpad and the problem was that I was using the wrong device. I was trying to use the /dev/input/event0, which is the Macintosh emulation, not the real synaptics device. So, if you want to specify the device, you need to loot at /proc/bus/input/devices, in the part that tells about your synaptic touchpad. In my case it was this:

I: Bus=0011 Vendor=0002 Product=0007 Version=25b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input10
U: Uniq=
H: Handlers=mouse1 event10
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003

The Handlers item lists the devices it will create for this device, so you can use /dev/input/mouse1 or /dev/input/event10. You must adapt for your case, but is very easy.

You can also decide not to specify the device, as schuay is doing. I think I'll do that too. It's easier to let X find out what to do.

Hope that helps.

Edit: just forgot to say that the configuration for the device in /etc/hal/fdi/policy/11-x11-synaptics.fdi is:

<merge key="input.x11_options.Device" type="string">/dev/input/event10</merge>

Last edited by denisfalqueto (2008-11-28 00:53:15)

V01D · 2008-12-01 14:54:45

Hi... FYI, my touchpad started working after I removed the entry on the xorg.conf. On the logs, it seemed that it wanted to open the device twice or something.

lfc4 · 2010-11-20 18:43:10

thayer wrote:

Assuming you do not want to deal with the evdev/hal/hotplugging crap, you can re-enable the old method of configuring devices by adding the following to the ServerFlags section:
"Option"    "AutoAddDevices"    "false"

Hello
After I had reinstalled xorg and kde lately my touchpad stopped to work. By adding the "AutoAddDevices" "false" in xorg.conf and rebooting everything is back to normal.
Thank you for the information thayer.

Arch Linux

#1 2008-11-18 21:20:29

Synaptics doesn't work at all

#2 2008-11-19 03:11:03

Re: Synaptics doesn't work at all

#3 2008-11-19 10:00:20

Re: Synaptics doesn't work at all

#4 2008-11-19 10:31:23

Re: Synaptics doesn't work at all

#5 2008-11-19 22:20:13

Re: Synaptics doesn't work at all

#6 2008-11-20 08:32:54

Re: Synaptics doesn't work at all

#7 2008-11-20 09:36:29

Re: Synaptics doesn't work at all

#8 2008-11-21 05:39:17

Re: Synaptics doesn't work at all

#9 2008-11-21 07:22:38

Re: Synaptics doesn't work at all

#10 2008-11-21 19:31:38

Re: Synaptics doesn't work at all

#11 2008-11-21 19:45:29

Re: Synaptics doesn't work at all

#12 2008-11-21 20:56:48

Re: Synaptics doesn't work at all

#13 2008-11-22 21:42:27

Re: Synaptics doesn't work at all

#14 2008-11-23 15:11:11

Re: Synaptics doesn't work at all

#15 2008-11-24 09:13:06

Re: Synaptics doesn't work at all

#16 2008-11-24 15:05:02

Re: Synaptics doesn't work at all

#17 2008-11-26 08:50:48

Re: Synaptics doesn't work at all

#18 2008-11-26 20:13:29

Re: Synaptics doesn't work at all

#19 2008-11-27 09:40:38

Re: Synaptics doesn't work at all

#20 2008-11-28 00:49:55

Re: Synaptics doesn't work at all

#21 2008-12-01 14:54:45

Re: Synaptics doesn't work at all

#22 2010-11-20 18:43:10

Re: Synaptics doesn't work at all

Board footer