Samsung QX410-J01 touchpad not recognized as Elantech

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Please download the package from the following link:

  http://people.canonical.com/~sforshee/psmouse-elantech-debug/v0.1/psmouse-elantech-debug-dkms_0.1_all.deb

After downloading, you can install it either by double-clicking on the downloaded file or else by opening a terminal and running 'sudo dpkg -i psmouse-elantech-debug-dkms_0.1_all.deb' from the directory where you downloaded the file. This will install a new version of the mouse driver with extra debug information enabled. To begin using the new driver you need to run 'sudo modprobe -r psmouse; sudo modprobe psmouse' in a terminal. It will also be used automatically when you reboot the computer, so you can just reboot if you prefer.

After loading the driver or rebooting, please run 'dmesg > dmesg.txt' in a terminal, and attach dmesg.txt to this bug. Thanks!

Seth, attached is the result of the dmesg after installing the deb package.

Joseph, I will try the upstream shortly

Craig: I'm not seeing the data I expect. Did you reboot or run 'sudo modprobe -r psmouse; sudo modprobe psmouse' after installation? This is necessary to use the new driver. If you did one of those, can you run the following in a terminal to make sure that the following file exists?

  ls /lib/modules/$(uname -r)/updates/dkms/psmouse.ko

Also, something to note is that if you have the debug driver package installed when testing the mainline build it's going to use that driver in preference to the one in the mainline build. That's not what we want, so please uninstall the package prior to testing the mainline build.

Hi Seth,

I actually tried both for psmouse. First I tried the modprobe approach but didn't see any additional expected debug information in the dmesg. Then I rebooted, but still didn't see anything different, so I figured it was correct.

craig@craig-laptop:~$ ls /lib/modules/$(uname -r)/updates/dkms/psmouse.ko
/lib/modules/3.0.0-12-generic/updates/dkms/psmouse.ko
craig@craig-laptop:~$

craig@craig-laptop:~/Downloads$ sudo dpkg --dry-run -i psmouse-elantech-debug-dkms_0.1_all.deb
(Reading database ... 257970 files and directories currently installed.)
Preparing to replace psmouse-elantech-debug-dkms 0.1 (using psmouse-elantech-debug-dkms_0.1_all.deb) ...
craig@craig-laptop:~/Downloads$ # looks like it's installed

So far all I have done is try your debug build of psmouse. I have not done anything with mainline. Is there anything else I can try? I am still not seeing anything debug related for the mouse.

Craig: If you're not getting the messages, it probably means that some other model detection is matching on it prior to elantech (but possibly initialization is failing). Please try the driver below. I added more debug to the general mouse detection logic. Thanks!

http://people.canonical.com/~sforshee/psmouse-elantech-debug/v0.2/psmouse-elantech-debug-dkms_0.2_all.deb

Cool, there are some debug lines near the bottom. Hopefully they are of value

It looks like something must be happening earlier in the detection that causes it to skip elantech. I've put up another build with some different logging to help narrow this down further. Thanks for being so responsive with your testing!

http://people.canonical.com/~sforshee/psmouse-elantech-debug/v0.3/psmouse-elantech-debug-dkms_0.3_all.deb

Here ya go. And no problem! I'm just happy someone cares enough to help make this work!

Hi Seth,

I went through the code in the .deb file and I figured out what's going on. So the max_proto that's set is an enum value of 5, which is PSMOUSE_IMPS. Elantech won't even get checked unless it's higher than PSMOUSE_IMEX, which is 6.

So what I ended up doing is this:

$ sudo rmmod psmouse
$ sudo modprobe psmouse proto=any

And boom, it recognized as elantech. I've included the dmesg to show you. I can definitely set this option in the modprobe config for this module, but is that all I can do? Is there anything else that would set the max_proto for me automatically?

OMFG, now I'm pissed. I see that in the /etc/modprobe.d there is a fun little file named psmouse.conf. In that file is a special little line:

options psmouse proto=imps

I have no clue why it's there but that was the issue. I removed that file and elantech gets recognized by default.

Sorry to completely waste your time on this issue.

This is user error (mine). Please disregard this bug and accept my apologies for wasting your time.