[Hardy] synaptic touchpad not detected

Thank you for your report. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. I have classified this bug as a bug in linux.

I also have the same problem. My dmesg is attached. As for the classification I think i should be more specifically a bug in the kernel as Goswin suggested.

Hi guys,

Care to just quickly test with the latest 2.6.24-11 kernel just to verify the issue still exists. Thanks.

Hoy hoy, still a no-go. Dmesg attached.
discostu@discostu:~$ uname -a
Linux discostu 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 GNU/Linux

discostu@discostu:~$ dmesg | grep input
[ 11.783818] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 11.815129] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 15.218221] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.0/input/input2
[ 15.234997] input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.0-1
[ 28.470983] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 29.114924] input: Power Button (FF) as /devices/virtual/input/input4
[ 29.125154] input: Lid Switch as /devices/virtual/input/input5
[ 29.125416] input: Power Button (CM) as /devices/virtual/input/input6
[ 30.702571] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:11/LNXVIDEO:00/input/input7

Hey, I did the same yesterday, and also no go. Can't show a dmesg from work, but I tried once without any editing of xorg.conf and once while adding a "Configured Touchpad", driver "Synaptics" to xorg.conf. When I get home, I'll give you a dmesg list like NJ did.

So this is without any alteration to xorg.conf:

[ 6.248144] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 7.032349] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 10.973286] input: HID 1241:1177 as /devices/pci0000:00/0000:00:1c.0/usb1/1-1/1-1:1.0/input/input2
[ 10.984776] input,hidraw0: USB HID v1.10 Mouse [HID 1241:1177] on usb-0000:00:1c.0-1
[ 24.629827] input: Power Button (FF) as /devices/virtual/input/input3
[ 24.641770] input: Sleep Button (CM) as /devices/virtual/input/input4
[ 24.657671] input: Lid Switch as /devices/virtual/input/input5
[ 24.817366] input: PC Speaker as /devices/platform/pcspkr/input/input6

...and this is with an added

Section "InputDevice"
 Identifier "Configured Touchpad"
 Driver "synaptics"
EndSection

to xorg.conf (don't know if that would even make a difference, but I just wanted to try), dmesg gave:

[ 7.651457] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 8.438943] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 12.381693] input: HID 1241:1177 as /devices/pci0000:00/0000:00:1c.0/usb1/1-1/1-1:1.0/input/input2
[ 12.391428] input,hidraw0: USB HID v1.10 Mouse [HID 1241:1177] on usb-0000:00:1c.0-1
[ 26.330081] input: Power Button (FF) as /devices/virtual/input/input3
[ 26.343810] input: Sleep Button (CM) as /devices/virtual/input/input4
[ 26.359791] input: Lid Switch as /devices/virtual/input/input5
[ 27.513535] input: PC Speaker as /devices/platform/pcspkr/input/input6

I just fired up Dapper and Edgy once more, on a live CD. Both recognized the touchpad without problems. I gathered some information from the systems that might be of interest.

[17179636.100000] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x92a0b1, caps: 0xa04713/0x200000
[17179636.136000] input: SynPS/2 Synaptics TouchPad as /class/input/input3

This is from dmesg (Edgy). Dapper showed identical listings. I also added the information shown on 'Hardware Information' as a screenshot.

I can boot back into Edgy anytime, so if you'd want me to execute some commands, or get info from other logs that might help solving this bug, please let me know.

Oh yeah, I also did a live boot in Feisty once more, and Feisty is the first to not recognize the touchpad. So it's been going on for quite some time already...

Kernel Update last night didn't help

discostu@discostu:~$ dmesg | grep input
[ 11.974385] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 12.000347] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 32.319114] input: PC Speaker as /devices/platform/pcspkr/input/input2
[ 34.023575] input: Power Button (FF) as /devices/virtual/input/input3
[ 34.074191] input: Lid Switch as /devices/virtual/input/input4
[ 34.106250] input: Power Button (CM) as /devices/virtual/input/input5
[ 35.159669] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:11/LNXVIDEO:00/input/input6
[ 2965.614215] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb1/1-1/1-1:1.0/input/input7
[ 2965.660767] input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.0-1

discostu@discostu:~$ uname -a
Linux discostu 2.6.24-12-generic #1 SMP Mon Mar 10 15:32:00 UTC 2008 i686 GNU/Linux

Same with me:

kuolas@NapaValley:~$ dmesg | grep input
[ 9.476682] input: Macintosh mouse button emulation as /class/input/input0
[ 9.508413] input: AT Translated Set 2 keyboard as /class/input/input1
[ 12.728000] input: PC Speaker as /class/input/input2
[ 12.916000] input: Genius NetScroll + Traveler as /class/input/input3
[ 12.916000] input: USB HID v1.10 Mouse [Genius NetScroll + Traveler] on usb-0000:00:1d.0-2
[ 15.820000] input: Power Button (FF) as /class/input/input4
[ 15.820000] input: Sleep Button (CM) as /class/input/input5
[ 15.820000] input: Lid Switch as /class/input/input6
[ 1296.452000] input: Genius NetScroll + Traveler as /class/input/input7
[ 1296.452000] input: USB HID v1.10 Mouse [Genius NetScroll + Traveler] on usb-0000:00:1d.0-2

This is a HP 530 Core Duo T2400 Notebook.

Toshiba Satellite A70 here

discostu@discostu:~$ sudo lshw
[sudo] password for discostu:
discostu
    description: Notebook
    product: Satellite A70
    vendor: TOSHIBA
    version: PSA70A-007001
    serial: 8433****K
    width: 32 bits
    capabilities: smbios-2.31 dmi-2.31 smp-1.4 smp
    configuration: boot=oem-specific chassis=notebook cpus=1 uuid=9BD00F6D-D695-11D8-8677-00023FD72086
  *-core
       description: Motherboard
       product: EDW10
       vendor: TOSHIBA
       physical id: 0
       version: Null
       serial: 012345****AB
       slot: SVGA-Out
     *-firmware
          description: BIOS
          vendor: TOSHIBA
          physical id: 0
          version: V1.50 (11/16/2004)
          size: 104KiB
          capacity: 448KiB
          capabilities: pci pcmcia pnp upgrade shadowing cdboot bootselect int13floppytoshiba int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp smartbattery biosbootspecification

Could someone try to boot with "i8042.debug=1" as kernel parameter and post the dmesg output. Maybe this gives further insight.

Hey mate. Done and attached (didn't work though). lspci and lsusb don't give anything overally interesting (can attach if required). But i find this line in the dmesg sorta interesting:
[ 60.747270] PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
Hope it helps. Its nearly 3am here will check back as soon as i get up :)

Check this out: What's this on System>Preferences>"Device Manager": PnP Device (SYN0132)

Synaptics detected by PnP?

gnome-device-manager give me:
PNP Device
Identifer: PNP0f13
Description: PS/2 Port for PS/2-style Mice
Connection: PNP (Plug-and-Play)

I see through my searches that passing the parameter psmouse.proto=imps at boot time helped some people in the past maybe it has something to do with that?

HAL Device manager detects SYN0312?

With the debugging of the i8042 enabled (and that is supposedly where the touchpad is connected), I see MUX errors. But I havn't found out what exactly the meaning of those is.

Things to try: does using one of those options change anything?
"i8042.noacpi=1" or "i8042.nomux=1"

I tried all the i8042.* bootoptions you suggested. None got my touchpad up, but for your reading pleasure I'll attach the dmesg logs for each boot option. If you need some more info on my system or my hardware, please ask (and suggest the right command - I'm not all that good with bash yet).

You havn't actually used those options. Sorry I was not very specific. You have to add those as kernel boot options. When grub starts (you may have to hit escape to get the menu), goto the kernel you want to use and hit 'e'. Then there are the boot arguments. Goto the one reading
"root=UUID=da2383c2-389a-457e-bd25-2c35cf1be8c2 ro quiet splash"
and change it to (for example)
"root=UUID=da2383c2-389a-457e-bd25-2c35cf1be8c2 ro quiet splash i8042.nomux=1"
Then hit enter (which brings you one level back) and then 'b' to boot with that configuration.

This is from Gusty:

This and below are from hardy with dist-upgrade done 2 days ago

Hey mate can i just thanks in advance from your help to date and continuing help :)

Hey Stefan, you're right, I added the options to the last line in Grub, which only said quitet. This time I've done it right I think. Still no touchpad, but let's hope you can find some oddities in our dmesg's that lead to the fix. Thanks for helping out so far!

Sorry, mine is a hardware problem, I tried with other distros and no go. Even with windows, it detects SYN0132 but theres no synaptics atached to it. I'm going to the warranty roard.

I've got the same problem here on a HP6710s notebook. It suddenly stopped working. Now I tried upgrading to hardy but didn't work. Interestingly it gets detected with tpconfig:
root@farnsworth:~# tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.

I was able to fix it by simply loading the psmouse module:

sudo modprobe psmouse

The device appears in /proc/bus/input/devices and can be used.

David, glad it worked for you! I tried the same (despite knowing better - i've tried modprobing several times), and tpconfig also finds the touchpad without problems, but modprobing doesn't change anything. Also no touchpad in .../devices. Well, yours has worked once with Gutsy (I assume) - mine hasn't worked since Feisty. Hopefully there will be someone finding a pattern here, who can fix whatever is holding the touchpad from being found during boot.

In my case It doesn't work under Windows Vista H.B. but:

kuolas@NapaValley:~$ sudo tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.

My symptoms are the same as Goswins (no to modprobing and not detected at boot.) Happy easter all :)

I have a same problem on Fujitsu Siemens Amilo Pi 2515 laptop.

root@discostu:/home/discostu# dmidecode
# dmidecode 2.9
SMBIOS 2.31 present.
35 structures occupying 1218 bytes.
...
Handle 0x001D, DMI type 21, 7 bytes
Built-in Pointing Device
 Type: Touch Pad
 Interface: PS/2
 Buttons: 2

root@discostu:/home/discostu# tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.

No love from the kernel and modules update from last night :(
Any word on progress Stefan?

discostu@discostu:~$ dmesg | grep input
[ 21.355079] input: Macintosh mouse button emulation as /devices/virtual/input/input0
[ 21.372780] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 25.127226] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb1/1-1/1-1:1.0/input/input2
[ 25.143765] input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.0-1
[ 43.602060] input: PC Speaker as /devices/platform/pcspkr/input/input3
[ 44.878435] input: Power Button (FF) as /devices/virtual/input/input4
[ 44.906263] input: Lid Switch as /devices/virtual/input/input5
[ 44.938308] input: Power Button (CM) as /devices/virtual/input/input6
[ 45.883372] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:11/LNXVIDEO:00/input/input7
discostu@discostu:~$ uname -a
Linux discostu 2.6.24-14-generic #1 SMP Thu Apr 3 04:49:29 UTC 2008 i686 GNU/Linux

Re: Bug # 195009
I also have this exact bug on my (custom-built) desktop system (Intel D865PERL Motherboard, Pentium 4. The system has an external Alps Glidepoint PS/2 serial port version (instead of a mouse) as well as a PS/2 keyboard. This is a dual boot system, and the touchpad works great under Win98SE. Under Ubuntu Gutsy 7.10.22-14 the touchpad is behaving just like a default mouse - no taps, must use the buttons to select. The system seems to think it is a mouse as well. A 'cat /proc/bus/input/devices' shows that it is not detecting the touchpad, and thinks that a "PS/2 Generic Mouse" is handled by mouse1 (a cat /dev/mouse1 shows garbage bits as you drag your finger). The /var/log/Xorg.0.log file also shows the standard message that it failed to detect the synaptics touchpad, and I think that my xorg.conf setup looks ok (based on lots of reading).

Finally, a dmidecode turns up no hint of a touchpad - just 2 PS/2 devices - a mouse and a keyboard (there is no mouse, just the touchpad).

tpconfig seems to find the device, but can't seem to set the tapmode (even under single-user mode without Xwindows running).

Everything points to a 'no detection' bug. No detection means I can't configure my standard tap-to-click and double-tap-to-drag behavior. It is driving me crazy(er).

Question - 1) can the system be TOLD that the 'mouse' is a 'touchpad'? I see the statement "alias pnp:dPNP0f13 psmouse" in the /etc/modprobe.d/isapnp file, but I don't know enough about what is going on to know if this needs changing or not.

Question - 2) Is there an on-line document that I can be reading to increase my understanding of kernel startup procedures? I've been looking at this for a week or so, and I must be just missing it (really don't want to hear the standard - 'the source code IS the documentation'). Hope this can be fixed soon, I've got miles to go....

1) Adding psmouse.proto=imps as a kernel parameter might help
Might also hellp:
sudo rmmod psmouse
sudo modprobe psmouse

2) Reading: http://web.telia.com/~u89404340/touchpad/trouble-shooting.txt

Hope it helps :)

I'm afraid I've tried all of theses suggestions, with no results. Put in the psmouse.proto=imps as a boot-time edit on the grub selection menu, and it was echoed properly, but didn't work. The rmmod/modprobe of psmouse was confirmed (both ways - in/out) with an lsmod | grep mouse with no results. This was done from a terminal window in Xwin (no restart) -- was that correct? I've read and worked through the trouble-shooting.txt file days ago (no joy). I was hoping for a much more detailed document. Perhaps the kernel is still changing too rapidly to make that type of documentation effort effective. I could send you more hard technical info, but I suspect that you've just seen it all before and your time is probably better spent swatting this deep in the code. I'm afraid I'm too new at this to be competent at that level.

I am sorry, but I currently have no more ideas. Starting with the 8032_debug option seems to be good to gather information (except for thos who have the touchpad attached to usb). Unfortunately, since I do not know how the trace should look, the best thing to do would be to try a upstream vanilla kernel and if that doesn't detect the touchpad as well, open a kernel bugzilla.

I had this problem - reconfiguring xorg and killing the server didn't help. My machine hung on reboot, so I booted into OS X to re-enable rEFIt. After that, it worked fine (using the xorg.conf I had generated earlier).

I had the same problem on hp nx8220. The problem now seems to be solved via modifying xorg.conf.
In the sever layout section I changed

 InputDevice "TouchPad" "AlwaysCore"
 InputDevice "Mouse" "CorePointer"

to
 InputDevice "TouchPad" "CorePointer"
 InputDevice "Mouse"

On my machine this fixed the issue.

It seems ours weren't detected by the kernel can you post your dmesg?

Of course. I attach dmesg and xorg.conf as well. Hope it helps.

[ 48.657193] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x25a0b1, caps: 0xa04793/0x300000
[ 48.657270] serio: Synaptics pass-through port at isa0060/serio4/input0
[ 48.696941] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8

See yours got recognised during boot... ours never did :(

Just for the weekend I drilled down to something that solved the problem in one case: if someone could just try to boot with "i8042.noloop=1" and cross his/her fingers.

Doesn't seem to have worked. No sure though. Dmesg attached. Thanks for keeping up the effort Stefan :)

Doesn't work for me either.
I think it's a common problem, not only for Linux. I used Everest
Ultimate to detect the touchpad in Windows, but got the same result, it
is recognized as a Logitech wheel mouse.

> Doesn't seem to have worked. No sure though. Dmesg attached. Thanks for
> keeping up the effort Stefan :)
>
> ** Attachment added: "dmesg.txt"
> http://launchpadlibrarian.net/14418595/dmesg.txt
>

A suggestion to everyone: post your machine model and specs.In this way we can see if there common hardware to complain. And anyone who can please test another OS to see if the software is the problem or if it's the touchpad.

The Machine:

This is a HP 530 Core Duo T2400 Notebook
Intel 945GME and ICH7 chipset.

The touchpad is not working on any OS tested (Ubuntu 7.10, 8.04, Windows V.H.B., Knoppix 2005)

My machine:

Fujitsu-Siemens Amilo Pi2515 Core 2 Duo T7100 Notebook
Intel 965 ICH8 chipset

The touchpad is recognized as a "PS/2 Logitech Wheel Mouse. It works but
no scroll function on the OS tested (Ubuntu 7.10, 8.04, Windows XP,
Windows Vista) The boot parameters, such as i8042.nomux, i8042.noloop,
etc. don't work.

> A suggestion to everyone: post your machine model and specs.In this way
> we can see if there common hardware to complain. And anyone who can
> please test another OS to see if the software is the problem or if it's
> the touchpad.
>

Seems like unfortunately this is Murphy's law in excess. We have a lot that can go wrong and it does. :-/ It seems quite a few (as far as I now understand the logs) might have problems with the active multiplexing (though it still requires a bit of reading to understand).
Generally, whenever you post message logs here, put in the ones with i8042.debug=1. This is the only way to see what the controller is doing (which should be the place the touchpad is connected normally). And we probably have to treat USB touchpads differently. There also seem to be some which have the touchpad detected but "only" not as touchpad but as a ps/2 mouse.

Just to cheer you up a little, my touchpad worked (!!) after booting with i8042.noloop=1. So your efforts have not been completely without effect. This bugreport is 'mine' so the make and model of my lappy are already known. I'll attach my dmesg and Xorg.0.log here - let me know if there are other logs or boot parameters you'd like me to try to help solve the other people's troublesome touchpad experiences.

My touchpad is working, it got back from the HP service center on my country (it took them a month to belive me that's not a software problem but hardware! HP Service department it's so good!).

kuolas@NapaValley:~$ sudo tpconfig -i
Found Synaptics Touchpad.
Firmware: 8.96 (multiple-byte mode).
Sensor type: unknown (0).
Geometry: rectangular/landscape/up.
Packets: absolute, 80 packets per second.
Corner taps disabled; no tap gestures.
Edge motion: none.
Z threshold: 6 of 7.
2 button mode; corner tap is right button click.
kuolas@NapaValley:~$

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input7
U: Uniq=
H: Handlers=mouse1 event7
B: EV=b
B: KEY=6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=11000003

Kernel update last night was no help, will try testing kernel parameters you've suggested soon stefan. Alvaro do you want to contact them and ask them what they did?

Notebook Model:
discostu@discostu:~$ sudo lshw
[sudo] password for discostu:
discostu
    description: Notebook
    product: Satellite A70
    vendor: TOSHIBA
    version: PSA70A-007001

I asked them, they didn't told what exactly they did. I just knew that they asked for parts to HP USA, those parts were a MOBO and a ney touchpad. The service was made by SONDA Uruguay.

But my touchpad was not working on any OS (Windows, Linux... err that's it)

@Goswin

if you could attach the output of dmidecode from your system, I'll forward that info to be included into mainline quirks.

Hello Stefan

I've put the output of dmidecode in the attachment. Thanks for your tireless assistance. People like you make Ubuntu rock so hard!

From upstream:

Any chance you could forward this patch to the user in question so it
can be tested before I apply it? Also, what model of the laptop is
that? DMI entires are not very descriptive unfortunately.

Thanks!

--
Dmitry

Signed-off-by: Dmitry Torokhov <email address hidden>
---
 drivers/input/serio/i8042-x86ia64io.h | 8 ++++++++
 1 file changed, 8 insertions(+)

Index: linux/drivers/input/serio/i8042-x86ia64io.h
===================================================================
--- linux.orig/drivers/input/serio/i8042-x86ia64io.h
+++ linux/drivers/input/serio/i8042-x86ia64io.h
@@ -118,6 +118,14 @@ static struct dmi_system_id __initdata i
                       DMI_MATCH(DMI_PRODUCT_VERSION, "VS2005R2"),
               },
       },
+ {
+ .ident = "MAM 2070",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Notebook"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "MAM 2070"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "5a"),
+ },
+ },
       { }
 };

Hey Stefan, I'd be glad to try it out, but how do I go about that? Can you (or someone else who'se done this before) give me a hand here?

Hi Goswin,

the simplest way (I hope) is to use the kernel image at http://people.ubuntu.com/~smb/bug195009/. You would first have to upgrade to the latest proposed kernel (activate -proposed in the apt sources), upgrade to that kernel and then manually install the test kernel package mentioned above. After that, booting the test kernel without the noloop option should also work.
If that works, please update the report and maybe also tell me which model your laptop is (you probably did before but to have that info together). Thanks.

He Stefan, I finally got around trying your fix, but the kernel is built for i386. I have an AMD64 installed. Could you produce one of those as well? Thanks!

Hi Goswin,

done. Same location as before.

Stefan, thanks for your quick reply. I've tried booting the new kernel twice, without the .noloop=1 argument, but the touchpad didn't come to life. This isn't what you expected, I guess, so if you want to investigate further, I can supply logs, configfiles, and whatnot. I'm very happy as it is, though (adding the bootparameter is a quick fix and I don't have to do it often), so if your attention is needed elsewhere then please do so.

I'm a novice so if this is useful then great; if not then please ignore

My Synaptics Touchpad was working great until kernel 2.6.18 (i think) when it suddenly stopped. By doing a diff on the source code and commenting out the changes in turn, I found that I can get the Touchpad working again by commenting out the following lines of the code in the file drivers/input/serio/i8042.c.

 if (wait_for_completion_timeout(&i8042_aux_irq_delivered,
     msecs_to_jiffies(250)) == 0) {
/*
 * AUX IRQ was never delivered so we need to flush the controller to
 * get rid of the byte we put there; otherwise keyboard may not work.
 */
  i8042_flush();
  retval = -1;
 }

It seems wait_for_completion_timeout fails and therefore the retval = -1 (i.e. fail). I do not understand why this fails or what this code does but the Touchpad seems fine with commenting out these lines and I have not noticed any other problems.

P.S. I'm using AMD64

@blush

This is actually the result of the problems with the loop command. You get there assuming the loop command does work and now is expected to return an interrupt when it is used. If the command is working that should happen, but for at least some of the boards the command does not do anything. A test before will run into a timeout but the code does not take this as an indication that the command is broken. And asking Dmitry he wrote "Unfortunately there are boxes that will loose keyboard if we mark loop as broken if it times out and assume that AUX is present."
Thus the manual workaround with i8042.noloop=1 or putting a board into a quirk table.

@Goswin

No I wasn't expected but if I had spent more time on the code around I might have noticed the whole quirk tables to be valid only for "__i386__" defined which probably isn't quite enough. ;-) Ok, I put another kernel at http://people.ubuntu.com/~smb/bug195009/ (sorry I was a lazy bloke and used the same version number again). I really hope this works this time. And hopefully the other fix (very, very lazy) does not interfere...

Stefan

Yup, this one works! Don't call yourself lazy though, after all the help you've given ;-) So to give you the additional info you requested about the laptop:

bios-version:M1.04
system-manufacturer:Notebook
system-product-name:MAM 2070
system-version:5a

Tthat's how the system identifies itself. Commercially it is known as a Cybermaxx, but that is a sub-brand of Medion. The bottom of the laptop also mentions a Medion-like type description (MD 95448) so maybe this quirk fixes some Medion issues (if any) as well.

Hey stefan good work!! I would be quite willing to be another guinea pig if you would like. Anyway great work! Any idea when this will be pushed in to the mainstream updates?

@NJ

probably not into Hardy (since it has for some the noloop=1 workaround). I am trying to get this quirk into upstream and by that maybe into Intrepid. Tests by you will only make sense at this stage, if your touchpad is found when using the i8042.noloop=1 option at boot. In that case post your dmidecode data (and maybe the human understandable model/manufacturer which medion for some reason does not like to reveal) and I would forward both entries to upstream.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

i have had a laptop for two years now and i have never thought that its touchpad would ever work nor at least be detected. until i come accross this thread. that i8042.noloop=1 option in grub was the magic!

here is my dmidecode if anyone would take a look at it. thanks a lot!

Ibex tried and the attachments are as follows

dmidecode

lspci -v

Basically it was a no-go. I tried booting without any other mouses and attached a usb one when it had fully booted to move around. Any suggestions?

I sent of the data for the blue fd5601 to the mailing list. Goswin's laptop is included already. So I would close this bug report. Ng, maybe you could create another report. This one is just becoming too big and has too many different things mixed.