On Thu, 2005-07-28 at 18:34 +0200, Marco d'Itri wrote:
> On Jul 28, Mourad De Clerck <email address hidden> wrote:
>
> > Let me know how I can help you chase down this bug.
> Are mousedev and all the other related drivers loaded?
mousedev is loaded in /etc/modules, just to be sure. Otherwise
everything I can think of (usbhid, bluetooth hidp etc) is all loaded by
hotplug etc.
> Does /sys/class/input/mice/dev exist?
yes.
$ cat /sys/class/input/mice/dev
13:63
> Does running udevstart make the device appear?
yes - doing a find in /dev/ before and after doing udevstart shows it
only affects /dev/input/mice - unlike previous episodes where lots of
other devices (like nvidia) were missing.
On Thu, 2005-07-28 at 18:34 +0200, Marco d'Itri wrote:
> On Jul 28, Mourad De Clerck <email address hidden> wrote:
>
> > Let me know how I can help you chase down this bug.
> Are mousedev and all the other related drivers loaded?
mousedev is loaded in /etc/modules, just to be sure. Otherwise
everything I can think of (usbhid, bluetooth hidp etc) is all loaded by
hotplug etc.
> Does /sys/class/ input/mice/ dev exist?
yes.
$ cat /sys/class/ input/mice/ dev
13:63
> Does running udevstart make the device appear?
yes - doing a find in /dev/ before and after doing udevstart shows it
only affects /dev/input/mice - unlike previous episodes where lots of
other devices (like nvidia) were missing.
--- dev_after_ boot_sorted. txt 2005-07-28 19:26:22.000000000 +0200 udevstart_ sorted. txt 2005-07-28 19:26:39.000000000 udevdb/ class@input@ event5 udevdb/ class@input@ mice udevdb/ class@input@ mouse0
+++ dev_after_
+0200
@@ -5805,2 +5805,3 @@
/dev/.
+/dev/.
/dev/.
@@ -5845,2 +5846,3 @@
/dev/input/event5
+/dev/input/mice
/dev/input/mouse0
> Did you read README.Debian?
yes - read and re-read.
-- Mourad