eMachines M6805 laptop. Keyboard and touchpad is unresponsive using the gentoo-dev-sources kernel (latest tested version 2.6.7-r9), although it works fine using vanilla-sources 2.6.7 (using the same .config on both kernels) Reproducible: Always Steps to Reproduce: 1. Buy eMachines laptop 2. Install Gentoo-Linux with gentoo-dev-sources kernel 3. Boot Actual Results: Machine booted, but without keyboard/touchpad support. The keyboard/touchpad CAN be made to work by: 1) Compiling the keyboard driver as a module (atkbd) 2) Hacking drivers/input/serio/i8042.c to override testing for the mouse/touchpad (see patch). Note this is a kludge, the real problem is elsewhere. I'm guessing that there is some module which needs to be loaded before the keyboard/mouse drivers in order for it to work, and that somehow gentoo-dev-sources changes the order in which the modules are loaded - hence why the keyboard will work when compiled as a module (ie, loaded last). I'm no kernel expert, but with some guidance hopefully we can find this bug (ideally before the next LiveCD is released).
Created attachment 35161 [details, diff] Kludge to get touchpad working
Are you _sure_ a 2.6.7 kernel from kernel.org works with the same .config? I don't see any patches in the g-d-s package that could affect this at all. What arch is this laptop (amd64 or x86)?
Created attachment 35251 [details] Kernel configuration This is the config used on both vanilla 2.6.7, and gentoo 2.6.7-r19.
Created attachment 35252 [details] dmesg from vanilla 2.6.7
Created attachment 35253 [details] dmesg from gentoo 2.6.7 r19
The architecture is amd64 (as stated in the hardware box above ;-) I don't think an emerge info would be of any use so I haven't included it. If no-one has any useful suggestions before tommorow I'll start applying the gentoo patches one at a time until I find the culprit (I hope there aren't that many..).
The laptop in question is an eMachines M6805. Flashing the BIOS with the firmware from the M6809 (slightly higher spec and newer model) has fixed this problem (and some other problems too). For information, the BIOS firmware can be found here: http://www.rmecc.com/~v2/em/index.html
Thanks for keeping us up-to-date.