[SOLVED] Alps touchpad not recognized

lupe · 09-10-2014, 01:46 PM

Hi,

Recently I got a new fujitsu-siemens notebook and cannot get the touchpad to work. No mouse movements, no response to buttons either.

From `dmesg`:
psmouse serio1: alps: Unknown ALPS touchpad: E7=73 03 c8, EC=73 04 13

I upgraded from Slackware64-14.1 to current but the problem persists.

There's some work done to get Alps touchpads to work in Dells like https://github.com/emmanuelthome/psmouse-alps. Tried to follow it, but couldn't compile the psmouse-alps package from http://www.dahetral.com/public-downl...2-and-3-5/view

# xinput --list
â â³ ImPS/2 Generic Wheel Mouse id=14 [slave pointer (2)]

xinput seems to detect it as a generic mouse.

So, what can I do?
Force somehow some alps driver in xorg.conf?
Include the E7=73 03 c8, EC=73 04 13 code somewhere in the kernel and compile it again?
Is this a bug?

allend · 09-11-2014, 08:09 AM

Have you tried adding the kernel boot options ' i8042.notimeout i8042.nomux' ?
(This can be done at boot by hitting TAB at the lilo boot screen. If successful, add the options to the the 'append=' line in your /etc/lilo.conf and then rerun lilo to make this permanent.)
http://forums.fedoraforum.org/showthread.php?t=299787
https://bbs.archlinux.org/viewtopic.php?pid=1189603

lupe · 10-02-2014, 08:38 AM

A line as:
append = "i8042.notimeout i8042.nomux"

in lilo.conf solved the issue.

Thanks allend!

allend · 10-02-2014, 09:09 AM

Glad you got it working.
Thanks for reporting back, as this may help someone else.

pbneves · 10-03-2014, 12:44 PM

I've already tried this solution putting that in the beggining of lilo.conf without success

Then occurred to me that i have a initrd to enable hibernation and because of that i had also a line with append="resume /dev/sda7" after the suggested line, and it was probably been overwritten by the second one.
So updating the line in the section of the custom initrd to append = "resume=/dev/sda7 i8042.notimeout i8042.nomux" solved the problem.

onebuck · 10-03-2014, 02:00 PM

Hi,

In the /etc/lilo.conf you can use 'addappend=' within the stanza you wish to boot. This will not overwrite the 'append=' in the global section.
From 'man lilo.conf';

Quote:

KERNEL OPTIONS (image=)
If the booted image is a Linux kernel, then one may pass command line parameters to this kernel.

addappend=<string>
(22.6) The kernel parameters from the specified string, are concatenated to the parameter(s) from an append= specification (see below). The
string must be enclosed within double quotes. Usually, the previous append= will specify parameters common to all kernels by appearing in the
top, or global, section of the configuration file and addappend= will be used to add local parameter(s) to an individual image. Addappend=
may be used only once per "image=" section.

append=<string>
Appends the options specified to the parameter line passed to the kernel. This is typically used to specify hardware parameters that can't be
entirely auto-detected or for which probing may be dangerous. Multiple kernel parameters are separated by a blank space, and the string must
be enclosed in double quotes. A local append= appearing withing an image= section overrides any global append= appearing in the top section
of the configuration file. Append= may be used only once per "image=" section. To concatenate parameter strings, use "addappend=". Example:

append="mem=96M hd=576,64,32 console=ttyS1,9600"

Hope this helps.
Have fun & enjoy!