[gentoo-user] off-topic: logitech mice (MX1000)

[gentoo-user] off-topic: logitech mice (MX1000)

[Allan Gottlieb]

It seems to me that this mouse sends two button events for some of the
"physical buttons".  For example moving the wheel to the left reports
   button press 13
   button press 6
   button release 6
   button release 13

Similar results for the many other buttons on the beast.

Is this what the device actually does or does it signify a faulty X
setup on my part?

I have the evdev driver in my kernel.

I use xorg.conf and have
Section "InputDevice"
    Identifier     "Logitech MX1000"
    Driver         "evdev"
    Option         "Device" "/dev/input/event2"
EndSection

gottlieb@allan /dev/input/by-id $ ls -l /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse 
lrwxrwxrwx 1 root root 9 Dec 15 11:20 /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse -> ../event2

thanks,
allan

[gentoo-user] Re: off-topic: logitech mice (MX1000)

[walt]

On 12/15/2009 11:11 AM, Allan Gottlieb wrote:
> It seems to me that this mouse sends two button events for some of the
> "physical buttons".  For example moving the wheel to the left reports
>     button press 13
>     button press 6
 > ...
>      Identifier     "Logitech MX1000"

To clarify a bit, what program are you using to identify the mouse events?

I looked up the Logitech MX 1000 on amazon.com, and the photos show only
one wheel, which is front-to-back, not left-to-right.  Am I getting this
wrong?

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Allan Gottlieb]

At Tue, 15 Dec 2009 18:09:15 -0800 walt <w41ter@gmail.com> wrote:

> On 12/15/2009 11:11 AM, Allan Gottlieb wrote:
>> It seems to me that this mouse sends two button events for some of the
>> "physical buttons".  For example moving the wheel to the left reports
>>     button press 13
>>     button press 6
>> ...
>>      Identifier     "Logitech MX1000"
>
> To clarify a bit, what program are you using to identify the mouse events?
>
> I looked up the Logitech MX 1000 on amazon.com, and the photos show only
> one wheel, which is front-to-back, not left-to-right.  Am I getting this
> wrong?

I used xev and also looked at emac's "view lossage".
The wheel rotates front-to-back, but can be pushed left or right.

If you look at the amazon page you can sort of see the left and right
arrows.

Thanks for any help you can give.
allan

[gentoo-user] Re: off-topic: logitech mice (MX1000)

[walt]

On 12/15/2009 10:05 PM, Allan Gottlieb wrote:
> At Tue, 15 Dec 2009 18:09:15 -0800 walt<w41ter@gmail.com>  wrote:
>
>> On 12/15/2009 11:11 AM, Allan Gottlieb wrote:
>>> It seems to me that this mouse sends two button events for some of the
>>> "physical buttons".  For example moving the wheel to the left reports
>>>      button press 13
>>>      button press 6
>>> ...
>>>       Identifier     "Logitech MX1000"
>>
>> To clarify a bit, what program are you using to identify the mouse events?
>>
>> I looked up the Logitech MX 1000 on amazon.com, and the photos show only
>> one wheel, which is front-to-back, not left-to-right.  Am I getting this
>> wrong?
>
> I used xev and also looked at emac's "view lossage".
> The wheel rotates front-to-back, but can be pushed left or right.
>
> If you look at the amazon page you can sort of see the left and right
> arrows.

I think a mouse that complicated would make me crazy.  The front-back wheel
rotation should map to buttons 4 and 5.  Does that part work correctly?

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Albert Hopkins]

On Wed, 2009-12-16 at 11:06 -0800, walt wrote:
> > If you look at the amazon page you can sort of see the left and
> right
> > arrows.
> 
> I think a mouse that complicated would make me crazy.  

There was a time when Windows and Mac users criticized X11 because it
had too many buttons (3).

Nowadays, Windows users seem to require 20 different buttons, wheels,
knobs, and whatever else they can throw on a pointer device, whereas
Macs seem to want to get rid of buttons altogether but require the user
to do cartwheels and other acrobatics with their fingers in order to do
a simple cut/paste.

FWIW, I have a Logitech mouse with a wheel that scrolls up and down,
presses down, and clicks left and right.  All seem to work fine, except
I don't use the latter as I haven't found any purpose for it although I
could possibly see it replacing ALT-Tab.  Nah... to confusing.

-a

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Allan Gottlieb]

At Wed, 16 Dec 2009 16:36:45 -0500 Albert Hopkins <marduk@letterboxes.org> wrote:

> On Wed, 2009-12-16 at 11:06 -0800, walt wrote:
>> > If you look at the amazon page you can sort of see the left and
>> right
>> > arrows.
>> 
>> I think a mouse that complicated would make me crazy.  
>
> There was a time when Windows and Mac users criticized X11 because it
> had too many buttons (3).
>
> Nowadays, Windows users seem to require 20 different buttons, wheels,
> knobs, and whatever else they can throw on a pointer device, whereas
> Macs seem to want to get rid of buttons altogether but require the user
> to do cartwheels and other acrobatics with their fingers in order to do
> a simple cut/paste.
>
> FWIW, I have a Logitech mouse with a wheel that scrolls up and down,
> presses down, and clicks left and right.  All seem to work fine, except
> I don't use the latter as I haven't found any purpose for it although I
> could possibly see it replacing ALT-Tab.  Nah... to confusing.

Right.  Mine (MX 1000) has those plus others (I inherited the mouse).
My problem is that several of these send multiple events (i.e. clicking
one physical button results in two button-down events for different X11
buttons and then the corresponding two button-up events).

I wonder how to handle this.  Actually, I have trouble believing it so
wonder if I have some config wrong, but mine are very simple configs.

allan

[gentoo-user] Re: off-topic: logitech mice (MX1000)

[walt]

On 12/16/2009 07:51 PM, Allan Gottlieb wrote:
> At Wed, 16 Dec 2009 16:36:45 -0500 Albert Hopkins<marduk@letterboxes.org>  wrote:
>
>> FWIW, I have a Logitech mouse with a wheel that scrolls up and down,
>> presses down, and clicks left and right.  All seem to work fine, except
>> I don't use the latter as I haven't found any purpose for it although I
>> could possibly see it replacing ALT-Tab.  Nah... to confusing.
>
> Right.  Mine (MX 1000) has those plus others (I inherited the mouse).
> My problem is that several of these send multiple events (i.e. clicking
> one physical button results in two button-down events for different X11
> buttons and then the corresponding two button-up events).

That's why I was wondering if just a simple front-or-back turn of the
wheel also produces two different button events for each notch -- you
should see only button-4 events for forward and only button-5 events for
backward.  (I actually see two button-4 events for each notch forward,
but the 'state' differs between the first and second event.)

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Michael Schreckenbauer]

Am Donnerstag, 17. Dezember 2009 16:07:46 schrieb walt:
> That's why I was wondering if just a simple front-or-back turn of the
> wheel also produces two different button events for each notch -- you
> should see only button-4 events for forward and only button-5 events for
> backward.  (I actually see two button-4 events for each notch forward,
> but the 'state' differs between the first and second event.)

You get one event for ButtonPress and one event for ButtonRelease

Regards
Michael

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Allan Gottlieb]

At Thu, 17 Dec 2009 16:30:58 +0100 Michael Schreckenbauer <grimlog@gmx.de> wrote:

> Am Donnerstag, 17. Dezember 2009 16:07:46 schrieb walt:
>> That's why I was wondering if just a simple front-or-back turn of the
>> wheel also produces two different button events for each notch -- you
>> should see only button-4 events for forward and only button-5 events for
>> backward.  (I actually see two button-4 events for each notch forward,
>> but the 'state' differs between the first and second event.)
>
> You get one event for ButtonPress and one event for ButtonRelease

Correct.  Remember that on the left or right motion I received two
presses and two releases for two different "X-buttons".

This same thing happens for other physical buttons on the beast.
Fortunately the two main buttons give just button 1 and button 3
respectively.
Another button just gives button 2 and the wheel rotation give button 4
in one direction and 5 in the other.  So it does work as a wheeled mouse
if I ignore all the other physical buttons.

allan

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Albert Hopkins]

On Wed, 2009-12-16 at 22:51 -0500, Allan Gottlieb wrote:
> Right.  Mine (MX 1000) has those plus others (I inherited the mouse).
> My problem is that several of these send multiple events (i.e.
> clicking
> one physical button results in two button-down events for different
> X11
> buttons and then the corresponding two button-up events).
> 
> I wonder how to handle this.  Actually, I have trouble believing it so
> wonder if I have some config wrong, but mine are very simple configs.
> 
> allan
> 

I don't have the mouse with me to check, but ran xev on it last night
and only saw one event for left-right wheel (button6 and button7 iirc).
Could it be perhaps there are 2 (X11) drivers listneing on this device
or are you using GPM or something like that?

-a

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Allan Gottlieb]

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

At Thu, 17 Dec 2009 11:49:43 -0500 Albert Hopkins <marduk@letterboxes.org> wrote:

> On Wed, 2009-12-16 at 22:51 -0500, Allan Gottlieb wrote:
>> Right.  Mine (MX 1000) has those plus others (I inherited the mouse).
>> My problem is that several of these send multiple events (i.e.
>> clicking
>> one physical button results in two button-down events for different
>> X11
>> buttons and then the corresponding two button-up events).
>> 
>> I wonder how to handle this.  Actually, I have trouble believing it so
>> wonder if I have some config wrong, but mine are very simple configs.
>> 
>> allan
>> 
>
> I don't have the mouse with me to check, but ran xev on it last night
> and only saw one event for left-right wheel (button6 and button7 iirc).
> Could it be perhaps there are 2 (X11) drivers listneing on this device
> or are you using GPM or something like that?

That sounds promising, but I see no evidence in the log file.
I assume this line
  (==) NVIDIA(0): Silken mouse enabled
doesn't count as the NVIDIA is a display driver and I see nothing
relevent in the doc that came with it.

I do have two InputDevice sections in xorg.conf about the mouse, but my
ServerLayout only mentions one.  I attach both my log and xorg.conf
below.

Thanks for helping.
allan


[-- Attachment #2: xorg.conf --]
[-- Type: text/plain, Size: 4411 bytes --]

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder58)  Thu Jun  5 00:08:24 PDT 2008

Section "ServerLayout"
    Identifier     "Nvidia / Logitech layout"
    Screen         "Nvidia screen" 0 0
    InputDevice    "Logitech MX1000" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "ServerLayout"
    Identifier     "Nvidia layout"
    Screen         "Nvidia screen" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen         0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath      "/usr/lib64/xorg/modules"
    FontPath        "/usr/share/fonts/dejavu/"
    FontPath        "/usr/share/fonts/corefonts/"
    FontPath        "/usr/share/fonts/misc/"
    FontPath        "/usr/share/fonts/ttf-bitstream-vera/"
    FontPath        "/usr/share/fonts/Type1/"
    FontPath        "/usr/share/fonts/100dpi/"
    FontPath        "/usr/share/fonts/75dpi/"
EndSection

#Section "ServerFlags"
#    Option         "AutoAddDevices"    "false"
#EndSection

Section "Module"
    Load           "glx"
    Load           "record"
    Load           "dbe"
    Load           "xtrap"
# AJG # Load  "dri"
    Load           "extmod"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mice"
    Option         "ZAxisMapping" "4 5 6 7"
EndSection

Section "InputDevice"
    Identifier     "Logitech MX1000"
    Driver         "evdev"
    Option         "Device" "/dev/input/event2"
EndSection

Section "Monitor"
    Identifier     "Dell wfp 3008"
    VendorName     "Dell"
    ModelName      "wfp 3008"
    VertRefresh     60.0
    ModeLine       "2560x1600" 268 2560 2608 2640 2720 1600 1603 1609 1646
    Option         "dpms"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Vendor0"
    ModelName      "Model0"
EndSection

Section "Device"
    Identifier     "Nvidia Quadro FX1700"
    Driver         "nvidia"
EndSection

Section "Device"

        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "SWcursor"           	# [<bool>]
        #Option     "HWcursor"           	# [<bool>]
        #Option     "NoAccel"            	# [<bool>]
        #Option     "ShadowFB"           	# [<bool>]
        #Option     "UseFBDev"           	# [<bool>]
        #Option     "Rotate"             	# [<str>]
        #Option     "VideoKey"           	# <i>
        #Option     "FlatPanel"          	# [<bool>]
        #Option     "FPDither"           	# [<bool>]
        #Option     "CrtcNumber"         	# <i>
        #Option     "FPScale"            	# [<bool>]
        #Option     "FPTweak"            	# <i>
        #Option     "DualHead"           	# [<bool>]
    Identifier     "Card0"
    Driver         "nv"
    VendorName     "nVidia Corporation"
    BoardName      "Unknown Board"
    BusID          "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier     "Nvidia screen"
    Device         "Nvidia Quadro FX1700"
    Monitor        "Dell wfp 3008"
    DefaultDepth    24
    SubSection     "Display"
        Viewport    0 0
        Depth       24
        Modes      "2560x1600"
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Viewport    0 0
        Depth       1
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       4
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       8
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       15
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       16
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       24
    EndSubSection
EndSection


[-- Attachment #3: Xorg.0.log --]
[-- Type: text/plain, Size: 11134 bytes --]


X.Org X Server 1.6.5
Release Date: 2009-10-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.31-gentoo-r6-ajg-2 x86_64 
Current Operating System: Linux allan 2.6.31-gentoo-r6-ajg-2 #2 SMP Thu Dec 10 11:39:39 EST 2009 x86_64
Build Date: 10 December 2009  12:20:56PM
 
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 17 09:39:02 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Nvidia / Logitech layout"
(**) |-->Screen "Nvidia screen" (0)
(**) |   |-->Monitor "Dell wfp 3008"
(**) |   |-->Device "Nvidia Quadro FX1700"
(**) |-->Input Device "Logitech MX1000"
(**) |-->Input Device "Keyboard0"
(==) Not automatically adding devices
(==) Not automatically enabling devices
(**) FontPath set to:
	/usr/share/fonts/dejavu/,
	/usr/share/fonts/corefonts/,
	/usr/share/fonts/misc/,
	/usr/share/fonts/ttf-bitstream-vera/,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/,
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/
(**) ModulePath set to "/usr/lib64/xorg/modules"
(II) Loader magic: 0xf20
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.4
	X.Org Video Driver: 5.0
	X.Org XInput driver : 4.0
	X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:1:0:0) 10de:040f:10de:049a nVidia Corporation G84 [Quadro FX 1700] rev 161, Mem @ 0xfc000000/16777216, 0xc0000000/536870912, 0xfa000000/33554432, I/O @ 0x0000dc80/128, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
	Module class: X.Org Server Extension
(II) NVIDIA GLX Module  185.18.36  Fri Aug 14 18:27:24 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib64/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "xtrap"
(WW) Warning, couldn't open module xtrap
(II) UnloadModule: "xtrap"
(EE) Failed to load module "xtrap" (module does not exist, 0)
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dri"
(WW) Warning, couldn't open module dri
(II) UnloadModule: "dri"
(EE) Failed to load module "dri" (module does not exist, 0)
(II) LoadModule: "dri2"
(WW) Warning, couldn't open module dri2
(II) UnloadModule: "dri2"
(EE) Failed to load module "dri2" (module does not exist, 0)
(II) LoadModule: "nvidia"
(II) Loading /usr/lib64/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
	Module class: X.Org Video Driver
(II) LoadModule: "evdev"
(II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 2.3.1
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 4.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib64/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.4.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 4.0
(II) NVIDIA dlloader X Driver  185.18.36  Fri Aug 14 17:51:02 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib64/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib64/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
	compiled for 1.6.5, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0):     enabled.
(II) NVIDIA(0): NVIDIA GPU Quadro FX 1700 (G84GL) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 60.84.63.00.17
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on Quadro FX 1700 at PCI:1:0:0:
(--) NVIDIA(0):     Dell (DFP-1)
(--) NVIDIA(0): Dell (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Dell (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):     "2560x1600"
(II) NVIDIA(0): Virtual screen size determined to be 2560 x 1600
(--) NVIDIA(0): DPI set to (100, 99); computed from "UseEdidDpi" X config
(--) NVIDIA(0):     option
(WW) NVIDIA(0): UBB is incompatible with the Composite extension.  Disabling
(WW) NVIDIA(0):     UBB.
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
	[0] -1	0	0xffffffff - 0xffffffff (0x1) MX[B]
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x00000000 (0x1) IX[B]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0):     configuration option may not be set correctly.  When the
(II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
(II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
(II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0):     Config Options in the README.
(II) NVIDIA(0): Setting mode "2560x1600"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
(**) Option "CorePointer"
(**) Logitech MX1000: always reports core events
(**) Logitech MX1000: Device: "/dev/input/event2"
(II) Logitech MX1000: Found 20 mouse buttons
(II) Logitech MX1000: Found scroll wheel(s)
(II) Logitech MX1000: Found relative axes
(II) Logitech MX1000: Found x and y relative axes
(II) Logitech MX1000: Configuring as mouse
(**) Logitech MX1000: YAxisMapping: buttons 4 and 5
(**) Logitech MX1000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech MX1000" (type: MOUSE)
(**) Logitech MX1000: (accel) keeping acceleration scheme 1
(**) Logitech MX1000: (accel) filter chain progression: 2.00
(**) Logitech MX1000: (accel) filter stage 0: 20.00 ms
(**) Logitech MX1000: (accel) set acceleration profile 0
(II) Logitech MX1000: initialized for relative axes.
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "XkbRules" "base"
(**) Keyboard0: XkbRules: "base"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)

[gentoo-user] Re: off-topic: logitech mice (MX1000)

[walt]

On 12/17/2009 01:23 PM, Allan Gottlieb wrote:

>
> I do have two InputDevice sections in xorg.conf about the mouse, but my
> ServerLayout only mentions one.  I attach both my log and xorg.conf
> below.

If you are using evdev (and you are) you should delete (or comment out)
anything to do with Input from your xorg.conf, e.g. these sections:

Section "InputDevice"
     Identifier     "Keyboard0"
     Driver         "kbd"
EndSection

Section "InputDevice"
     Identifier     "Mouse0"
     Driver         "mouse"
     Option         "Protocol" "auto"
     Option         "Device" "/dev/input/mice"
     Option         "ZAxisMapping" "4 5 6 7"
EndSection

and also remove/comment these lines from ServerLayout:
     InputDevice    "Mouse0" "CorePointer"
     InputDevice    "Keyboard0" "CoreKeyboard"

The evdev driver is intended to replace *all* of that stuff.

BTW, I remember having a section like this in my xorg.conf, but
I don't have it any longer and I don't think you really need it:
Section "InputDevice"
     Identifier     "Logitech MX1000"
     Driver         "evdev"
     Option         "Device" "/dev/input/event2"
EndSection

I think that the evdev driver is loaded by default now, so you
don't need to mention it in xorg.conf.

Caveat:  I needed to add /etc/hal/fdi/policy/10-x11-logitech.fdi
to replace two lines in my xorg.conf because my mouse has four
buttons and no wheel.  You obviously don't have that problem, so
I think your mouse should Just Work without any extra fdi files.

Re: [gentoo-user] Re: off-topic: logitech mice (MX1000)

[Allan Gottlieb]

At Thu, 17 Dec 2009 15:34:51 -0800 walt <w41ter@gmail.com> wrote:

> On 12/17/2009 01:23 PM, Allan Gottlieb wrote:
>
>>
>> I do have two InputDevice sections in xorg.conf about the mouse, but my
>> ServerLayout only mentions one.  I attach both my log and xorg.conf
>> below.
>
> If you are using evdev (and you are) you should delete (or comment out)
> anything to do with Input from your xorg.conf, e.g. these sections:
>
> Section "InputDevice"
>     Identifier     "Keyboard0"
>     Driver         "kbd"
> EndSection
>
> Section "InputDevice"
>     Identifier     "Mouse0"
>     Driver         "mouse"
>     Option         "Protocol" "auto"
>     Option         "Device" "/dev/input/mice"
>     Option         "ZAxisMapping" "4 5 6 7"
> EndSection
>
> and also remove/comment these lines from ServerLayout:
>     InputDevice    "Mouse0" "CorePointer"
>     InputDevice    "Keyboard0" "CoreKeyboard"
>
> The evdev driver is intended to replace *all* of that stuff.

Yes, but those lines are effectively "commented out".
I have three ServerLayout sections but only the first counts (see
excerpt from the xorg.conf man page below).  The first ServerLayout
section (the "active one") references the logitech mouse and not mouse0
so the mouse driver is not loaded at all.

I do specify the keyboard, but that is working fine.

> BTW, I remember having a section like this in my xorg.conf, but
> I don't have it any longer and I don't think you really need it:
> Section "InputDevice"
>     Identifier     "Logitech MX1000"
>     Driver         "evdev"
>     Option         "Device" "/dev/input/event2"
> EndSection
>
> I think that the evdev driver is loaded by default now, so you
> don't need to mention it in xorg.conf.
>
> Caveat:  I needed to add /etc/hal/fdi/policy/10-x11-logitech.fdi
> to replace two lines in my xorg.conf because my mouse has four
> buttons and no wheel.  You obviously don't have that problem, so
> I think your mouse should Just Work without any extra fdi files.

I do not use the hal stuff.  I was scared off by the horror stories
reported here.  Perhaps this summer I will give it a go.

thanks again for helping,
allan

SERVERLAYOUT SECTION
       The config file may have multiple ServerLayout sections.  A
       "server layout" represents the binding of one or more screens
       (Screen sections) and one or more input devices (InputDevice
       sections) to form a complete configuration.  In multi-head
       configurations, it also specifies the relative layout of the
       heads.  A ServerLayout section is considered "active" if it is
       referenced by the -layout command line option or by an Option
       "DefaultServerLayout" entry in the ServerFlags section (the
       former takes precedence over the latter).  If those options are
       not used, the first ServerLayout section found in the config file
       is con- sidered the active one.  If no ServerLayout sections are
       present, the single active screen and two active (core) input
       devices are selected as described in the relevant sections above.

Re: [gentoo-user] off-topic: logitech mice (MX1000)

[John Campbell]

On 12/15/2009 11:11 AM, Allan Gottlieb wrote:
> It seems to me that this mouse sends two button events for some of the
> "physical buttons".  For example moving the wheel to the left reports
>    button press 13
>    button press 6
>    button release 6
>    button release 13
> 
> Similar results for the many other buttons on the beast.
> 
> Is this what the device actually does or does it signify a faulty X
> setup on my part?
> 
> I have the evdev driver in my kernel.
> 
> I use xorg.conf and have
> Section "InputDevice"
>     Identifier     "Logitech MX1000"
>     Driver         "evdev"
>     Option         "Device" "/dev/input/event2"
> EndSection
> 
> gottlieb@allan /dev/input/by-id $ ls -l /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse 
> lrwxrwxrwx 1 root root 9 Dec 15 11:20 /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse -> ../event2

As I recall, the fix for this problem is a sys-adm/lomoco.

Logitech mice actually produce those double events...  lomoco allows you
tell the mouse to stop.  I've got a udev rule for it, I think lomoco put
it there, but I've had logitech MX mice for years and lomoco is a fork
of a fork and may no longer contain the udev script.

You also might look into imwheel from the Mandrake distrabution as it
contains patches to deal with more than 10 buttons.

Re: [gentoo-user] off-topic: logitech mice (MX1000)

[Allan Gottlieb]

At Sun, 20 Dec 2009 21:04:12 -0800 John Campbell <jdc.rpv@cox.net> wrote:

> On 12/15/2009 11:11 AM, Allan Gottlieb wrote:
>> It seems to me that this mouse sends two button events for some of the
>> "physical buttons".  For example moving the wheel to the left reports
>>    button press 13
>>    button press 6
>>    button release 6
>>    button release 13
>> 
>> Similar results for the many other buttons on the beast.
>> 
>> Is this what the device actually does or does it signify a faulty X
>> setup on my part?
>> 
>> I have the evdev driver in my kernel.
>> 
>> I use xorg.conf and have
>> Section "InputDevice"
>>     Identifier     "Logitech MX1000"
>>     Driver         "evdev"
>>     Option         "Device" "/dev/input/event2"
>> EndSection
>> 
>> gottlieb@allan /dev/input/by-id $ ls -l /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse 
>> lrwxrwxrwx 1 root root 9 Dec 15 11:20 /dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse -> ../event2
>
> As I recall, the fix for this problem is a sys-adm/lomoco.
>
> Logitech mice actually produce those double events...  lomoco allows you
> tell the mouse to stop.  I've got a udev rule for it, I think lomoco put
> it there, but I've had logitech MX mice for years and lomoco is a fork
> of a fork and may no longer contain the udev script.
>
> You also might look into imwheel from the Mandrake distrabution as it
> contains patches to deal with more than 10 buttons.

Magnificent!! I did really think the mouse could be sending
button events for two different logical buttons when only one physical
button was pushed.  That got me looking at xorg.conf to see where I
screwed up.  But, as you said, the MX mice do send events for two
buttons.

As you also said lomoco fixes it.

"sudo lomoco --nosms" is now in my startup script.

Thank you very much !

allan