I am living a huge pain with kernel 2.6.9 upgrading. It so huge that I don't know how to start my explanation.
Ok, the problem is that my laptop touchpad is not recognized with 2.6.9 kernel. I have selected all possible options in config file
CONFIG_INPUT_EVDEV=y and m
CONFIG_INPUT_MOUSEDEV=y and m
CONFIG_INPUT_MOUSE=y and m
CONFIG_INPUT_MOUSEDEV_PSAUX=y and m
CONFIG_MOUSE_PS2=y and m
Finally, I thought that it could be a non selected option in kernel config file. So I had the oportunity to try and upgrade to Fedora Core 3 ( Kernel 2.6.9 ). During the upgrading the mouse was not detected, so precompiled kernel do not detect my touchpad. It works with my 2.4.23 kernel. So I discard this error
With kernel 2.6.9 there is no mouse in /proc/bus/input/devices.
IRQ 12 is not assigned ( /proc/interrupts ). IRQ 12 is assigned for the mouse in the BIOS by Default with no change possibility. I discard also IRQ conflict because it is not assigned.
Xfree problem ? To avoid this possibility, I turned on console mouse support. X was not the problem.
I have also tried to pass paramenters to kernel boot (psmouse_proto= imps, ps2, synps , etc ) No luck..
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
mmmm.....nothing strange, but no more information ( SynPS/2 )
If I select pc110pad in .config file, it appears in /proc/bus/input/devices. But pc110pad use IRQ 10. Mouse is in IRQ 12 in the bios, so I changed pc110pad.c to be in IRQ 12 and I recompiled the kernel again. It seems to be loaded ( dmesg ) but it does not work. Finally, I think it is not a pc110pad
I have tried 2.6.5 Kernel with SUSE LiveCD. It has worked. /proc/bus/input/devices output is:
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
H: Handlers=mouse1 event2
B: KEY=6420 0 670000 0 0 0 0 0 0 0 0
I am not sure if it could be a kernel bug. Does anybody know something about this ?