Re: /dev/input/mice doesn't work in test9?
Date: Sat Nov 01 2003 - 15:57:34 EST
Hi Andrey and Shawn :)
* "Andrey Borzenkov" <arvidjaar@xxxxxxx> dixit:
> > I'm sure I'm just missing something stupid, but google doesn't
> > seem to turn up anything, so...
Exactly the same for me...
> > I'm trying to use 2.6.0-test9 on a machine with a USB mouse. With 2.4, I
> > have X configured to use /dev/input/mice (c 13 63) as my mouse pointer,
> > and it works great. With test9, XFree86 fails to start because it can't
> > open the mouse. The error is "xf86OpenSerial: Cannot open device /dev/
> > input/mice No such device.".
My problem is a bit different. I'm using 2.4.21, with an USB
mouse. I have 'input' built-in, and hid and mousedev as modules.
Well, if I do a cat /dev/mouse (c 13 32) or /dev/mice (c 13 63), I
always get ENODEV, unless I manually load hid and mousedev. The logs
doesn't say anything like 'cannot find driver for char-major-13' or
whatever. It just seems that 'mousedev' is never autoloaded :?
> The whole input subsystem has changed between 2.4 and 2.6.
> Unfortunately, input sysbsystem hotplugging is not currently
> implemented. Your best bet is to forcibly load mousedev during
But hotplugging is for connecting and disconnecting devices, not
for autoloading modules. I mean, if I access any char-major-13, and
the corresponding modules is not loaded, it should autoload :?
The rest of devices in my system are properly autoloaded on
demand, but hid and mousedev are not :( Am I doing something wrong?
> Alternatively look into hotplug for usermap, it allows provide fake
> mapping for modules - you could add mapping from UDB IDs of oyur
> mouse to mousedev. Loading it statically is likely to be more
Exactly... Anyway, if I build 'mousedev' into my kernel instead
of making it a module, should I do the same with 'hid' or
char-major-13 *is* autoloaded?
Thanks a lot in advance. I'm missing on this subject...
Raúl Núñez de Arenas Coronado
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/