touchpad not detected by kernel in hardy heron

Bug #196808 reported by NJ
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Stefan Bader

Bug Description

Binary package hint: linux-image-2.6.24-10-generic

As Per this post: http://ubuntuforums.org/showthread.php?t=700390

In the latest hardy heron the Touchpad on my laptop doesn't seem to be getting detected by the kernel (newest or previous w/ full apt-get update + apt-get dist-upgrade done just before this post) and thus doesn't work at all in Xorg.

uname -a
Linux discostu 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux

discostu@discostu:~$ dmesg | egrep -i 'input|touch|track'
[ 23.523263] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 23.543112] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 26.933390] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.0/input/input2
[ 26.959136] input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.0-1
[ 36.410198] input: PC Speaker as /devices/platform/pcspkr/input/input3

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi NJ,

Just curious what happens if you do:

sudo rmmod psmouse
sudo modprobe psmouse

Care to attach your dmesg output after having done this?

Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Still doesn't work. Already had tried that. Dmesg attached.

Revision history for this message
DFreeze (dfreeze) wrote :

Could it be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195009

I too have no touchpad at all...

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Yeah think it might be. Commented on your thread too

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi NJ,

I'm going to go ahead and mark this as a duplicate of bug 195009 for now. We can easily undup it later if necessary. If you can, please follow up with any further comments at bug 195009. Thanks!

Revision history for this message
Stefan Bader (smb) wrote :

Hi NJ, I unduped this since I wanted to close the other one, which was resolved for the original reporter and got a bit long anyway. To summarize what I took from the other bug:
- your touchpad is not detected by the kernel in any way (that mouse that shows up is a external USB one)
- i8042.noloop=1 doesn't help you

Can you try to boot with "i8042.debug=1" and post the dmesg of that run (more usefull if this catches the beginning of the i8042 messages). At least with a detected touchpad this is hard, since that gets a bit noisy.

Changed in linux:
assignee: nobody → stefan-bader-canonical
Revision history for this message
Pablo López Martín (mr-bible2001) wrote :

same problem here on a Toshiba Satellite Pro M10 laptop with alps touchpad. Kernel doesn't recognize the touchpad, only as a PS/2 Generic Mouse.

Revision history for this message
Pablo López Martín (mr-bible2001) wrote :
Revision history for this message
Pablo López Martín (mr-bible2001) wrote :

i8042.noloop=1 or i8042.nomux at boot time don't work either.

Revision history for this message
Pablo López Martín (mr-bible2001) wrote :

I opened bug in upstream and it got fixed, at least for Toshiba Satellite Pro M10 Alps Touchpad. The problem was that the signature for that particular Touchpad was not recognized. Attaching patch for kernel 2.6.29.1. Check http://bugzilla.kernel.org/show_bug.cgi?id=13134 for more info.

Regards,

Pablo

P.S.: Depending on your touchpad's signature you might to need it added into alps.c with a patch

Revision history for this message
Stefan Bader (smb) wrote :

I case NJ's touchpad is in the same laptop, I placed kernels containing Pablo's fix to http://people.ubuntu.com/~smb/bug196808/

@NJ: can you test one of those and give feedback whether it fixes your case as well? If not can you provide your dmesg when booting with "i8042.debug=1"?

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Whoa we're still going on this?!
Alrighty I'll try it tonight.
So just download the .deb and install? I'll add itself to grub etc (and will leave other kernels intack and bootable)?

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Ummm... small problem I've upgraded to intrepid. Will this still work? Does someone want to patch the intrepid kernel for me?

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Ok installed it and it booted fine (in intrepid) though the mousepad still doesn't work. Dmesg attached.

Revision history for this message
Stefan Bader (smb) wrote : Re: [Bug 196808] Re: touchpad not detected by kernel in hardy heron

Just about when I prepared Intrepid kernels. :) But as it doesn't work. Will
keep that in mind for the next test kernel. Please use "i8042.debug=1" to boot.
Otherwise there is no relevant debug data.

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

I'll try booting with that command line tonight. If it doesn't work I'll flatten it completely and install 9.04...

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Ignore above... obviously it didn't work :-p
Anyway here's the debug dmesg from intrepid. Now to install Jaunty and I'll post a dmesg from that!

Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Umm... apart from my touchpad still not working... Best Ubuntu Ever!
So a fresh install (not upgrade) of jaunty and it still doesn't work. Debug Dmesg attached.

Revision history for this message
Stefan Bader (smb) wrote :

I see. Has been some time. Yours was the one that definitely had MUX problems. Could you (while keeping the i8042.debug=1) add a i8042.nomux=1 and add that dmesg as well?

Stefan Bader (smb)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
NJ (njspam+ubuntulaunchpad) wrote :

Sorry for the late reply. Dmesg is attached.
I've actually formatted the laptop and put XP back on it... however I can't find any drivers to get the touchpad working in that either. So its either a really unique touchpad or something is farked.

Since it now only seems to be me with this bug, after a quick look over the dmesg to see if it gives you any ideas... I'd just close this bug. I've just given up on it and I'm looking at a new laptop anyway.

Stefan, thanks for all your help and perseverance over more than a year!

NJ

Revision history for this message
Stefan Bader (smb) wrote :

As far as I can see, with muxing you get a lot of timeouts. Without, the driver tries to find out what is on the AUX port (0xd4, 0xf2) and receives just an error (0xfc). Not sure what the next things are but it seems to act not like a synaptics touchpad.

And with your finding that even XP fails to do something sensible, I too would suspect the hardware being at fault.

Revision history for this message
Stefan Bader (smb) wrote :

Beside of all the other stuff in this report, I take NJ's response and close this bug as invalid as it likely is in his case.

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