On Jan 31, Joey Hess <joeyh@debian.org> wrote: > Oh, so it's udev that's responsible for what IIRC is a race that can > cause X to not see the ps/2 mouse if the module is loaded as part of X's > setup? Nice design. :-P This is the *upstream* design... The official word on this is that if you manually load a module then you need to wait for the device with a loop (which sucks if you do not know the device name, so you should use a dev.d script when possible). > FWIW, we have worked around this bug in d-i unstable for at least i386 > and amd64 by always putting psmouse in /etc/modules. Lack of serio hotplug support is a kernel bug, but I see that the needed bits are being merged. -- ciao, Marco
Attachment:
signature.asc
Description: Digital signature