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