Erratic touchpad (can be fixed by adding "i8042.nomux=1" in kernel cmdline)

Bug #585699 reported by YannUbuntu
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Bug: after several minutes, the cursor (touchpad, but I think it happened also with mouse) can get erratic move, and the clicks are disabled.

Concerns: Ubuntu 8.10 until Ubuntu 10.04 (I think I did not have this bug on Ubuntu 7.10 nor 8.04). On live-cd and installation on hard disk. My pc is a NEC LL550/H.

Workaround used since Ubuntu 8.10 : I add "i8042.nomux=1" in kernel cmdline.

Efficiency of this workaround : nearly perfect (I still sometimes have disabled clicks, like today, but it occured maybe 2 times in 2 years)

Other: I wonder if I should also add "i8042.reset=1" in kernel cmdline (seen on other similar bug reports), how can I test its efficiency ? what are the meanings/effects of "i8042.nomux=1" and "i8042.reset=1" ?

Best regards.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yyy 2688 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0000000 irq 16'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,10338802,00100002 HDA:11c13026,1033880b,00100700'
   Controls : 19
   Simple ctrls : 13
CheckboxSubmission: 7bf4676ac92338d1d362954586c33b04
CheckboxSystem: bd9978d0ff03d4f55482fc24a6cdac35
Date: Wed May 26 13:33:50 2010
HibernationDevice: RESUME=UUID=def8769f-2a4a-43b5-b9d9-c27f7234ac7d
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100328)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: NEC PC-LL550HG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=b3f9b3f2-a0c7-49c1-ae50-f849a02fd52e ro quiet splash i8042.nomux=1
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 01/06/2007
dmi.bios.vendor: NEC
dmi.bios.version: NOTE BIOS Version /524A0402
dmi.board.name: HAL50
dmi.board.vendor: NEC
dmi.board.version: 20C2B
dmi.chassis.type: 10
dmi.chassis.vendor: NEC
dmi.modalias: dmi:bvnNEC:bvrNOTEBIOSVersion/524A0402:bd01/06/2007:svnNEC:pnPC-LL550HG:pvr:rvnNEC:rnHAL50:rvr20C2B:cvnNEC:ct10:cvr:
dmi.product.name: PC-LL550HG
dmi.sys.vendor: NEC

Revision history for this message
YannUbuntu (yannubuntu) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi YannUbuntu,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
YannUbuntu (yannubuntu) wrote :

@Jeremy: which version of kernel would you prefer me to test? (v2.6.32.11-lucid/ ? v2.6.34-lucid/ ? daily ? ).
Then, which DEB do I have to install? (i think linux-headers-..i386 + linux-headers-..all + linux-image-...i386 , please confirm)

is there a risk for my data or hardware ?
(according to /usr/bin/jockey-gtk, I don't use any proprietary driver)

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
YannUbuntu (yannubuntu)
Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
YannUbuntu (yannubuntu) wrote :

I need an answer to this question : which DEB do I have to install?
is it ok to install the 2 DEB from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ ?

Revision history for this message
YannUbuntu (yannubuntu) wrote :

I installed today's kernel (linux-headers-2.6.36-999-generic_2.6.36-999.201008241121) and tested it without i8042.nomux=1. I reproduced the bug 3 times in 3 hours. (while moving the touchpad, the cursor disappears and quickly reappears in another place of the screen).

tags: removed: needs-upstream-testing
Revision history for this message
YannUbuntu (yannubuntu) wrote :

I removed the "i8042.nomux=1" (and continued using 2.6.36-999 kernel), and had no bug any more with the touchpad.

FYI, I had a big crash while using this new kernel with Nomux (https://bugzilla.kernel.org/show_bug.cgi?id=17091), do you think it is related to Nomux ?

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

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