There are two ways to select the mouse type under Yast2: through Hardware / Select Mouse Model and through Hardware / Graphics Card and Monitor. The latter route gets you into Sax2, which has an Input Devices section. The odd thing is that the two modules have very different lists of mice. It's quite mysterious as to how the two selections interact, especially if the selections are different. I ran into an odd problem where my mouse wheel was recognized when it was moving down but not when it was moving up. (I verified by booting into Windows that the hardware was OK.) Eventually by fiddling with the mouse selections I got the upward motion to be recognized too, but I'm very unclear as to what is going on. Paul Abrahams
On Fri, 2 Jan 2004 12:46:38 -0500, "Paul W. Abrahams" <abrahams@acm.org> wrote:
There are two ways to select the mouse type under Yast2: through Hardware / Select Mouse Model and through Hardware / Graphics Card and Monitor. The latter route gets you into Sax2, which has an Input Devices section.
... there's a third method: apply the entries to the /etc/X11/XF86Config[-4] file :)
The odd thing is that the two modules have very different lists of mice. It's quite mysterious as to how the two selections interact, especially if the selections are different. I ran into an odd problem where my mouse wheel was recognized when it was moving down but not when it was moving up. (I verified by booting into Windows that the hardware was OK.) Eventually by fiddling with the mouse selections I got the upward motion to be recognized too, but I'm very unclear as to what is going on.
... i've seen this before too: it was simply the rwong mouse settings. which make/model mouse are you using and what's its interface? -- << http://michaeljtobler.homelinux.com/ >> It's not the valleys in life I dread so much as the dips. -- Garfield
On Friday 02 January 2004 1:23 pm, mjt wrote:
On Fri, 2 Jan 2004 12:46:38 -0500, "Paul W. Abrahams" <abrahams@acm.org> wrote:
There are two ways to select the mouse type under Yast2: through Hardware / Select Mouse Model and through Hardware / Graphics Card and Monitor. The latter route gets you into Sax2, which has an Input Devices section.
... there's a third method: apply the entries to the /etc/X11/XF86Config[-4] file :)
The odd thing is that the two modules have very different lists of mice. It's quite mysterious as to how the two selections interact, especially if the selections are different. I ran into an odd problem where my mouse wheel was recognized when it was moving down but not when it was moving up. (I verified by booting into Windows that the hardware was OK.) Eventually by fiddling with the mouse selections I got the upward motion to be recognized too, but I'm very unclear as to what is going on.
... i've seen this before too: it was simply the rwong mouse settings. which make/model mouse are you using and what's its interface?
I'm using a Logitech Trackman Wheelmouse with a PS/2 connection, and that one isn't in either database. So I have to fake it somehow. Paul Abrahams
On Fri, 2 Jan 2004 13:50:08 -0500, "Paul W. Abrahams" <abrahams@acm.org> wrote:
its interface?
I'm using a Logitech Trackman Wheelmouse with a PS/2 connection, and that one isn't in either database. So I have to fake it somehow.
... i use a logitech cordless mouseman wheel - it's a four button with wheel. here my entry in /etc/XF86Config-4 Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "5" Option "Device" "/dev/mouse" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection a groups.google search turned up this for their trackman: Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "5" Option "Device" "/dev/mouse" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection -- << http://michaeljtobler.homelinux.com/ >> Feel disillusioned? I've got some great new illusions ...
On Fri, 2 Jan 2004 13:06:53 -0600, mjt <mjtobler@earthlink.net> wrote:
button with wheel. here my entry in /etc/XF86Config-4
.... correction....................../etc/X11/XF86Config-4 -- << http://michaeljtobler.homelinux.com/ >> "I am not sure what this is, but an `F' would only dignify it." -- English Professor
"Paul W. Abrahams" <abrahams@acm.org> writes:
There are two ways to select the mouse type under Yast2: through Hardware / Select Mouse Model and through Hardware / Graphics Card and Monitor.
Mouse can be used by gpm and by the X server. It is possible that each program uses different configuration settings.
It's quite mysterious as to how the two selections interact, especially if the selections are different.
IMHO both settings should be independent. In the past, gpm monitored the mouse in Linux console and X server in GUI. It worked OK but gpm is not activated by default nowadays. Perhaps there is a conflict for certain HW. -- A.M.
On Friday 02 January 2004 2:31 pm, Alexandr Malusek wrote:
"Paul W. Abrahams" <abrahams@acm.org> writes:
There are two ways to select the mouse type under Yast2: through Hardware / Select Mouse Model and through Hardware / Graphics Card and Monitor.
Mouse can be used by gpm and by the X server. It is possible that each program uses different configuration settings.
It's quite mysterious as to how the two selections interact, especially if the selections are different.
IMHO both settings should be independent. In the past, gpm monitored the mouse in Linux console and X server in GUI. It worked OK but gpm is not activated by default nowadays. Perhaps there is a conflict for certain HW.
I'm not that familiar with gpm, but a glance at the manpage suggests that it applies only to a textual environment and is intended to be running only when X is not running. So I'm somewhat doubtful that either configuration section applies to gpm. Certainly the one in Sax2 wouldn't since Sax2 is intended specifically to configure X. My guess is that the other one doesn't apply to gpm either. Do you know, perchance? Paul Abrahams
"Paul W. Abrahams" <abrahams@acm.org> writes:
... I'm not that familiar with gpm, but a glance at the manpage suggests that it applies only to a textual environment and is intended to be running only when X is not running.
"Not active" may be better words than "not running". I can start both X and gpm on my computer (PS/2 mouse). If I switch to text mode via e.g. Ctrl-Alt-F2, then gpm is activated and I can use the mouse to copy and paste text there.
So I'm somewhat doubtful that either configuration section applies to gpm.
IMHO SaX2 modifies /etc/X11/XF86Config and YaST modifies /etc/sysconfig/mouse, which contains both gpm and X related variables and is used by gpm. I don't know why SUSE keeps X related configuration there but they may have a reason. -- A.M.
participants (3)
-
Alexandr Malusek -
mjt -
Paul W. Abrahams