Track pad not detected - Acer ES1-511

Bug #1449782 reported by Jim Kulakowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Computer Model: Acer ES1-511-C0DV
Touchpad Manufacturer: Synaptics

Scenario
-------------
I recently acquired a used Acer ES1-511, which came installed with Windows 7. I planned to only use the laptop with a Linux distro.

Initially, I installed The latest Ubuntu distro (32-Bit) in parallel with Windows 7. Upon testing the environment from a USB install drive, I used Ubuntu's partitioner to shrink the Windows 7 partition significantly. The trackpad was working fine and I went ahead with the install. Everything was great.

When I realized that I had installed the 32-Bit version and that my system was easily capable of running the 64-Bit version, I decided to re-install the 64-Bit OS.

In the testing scenario, everything was fine. I wet ahead with the install, but this time, I decided to just overwrite the entire system and erase Windows 7 completely. I decided that I would only use Ubuntu. When install was complete, I restarted the computer and that's when the issue began.

On reboot, The trackpad did not respond. I tried a number fixes that I found in the forums, but when I search in terminal under lspci and a number of other commands, the trackpad does not exist on any list. There isn't even and unknown device.

Concerned that it may be an Ubunut 64-Bit issue, I decided to try a different distro - Elementary OS. Unfortunately, I'm still having the issue. I can control everything with a USB mouse, but the trackpad is still unresponsive.

Any help would be greatly appreciated. Thanks!
---
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: jmkulakowski 1294 F...m pulseaudio
 /dev/snd/controlC0: jmkulakowski 1294 F.... pulseaudio
CurrentDesktop: Pantheon
DistroRelease: elementary OS 0.3
HibernationDevice: RESUME=UUID=7cc48182-087f-4f5e-8d18-856a6775d8e4
InstallationDate: Installed on 2015-04-29 (0 days ago)
InstallationMedia: elementary OS 0.3 "Freya" - Stable amd64 (20150411)
MachineType: Acer Aspire ES1-511
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic root=UUID=daac24db-1fe0-41a5-be63-c5ea845bec43 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic N/A
 linux-firmware 1.127.11
Tags: freya
Uname: Linux 3.16.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/14/2014
dmi.bios.vendor: Acer
dmi.bios.version: V1.02
dmi.board.name: Aspire ES1-511
dmi.board.vendor: Acer
dmi.board.version: V1.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrV1.02:bd04/14/2014:svnAcer:pnAspireES1-511:pvrV1.02:rvnAcer:rnAspireES1-511:rvrV1.02:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire ES1-511
dmi.product.version: V1.02
dmi.sys.vendor: Acer

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1449782

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected freya
description: updated
Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : BootDmesg.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : CRDA.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : IwConfig.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : Lspci.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : Lsusb.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : ProcModules.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : PulseList.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : RfKill.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : UdevDb.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : UdevLog.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote :

I've updated the reports

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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/v4.1-rc1-vivid/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jim Kulakowski (jmkulakowski) wrote :

I'm happy to try and test the upstream kernel, but I'm having a bit of trouble understanding how to do so. I've read through the instructions here: https://wiki.ubuntu.com/KernelMainlineBuilds but I'm not sure how to obtain the correct files. Is there a link to download the latest build or do I have to copy and paste the text from each file?

I also want to make sure I'm grabbing the right build. Is this the one?:
  v4.1-rc1-vivid/

Once I have the files, I know I'm supposed to run the following command:
  sudo dpkg -i *.deb

...but how do I point it to the right package? Do I have to create a .deb file? I could use some assistance for sure.

Thanks,
Jim

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote :

Thank you so much for your help! I actually ended up reinstalling the latest stable version (14.04) and the issue is resolved. I'll go ahead and mark it as such.

Thanks again!

Jim

Revision history for this message
Jim Kulakowski (jmkulakowski) wrote :

The issue was resolved with a reinstall of the latest stable version (14.04)

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.