Synaptics touchpad (no physical buttons) not responding. Installed xf86-input-synaptics-1.8.2-76.1.x86_64 but still not working. Not clear if any further configuration needed for this driver. Output from ‘synclient -l’ says “Couldn’t find synaptics properties. No synaptics driver loaded?”
It may be that no linux driver yet exists for this touchpad. Any help welcome.
You’ve probably answered your own question here 
Anyway, share the touchpad info
/usr/sbin/hwinfo --mouse
cat /proc/bus/input/devices
FWIW, I did turn up this Ubuntu thread discussing similar Novatech models
http://ubuntuforums.org/showthread.php?t=2214287
Maybe the boot parameter ‘i8042.noloop’ will work for this hardware too?
Hi. Thanks for quick response. Here’s the output requested:
peted@linux-sdu2:~> /usr/sbin/hwinfo --mouse
27: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: eqBD.fuAIdassRJF
Parent ID: uIhY.2DFUsyrieMD
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
SysFS BusID: 3-4:1.0
Hardware Class: mouse
Model: “USB Optical Mouse”
Hotplug: USB
Vendor: usb 0x192f
Device: usb 0x0916 “USB Optical Mouse”
Revision: “2.00”
Compatible to: int 0x0200 0x0001 “Generic USB Mouse”
Driver: “usbhid”
Driver Modules: “usbhid”
Speed: 1.5 Mbps
Module Alias: “usb:v192Fp0916d0200dc00dsc00dp00ic03isc01ip02in00”
Driver Info #0:
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #26 (Hub)
peted@linux-sdu2:~> cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name=“AT Translated Set 2 keyboard”
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name=“Lid Switch”
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
U: Uniq=
H: Handlers=event1
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name=“Sleep Button”
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=4000 0 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name=“Power Button”
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=192f Product=0916 Version=0111
N: Name=“USB Optical Mouse”
P: Phys=usb-0000:00:14.0-4/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/0003:192F:0916.0001/input/input4
U: Uniq=
H: Handlers=mouse0 event4
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=103
B: MSC=10
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name=“Video Bus”
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name=“PC Speaker”
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=04f2 Product=b3a3 Version=5465
N: Name=“USB2.0 HD UVC WebCam”
P: Phys=usb-0000:00:14.0-10/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/input/input7
U: Uniq=
H: Handlers=kbd event7
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=“HDA Intel HDMI HDMI/DP,pcm=3”
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=“HDA Intel HDMI HDMI/DP,pcm=7”
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input9
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=“HDA Intel HDMI HDMI/DP,pcm=8”
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input10
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=“HDA Intel PCH Mic”
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input11
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name=“HDA Intel PCH Headphone”
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input12
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=4
peted@linux-sdu2:~> /usr/sbin/hwinfo --touchpad
Usage: hwinfo [OPTIONS]
Probe for hardware.
Options:
–<HARDWARE_ITEM>
This option can be given more than once. Probe for a particular
HARDWARE_ITEM. Available hardware items are:
all, arch, bios, block, bluetooth, braille, bridge, camera,
cdrom, chipcard, cpu, disk, dsl, dvb, fingerprint, floppy,
framebuffer, gfxcard, hub, ide, isapnp, isdn, joystick, keyboard,
memory, modem, monitor, mouse, netcard, network, partition,
pci, pcmcia, pcmcia-ctrl, pppoe, printer, redasd,
reallyall, scanner, scsi, smp, sound, storage-ctrl, sys, tape,
tv, uml, usb, usb-ctrl, vbe, wlan, xen, zip
–short
Show only a summary. Use this option in addition to a hardware
probing option.
–listmd
Normally hwinfo does not report RAID devices. Add this option to
see them.
–only DEVNAME
This option can be given more than once. If you add this option,
only data about devices with DEVNAME will be shown.
–save-config SPEC
Store config for a particular device below /var/lib/hardware.
SPEC can be a device name, an UDI, or ‘all’. This option must be
given in addition to a hardware probing option.
–show-config UDI
Show saved config data for a particular device.
–map
If disk names have changed (e.g. after a kernel update) this
prints a list of disk name mappings. Note that you must have
used --save-config at some point before for this can work.
–debug N
Set debug level to N. The debug info is shown only in the log
file. If you specify a log file, the debug level is implicitly
set to a reasonable value.
–verbose
Increase verbosity. Only together with --map.
–log FILE
Write log info to FILE.
–dump-db N
Dump hardware data base. N is either 0 for the external data
base in /var/lib/hardware, or 1 for the internal data base.
–version
Print libhd version.
–help
Print usage.
peted@linux-sdu2:~> info update-grub
peted@linux-sdu2:~> man update-grub
No manual entry for update-grub
peted@linux-sdu2:~>
I’m using an external USB mouse at present and it’s giving problems. Wary about the i8042 parameter as some users have ended up with unbootable system after using it. Also, instructions in /etc/default/grub say to use “grub2-mkconfig -o /boot/grub2/grub.cfg” after the update (rather than update-grub) although they probably have the same effect.
Don’t add it permanent until you have tested it
At grub menu press e key for edit mode find line starting with linux go to end of line (it wraps) and enter the new parameter press F10 to boot. Next boot it will be gone
Thanks for the tip. Tried the boot with the i8042 parameter added but still no touchpad. There are newer versions of xf86-input-synaptics and xf86-input-evdev available in the tumbleweed repo so will try with these.
Hang on - Don’t mix packages from different versions or you will break your system. The output from hwinfo and /proc/bus/input/devices did not report your touchpad in any way. I would have expected even an unsupported device to be reported. It’s behaving as if it is disabled - any hardware switch of Fn key present for turning it off/on?
I thought that was odd too. I can’t see any hardware switch but I’ll double check on the documentation I have. It looks like SUSE is just not recognising the touchpad at all. Maybe that was the idea of i8042 parameter but it didn’t appear to work. I saw the suggestion to update the 2 drivers on another thread but I’ll hold back on that for now. The only other information I can find on this issue is on the synaptics site where it says they have created driver software called ‘Synaptics Gesture Suite for Linux (touchpads)’ (SGS-L) but they supply it only to ‘OEM partners’ (maybe Novatech don’t qualify as OEM partners).
It’s likely that a bug report will need to be submitted, since the kernel doesn’t appear to recognise it at all.
From this kernel parameters page, these are the i8042 parameters the might be of interest
i8042.debug [HW] Toggle i8042 debug mode
i8042.direct [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
keyboard and cannot control its state
(Don't attempt to blink the leds)
i8042.noaux [HW] Don't check for auxiliary (== mouse) port
i8042.nokbd [HW] Don't check/create keyboard port
i8042.noloop [HW] Disable the AUX Loopback command while probing
for the AUX port
i8042.nomux [HW] Don't check presence of an active multiplexing
controller
i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX
controllers
i8042.notimeout [HW] Ignore timeout condition signalled by controller
i8042.reset [HW] Reset the controller during init and cleanup
i8042.unlock [HW] Unlock (ignore) the keylock
i8042.kbdreset [HW] Reset device connected to KBD port
I have seen posts suggesting that i8042.nomux helps with getting some hardware detected. YMMV.
If at first you don’t succeed…
After looking at your kernel parameter page, I guessed I’d put the i8042.noloop in incorrectly. Tried again (correctly this time) and, hey presto, the touchpad activated (though some functions don’t appear to be working eg. right click).
Here’s the output from the /usr/sbin/hwinfo command after rebooting.
peted@linux-sdu2:~> /usr/sbin/hwinfo --mouse
27: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: eqBD.fuAIdassRJF
Parent ID: uIhY.2DFUsyrieMD
SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0
SysFS BusID: 3-4:1.0
Hardware Class: mouse
Model: “USB Optical Mouse”
Hotplug: USB
Vendor: usb 0x192f
Device: usb 0x0916 “USB Optical Mouse”
Revision: “2.00”
Compatible to: int 0x0200 0x0001 “Generic USB Mouse”
Driver: “usbhid”
Driver Modules: “usbhid”
Speed: 1.5 Mbps
Module Alias: “usb:v192Fp0916d0200dc00dsc00dp00ic03isc01ip02in00”
Driver Info #0:
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #26 (Hub)
36: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.249]
Unique ID: AH6Q.Y_f5kDtfqz2
Hardware Class: mouse
Model: “SynPS/2 Synaptics TouchPad”
Vendor: 0x0002
Device: 0x0007 “SynPS/2 Synaptics TouchPad”
Compatible to: int 0x0210 0x0001
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event1, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
Device Number: char 13:63 (char 13:32)
Driver Info #0:
Buttons: 1
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
peted@linux-sdu2:~>
Thanks for your help. I’ll update this thread when I get all the touchpad functions working properly.
That’s great news and could be of help to others who have similar hardware and come searching.
Thanks for your help. I’ll update this thread when I get all the touchpad functions working properly.
I look forward to reading about your progress with this.
Some good documentation on touchpad configuration here:
https://wiki.archlinux.org/index.php/Touchpad_Synaptics
https://help.ubuntu.com/community/SynapticsTouchpad
After reading instructions from various sites around the web plus the ‘man synaptics’ pages I was able to figure out the basics for the clickpad configuration. Probably the fullest description of the configuration parameters I could find was on personal.tctwest.net/~mlewis00/XF86Config-4.synaptics
If you haven’t used a clickpad before then it helps to know the difference between a tap and a click. In the end I found the default set-up was ok for now.
Thanks for the update. Yes, the man page for synaptics has a section dealing with ClickPad support and the ‘SoftButtonAreas’ option used to customise tocuhpad area with respect to various button emulations.