Synaptics cPad (touchpad) isnt detected

[sysitos]

Binary package hint: xserver-xorg-input-synaptics

Hardware: Toshiba Satellite 5200-903
Fresh installation of Feisty with herd4, touchpad only works as normal mouse.

Xorg.0.log:
(EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device
(EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics Touchpad"
(II) UnloadModule: "synaptics"

#cat /proc/bus/input/devices
I: Bus=0003 Vendor=06cb Product=0003 Version=0100
N: Name="Synaptics Inc. Synaptics cPad"
P: Phys=usb-0000:02:06.0-3/input0
S: Sysfs=/class/input/input2
H: Handlers=mouse1 event2 ts1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

but there is also a
I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0 ts0
don't know, where it comes from

here is the important snippet from the xorg.conf
Section "InputDevice"
 Identifier "Synaptics Touchpad"
 Driver "synaptics"
  Option "SendCoreEvents" "true"
 Option "Device" "/dev/psaux"
 Option "Protocol" "auto-dev"
 Option "HorizScrollDelta" "0"
EndSection

Section "ServerLayout"
 InputDevice "Synaptics Touchpad"

btw, there was no problem with Kubuntu 6.10 and the touchpad.

#laptop-detect && echo yes shows yes

(Could be the a similar bug as https://launchpad.net/ubuntu/+source/laptop-detect/+bug/89113)

[Wolf Rogner (war-rsb)]

/etc/X11/xorg.conf contains a section "InputDevice" for Identifier "Synaptics"

I have the SHMConfig option "on"

I get the same error messags in the /var/log/Xorg.0.log as described above

Query of the pad with synclient -l reports:

Can't access shared memory area. SHMConfig disabled?

(Well, No)

I have followed the help pages describing solutions somewhere else in the wiki. No success.

Reading from file /dev/psaux returns no result (as opposed to /dev/input/mice or /dev/input/event0)

(This tells me that the /dev/psaux device is not attached)

Reproducable in Edgy and Feisty (herd 1..5)

Question: Where can I read about how hardware detection works. Reading all the reports here, it seems to me that the problem does not lie in the XOrg system but somewhere in the detection mechanism.

Thanks, Wolf

[Wolf Rogner (war-rsb)]

Here are some additional observations:

Upon startup of X-server the server tries to load the synaptics driver:

"Loading /usr/lib/xorg/modules/input/synaptics_drv.so"

a bit later it reports that it could not find a device at BusID 0:2:0

"(II) Primary Device is: PCI 00:02:0
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found"

However, the device manager reports the Synaptics pad at pnp0/00:08

Can this be the cause of the incompatibility?

[Cinar Sahin (csahin)]

I have the same problem with Toshiba Satelllite 5105-S701. Here's the relevant section from the xorg log:

Query no Synaptics: 6003C8
(EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device
(EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics Touchpad"
(II) UnloadModule: "synaptics"
(WW) <default pointer>: No Device specified, looking for one...
(II) <default pointer>: Setting Device option to "/dev/input/mice"
(--) <default pointer>: Device: "/dev/input/mice"
(==) <default pointer>: Protocol: "Auto"

[Resnick (resnick147)]

I have the same issue on a Toshiba Satellite S5200-801.

The touchpad does not work at all after upgrade to Feisty, while it worked fine with Edgy.
The relevant logs are identical to those above.

[Resnick (resnick147)]

Reading dmesg i noticed that the device keeps on "resetting", this might be the cause of the problems:

[ 699.180000] input: Synaptics Inc. Synaptics cPad as /class/input/input8
[ 699.180000] input: USB HID v1.00 Mouse [Synaptics Inc. Synaptics cPad] on
usb-0000:02:06.0-3
[ 952.224000] usb 2-3: USB disconnect, address 5
--
[ 953.196000] input: Synaptics Inc. Synaptics cPad as /class/input/input9
[ 953.196000] input: USB HID v1.00 Mouse [Synaptics Inc. Synaptics cPad] on
usb-0000:02:06.0-3
[ 1458.896000] usb 2-3: USB disconnect, address 6
--

and so on..

Can anyone reproduce?

By the way, this could also be a factor:
https://bugs.launchpad.net/ubuntu/+source/cpad-kernel/+bug/109103

[Wolf Rogner (war-rsb)]

It started to work with kernel 2.6.20.16 with me.

thanks

[Resnick (resnick147)]

> It started to work with kernel 2.6.20.16 with me.

not for me, the problem occurs with kernel 2.6.20-16-generic

[schlady (schlady)]

cPad didnt work since last Feisty Kernel update (dont know which version it was) and also doesnt work under gutsy (2.6.22-8-generic).

cPad keeps on resetting:

[ 711.092000] usb 1-3: USB disconnect, address 3
[ 711.836000] usb 1-3: new full speed USB device using ohci_hcd and address 4
[ 712.048000] usb 1-3: configuration #1 chosen from 1 choice
[ 712.056000] input: Synaptics Inc. Synaptics cPad as /class/input/input9
[ 712.056000] input: USB HID v1.00 Mouse [Synaptics Inc. Synaptics cPad] on usb-0000:02:06.0-3
[ 784.644000] usb 1-3: USB disconnect, address 4
[ 785.392000] usb 1-3: new full speed USB device using ohci_hcd and address 5
[ 785.604000] usb 1-3: configuration #1 chosen from 1 choice
[ 785.612000] input: Synaptics Inc. Synaptics cPad as /class/input/input10
[ 785.612000] input: USB HID v1.00 Mouse [Synaptics Inc. Synaptics cPad] on usb-0000:02:06.0-3

[Pascal De Vuyst (pascal-devuyst)]

Thanks for your bug report.
Please provide the minimal information as described here: https://wiki.ubuntu.com/KernelTeamBugPolicies.

[VousDeux (launchpad-blahdot)]

Hello:

The problem described in this bug report seems to be an exact match for the problem I have been experiencing. I am running Gutsy on an MSI MS-1719 notebook.

My problem is that my touch pad seems to work, but I cannot adjust it, or disable it. It is way too sensitive, so I am constantly bumping it while trying to type. When I try to adjust it, I get the errors about shared memory being inaccessible.

I have also tried loading the xfree86 version of the synaptics driver, but the Xorg.0.log would not find this driver even though I had created a symlink. My guess is that it didn't like the fact that the Xorg driver ends with '.so', and the xfree86 driver ends with '.o', but I'm no expert for sure.

In addition to the files listed in the KernelTeamBugPolicies, I have attached output from 'cat /proc/bus/input/devices', Xorg.0.log, and xorg.conf. The logs seem to indicate that the device could not be detected, so the driver was unloaded.

Thanks

[kaffeeringe (kontakt-kaffeeringe)]

I also have the Toshiba 5200-903 and cpad fails to work. Without the drivers the touchpad basically works - it's only very badly configured (like the standard settings in Windows too) So I hoped to change this with the proper drivers.

[Wolf Rogner (war-rsb)]

This is ancient. Can we close it?

[VousDeux (launchpad-blahdot)]

Why would you think it is ancient with posts as recent as 10/6/07? The issue is obviously alive and well for some of us, and I'm sure we would all be very interested in resolving it.

Why is the bug still listed as incomplete? I have posted data that should have cerainly completed it. If it is indeed incomplete, I would be happy to complete it if someone would be kind enough to let me know what is missing.

[sysitos (sysitos)]

Can't check the situation for Toshiba anymore, because I changed to another vendor, and there is the touchpad working with Kubuntu. So feel free to close the case, but it seems that other users have the same problem as I had, so a good solution would be to check it again. Thanks.

[Wolf Rogner (war-rsb)]

VousDeux: Do you still experience the issue?

We have 8.04 now and none of my machines has trouble working with Syaptics any more.

Please confirm as it is helpful to the developers to keep a clear view on open issues, Thanks.

[sysitos (sysitos)]

As I already wrote, I can't verify anymore this bug, because of hardware change. So fell free to close the case.

[VousDeux (launchpad-blahdot)]

Hello:

Thanks for asking. I didn't even know anyone was even paying any attention to this issue.

I have installed 8.04, but was unable to install ksynaptics (Adept doesn't even acknowledge that I requested the install). While the touch pad does not appear under the Keyboard & Mouse settings, I did find the following entry in the Xorg.0.log that suggests a driver was loaded:

(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
 compiled for 4.3.99.902, module version = 1.0.0
 Module class: X.Org XInput Driver
 ABI class: X.Org XInput driver, version 2.0

I have also since installed KDE4, but I still cannot install ksynaptics, and the touchpad still does not appear in the Keyboard & Mouse settings. I guess I don't know for sure how to answer the question because I don't have any tools with which to attempt to configure it.

Please forgive my ignorance, but I still don't know how to adjust the settings. And, since it has been so long since I tried to figure this out before, I remember pretty much nothing about how I was able troubleshoot it before. I sure wish someone could have contacted me while it was fresh on my mind.

Thanks again,

Jerry

[VousDeux (launchpad-blahdot)]

Hello again:

I looked further down in that same Xorg.0.log and found the following entries:

(II) Synaptics touchpad driver version 0.14.6 (1406)
Synaptics Touchpad no synaptics event device found (checked 20 nodes)
(**) Option "Device" "/dev/psaux"
(**) Option "SHMConfig" "on"
(**) Option "HorizEdgeScroll" "0"
Query no Synaptics: 6003C8
(EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device
(EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics Touchpad"
(II) UnloadModule: "synaptics"

I guess this means that something still isn't right.

I don't know what to do with it.

Thanks,

Jerry

[VousDeux (launchpad-blahdot)]

I'm sorry for the spotty responses...I'm just trying to remember how I was troubleshooting before.

I just recalled that one of the commands I was using to test before was: synclient -l

When I execute this command I get this familiar response: "Can't access shared memory area. SHMConfig disabled?"

I do have SHMConfig set to "on" in the proper place within the xorg.conf. This has been verified repeatedly.

Thanks again,

Jerry

[VousDeux (launchpad-blahdot)]

One more FYI:

grep -ni shm /var/log/Xorg.0.log
494:(II) Initializing built-in extension MIT-SHM
538:(**) Option "SHMConfig" "on"

[sloan1919 (raydwhite)]

I'm still having this same issue.

Here is the relative information:
xorg.conf:

Section "InputDevice"
        Identifier "Synaptics Touchpad"
        Driver "synaptics"
        Option "SendCoreEvents" "true"
        Option "Device" "/dev/psaux"
        Option "Protocol" "auto-dev"
        Option "SHMConfig" "on"
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
        screen "Default Screen"
        Inputdevice "Synaptics Touchpad" "SendCoreEvents"
EndSection

XORG Log:
(II) Synaptics touchpad driver version 0.14.6 (1406)
Synaptics Touchpad no synaptics event device found (checked 21 nodes)
(**) Option "Device" "/dev/psaux"
(**) Option "SHMConfig" "on"
Query no Synaptics: 6003C8
(EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device
(EE) Synaptics Touchpad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics Touchpad"
(II) UnloadModule: "synaptics"

#cat /proc/bus/input/devices :

I: Bus=0011 Vendor=0002 Product=0001 Version=7321
N: Name="PS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input10
U: Uniq=
H: Handlers=mouse3 event10
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

Its clearly related to the detection of device. Any ideas?

Sloan

[sloan1919 (raydwhite)]

Almost forgot

2.6.24-19-generic

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[hasi (whynot-nurfuerspam)]

I have this problem on Ibex alpha 5 (kubuntu).
I am using a new DELL Latitude E6400.
Synaptics not detected by X.

[hasi (whynot-nurfuerspam)]

Since this bug seems to combine several independent issues, I filed a bug for the problem on the DELL Latitude E6400. (https://bugs.launchpad.net/ubuntu/+bug/270643).

Notably, this problem still exists on the 2.6.27-3 kernel (Intrepid alpha5)

[Eli (eli-maes)]

Same thing on a latitude E6500, also on Intrepid alpha5, anyone got this working so far?

[sloan1919 (raydwhite)]

I have yet to find a fix that works. Interesting thing with my Alps touchpad is maybe once out of 50 reboots it will detect it properly as a synpatics pad and everything works like a charm. I have tried to figure out what is happening differently on that reboot than with the others and I can't find anything different. Its seems that if we could make it so that we force it to be recognized as a synpatics pad, that would at least temporarily solve the problem until we can figure out what the heck is going on with these things.

[hasi (whynot-nurfuerspam)]

@sloan1919:

In your "/proc/bus/input/devices" output shown above, the ALPS is present. Is that what happens every time or every 50 times?

In my case (Dell E6400), I never saw it appear in "/proc/bus/input/devices". However, if there is a small chance that it gets recognized, I could automatically grep for it on startup and do further research when it is detected correctly.

Also, are you still on 2.6.24?

[mehturt (mehturt)]

Having the same problem on Dell Latitude D630

[sloan1919 (raydwhite)]

hasi:
If it says ALPS there is a chance that X might detect it correctly. Today it says

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse2 event9
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

Its just a crap shoot I guess. lol

[strk (strk)]

Same problem on Asus W7J laptop.

X:
 Synaptics Touchpad no synaptics event touchpad found (checked 19 nodes)
 Query no Synaptics: 6003C8
 (EE) Synaptics Touchpad no synaptics touchpad detected and no repeater device

tpconfig:
 Found Synaptics Touchpad.
 Firmware: 8.96 (multiple-byte mode).

/proc/bus/input/devices contains *NO* "synaptics" label, the only entry with "mouse" label is:
 I: Bus=0017 Vendor=0001 Product=0001 Version=0100
 N: Name="Macintosh mouse button emulation"
 P: Phys=
 S: Sysfs=/devices/virtual/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

This is a fresh install of Ubuntu 8.04.1 (from alternate disk).
It used to work on the same machine before a disk crash forced me to reinstall,
and it was at 8.04 already (dist-upgraded w/out major problems).

[Mariusz Domański (mario.7)]

Try to reload psmouse module:
sudo rmmod psmouse && sudo modprobe psmouse

and restart Xserver.

[William Grant (wgrant)]

Can people please try with the Intrepid beta? If it doesn't work there, please attach /var/log/Xorg.0.log and the output of lshal.

[sloan1919 (raydwhite)]

What is the easiest way to upgrade to Intrepid beta. Can someone link me to a step by step. Thanks.

Sloan

[William Grant (wgrant)]

See https://help.ubuntu.com/community/IntrepidUpgrades.

[William Grant (wgrant)]

This is probably a kernel bug, and needs testing on 8.10.

[Leann Ogasawara (leannogasawara)]

Just curious if anyone who had this issue was able to test the latest Jaunty 9.04 release yet and confirm if this issue remains? Please let us know. Thanks.

http://www.ubuntu.com/getubuntu/download

[Peter Matulis (petermatulis)]

Hi Leann, I have a support case involving this problem. They are running 8.04. Shall I have them test with a 9.04 live CD? We just want to turn the touchpad off. Is there no other way?

[Maciek (msakrejda)]

I'm pretty sure I'm hitting the same bug on a different laptop model. I'm attaching the files requested in the DebuggingTouchpadDetection wikki page. This is on Jaunty, and my touchpad does not work at all.

[Leann Ogasawara (leannogasawara)]

@Maciek,

Care to open a new bug report as you have a different set of hardware and it also seems you are experiencing a slightly different bug where your touchpad does not work at all whereas the original bug reporter noted, "touchpad only works as normal mouse". We can easily mark bugs as duplicates later on if necessary but it is initially more helpful to have bugs target a specific issue against a specific set of hardware. Thanks.

Having not heard back from @sysitos, the original bug reporter, I'm closing this bug for now. sysitos, please reopen if you can confirm this issue remains in the latest Jaunty release. If anyone else is still experiencing issues, please open a new report. Thanks.