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@xxxxxxxxxxxxxx - - 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 - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx
