[Aspire S7-392] Touchpad reported as: "elantech: unknown hardware version, aborting"

Bug #1232877 reported by clayton craft
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Only basic functionality (right/left click, moving pointer) work. Expectation is that the device would be detected as a touchpad with support for multitouch/scrolling/etc. The laptop is an Acer S7 392. Please let me know if I can provide more information to help!

$ lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

$ uname -a
Linux ultrabook 3.11.0-9-generic #16-Ubuntu SMP Fri Sep 27 15:08:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-9-generic 3.11.0-9.16
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: craftyguy 2497 F.... pulseaudio
 /dev/snd/controlC0: craftyguy 2497 F.... pulseaudio
Date: Sun Sep 29 12:17:48 2013
HibernationDevice: RESUME=UUID=43274a69-d023-452a-9f3a-70c188b4405b
InstallationDate: Installed on 2013-09-28 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer Aspire S7-392
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-9-generic N/A
 linux-backports-modules-3.11.0-9-generic N/A
 linux-firmware 1.114
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.03
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Storm2
dmi.board.vendor: Acer
dmi.board.version: V2.03
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.03
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.03:bd06/07/2013:svnAcer:pnAspireS7-392:pvrV2.03:rvnAcer:rnStorm2:rvrV2.03:cvnAcer:ct10:cvrV2.03:
dmi.product.name: Aspire S7-392
dmi.product.version: V2.03
dmi.sys.vendor: Acer

Revision history for this message
clayton craft (craftyguy) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Touchpad reported as: "elantech: unknown hardware version, aborting"

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc3-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
clayton craft (craftyguy) wrote :

Confirmed in upstream:

clayton@ultrabook:~$ dmesg|grep -i elan
[ 7.263829] usb 2-7: Manufacturer: ELAN
[ 17.900924] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/input/input6
[ 17.901119] hid-multitouch 0003:04F3:015B.0001: input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-7/input0
[ 18.453420] psmouse serio1: elantech: unknown hardware version, aborting...
[ 18.659623] input: PS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input14
clayton@ultrabook:~$ uname -a
Linux ultrabook 3.12.0-031200rc3-generic #201309291835 SMP Sun Sep 29 22:37:02 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
clayton craft (craftyguy) wrote :

I have reported the bug to my best guess for maintainers ( <email address hidden>), and as of right now I have not heard back yet.

tags: added: kernel-bug-reported-upstream
Revision history for this message
kendatsuba (kendatsuba) wrote :

Unfortunately, even if the driver complains of an unknown hardware version, the firmware version of the touchpad is not mentioned in the emitted error message:

[ 18.453420] psmouse serio1: elantech: unknown hardware version, aborting...

The module contained in the attached dkms package should print the firmware version along with the error message. By knowing the firmware version, it will be possible to force the recognition of the touchpad and see if the structure of the packets is the same used by one of the already supported firmwares.

Here are the steps you must follow:

sudo dkms ldtarball psmouse-elantech-show-version.tar.gz
sudo dkms install -m psmouse -v elantech-show-version

sudo rmmod psmouse
sudo modprobe psmouse

and post the output of the following command:

dmesg | grep elantech

When you're done don't forget to remove the module:

sudo dkms remove -m psmouse -v elantech-show-version --all

Revision history for this message
clayton craft (craftyguy) wrote :

Here's the output after building/loading that module:

clayton@ultrabook:~/Downloads$ dmesg|grep elantech
[ 15.277239] psmouse serio1: elantech: unknown hardware version, aborting...
[ 425.625027] psmouse serio1: elantech: unknown hardware version, aborting...
[ 1214.662773] psmouse serio1: elantech: unknown hardware version, aborting...
[ 1365.084133] psmouse serio1: elantech: unknown hardware version 0x581f01, aborting...

Revision history for this message
clayton craft (craftyguy) wrote :
Download full text (3.8 KiB)

I've made some (hopefully) interesting progress:

The firmware version seems to be 8, using the formula in the elantech_set_properties function, so I modified the file like this to force it to set hw_version to 4:

clayton@ultrabook:~/Downloads$ diff -Naur psmouse-old/dkms_source_tree/src/elantech.c psmouse/dkms_source_tree/src/elantech.c
--- psmouse-old/dkms_source_tree/src/elantech.c 2013-10-03 16:09:47.000000000 -0700
+++ psmouse/dkms_source_tree/src/elantech.c 2013-10-03 18:39:11.032740195 -0700
@@ -1315,6 +1315,9 @@
   case 7:
    etd->hw_version = 4;
    break;
+ case 8:
+ etd->hw_version = 4;
+ break;
   default:
    return -1;
   }

Loaded the module:

clayton@ultrabook:~/Downloads$ dmesg|grep elan
[ 15.277239] psmouse serio1: elantech: unknown hardware version, aborting...
[ 425.625027] psmouse serio1: elantech: unknown hardware version, aborting...
[ 1214.662773] psmouse serio1: elantech: unknown hardware version, aborting...
[ 1365.084133] psmouse serio1: elantech: unknown hardware version 0x581f01, aborting...
[ 1529.552056] psmouse serio1: elantech: unknown hardware version, aborting...
[ 2669.112462] psmouse serio1: elantech: unknown hardware version 0x581f01, aborting...
[ 3124.034920] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x581f01)
[ 3124.053875] psmouse serio1: elantech: Synaptics capabilities query result 0x50, 0x17, 0x0d.

And now getting some response from synclient:

clayton@ultrabook:~/Downloads/psmouse$ synclient
Parameter settings:
    LeftEdge = 130
    RightEdge = 3126
    TopEdge = 95
    BottomEdge = 1681
    FingerLow = 1
    FingerHigh = 1
    MaxTapTime = 180
    MaxTapMove = 163
    MaxDoubleTapTime = 180
    SingleTapTimeout = 180
    ClickTime = 100
    EmulateMidButtonTime = 0
    EmulateTwoFingerMinZ = 282
    EmulateTwoFingerMinW = 7
    VertScrollDelta = 74
    HorizScrollDelta = 74
    VertEdgeScroll = 0
    HorizEdgeScroll = 0
    CornerCoasting = 0
    VertTwoFingerScroll = 1
    HorizTwoFingerScroll = 1
    MinSpeed = 1
    MaxSpeed = 1.75
    AccelFactor = 0.0539374
    TouchpadOff = 0
    LockedDrags = 0
    LockedDragTimeout = 5000
    RTCornerButton = 2
    RBCornerButton = 3
    LTCornerButton = 0
    LBCornerButton = 0
    TapButton1 = 1
    TapButton2 = 3
    TapButton3 = 0
    ClickFinger1 = 1
    ClickFinger2 = 3
    ClickFinger3 = 0
    CircularScrolling = 0
    CircScrollDelta = 0.1
    CircScrollTrigger = 0
    PalmDetect = 0
    PalmMinWidth = 10
    PalmMinZ = 200
    CoastingSpeed = 20
    CoastingFriction = 50
    PressureMotionMinZ = 30
    PressureMotionMaxZ = 160
    PressureMotionMinFactor = 1
    PressureMotionMaxFactor = 1
    ResolutionDetect = 1
    GrabEventDevice ...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

craftyguy, as per http://us.acer.com/ac/en/US/content/drivers an update is available for your BIOS (2.05). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
clayton craft (craftyguy) wrote :

I would love to be able to update my BIOS, however Acer's flash tool only supports Windows. The BIOS appears to be based on Insyde EFI, and I was able to extract a .fd file, however I wasn't able to find a utility to actually flash it (from freedos or ??). Do you, or anyone here, know of a way to update this?

Revision history for this message
kendatsuba (kendatsuba) wrote :

Maybe I'm wrong but I don't think that a BIOS update will change anything, since this problem appears to be related to a new firmware version not yet supported by the driver.

craftguy, could you please report if your patch solved the problem? does the touchpad work as expected with hw_version = 4? In that case we can forward the patch to the subsystem maintainers.

Revision history for this message
clayton craft (craftyguy) wrote :

I did, here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232877/comments/9

As far as I can tell, everything seems to be working properly

Revision history for this message
penalvch (penalvch) wrote :

kendatsuba, regarding your comments :
>"Maybe I'm wrong but I don't think that a BIOS update will change anything, since this problem appears to be related to a new firmware version not yet supported by the driver."

As you may have noticed in https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette , one would not want to presume what a BIOS update will or won't change, as they are a black box generally not tested to linux, and specifically Ubuntu. As well, hardware maintainers have already made clear bugs reported with outdated and/or buggy BIOS would need to be updated first before considered valid.

Revision history for this message
Matthew Walker (matt-g-d-walker) wrote :

Here is a I made patch that fixes this. I have submitted it upstream. A BIOS update is unnessesary. I have tested it and it works, I would appreciate other people trying it though.

Revision history for this message
clayton craft (craftyguy) wrote :

Unfortunately I killed my system when trying to apply a BIOS update to check another bug I reported, so I'm not able to confirm your patch (though I don't see any reason why that patch wouldn't work..)

tags: added: patch
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for submitting the patch upstream, Matthew. Did you submit the patch to LKML or one of the sub-system mailing lists? It would be great if you could post the SHA1 for the commit when it is accepted into mainline. Trusty will pickup the patch when it is rebased to upstream. Saucy and other earlier releases would get your patch from the stable updates if you cc'd the patch to <email address hidden>.

Revision history for this message
Daniel (skorka-b) wrote :

Same isssue on an Sony SVF13N1L2ES, bios R0220VA. Standard kernel for 13.10 (3.11.0-14-generic) and latest mainline kernel (3.13.0-031300rc5-generic) say:
psmouse serio1: elantech: unknown hardware version, aborting...

Using module from comment #7 gives:
psmouse serio1: elantech: unknown hardware version 0x595f02, aborting...

which works out to version 9 in the drivers logic.
I did not try forcing recognition as hardware version 4, as I'm a little worried of inflicting damage.

Revision history for this message
penalvch (penalvch) wrote :

Daniel, thank you for your comment. So your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

summary: - Touchpad reported as: "elantech: unknown hardware version, aborting"
+ [Aspire S7-392] Touchpad reported as: "elantech: unknown hardware
+ version, aborting"
tags: added: bios-outdated-2.05
Revision history for this message
penalvch (penalvch) wrote :

craftyguy, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232877/comments/16 regarding the hardware is now broken. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Matthew Walker, thank you for submitting your patch upstream. Given this is submitted as per http://www.spinics.net/lists/linux-input/msg28488.html the discussion may continue and be tracked on the linux-input mailing list for inclusion into linux-stable.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Invalid
Revision history for this message
cosmin (wizardelo) wrote :

hello,

i have same issue with multi-touch elantech touchpad. hardware unrecognized
i have used the show-version module to check it up but im not sure how to read what hardware version is
any help please?

radu@radu-Lenovo-Z710:/usr/src$ dmesg | grep elantech
[ 254.222645] psmouse serio1: elantech: unknown hardware version, aborting...
[ 254.946217] psmouse serio1: elantech: unknown hardware version, aborting...
[ 1195.141242] psmouse serio1: elantech: unknown hardware version 0x595f03, aborting...

Revision history for this message
kendatsuba (kendatsuba) wrote :

@cosmin, I think this bug is closed/invalid, anyway your hardware version seems to be 9 so please refer to:

https://bugs.launchpad.net/bugs/1166442

comment #137, for a possibly working solution

Revision history for this message
penalvch (penalvch) wrote :

cosmin, thank you for your comment. As this bug report is closed Invalid, and you are not the original reporter, it is not focused on your problem or hardware. If you have a bug in Ubuntu, please feel free to file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will prevent your problem from being addressed.

Thank you for your understanding.

Revision history for this message
Eus (eus-member) wrote :

I have a system that matches the original reporter's system except for the machine's manufacturer that in my case is ASUS, for the Elantech's complete hardware string that in my case is 0x381f00, and for the kernel version that in my case is 3.11.0-22-generic.

I confirm that Matthew Walker's patch in comment #15 works fine.

Revision history for this message
Eus (eus-member) wrote :

I confirm that the problem exists in Saucy and that Matthew Walker's fix works.

Changed in linux (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Eus, thank you for your comment. As this bug report is closed Invalid, and you are not the original reporter, it is not focused on your problem or hardware. If you have a bug in Ubuntu, please feel free to file a new report by executing the following in a terminal:
ubuntu-bug xorg

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will prevent your problem from being addressed.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.