| 1 |
Javier Payno wrote: |
| 2 |
|
| 3 |
> |
| 4 |
>I think I might have solved this problem. I have changed the xorg.conf mouse |
| 5 |
>protocol from "auto" to "PS/2". The mouse is still connected to a USB port |
| 6 |
>and now appears to work correctly. |
| 7 |
>How strange, perhaps Peter and Dale could try this and see if it solves their |
| 8 |
>problem as well. |
| 9 |
> |
| 10 |
>Ho wait my mouse wheel isn't working now - back to the drawing board |
| 11 |
> |
| 12 |
>Paul |
| 13 |
> |
| 14 |
> |
| 15 |
|
| 16 |
|
| 17 |
Funny, I thought about that thread when I saw it was taking one click |
| 18 |
twice too. May want to check on that. If you look in the Xorg.0.log |
| 19 |
file in /var/log it should tell you what it tries to see it as. It may |
| 20 |
be seeing it as the wrong thing. This may help too: |
| 21 |
|
| 22 |
> root@smoker / # dmesg | grep mouse |
| 23 |
> mice: PS/2 mouse device common for all mice |
| 24 |
> root@smoker / # |
| 25 |
|
| 26 |
|
| 27 |
See what that says and let us know if we can help, or it fixes it. I |
| 28 |
may would believe dmesg myself. Make sure you and a editor gets along |
| 29 |
though. GUI may not come up at all if it can't find a little rat |
| 30 |
running around. |
| 31 |
|
| 32 |
Dale |
| 33 |
:-) |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
To err is human, I'm most certainly human. |
| 38 |
|
| 39 |
I have four rigs: |
| 40 |
|
| 41 |
1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives. Named Smoker |
| 42 |
2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive. Named Swifty |
| 43 |
3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 224MBs of ram and a 2.5GB drive. Named Pokey |
| 44 |
4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive. Named Putput |
| 45 |
|
| 46 |
All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers. |
| 47 |
|
| 48 |
-- |
| 49 |
gentoo-user@g.o mailing list |
Archives