hwinfo --mouse   

17: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_46d_c041_noserial_if0_logicaldev_input
  Unique ID: hSuP.xCkw_U0ZPy7
  Parent ID: pBe4.HuT0cES8p82
  SysFS ID: /devices/pci0000:00/0000:00:02.1/usb2/2-2/2-2:1.0
  SysFS BusID: 2-2:1.0
  Hardware Class: mouse
  Model: "Logitech USB Gaming Mouse"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech Inc."
  Device: usb 0xc041 "USB Gaming Mouse"
  Revision: "46.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: 12 Mbps
  Module Alias: "usb:v046DpC041d4600dc00dsc00dp00ic03isc01ip02"
  Driver Info #0:
    Buttons: 8
    Wheels: 2
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #16 (Hub)

Stefan what about the udev rules ? You mentioned we will include
such rules but currently we don't ? Assign the bug back to me if
I can rely on the rules to make use of the evdev driver

Thanks

i have no clue about udev at all. Probably Christian or Hannes can help on this one

Why don't you ask mister udev himself?

Further, Marcus, every package may add special rules to /etc/udev/rules.d.

What does:
  find /dev/input/
print?

It shows the following:

/dev/input/
/dev/input/event2
/dev/input/by-path
/dev/input/by-path/pci-0000:00:02.1-usb-0:2:1.0-event-mouse
/dev/input/by-path/pci-0000:00:02.1-usb-0:2:1.0-mouse
/dev/input/by-id
/dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse
/dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-mouse
/dev/input/mouse0
/dev/input/mice
/dev/input/event0
/dev/input/event1

Marcus,
  /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse
is created by the generic "persistent input rules". That should work the same way like the custom rule mentioned here.

ok, so we should probably add the rules for mice to the X packages? or to the Basesystem? Not my area anyway :-)

put Stefan to CC

Ok. What needs to be done exactly, Seife? I can add some files to xorg-x11-driver-input, if this helps.

I have no idea. Maybe we should just get such a device and try it.
I am not sure if the special udev rules are needed at all - shouldn't the kernel abstract this all for us?

Yes, I think if we need a special SaX2 configuration for this device anyway
(driver "evdev", device "/dev/input/g5") - probably by a profile - it would make sense to add this special udev rule to SaX2 as well.

Finaly, I've got it working! The following works for me unter SL10.1:

Section "InputDevice"
    Identifier     "Mouse[1]"
    Driver         "evdev"
    Option         "Protocol" "event"
    Option         "SendCoreEvents" "true"
    Option         "Buttons" "8"
    Option         "Device" "/dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse"
    Option         "Name" "Logitech USB Gaming Mouse"
    Option         "Vendor" "Sysp"
    Option         "ZAxisMapping" "7 8"
EndSection

This was mentioned under http://www.unixboard.de/vb3/showthread.php?t=20028 and should also work for Logitech MX 500 and MX 1000 mice.

yes I see that /dev/input listed this device as:

   /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse

but hwinfo doesn't list this device. How can I check that the device
listed in hwinfo for example:

  /dev/input/event3

is mapped to 

  /dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse

? Added snwint to CC
  
  

Hm, was indeed missing. Fixed in hwinfo-13.2.

I added support for the evdev driver into sax2. currently only
one device is using the driver because it's a very new driver.

support has been added for the following device:

   0x046d : 0xc041 : logitech-Gaming

if evdev works reliable we can enhance the Input map