On Wed, Jan 13, 2010 at 04:05:26PM +0000, Julien Cristau wrote: > On Wed, Jan 13, 2010 at 16:19:25 +0100, Agustin Martin wrote: > > > Finally found the reason for this problem, kernel evdev module was not > > loaded. I have worked around this by explicitly adding evdev to > > /etc/modules in my sid box. > > > > However, until last weekend/this week, it was automagically loaded, with no > > need for explicit inclusion into /etc/modules. What has changed in this time > > to trigger the problem? > > > It's autoloaded just fine here, and apparently for everyone else, > without touching /etc/modules. No clue.
I finally found what I think is causing evdev not be loaded, and that is related to my system being non-standard, so I will fix that locally. I do not know which exact xserver-xorg change made that happens, but I do not think that is very relevant now. More details follow in case I am not the only one setting this kind of non-standard systems. In my system I have different partitions for different dists (sid, ...) and all the boot+kernel+modules stuff is at a different place. Each dist partition has proper symlinks, and special code is added to /etc/init.d to make sure partition containing /lib/modules is mounted just before /etc/init.d/module-init-tools is run and unmounted afterwards, before /etc/init.d/checkfs is run, so /etc/modules is honoured. Things are mounted again later according to /etc/fstab. The problem in my system is that with the above setup udev init scripts are run way before /lib/modules is mounted and so evdev module is not loaded by udev because is not found. I have to see what is the best workaround for this in my system. Having evdev in /etc/modules seems simpler, but I have to investigate other possibilities, like mounting before /etc/init.d/udev is run. Sorry for the noise and thanks a lot for the feedback. Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org