Turning off LEDs on MSI GM10 gaming mouse

[Robert Moskowitz]

I got this mouse for its very light touch.  I developed a pinched nerve 
and it hurts to mouse...

Pricy for me at $30, but the price of heath?

Anyway I hate the LEDs.  I put tape over their big LED, but the roller 
has its LED.  My search on the web says that the LEDs can be turned of 
with the system software.  Interestingly enough, my Windows7 system can't...

Fedora 28 and 29-beta do see it:

MSI GM10 MSI GM10 Gaming Mouse as 
/devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse [MSI 
GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as 
/devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as 
/devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9

But Xfce mouse settings does not give me any option to turn off the 
LEDs.  I would be happy with a command line command for this one.

[Samuel Sieb]

On 9/20/18 8:48 AM, Robert Moskowitz wrote:
>  Anyway I hate the LEDs.  I put tape over their big LED, but the
> roller 
>  has its LED.  My search on the web says that the LEDs can be turned of 
>  with the system software.  Interestingly enough, my Windows7 system 
>  can't...
>  
>  Fedora 28 and 29-beta do see it:
>  
>  MSI GM10 MSI GM10 Gaming Mouse as 
>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
>
>  
>  hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse [MSI 
>  GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
>  input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as 
>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
>
>  
>  input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as 
>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
>  
Look in /proc/bus/input/devices and copy all the sections that 
correspond to the mouse.  They should all have the same Phys= line 
pointing to the same usb device.

[Robert Moskowitz]

On 9/20/18 12:32 PM, Samuel Sieb wrote:
>  On 9/20/18 8:48 AM, Robert Moskowitz wrote:
> > Anyway I hate the LEDs.  I put tape over their big LED, but the 
> > roller has its LED.  My search on the web says that the LEDs can be 
> > turned of with the system software. Interestingly enough, my Windows7 
> > system can't...
> >
> > Fedora 28 and 29-beta do see it:
> >
> > MSI GM10 MSI GM10 Gaming Mouse as 
> >
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
>
> >
> > hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse 
> > [MSI GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
> > input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as 
> >
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
>
> >
> > input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as 
> >
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
>
>
>
>  Look in /proc/bus/input/devices and copy all the sections that 
>  correspond to the mouse.  They should all have the same Phys= line 
>  pointing to the same usb device. 
Here is what I am seeingon my F28 system:

I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
N: Name="MSI GM10 MSI GM10 Gaming Mouse"
P: Phys=usb-0000:00:12.0-3.4/input0
S: 
Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1
0.0016/input/input63
U: Uniq=
H: Handlers=mouse1 event7
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
N: Name="MSI GM10 MSI GM10 Gaming Mouse Keyboard"
P: Phys=usb-0000:00:12.0-3.4/input1
S: 
Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
0.0017/input/input65
U: Uniq=
H: Handlers=sysrq kbd event9
B: PROP=0
B: EV=100013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10

I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
N: Name="MSI GM10 MSI GM10 Gaming Mouse Consumer Control"
P: Phys=usb-0000:00:12.0-3.4/input1
S: 
Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
0.0017/input/input66
U: Uniq=
H: Handlers=kbd event17
B: PROP=0
B: EV=1f
B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000 
677bfad9415fe
d 9ed68000004400 10000002
B: REL=40
B: ABS=100000000
B: MSC=10

So I am looking for a command that turns off the LEDs on the mouse...

thanks

[Rick Stevens]

On 9/20/18 9:42 AM, Robert Moskowitz wrote:
>  
>  
>  On 9/20/18 12:32 PM, Samuel Sieb wrote:
> > On 9/20/18 8:48 AM, Robert Moskowitz wrote:
> >> Anyway I hate the LEDs.  I put tape over their big LED, but the
> >> roller has its LED.  My search on the web says that the LEDs can be
> >> turned of with the system software. Interestingly enough, my Windows7
> >> system can't...
> >>
> >> Fedora 28 and 29-beta do see it:
> >>
> >> MSI GM10 MSI GM10 Gaming Mouse as
> >>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
> >>
> >> hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse
> >> [MSI GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
> >> input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as
> >>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
> >>
> >> input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as
> >>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
> >
> >
> >
> > Look in /proc/bus/input/devices and copy all the sections that
> > correspond to the mouse.  They should all have the same Phys= line
> > pointing to the same usb device.
>  
>  Here is what I am seeingon my F28 system:
>  
>  I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
>  N: Name="MSI GM10 MSI GM10 Gaming Mouse"
>  P: Phys=usb-0000:00:12.0-3.4/input0
>  S:
>  Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1
>  
>  0.0016/input/input63
>  U: Uniq=
>  H: Handlers=mouse1 event7
>  B: PROP=0
>  B: EV=17
>  B: KEY=1f0000 0 0 0 0
>  B: REL=103
>  B: MSC=10
>  
>  I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
>  N: Name="MSI GM10 MSI GM10 Gaming Mouse Keyboard"
>  P: Phys=usb-0000:00:12.0-3.4/input1
>  S:
>  Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
>  
>  0.0017/input/input65
>  U: Uniq=
>  H: Handlers=sysrq kbd event9
>  B: PROP=0
>  B: EV=100013
>  B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
>  B: MSC=10
>  
>  I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
>  N: Name="MSI GM10 MSI GM10 Gaming Mouse Consumer Control"
>  P: Phys=usb-0000:00:12.0-3.4/input1
>  S:
>  Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
>  
>  0.0017/input/input66
>  U: Uniq=
>  H: Handlers=kbd event17
>  B: PROP=0
>  B: EV=1f
>  B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000
>  677bfad9415fe
>  d 9ed68000004400 10000002
>  B: REL=40
>  B: ABS=100000000
>  B: MSC=10
>  
>  So I am looking for a command that turns off the LEDs on the mouse...
>  
Uhm, try "xinput --list". Find the device that represents the mouse.
For example, I'm using a Logitech Wave keyboard and mouse, so I see:

[root@prophead ~]# xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver                   	id=11	[slave  pointer  (2)]
⎜   ↳ TigerVNC pointer                        	id=15	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ Logitech USB Receiver                   	id=10	[slave  keyboard (3)]
    ↳ gspca_zc3xx                             	id=12	[slave  keyboard (3)]
    ↳ USB Sound Device                        	id=13	[slave  keyboard (3)]
    ↳ Logitech USB Receiver                   	id=14	[slave  keyboard (3)]
    ↳ TigerVNC keyboard                       	id=16	[slave  keyboard (3)]

Under the "Virtual core pointer" section, I see the USB receiver for the
mouse as device 11.

Once you find the device, try "xinput --list-props <device-number>" to
get a list of its properties and post that. Perhaps we can find
something that can be buggered via "xinput --set-prop" that'd turn
them off. Can't swear to it--this is a wild stab in the dark.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-    Admitting you have a problem is the first step toward getting   -
-    medicated for it.      -- Jim Evarts (http://www.TopFive.com)   -
----------------------------------------------------------------------

[Samuel Sieb]

On 9/20/18 9:42 AM, Robert Moskowitz wrote:
>  Here is what I am seeingon my F28 system:
>  
>  I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
>  N: Name="MSI GM10 MSI GM10 Gaming Mouse"
>  P: Phys=usb-0000:00:12.0-3.4/input0
>  S: 
>  Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1 
>  
>  0.0016/input/input63
>  U: Uniq=
>  H: Handlers=mouse1 event7
>  B: PROP=0
>  B: EV=17
>  B: KEY=1f0000 0 0 0 0
>  B: REL=103
>  B: MSC=10 
[...]

>  0.0017/input/input65
>  U: Uniq=
>  H: Handlers=sysrq kbd event9
>  B: PROP=0
>  B: EV=100013
>  B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
>  B: MSC=10 
[...]

>  0.0017/input/input66
>  U: Uniq=
>  H: Handlers=kbd event17
>  B: PROP=0
>  B: EV=1f
>  B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000 
>  677bfad9415fe
>  d 9ed68000004400 10000002
>  B: REL=40
>  B: ABS=100000000
>  B: MSC=10
>  
>  So I am looking for a command that turns off the LEDs on the mouse... 
That's quite the device.  There aren't any LED controls there.  I looked 
up the device and I'm assuming it's this one:
https://www.msi.com/Gaming-gear/Clutch-GM10-GAMING-MOUSE
I can't find any indication that the LEDs are software controlled in any 
way.  They only change according to the DPI setting.

[Robert Moskowitz]

On 9/20/18 2:30 PM, Samuel Sieb wrote:
>  On 9/20/18 9:42 AM, Robert Moskowitz wrote:
> > Here is what I am seeingon my F28 system:
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse"
> > P: Phys=usb-0000:00:12.0-3.4/input0
> > S: 
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1 
> >
> > 0.0016/input/input63
> > U: Uniq=
> > H: Handlers=mouse1 event7
> > B: PROP=0
> > B: EV=17
> > B: KEY=1f0000 0 0 0 0
> > B: REL=103
> > B: MSC=10
>
>  [...]
>
> > 0.0017/input/input65
> > U: Uniq=
> > H: Handlers=sysrq kbd event9
> > B: PROP=0
> > B: EV=100013
> > B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
> > B: MSC=10
>
>  [...]
>
> > 0.0017/input/input66
> > U: Uniq=
> > H: Handlers=kbd event17
> > B: PROP=0
> > B: EV=1f
> > B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000 
> > 677bfad9415fe
> > d 9ed68000004400 10000002
> > B: REL=40
> > B: ABS=100000000
> > B: MSC=10
> >
> > So I am looking for a command that turns off the LEDs on the mouse...
>
>  That's quite the device.  There aren't any LED controls there.  I 
>  looked up the device and I'm assuming it's this one:
>  https://www.msi.com/Gaming-gear/Clutch-GM10-GAMING-MOUSE
>  I can't find any indication that the LEDs are software controlled in 
>  any way.  They only change according to the DPI setting. 
That's the one.   I got it for its 'light touch', as I have developed a 
pinch nerve and mousing HURTS!

I bought it locally (Micro Center), then found out about the LEDs. I did 
some googling and found an exchange on Amazon comments about it that 
claim they turned off the LEDs via software.

And, yes, pushing the DPI button changes to colors, but does not turn 
them off.

:(

Can anyone recommend a mouse with a REAL light touch and for the scroll 
wheel as well.  Especially the scroll wheel.  I am about to take this 
mouse back.  :(

thanks

[Robert Moskowitz]

On 9/20/18 1:56 PM, Rick Stevens wrote:
>  On 9/20/18 9:42 AM, Robert Moskowitz wrote:
> >
> > On 9/20/18 12:32 PM, Samuel Sieb wrote:
> >> On 9/20/18 8:48 AM, Robert Moskowitz wrote:
> >>> Anyway I hate the LEDs.  I put tape over their big LED, but the
> >>> roller has its LED.  My search on the web says that the LEDs can be
> >>> turned of with the system software. Interestingly enough, my Windows7
> >>> system can't...
> >>>
> >>> Fedora 28 and 29-beta do see it:
> >>>
> >>> MSI GM10 MSI GM10 Gaming Mouse as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
> >>>
> >>> hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse
> >>> [MSI GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
> >>> input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
> >>>
> >>> input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
> >>
> >>
> >> Look in /proc/bus/input/devices and copy all the sections that
> >> correspond to the mouse.  They should all have the same Phys= line
> >> pointing to the same usb device.
> > Here is what I am seeingon my F28 system:
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse"
> > P: Phys=usb-0000:00:12.0-3.4/input0
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1
> >
> > 0.0016/input/input63
> > U: Uniq=
> > H: Handlers=mouse1 event7
> > B: PROP=0
> > B: EV=17
> > B: KEY=1f0000 0 0 0 0
> > B: REL=103
> > B: MSC=10
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse Keyboard"
> > P: Phys=usb-0000:00:12.0-3.4/input1
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >
> > 0.0017/input/input65
> > U: Uniq=
> > H: Handlers=sysrq kbd event9
> > B: PROP=0
> > B: EV=100013
> > B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
> > B: MSC=10
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse Consumer Control"
> > P: Phys=usb-0000:00:12.0-3.4/input1
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >
> > 0.0017/input/input66
> > U: Uniq=
> > H: Handlers=kbd event17
> > B: PROP=0
> > B: EV=1f
> > B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000
> > 677bfad9415fe
> > d 9ed68000004400 10000002
> > B: REL=40
> > B: ABS=100000000
> > B: MSC=10
> >
> > So I am looking for a command that turns off the LEDs on the mouse...
>  Uhm, try "xinput --list". Find the device that represents the mouse. 
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave 
pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                  id=16    [slave 
pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                       id=17    [slave 
pointer  (2)]
⎜   ↳ MSI GM10 MSI GM10 Gaming Mouse Consumer Control    id=12 [slave  
pointer
  (2)]
⎜   ↳ MSI GM10 MSI GM10 Gaming Mouse              id=20    [slave 
pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
     ↳ Virtual core XTEST keyboard                 id=5    [slave 
keyboard (3)]
     ↳ Power Button                                id=6    [slave 
keyboard (3)]
     ↳ Video Bus                                   id=7    [slave 
keyboard (3)]
     ↳ Power Button                                id=8    [slave 
keyboard (3)]
     ↳ Sleep Button                                id=9    [slave 
keyboard (3)]
     ↳ Integrated Camera                           id=14    [slave 
keyboard (3)]
     ↳ AT Translated Set 2 keyboard                id=15    [slave 
keyboard (3)]
     ↳ ThinkPad Extra Buttons                      id=18    [slave 
keyboard (3)]
     ↳   USB Keyboard                              id=10    [slave 
keyboard (3)]
     ↳   USB Keyboard System Control               id=11    [slave 
keyboard (3)]
     ↳ MSI GM10 MSI GM10 Gaming Mouse Consumer Control    id=13 [slave  
keyboard
  (3)]
     ↳ MSI GM10 MSI GM10 Gaming Mouse Keyboard     id=19    [slave 
keyboard (3)]


>  Once you find the device, try "xinput --list-props
> <device-number>" to
>  get a list of its properties and post that. Perhaps we can find
>  something that can be buggered via "xinput --set-prop" that'd turn
>  them off. Can't swear to it--this is a wild stab in the dark. 
$ xinput --list-props 12
Device 'MSI GM10 MSI GM10 Gaming Mouse Consumer Control':
     Device Enabled (141):    1
     Coordinate Transformation Matrix (143):    1.000000, 0.000000, 
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
     libinput Natural Scrolling Enabled (276):    0
     libinput Natural Scrolling Enabled Default (277):    0
     libinput Send Events Modes Available (261):    1, 0
     libinput Send Events Mode Enabled (262):    0, 0
     libinput Send Events Mode Enabled Default (263):    0, 0
     Device Node (264):    "/dev/input/event17"
     Device Product ID (265):    3504, 3344
     libinput Drag Lock Buttons (278):    <no items>
     libinput Horizontal Scroll Enabled (279):    1

$ xinput --list-props 20
Device 'MSI GM10 MSI GM10 Gaming Mouse':
     Device Enabled (141):    1
     Coordinate Transformation Matrix (143):    1.000000, 0.000000, 
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
     libinput Natural Scrolling Enabled (276):    0
     libinput Natural Scrolling Enabled Default (277):    0
     libinput Scroll Methods Available (280):    0, 0, 1
     libinput Scroll Method Enabled (281):    0, 0, 0
     libinput Scroll Method Enabled Default (282):    0, 0, 0
     libinput Button Scrolling Button (283):    2
     libinput Button Scrolling Button Default (284):    2
     libinput Middle Emulation Enabled (285):    0
     libinput Middle Emulation Enabled Default (286):    0
     libinput Accel Speed (287):    0.000000
     libinput Accel Speed Default (288):    0.000000
     libinput Accel Profiles Available (289):    1, 1
     libinput Accel Profile Enabled (290):    1, 0
     libinput Accel Profile Enabled Default (291):    1, 0
     libinput Left Handed Enabled (292):    0
     libinput Left Handed Enabled Default (293):    0
     libinput Send Events Modes Available (261):    1, 0
     libinput Send Events Mode Enabled (262):    0, 0
     libinput Send Events Mode Enabled Default (263):    0, 0
     Device Node (264):    "/dev/input/event7"
     Device Product ID (265):    3504, 3344
     libinput Drag Lock Buttons (278):    <no items>
     libinput Horizontal Scroll Enabled (279):    1

Nothing promising looking to me...

Perhaps you recognize something.

Thanks

BTW, are you the Richard Stevens that authored TCP/IP Illustrated that I 
met years ago at IETF?

[Rick Stevens]

On 9/20/18 1:32 PM, Robert Moskowitz wrote:
>  
>  
>  On 9/20/18 1:56 PM, Rick Stevens wrote:
> > On 9/20/18 9:42 AM, Robert Moskowitz wrote:
> >>
> >> On 9/20/18 12:32 PM, Samuel Sieb wrote:
> >>> On 9/20/18 8:48 AM, Robert Moskowitz wrote:
> >>>> Anyway I hate the LEDs.  I put tape over their big LED, but the
> >>>> roller has its LED.  My search on the web says that the LEDs can be
> >>>> turned of with the system software. Interestingly enough, my Windows7
> >>>> system can't...
> >>>>
> >>>> Fedora 28 and 29-beta do see it:
> >>>>
> >>>> MSI GM10 MSI GM10 Gaming Mouse as
> >>>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
> >>>>
> >>>>
> >>>> hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse
> >>>> [MSI GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
> >>>> input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as
> >>>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
> >>>>
> >>>>
> >>>> input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as
> >>>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
> >>>>
> >>>
> >>>
> >>> Look in /proc/bus/input/devices and copy all the sections that
> >>> correspond to the mouse.  They should all have the same Phys= line
> >>> pointing to the same usb device.
> >> Here is what I am seeingon my F28 system:
> >>
> >> I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> >> N: Name="MSI GM10 MSI GM10 Gaming Mouse"
> >> P: Phys=usb-0000:00:12.0-3.4/input0
> >> S:
> >> Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1
> >>
> >>
> >> 0.0016/input/input63
> >> U: Uniq=
> >> H: Handlers=mouse1 event7
> >> B: PROP=0
> >> B: EV=17
> >> B: KEY=1f0000 0 0 0 0
> >> B: REL=103
> >> B: MSC=10
> >>
> >> I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> >> N: Name="MSI GM10 MSI GM10 Gaming Mouse Keyboard"
> >> P: Phys=usb-0000:00:12.0-3.4/input1
> >> S:
> >> Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >>
> >>
> >> 0.0017/input/input65
> >> U: Uniq=
> >> H: Handlers=sysrq kbd event9
> >> B: PROP=0
> >> B: EV=100013
> >> B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
> >> B: MSC=10
> >>
> >> I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> >> N: Name="MSI GM10 MSI GM10 Gaming Mouse Consumer Control"
> >> P: Phys=usb-0000:00:12.0-3.4/input1
> >> S:
> >> Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >>
> >>
> >> 0.0017/input/input66
> >> U: Uniq=
> >> H: Handlers=kbd event17
> >> B: PROP=0
> >> B: EV=1f
> >> B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000
> >> 677bfad9415fe
> >> d 9ed68000004400 10000002
> >> B: REL=40
> >> B: ABS=100000000
> >> B: MSC=10
> >>
> >> So I am looking for a command that turns off the LEDs on the mouse...
> > Uhm, try "xinput --list". Find the device that represents the mouse.
>  
>  ⎡ Virtual core pointer                        id=2    [master pointer  (3)]
>  ⎜   ↳ Virtual core XTEST pointer                  id=4    [slave
>  pointer  (2)]
>  ⎜   ↳ SynPS/2 Synaptics TouchPad                  id=16    [slave
>  pointer  (2)]
>  ⎜   ↳ TPPS/2 IBM TrackPoint                       id=17    [slave
>  pointer  (2)]
>  ⎜   ↳ MSI GM10 MSI GM10 Gaming Mouse Consumer Control    id=12 [slave 
>  pointer
>   (2)]
>  ⎜   ↳ MSI GM10 MSI GM10 Gaming Mouse              id=20    [slave
>  pointer  (2)]
>  ⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
>      ↳ Virtual core XTEST keyboard                 id=5    [slave
>  keyboard (3)]
>      ↳ Power Button                                id=6    [slave
>  keyboard (3)]
>      ↳ Video Bus                                   id=7    [slave
>  keyboard (3)]
>      ↳ Power Button                                id=8    [slave
>  keyboard (3)]
>      ↳ Sleep Button                                id=9    [slave
>  keyboard (3)]
>      ↳ Integrated Camera                           id=14    [slave
>  keyboard (3)]
>      ↳ AT Translated Set 2 keyboard                id=15    [slave
>  keyboard (3)]
>      ↳ ThinkPad Extra Buttons                      id=18    [slave
>  keyboard (3)]
>      ↳   USB Keyboard                              id=10    [slave
>  keyboard (3)]
>      ↳   USB Keyboard System Control               id=11    [slave
>  keyboard (3)]
>      ↳ MSI GM10 MSI GM10 Gaming Mouse Consumer Control    id=13 [slave 
>  keyboard
>   (3)]
>      ↳ MSI GM10 MSI GM10 Gaming Mouse Keyboard     id=19    [slave
>  keyboard (3)]
>  
>  
> > Once you find the device, try "xinput --list-props <device-number>"
> to
> > get a list of its properties and post that. Perhaps we can find
> > something that can be buggered via "xinput --set-prop" that'd turn
> > them off. Can't swear to it--this is a wild stab in the dark.
>  
>  $ xinput --list-props 12
>  Device 'MSI GM10 MSI GM10 Gaming Mouse Consumer Control':
>      Device Enabled (141):    1
>      Coordinate Transformation Matrix (143):    1.000000, 0.000000,
>  0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
>      libinput Natural Scrolling Enabled (276):    0
>      libinput Natural Scrolling Enabled Default (277):    0
>      libinput Send Events Modes Available (261):    1, 0
>      libinput Send Events Mode Enabled (262):    0, 0
>      libinput Send Events Mode Enabled Default (263):    0, 0
>      Device Node (264):    "/dev/input/event17"
>      Device Product ID (265):    3504, 3344
>      libinput Drag Lock Buttons (278):    <no items>
>      libinput Horizontal Scroll Enabled (279):    1
>  
>  $ xinput --list-props 20
>  Device 'MSI GM10 MSI GM10 Gaming Mouse':
>      Device Enabled (141):    1
>      Coordinate Transformation Matrix (143):    1.000000, 0.000000,
>  0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
>      libinput Natural Scrolling Enabled (276):    0
>      libinput Natural Scrolling Enabled Default (277):    0
>      libinput Scroll Methods Available (280):    0, 0, 1
>      libinput Scroll Method Enabled (281):    0, 0, 0
>      libinput Scroll Method Enabled Default (282):    0, 0, 0
>      libinput Button Scrolling Button (283):    2
>      libinput Button Scrolling Button Default (284):    2
>      libinput Middle Emulation Enabled (285):    0
>      libinput Middle Emulation Enabled Default (286):    0
>      libinput Accel Speed (287):    0.000000
>      libinput Accel Speed Default (288):    0.000000
>      libinput Accel Profiles Available (289):    1, 1
>      libinput Accel Profile Enabled (290):    1, 0
>      libinput Accel Profile Enabled Default (291):    1, 0
>      libinput Left Handed Enabled (292):    0
>      libinput Left Handed Enabled Default (293):    0
>      libinput Send Events Modes Available (261):    1, 0
>      libinput Send Events Mode Enabled (262):    0, 0
>      libinput Send Events Mode Enabled Default (263):    0, 0
>      Device Node (264):    "/dev/input/event7"
>      Device Product ID (265):    3504, 3344
>      libinput Drag Lock Buttons (278):    <no items>
>      libinput Horizontal Scroll Enabled (279):    1
>  
>  Nothing promising looking to me...
>  
>  Perhaps you recognize something.
>  
Hmmm, nope. Like I said, it was a wild stab in the dark. I had hoped
something would have shown up. Guess not.

If you're willing to play, you could try stuff such as:

	xset [-]led <number>

where "<number>" is a number from 1 to 32. It's normally used to
control
the keyboard LEDs, but one of them may work on your mouse. The

	xset led <number>

turns on the LED,

	xset -led <number>

turns it off (supposedly).

>  BTW, are you the Richard Stevens that authored TCP/IP Illustrated
> that I
>  met years ago at IETF?
>  
Nope, although that's probably the third time I've been mistaken for him
(much to his chagrin, I'm sure). I'm pretty sure he's a lot smarter and
certainly a better writer (although I was published in Byte, Amiga
Transactor and Read-Only-Magazine back in the day) than I am.

Back in the 80s, you'd have found me at the ANSI C or SCSI committee
meetings. My company insisted I represent them (I wasn't quick
enough to duck) so I was involved in both and yes, you can blame me in
part for the first release of ANSI C. I'm sorry about that.

I was also fairly active in the Amiga community (along with Joanne Dow,
often seen in this forum), DECUS, VCC, WCCF and several other nefarious
organizations. Weird stuff happens during a 45-year career in computers
and electronics--some of which is embarrassing to admit. ;p
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-      "Microsoft is a cross between The Borg and the Ferengi.       -
-  Unfortunately they use Borg to do their marketing and Ferengi to  -
-               do their programming."  -- Simon Slavin              -
----------------------------------------------------------------------

[Ed Greshko]

On 9/21/18 4:24 AM, Robert Moskowitz wrote:
>  Can anyone recommend a mouse with a REAL light touch and for the
> scroll wheel as
>  well.  Especially the scroll wheel.  I am about to take this mouse back. 
Have you considered  something like a Kensington Expert Mouse Wireless Trackball?  It
isn't one of those trackball mice that you use your thumb. 
It has a giant trackball that you use your index finger to manipulate.  I had wrist
issues and moved to that a few years ago.  It even works much better than
a mouse since I have multiple screens and moving between them is a breeze.  No more
lifting the mouse.  Plus, it is nice, big, and heavy and the cats
don't knock it off my desk.  :-)

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."

[Robert Moskowitz]

On 9/20/18 6:33 PM, Ed Greshko wrote:
>  On 9/21/18 4:24 AM, Robert Moskowitz wrote:
> > Can anyone recommend a mouse with a REAL light touch and for the scroll wheel as
> > well.  Especially the scroll wheel.  I am about to take this mouse back.
>  Have you considered  something like a Kensington Expert Mouse Wireless Trackball?  It
>  isn't one of those trackball mice that you use your thumb. 
The mouse and keyboard are connected to a KVM.  I just switched to the 
Tripplite KVM that accepts USB unlike my old Belkin that required old 
PS/2.  So wireless is out.  thanks

>  It has a giant trackball that you use your index finger to
> manipulate.  I had wrist
>  issues and moved to that a few years ago.  It even works much better than
>  a mouse since I have multiple screens and moving between them is a breeze.  No more
>  lifting the mouse.  Plus, it is nice, big, and heavy and the cats
>  don't knock it off my desk.  :-)
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Ed Greshko]

On 9/21/18 7:41 AM, Robert Moskowitz wrote:
>  On 9/20/18 6:33 PM, Ed Greshko wrote:
> > On 9/21/18 4:24 AM, Robert Moskowitz wrote:
> >> Can anyone recommend a mouse with a REAL light touch and for the scroll wheel as
> >> well.  Especially the scroll wheel.  I am about to take this mouse back.
> > Have you considered  something like a Kensington Expert Mouse Wireless Trackball? 
> It
> > isn't one of those trackball mice that you use your thumb. 
>
>  The mouse and keyboard are connected to a KVM.  I just switched to the Tripplite
>  KVM that accepts USB unlike my old Belkin that required old PS/2.  So wireless is
>  out.  thanks
>  
I'm not familiar with Tripp Lite.  You say it has USB?  Wouldn't that mean
it would
accept the USB dongle of the Kensington?

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."

[George N. White III]

On Thu, 20 Sep 2018 at 20:43, Robert Moskowitz <rgm(a)htt-consult.com&gt; wrote:
>  On 9/20/18 6:33 PM, Ed Greshko wrote:
>
>  On 9/21/18 4:24 AM, Robert Moskowitz wrote:
>
>  Can anyone recommend a mouse with a REAL light touch and for the scroll wheel as
>  well.  Especially the scroll wheel.  I am about to take this mouse back.
>
>  Have you considered  something like a Kensington Expert Mouse Wireless Trackball?  It
>  isn't one of those trackball mice that you use your thumb.
>  
I know a number of people whose RSI led them to look for alternatives
to mice.  Some of them
found Wacom Bamboo touchpads were comfortable, some like trackballs,
some use a laptop-style keyboard with built-in touchpad, and some just
switched to their spare hand.   At work we had
a collection of alternative devices so people could try them and
decide what was best for them.

>  The mouse and keyboard are connected to a KVM.  I just switched to the Tripplite KVM that
> accepts
>  USB unlike my old Belkin that required old PS/2.  So wireless is out.  thanks 
Some wireless mice do work with some USB KVM's, so wireless may still
be an option.

>  It has a giant trackball that you use your index finger to manipulate.  I had wrist
>  issues and moved to that a few years ago.  It even works much better than
>  a mouse since I have multiple screens and moving between them is a breeze.  No more
>  lifting the mouse.  Plus, it is nice, big, and heavy and the cats
>  don't knock it off my desk.  :-)
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail] 


-- 
George N. White III

[Ed Greshko]

On 9/21/18 8:22 AM, George N. White III wrote:
>  Some wireless mice do work with some USB KVM's, so wireless may
> still
>  be an option. 
Besides, Kensington makes a wired USB trackball.

https://www.kensington.com/us/us/4493/k64325/expert-mouse-wired-trackball

So, that option exists as well.  One just has to do a bit of looking.

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."

[Robert Moskowitz]

On 9/20/18 7:55 PM, Ed Greshko wrote:
>  On 9/21/18 7:41 AM, Robert Moskowitz wrote:
> >
> > On 9/20/18 6:33 PM, Ed Greshko wrote:
> >> On 9/21/18 4:24 AM, Robert Moskowitz wrote:
> >>> Can anyone recommend a mouse with a REAL light touch and for the scroll wheel
> as
> >>> well.  Especially the scroll wheel.  I am about to take this mouse back.
> >> Have you considered  something like a Kensington Expert Mouse Wireless
> Trackball?  It
> >> isn't one of those trackball mice that you use your thumb.
> > The mouse and keyboard are connected to a KVM.  I just switched to the Tripplite
> > KVM that accepts USB unlike my old Belkin that required old PS/2.  So wireless is
> > out.  thanks
> >
>  I'm not familiar with Tripp Lite.  You say it has USB?  Wouldn't that mean it
> would
>  accept the USB dongle of the Kensington? 
I am big on Tripplite UPS (since '84), but this is my first other 
product from them.  Their B006-VU4-R.

There are tagged ports for keyboard and mouse, so it may be that they 
are implemented separately.  Or it could just not matter.  But why label 
them if it doesn't matter?

Somewhere I have an old wireless keyboard.  I may dig it out and see if 
it still works...

[stan]

On Thu, 20 Sep 2018 11:48:16 -0400
Robert Moskowitz <rgm(a)htt-consult.com&gt; wrote:

>  I got this mouse for its very light touch.  I developed a pinched
>  nerve and it hurts to mouse...
>  
>  Pricy for me at $30, but the price of heath?
>  
>  Anyway I hate the LEDs.  I put tape over their big LED, but the
>  roller has its LED.  My search on the web says that the LEDs can be
>  turned of with the system software.  Interestingly enough, my
>  Windows7 system can't... 
Not an answer for your desire for a software solution, but if everything
else is satisfactory (you aren't going to return it), and you know you
will never want the LEDs, why not take the mouse apart, and snip one of
the leads to each of the LEDs?

[Samuel Sieb]

On 9/20/18 8:18 PM, stan wrote:
>  Not an answer for your desire for a software solution, but if
> everything
>  else is satisfactory (you aren't going to return it), and you know you
>  will never want the LEDs, why not take the mouse apart, and snip one of
>  the leads to each of the LEDs? 
Or tape over them on the outside.

[Robert Moskowitz]

On 9/21/18 12:22 AM, Samuel Sieb wrote:
>  On 9/20/18 8:18 PM, stan wrote:
> > Not an answer for your desire for a software solution, but if everything
> > else is satisfactory (you aren't going to return it), and you know you
> > will never want the LEDs, why not take the mouse apart, and snip one of
> > the leads to each of the LEDs? 
I am seriously considering this.

>  Or tape over them on the outside. 
I have done this for their big LED on the front of the mouse with black 
duck tape and still some light shows through.  But I can't do it for the 
wheel's light.

[Robin Laing]

On 20/09/2018 18:57, Ed Greshko wrote:
>  On 9/21/18 8:22 AM, George N. White III wrote:
> > Some wireless mice do work with some USB KVM's, so wireless may still
> > be an option.
>  
>  Besides, Kensington makes a wired USB trackball.
>  
>  https://www.kensington.com/us/us/4493/k64325/expert-mouse-wired-trackball
>  
>  So, that option exists as well.  One just has to do a bit of looking.
>  
>   


I would recommend these as well.

I have used one for over a decade.  Presently have 3 in the house and 1 
at work.

Only issue that requires replacement of the trackball I have had is 
losing one of the jewels that the track ball runs on.  Found a place 
that sells sapphire balls that are the same size to replace the lost 
ones.  Ball bearings from a bearing do not last long.  You do need 
sapphire or ruby.

My son broke his while gaming.  It is very old and will need to be 
replaced as I lost some of the parts from where it broke.  Still working 
with a bit of super glue.

The big ball is replaceable as well as the foam wrist rest at the base.

Micro-switches inside the trackball are cheap and easy to replace.

With some practice, I can do CAD drawings with mine.

The ball is 55mm in diameter.

I have not customized mine as I never really needed any changes from the 
default.

Robin

[Stephen Morris]

On 21/9/18 3:56 am, Rick Stevens wrote:
>  On 9/20/18 9:42 AM, Robert Moskowitz wrote:
> >
> > On 9/20/18 12:32 PM, Samuel Sieb wrote:
> >> On 9/20/18 8:48 AM, Robert Moskowitz wrote:
> >>> Anyway I hate the LEDs.  I put tape over their big LED, but the
> >>> roller has its LED.  My search on the web says that the LEDs can be
> >>> turned of with the system software. Interestingly enough, my Windows7
> >>> system can't...
> >>>
> >>> Fedora 28 and 29-beta do see it:
> >>>
> >>> MSI GM10 MSI GM10 Gaming Mouse as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.0/0003:0DB0:0D10.0003/input/input6
> >>>
> >>> hid-generic 0003:0DB0:0D10.0003: input,hidraw2: USB HID v1.11 Mouse
> >>> [MSI GM10 MSI GM10 Gaming Mouse] on usb-1c14400.usb-1.4/input0
> >>> input: MSI GM10 MSI GM10 Gaming Mouse Keyboard as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input8
> >>>
> >>> input: MSI GM10 MSI GM10 Gaming Mouse Consumer Control as
> >>>
> /devices/platform/soc@1c00000/1c14400.usb/usb2/2-1/2-1.4/2-1.4:1.1/0003:0DB0:0D10.0004/input/input9
> >>
> >>
> >> Look in /proc/bus/input/devices and copy all the sections that
> >> correspond to the mouse.  They should all have the same Phys= line
> >> pointing to the same usb device.
> > Here is what I am seeingon my F28 system:
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse"
> > P: Phys=usb-0000:00:12.0-3.4/input0
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/0003:0DB0:0D1
> >
> > 0.0016/input/input63
> > U: Uniq=
> > H: Handlers=mouse1 event7
> > B: PROP=0
> > B: EV=17
> > B: KEY=1f0000 0 0 0 0
> > B: REL=103
> > B: MSC=10
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse Keyboard"
> > P: Phys=usb-0000:00:12.0-3.4/input1
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >
> > 0.0017/input/input65
> > U: Uniq=
> > H: Handlers=sysrq kbd event9
> > B: PROP=0
> > B: EV=100013
> > B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
> > B: MSC=10
> >
> > I: Bus=0003 Vendor=0db0 Product=0d10 Version=0111
> > N: Name="MSI GM10 MSI GM10 Gaming Mouse Consumer Control"
> > P: Phys=usb-0000:00:12.0-3.4/input1
> > S:
> > Sysfs=/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/0003:0DB0:0D1
> >
> > 0.0017/input/input66
> > U: Uniq=
> > H: Handlers=kbd event17
> > B: PROP=0
> > B: EV=1f
> > B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1 130f938b17c000
> > 677bfad9415fe
> > d 9ed68000004400 10000002
> > B: REL=40
> > B: ABS=100000000
> > B: MSC=10
> >
> > So I am looking for a command that turns off the LEDs on the mouse...
>  Uhm, try "xinput --list". Find the device that represents the mouse.
>  For example, I'm using a Logitech Wave keyboard and mouse, so I see:
>
>  [root@prophead ~]# xinput --list
>  ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
>  ⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
>  ⎜   ↳ Logitech USB Receiver                   	id=11	[slave  pointer  (2)]
>  ⎜   ↳ TigerVNC pointer                        	id=15	[slave  pointer  (2)]
>  ⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
>       ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
>       ↳ Power Button                            	id=6	[slave  keyboard (3)]
>       ↳ Video Bus                               	id=7	[slave  keyboard (3)]
>       ↳ Power Button                            	id=8	[slave  keyboard (3)]
>       ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
>       ↳ Logitech USB Receiver                   	id=10	[slave  keyboard (3)]
>       ↳ gspca_zc3xx                             	id=12	[slave  keyboard (3)]
>       ↳ USB Sound Device                        	id=13	[slave  keyboard (3)]
>       ↳ Logitech USB Receiver                   	id=14	[slave  keyboard (3)]
>       ↳ TigerVNC keyboard                       	id=16	[slave  keyboard (3)]
>
>  Under the "Virtual core pointer" section, I see the USB receiver for the
>  mouse as device 11.
>
>  Once you find the device, try "xinput --list-props <device-number>" to
>  get a list of its properties and post that. Perhaps we can find
>  something that can be buggered via "xinput --set-prop" that'd turn
>  them off. Can't swear to it--this is a wild stab in the dark. 
Hi Rick, just a silly question, below is what I see from xinput --list.

bash-4.4$ xinput --list
⎡ Virtual core pointer                          id=2    [master pointer  
(3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave pointer  (2)]
⎜   ↳ Logitech USB Receiver Mouse               id=11   [slave pointer  (2)]
⎜   ↳ Logitech USB Receiver Consumer Control    id=12   [slave pointer  (2)]
⎜   ↳ Logitech USB Receiver Mouse               id=18   [slave pointer  (2)]
⎜   ↳ Logitech USB Receiver Consumer Control    id=19   [slave pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard 
(2)]
     ↳ Virtual core XTEST keyboard               id=5    [slave keyboard 
(3)]
     ↳ Power Button                              id=6    [slave keyboard 
(3)]
     ↳ Power Button                              id=7    [slave keyboard 
(3)]
     ↳ Logitech G533 Gaming Headset Consumer Control     id=8 [slave  
keyboard (3)]
     ↳ Logitech G533 Gaming Headset              id=9    [slave keyboard 
(3)]
     ↳ Logitech USB Receiver                     id=10   [slave keyboard 
(3)]
     ↳ Logitech USB Receiver System Control      id=13   [slave keyboard 
(3)]
     ↳ Logitech Gaming Keyboard G910             id=14   [slave keyboard 
(3)]
     ↳ Logitech Gaming Keyboard G910 Keyboard    id=15   [slave keyboard 
(3)]
     ↳ Logitech Gaming Keyboard G910 Consumer Control    id=16 [slave  
keyboard (3)]
     ↳ Logitech USB Receiver                     id=17   [slave keyboard 
(3)]
     ↳ Logitech USB Receiver System Control      id=20   [slave keyboard 
(3)]
     ↳ Logitech USB Receiver Consumer Control    id=21   [slave keyboard 
(3)]
     ↳ Logitech USB Receiver Consumer Control    id=22   [slave keyboard 
(3)]

With the two mouse entries under "Virtual core pointer", how do you tell 
which is the mouse and which is the Powerplay Wireless charging system 
both of which have separately configurable leds? (The mouse wireless 
transmitter plugged into my pc may or may not be being used under Linux, 
under windows the logitech software says the transmitter is not being 
used and can be removed, and when I do so the mouse still functions 
seemingly through the Powerplay mat (and having just tried it the same 
is true under Linux, I can removed the transmitter and the mouse still 
functions). The logitech software provides functionality to control the 
leds on the mouse and Powerplay separately or to synch them, it doesn't 
provide the same synch for the keyboard. There is utility software for 
linux on Github that provides a subset of the functionality that the 
logitech software provides, but that software won't compile under the 
current Fedora kernels.)

Below is my results from listing the properties of both devices, and 
from what I can see there doesn't appear to be any properties relative 
to the leds on either device, but then I can't say I understand 
everything I'm seeing anyway.

bash-4.4$ xinput --list-props 11
Device 'Logitech USB Receiver Mouse':
         Device Enabled (147):   1
         Coordinate Transformation Matrix (149): 1.000000, 0.000000, 
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
         libinput Natural Scrolling Enabled (282):       0
         libinput Natural Scrolling Enabled Default (283):       0
         libinput Scroll Methods Available (284):        0, 0, 1
         libinput Scroll Method Enabled (285):   0, 0, 0
         libinput Scroll Method Enabled Default (286):   0, 0, 0
         libinput Button Scrolling Button (287): 2
         libinput Button Scrolling Button Default (288): 2
         libinput Middle Emulation Enabled (289):        0
         libinput Middle Emulation Enabled Default (290):        0
         libinput Accel Speed (291):     0.000000
         libinput Accel Speed Default (292):     0.000000
         libinput Accel Profiles Available (293):        1, 1
         libinput Accel Profile Enabled (294):   1, 0
         libinput Accel Profile Enabled Default (295):   1, 0
         libinput Left Handed Enabled (296):     0
         libinput Left Handed Enabled Default (297):     0
         libinput Send Events Modes Available (267):     1, 0
         libinput Send Events Mode Enabled (268):        0, 0
         libinput Send Events Mode Enabled Default (269):        0, 0
         Device Node (270):      "/dev/input/event12"
         Device Product ID (271):        1133, 50490
         libinput Drag Lock Buttons (298):       <no items>
         libinput Horizontal Scroll Enabled (299):       1
bash-4.4$ xinput --list-props 18
Device 'Logitech USB Receiver System Control':
         Device Enabled (147):   1
         Coordinate Transformation Matrix (149): 1.000000, 0.000000, 
0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
         libinput Send Events Modes Available (267):     1, 0
         libinput Send Events Mode Enabled (268):        0, 0
         libinput Send Events Mode Enabled Default (269):        0, 0
         Device Node (270):      "/dev/input/event5"
         Device Product ID (271):        1133, 50489

regards,

Steve

> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
> - AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
> -                                                                    -
> -    Admitting you have a problem is the first step toward getting   -
> -    medicated for it.      -- Jim Evarts (http://www.TopFive.com)   -
> ----------------------------------------------------------------------
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

On 9/27/18 9:18 PM, Stephen Morris wrote:
>  Below is my results from listing the properties of both devices, and
>
>  from what I can see there doesn't appear to be any properties relative 
>  to the leds on either device, but then I can't say I understand 
>  everything I'm seeing anyway.
>  
>  bash-4.4$ xinput --list-props 11
>  Device 'Logitech USB Receiver Mouse': 
I don't think you're going to find the LED controls here.

>           Device Node (270):      "/dev/input/event12"
Check in /proc/bus/input/devices or run "evtest /dev/input/event12" to 
see if there are any supported LEDs on the device.

Can you provide a link to the utility software?  I wonder why the kernel 
version matters.

[Stephen Morris]

On 21/9/18 11:17 am, Robert Moskowitz wrote:
>  On 9/20/18 7:55 PM, Ed Greshko wrote:
> > On 9/21/18 7:41 AM, Robert Moskowitz wrote:
> >>
> >> On 9/20/18 6:33 PM, Ed Greshko wrote:
> >>> On 9/21/18 4:24 AM, Robert Moskowitz wrote:
> >>>> Can anyone recommend a mouse with a REAL light touch and for the 
> >>>> scroll wheel as
> >>>> well.  Especially the scroll wheel.  I am about to take this mouse 
> >>>> back.
> >>> Have you considered  something like a Kensington Expert Mouse 
> >>> Wireless Trackball?  It
> >>> isn't one of those trackball mice that you use your thumb.
> >> The mouse and keyboard are connected to a KVM.  I just switched to 
> >> the Tripplite
> >> KVM that accepts USB unlike my old Belkin that required old PS/2.  
> >> So wireless is
> >> out.  thanks
> >>
> > I'm not familiar with Tripp Lite.  You say it has USB?  Wouldn't that 
> > mean it would
> > accept the USB dongle of the Kensington?
>
>  I am big on Tripplite UPS (since '84), but this is my first other 
>  product from them.  Their B006-VU4-R.
>
>  There are tagged ports for keyboard and mouse, so it may be that they 
>  are implemented separately.  Or it could just not matter. But why 
>  label them if it doesn't matter?
>
>  Somewhere I have an old wireless keyboard.  I may dig it out and see 
>  if it still works... 
In an earlier thread in this list of threads I posted the xinput data 
for my logitech devices. I am using a Logitech Powerplay Wireless 
Charging "Mat" the plugs in via usb and a Logitech G910 gaming mouse 
that is designed to work with the Powerplay or without it. If using the 
Powerplay you don't need to plug the wireless transmitter for the mouse 
into the usb, and the mouse also comes with a cable so that you can run 
it wired if you want to, and as a side effect running it wired also 
charges the built in battery. Situated just below the scroll wheel on 
the mouse there is a button to switch between the scroll wheel having 
the normal drag and no drag at all so that when you scroll the wheel you 
can't even feel it. Under that button there is also two buttons for 
scrolling the dpi up and down as well. It also has 4 side buttons on it 
with caps that can be removed and replaced with caps that disable the 4 
side buttons if you want to. I haven't tested it but the scroll wheel 
can be tilted left and right if to provide horizontal scrolling if you 
want it. The one issue with this mouse, based on what you said in an 
earlier thread, is it is significantly more expensive than what you paid 
for your existing mouse. Both devices have leds, but if you have windows 
the logitech software provides the capability of storing the dpi and led 
configurations in the device itself, in which case they function in that 
configured mode under Linux. I have set both my devices and my logitech 
gaming keyboard up that way as the linux utilities available on Github 
don't compile under the current F28 current kernels, the person who 
wrote the software on Github does have binary modules that you need to 
copy to the appropriate system directories which may work, but I would 
rather compile them through dkms so that the get recompiled every kernel 
change.


regards,

Steve

>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

On 28/9/18 2:39 pm, Samuel Sieb wrote:
>  On 9/27/18 9:18 PM, Stephen Morris wrote:
> > Below is my results from listing the properties of both devices, and 
> > from what I can see there doesn't appear to be any properties 
> > relative to the leds on either device, but then I can't say I 
> > understand everything I'm seeing anyway.
> >
> > bash-4.4$ xinput --list-props 11
> > Device 'Logitech USB Receiver Mouse':
>
>  I don't think you're going to find the LED controls here.
>
> >          Device Node (270): "/dev/input/event12"
>
>  Check in /proc/bus/input/devices or run "evtest /dev/input/event12" to 
>  see if there are any supported LEDs on the device.
>
>  Can you provide a link to the utility software?  I wonder why the 
>  kernel version matters. 
I've just checked the git repo I downloaded and I was not correct in 
thinking it was software for the mouse, it is actually software to 
control the led's etc on, among a few others, the Logitech G910 Orion 
Spectrum keyboard I have.

I can't find the actual url for the actual site at the moment, but <a 
href="https://sites.google.com/mohamadsaada.com/logigsk/home"&g...

is his link to ready to deploy jars that he has which may enable you to 
find his site.

I got compile errors when I tried to compile his code, but I'm not sure 
whether its the same issue with the wifi driver software I have to 
compile, in that it is sensitive to needed functions being moved between 
header include files, or whether the source code is using syntax the 
Fedora compiler doesn't like, as it does produce messages that the code 
has warnings that the compiler is turning into errors.

I'm not that concerned with turning the led's off, I was looking at this 
for interest. I can play around with the configurations under the 
Logitech software in windows and store the results in the devices to 
make them OS independent.

regards,

Steve

> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Stephen Morris]

On 28/9/18 2:39 pm, Samuel Sieb wrote:
>  On 9/27/18 9:18 PM, Stephen Morris wrote:
> > Below is my results from listing the properties of both devices, and 
> > from what I can see there doesn't appear to be any properties 
> > relative to the leds on either device, but then I can't say I 
> > understand everything I'm seeing anyway.
> >
> > bash-4.4$ xinput --list-props 11
> > Device 'Logitech USB Receiver Mouse':
>
>  I don't think you're going to find the LED controls here.
>
> >          Device Node (270): "/dev/input/event12"
>
>  Check in /proc/bus/input/devices or run "evtest /dev/input/event12" to 
>  see if there are any supported LEDs on the device.
>
>  Can you provide a link to the utility software?  I wonder why the 
>  kernel version matters. 
Hi Sam, doing a google search I just found a link to a site that 
provides software to configure the buttons and possibly the leds on 
Logitech gaming mice, of which the Logitech G903 gaming mouse is one of 
the ones supported.

The link is https://github.com/libratbag/piper. The software is a GTK+ 
front end to the ratbagd DBUS daemon which appears to be in the Fedora 
repositories.

I also found a link to a piper F28 repository, but the version of 
libratbagd in the F28 repositories is too old for piper to be installed.


regards,

Steve

_______________________________________________

> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]