Mailinglist Archive: opensuse (3653 mails)
| < Previous | Next > |
Re: [SLE] Before Cat eat the "mouse", how can i configure it ( :
- From: Ralph Sanford <rsanford@xxxxxxxxxxxxxxx>
- Date: 01 Jun 2002 00:02:37 -0600
- Message-id: <1022911358.1116.40.camel@rsanford>
On Fri, 2002-05-31 at 14:25, dan wrote:
>
> > After failed to reconfigure my system due to red-carpets installations i
> > reinstalled the whole system with KDE with SO default.
> >
> > When i was installing I pulled the mouse from usb and touchpad start
> > working, later on i tried to activate mouse it didn't work.
>
> it's work w/s two mice(PS/2 on kbrd and USB)
>
> Section "InputDevice"
> Driver "mouse"
> Identifier "Mouse[1]"
> Option "ButtonNumber" "3"
> Option "Device" "/dev/mouse"
> Option "Emulate3Buttons" "on"
> Option "Emulate3Timeout" "50"
> Option "InputFashion" "Mouse"
> Option "Name" "Autodetection"
> Option "Protocol" "imps/2"
> Option "Vendor" "Sysp"
> Option "ZAxisMapping" "4 5"
> EndSection
>
> Section "InputDevice"
> Driver "mouse"
> Identifier "Mouse[3]"
> Option "Device" "/dev/psaux"
> Option "InputFashion" "Auto"
> Option "Name" "Autodetection"
> Option "Protocol" "ps/2"
> Option "Vendor" "Sysp"
> EndSection
>
>
>
I made a similar change last week to my laptop and now it works with the
eraser top, ps/2 mouse or usb mouse. However there are two caveats to
be aware of:
1. I could not find how to inflict the above changes to my system using
Yast or Sax. So this means manually editing etc/X11/XF86config and this
file has a big warning at the top of it that says do not edit this.
2. If you decide to ignore the warning from Suse and edit this file
then you will need to add another line in the Section "ServerLayout"
which is much lower in the same file. Where the file currently has
InputDevice "Mouse [1]", "CorePointer"
you will need to add another line describing the second mouse. On my
system the second mouse is [2] not [3] like the example above.
InputDevice "Mouse [1]", "CorePointer"
InputDevice "Mouse [2]", "SendCoreEvents"
This works for me, YMMV.
--
Ralph Sanford - If your government does not trust you,
rsanford@xxxxxxxxxxxxxxx - should you trust your government?
DH/DSS Key - 0x7A1BEA01
>
> > After failed to reconfigure my system due to red-carpets installations i
> > reinstalled the whole system with KDE with SO default.
> >
> > When i was installing I pulled the mouse from usb and touchpad start
> > working, later on i tried to activate mouse it didn't work.
>
> it's work w/s two mice(PS/2 on kbrd and USB)
>
> Section "InputDevice"
> Driver "mouse"
> Identifier "Mouse[1]"
> Option "ButtonNumber" "3"
> Option "Device" "/dev/mouse"
> Option "Emulate3Buttons" "on"
> Option "Emulate3Timeout" "50"
> Option "InputFashion" "Mouse"
> Option "Name" "Autodetection"
> Option "Protocol" "imps/2"
> Option "Vendor" "Sysp"
> Option "ZAxisMapping" "4 5"
> EndSection
>
> Section "InputDevice"
> Driver "mouse"
> Identifier "Mouse[3]"
> Option "Device" "/dev/psaux"
> Option "InputFashion" "Auto"
> Option "Name" "Autodetection"
> Option "Protocol" "ps/2"
> Option "Vendor" "Sysp"
> EndSection
>
>
>
I made a similar change last week to my laptop and now it works with the
eraser top, ps/2 mouse or usb mouse. However there are two caveats to
be aware of:
1. I could not find how to inflict the above changes to my system using
Yast or Sax. So this means manually editing etc/X11/XF86config and this
file has a big warning at the top of it that says do not edit this.
2. If you decide to ignore the warning from Suse and edit this file
then you will need to add another line in the Section "ServerLayout"
which is much lower in the same file. Where the file currently has
InputDevice "Mouse [1]", "CorePointer"
you will need to add another line describing the second mouse. On my
system the second mouse is [2] not [3] like the example above.
InputDevice "Mouse [1]", "CorePointer"
InputDevice "Mouse [2]", "SendCoreEvents"
This works for me, YMMV.
--
Ralph Sanford - If your government does not trust you,
rsanford@xxxxxxxxxxxxxxx - should you trust your government?
DH/DSS Key - 0x7A1BEA01
| < Previous | Next > |