Bug 137360

Please attach the output of `hwinfo --mouse' as well as the file /etc/sysconfig/mouse.

In general, a PS/2 mouse is a PS/2 mouse (what model description is used is rather dismissable, because they all use the same protocol). If you set BUTTONS="3" and WHEELS="1" in /etc/sysconfig/mouse and run SuSEconfig, it should work.

Please also attach the YaST log.

Hi
here's the requested info
hwinfo --mouse
15: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_46d_c50e_noserial_if0_logicaldev_input
  Unique ID: cLrx.r+G0OqTk0u7
  Parent ID: k4bc.Vz1tz+Eq6y6
  SysFS ID: /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0
  SysFS BusID: 1-2:1.0
  Hardware Class: mouse
  Model: "Logitech USB Receiver"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech Inc."
  Device: usb 0xc50e "USB Receiver"
  Revision: "25.00"
  Compatible to: int 0x0210 0x0028
  Driver: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse0)
  Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event2
  Device Number: char 13:63 (char 13:32)
  Speed: 1.5 Mbps
  Module Alias: "usb:v046DpC50Ed2500dc00dsc00dp00ic03isc01ip02"
  Driver Info #0:
    Buttons: 8
    Wheels: 2
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

## Path:            Hardware/Mouse/Console
## Description:     Console mouse configuration
## ServiceRestart:  gpm
#
## Type:        string(/dev/input/mice,/dev/psaux)
## Default:         ""
#
# The mouse device used on the console by gpm.
# The default value is generated by YaST.
#
MOUSEDEVICE=""

## Type:        string(imps2,ms,ms3,msc,mman,ps2,syn,synps2)
## Default:     ""
#
# The mouse type which defines the mouse protocol used by gpm for the mouse
# device in the variable MOUSEDEVICE
# The default value is generated by YaST
#
MOUSETYPE=""

## Type:        string
## Default:     ""
#
# You can define your own options to start gpm here. If the variable is empty
# then the gpm will start with the option "-m $MOUSEDEVICE -t $MOUSETYPE"
#
GPM_PARAM=""

## Type:        string(raw,imps2,ms,ms3,msc,mman,ps2,syn,synps2)
## Default:     ""
#
# Define type of repeating for gpm. This is usually needed when you want to
# use gpm together with XFree. All mouse data will be repeated in fifo
# /dev/gpmdata. Use "raw" for repeating same data as received by gpm.
#
GPM_REPEAT=""

# The full name of the attached mouse.
#
FULLNAME="Ignore Mouse -- regardless of if one exists"

# The YaST-internal identifier of the attached mouse.
#
YAST_MOUSE="ignore"

# Mouse device used for the X11 system.
#
XMOUSEDEVICE=""

# The number of buttons of the attached mouse.
#
BUTTONS="0"

# The number of wheels of the attached mouse.
#
WHEELS="0"

As far as the yast2 log...which one is it?
Does it have a particular name?
I have submitted bug #137361 because I find yast2 logs too difficult to submit.
Ioannis

I followed your advise and I solved the problem.
Yet why yast2 failed to auto-configure my mouse properly?
In 9.3 it configured it better.
I think that this might be a yast2 bug.
Ioannis

Yes, you're right. Ordinarily this works, but YaST sets BUTTONS to 0 and WHEELS to 0, this is not quite right, it looks like the mouse wasn't detected at all...

Marcus: Please look into this.

The discussion here is about GPM (The mouse for the console) right ?
Otherwise it wouldn't make sense to talk about /etc/sysconfig/mouse and
the entries there which solves your problem according to your answers

First of all you are right, in former times we automatically setup the
GPM parameters in /etc/sysconfig/mouse but for 10.0 I got a request not to
start the GPM configuration during a graphical installation because people
will not understand the difference between the GPM for the console and the
mouse they can see on the currently running X-Server. This was the reason
why it has been removed from a graphical installation session. In a text
based installation the GPM will be setup automatically like you are used too

As result GPM is NOT configured automatically on your system anymore. To
solve this you simply need to call:

  yast2 mouse

accept the detected setting or select a mouse from the list and save.
That's it. After this you can start GPM like you did it before.

   rcgpm start