Re: Thinkpad Touchpad no longer works
On Fri, Oct 16, 2009 at 21:49:34 +0100, Barry Samuels wrote:
> On 16/10/09 21:22:22, Barry Samuels wrote:
> > On 16/10/09 20:13:45, Andrew Sackville-West wrote:
> > > On Fri, Oct 16, 2009 at 02:12:59PM -0400, Celejar wrote:
> > > > On Fri, 16 Oct 2009 18:42:05 +0100 Barry Samuels wrote:
[...]
> > > > > SynPS/2 Synaptics Touchpad The /dev/input/event* device nodes seem
> > > > > to be missing
[...]
> > > > Not sure, but in the kernel config, there's something called
> > > > CONFIG_INPUT_DEV (Device Drivers / Input device support / Event
> > > > interface).
[...]
> > > > Perhaps your kernel doesn't have this enabled?
> >
> > It is enabled.
> >
> > > from the tone of the prior thread, I assume it's a stock kernel, so,
> > > OP, let us know if it's not.
> >
> > No it's not. I compile my own kernels.
[...]
> > The output of lshal -u $(hal-find-by-capability --capability
> > input.touchpad) is:
> >
> > udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input'
[...]
> > input.device = '/dev/event7' (string)
[...]
> > linux.sysfs_path = '/sys/class/input/input7/event7' (string)
> >
> > I hope it means more to you than it does to me. :)
>
> Just noticed something. On my desktop event0, event1, mice, mouse0 etc are
> in /dev/input but on the laptop they are in /dev and /dev/input has only
> by-id and by-path
>
> Is that significant?
Yes, it is; it probably means that something goes wrong when udev
creates the device node for the touchpad. My first guess is that you
upgraded to a newer version of udev, and that it now expects some novel
piece of information that your custom kernel does not provide. (IOW, I
side with Celejar and Andrew in suspecting your kernel configuration is
the cause of your problems.)
Please install the newest stock kernel and boot into it; this will
immediately tell us if we are on the right track. Once we have
established that, we can delve into the details to find the relevant
setting.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: