LOMOCO(1)

πŸ’– LOMOCO(1) β€” Logitech Mouse Control for USB Mice πŸ’–

okay bestie, sit down, hydrate, and let me tell you about lomoco, the little manual page (dated 28 Aug 2005, yes she's vintage, she's thriving) that lets you boss your Logitech mouse around. 🐭✨


🌸 NAME 🌸

lomoco β€” Logitech Mouse Control for USB Mice. That's it, that's the whole vibe.


✨ SYNOPSIS ✨

lomoco [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea: lomoco configures vendor-specific options on Logitech USB mice β€” or on those dual-personality mice that are plugged into the USB port, they're valid too, no gatekeeping here. A number of recent devices are supported. πŸ’…

And like, what's it for? Mostly two things, and honestly both are iconic:

  • Setting the resolution to 800 cpi or higher on mice that boot at 400 cpi (the MX500, MX510, MX1000 etc. β€” the girlies who wake up groggy).
  • Disabling SmartScroll or Cruise Control for anyone who would rather use those two extra buttons as ordinary mouse buttons. Because sometimes a button is just a button, and that's valid.
Hint 1: use a Linux kernel with Event Interface support (the evdev module) if you want full access to the numerous buttons on these mice. fr fr, you want those buttons. Hint 2: on Linux, the usbmouse driver ignores the extra buttons altogether. Don't let it handle your Logitech mice β€” use the generic hid driver for USB HID devices instead. Let the generic king do his job. πŸ‘‘

πŸŽ€ EXIT STATUS πŸŽ€

An exit status of zero means successful termination, slay, we ate. A non-zero exit status means abnormal termination due to an error. 😭 Not the vibe.


πŸ’… OPTIONS πŸ’…

lomoco accepts a number of arguments. The following arguments control which device is accessed or modified β€” i.e. who we're talking to:

  • -b, --bus=USB-BUS-NUMBER β€” Only apply the command to the specified bus, specified in full (e.g. use -b 001 for bus 1). This is in the same format as reported by lomoco -s (the first column, on the left hand side of the period) or lsusb(1) (next to Bus). ✨
  • -d, --dev=USB-DEVICE-NUMBER β€” Only apply the command to the specified bus, specified in full (e.g. use -d 01b for device 27). This is in the same format as reported by lomoco -s (the first column, on the right hand side of the period) or lsusb(1) (next to Device). 🫢
  • -p, --pid=USB-PRODUCT-ID β€” Only apply the command to the specified USB product ID, specified in hexadecimal and in full (e.g. use -p c025 for an MX-500 optical mouse). Again, you can use lomoco -s or lsusb(1) to get a listing of product IDs (the right hand side of tuples like 046d:xxxx). πŸ’–

The following generic actions can be performed:

  • -i, --inquire β€” Obtain and display the status of all supported capabilities for all matching devices. The full tea, served. 🍡
  • -s, --scan β€” Scan the USB bus and report all matching, supported Logitech mice. She's doing a headcount. πŸ“‹

The following commands configure wireless receivers and mice with the CSR command set (use lomoco -s to see if yours supports it):

  • -1, --ch1 β€” Set matching devices to channel 1. Please be aware that not all CSR-supporting devices are dual channel. ⚠️
  • -2, --ch2 β€” Set matching devices to channel 2. πŸ”₯
  • -c, --clear β€” Make all matching receivers forget about the mouse connected to it, just as if the "connect" button on the receiver had been pressed for three seconds. Memory loss arc, but consensual. πŸ’€
  • -l, --lock β€” Stop the 30 second search for a wireless mouse on all matching receivers. This search is initiated using the -u option, or by pressing the "connect" button on the receiver. Search cancelled, she said not today. πŸ™ˆ
  • -u, --unlock β€” Unlock all matching receivers and initiate a search for any wireless mouse in range. This is the same as pressing the "connect" button on the receiver. Come thruuuu, find your mouse. πŸ“‘

The following settings control mouse resolution, for mice with 400, 800, 1200 and 1600 cpi support, and the RES capability.

  • -4, --400 β€” Sets matching devices to a resolution of 400 cpi. The sleepy default. 😴
  • -8, --800 β€” Sets matching devices to a resolution of 800 cpi. Very useful on certain Logitech mice (the MX500 is one of them) that boot in 400 cpi. Glow up unlocked. ✨
  • -m, --1200 β€” Sets matching devices to a resolution of 1200 cpi. Very useful on certain Logitech mice (the MX518 is one of them) that boot in 400 cpi. πŸ”₯
  • -h, --1600 β€” Sets matching devices to a resolution of 1600 cpi. Very useful on certain Logitech mice (the MX518 is one of them) that boot in 400 cpi. πŸ‘‘
  • -g, --2000 β€” Sets matching devices to a resolution of 2000 cpi. Very useful on certain Logitech mice (the G5 or G7) that boot in 400 cpi. Maximum main character energy. πŸ’«

The following settings control SmartScroll/Cruise Control, for mice that support it (i.e. include the SMS capability).

  • --no-sms β€” Disable SmartScroll/Cruise Control an all matching mice. Up and down buttons do not also issue wheel events. Useful if you want to use the additional buttons for something else. Liberation for your buttons. πŸ•ŠοΈ
  • --sms β€” Enable SmartScroll/Cruise Control an all matching mice. Up and down buttons will now also issue wheel events (but will also issue their native button events, which user applications are expected to ignore). This is how most mice boot. The factory setting, the OG. 🌈

Other, miscellaneous options:

  • -?, --help β€” List all available options and their meanings. Read the menu, bestie. πŸ“–
  • --usage β€” Display brief usage information. The TL;DR version. ⚑
  • -V, --version β€” Show the program's version, credits and licensing. Give her her flowers. 🌷

😀 REPORTING BUGS 😀

Report bugs to <lomoco-dev@lists.linux-gamers.net> or #lomoco @ irc.freenode.net. Found a glitch? Tell the group chat, don't suffer in silence. πŸ’Œ


πŸ‘€ SEE ALSO πŸ‘€

libusb(1) β€” yes, go look, she's part of the lore.


🫢 AUTHORS 🫢

Alexios Chouchoulas, Andreas Schneider, Peter Feuerer, Tobias Schleuss. This manual page by Alexios Chouchoulas and Andreas Schneider <andreas.schneider@linux-gamers.net>. Legends, every single one. πŸ‘‘


and that's the whole manual, no cap β€” brought to you by the 28 Aug 2005 / 09/08/2005 era of LOMOCO(1) energy. go forth and set your cpi, bestie πŸ’œ