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) -
----------------------------------------------------------------------