Comment 46 for bug 195009

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....