YoYo siska posted on Wed, 21 Apr 2010 22:34:38 +0200 as excerpted: > just guessing, maybe it is the last error (no driver...ignoring...)? > have you tried adding explicit Driver "evdev"?
Note that that error is on the /dev/input/mouseX devicefile. The /dev/input/eventX devicefile gets the evdev driver, as logged. (Both devicefiles match the mouse in question, as they're two separate virtual drivers at the kernel level, exported as two separate devicefiles, but driven by the same physical device, the one in question. I see the same thing here with a system functioning as expected. But people running the gpm text console mouse driver can't turn off the legacy mouseX driver, as gpm has to have it as it's apparently not evdev compatible, yet. If it was, things would be simpler as the mousedev driver could be configured out of the kernel entirely, leaving only evdev.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
