I will hope and dream that this might someday lead to more mmo/12-button mice on the market, or at least the ability to customize them without relying on their proprietary software.

This. I greatly prefer mice with a large number of customizable buttons, but they’re something of a rarity and universally use Windows-only software.

eta: or discontinued.

On the software side there’s plenty of linux alternatives to the windows only stuff. Not at my computer to check program names, but my 12 side button mouse is just as usable as it was back on windows.

Same here. My Logitech 602 works fine with… I think it was Piper?

Yep, Piper is what I use with my Logitech G600.

How does piper compare to solaar?

I’m not sure, I never heard of Solaar until you mentioned it!

I find Piper to be excellent though. For my G600 I can control the LEDs, remap the buttons, set the various DPI resolutions and control the report rate. It does everything I used the old Logitech Gaming Software for (fuck Logitech G Hub).

Both the 600 and 602 were both discontinued though, right?

Yeah, I think so. I had a backup G600 that replaced my old one a couple of years ago.

I think they discontinued it before then brought it back for a while but looking on Amazon UK it seems unavailable. RIP G600 :(

depends on the mouse model, many are not supported or the macro works bit you cannot edit them. Also corsair software had an automatic switch of the macro profile depending on the main window opened, that was amazing, you could always had the right one without doing anything

I’m holding out moving to Linux because of my G600 and G13. I believe G13 driver support is in the making.

are you changing settings frequently? if not, settings should be stored on the on board memory and it will continue working on linux

I keep games controls on default and set them up to my G600 mouse and G13 gameboard on Logitech control panel for games and other software. I have dozens of settings.

Have you tried OpenLogi? I’m not sure if it supports that model specifically, but it supports a lot.

It does seem to support newer models, G600 and especially G13 are quite old and no longer supported even by newer Logitech software. Thanks for the tip anyways, I collect these for possible future needs.

I’ve had two of those in the past and really liked them but they died on me too fast.

100000% this. Also wireless charging mousepads. I have the Logitech Power pad or whatever it’s called and it works perfectly (with their compatible mice, none of which is a 12button 😑)

Linux?

Their keyboards that are open source firmware were so I would imagine

I’d be impressed if you could find a mouse that didn’t work on Linux

As if ploopy.co didn’t exist 😞

Still happy to see new open source firmware for mice being developed and implemented in new products. More options is always better.

I think Ploopy’s firmware is straight microcontroller firmware for the RP2040. This Keychron firmware appears to be an OS with wide hw support.

They make mice?

They do. I have had their M6 mouse for a few years.

It’s fairly good but after some time the side-ways scroll wheel failed for me. It also doesn’t track as well on some surfaces as my previous Logitech, but otherwise it’s good.

Gods, I really hope they consider Linux or at least SteamOS for software support.

Having my Logitech and Corsair mice without the ability to actively rebind anything on my Linux host (without the use of Windows VMs) is painfully annoying.

QMK VIA

They are talking about the firmware that runs on the device. The user front-end to easily configure it is another story. Hopefully it’s going to quickly get support for Linux as they are starting from well established Open-source projects for keyboard firmware (QMK and ZMK). If it works like for keyboards, you will be able to configure your mouse with something like VIA that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.

I have 2 keychon keyboards, an old one and a newer one with QMK firmware. Both have worked perfectly well for Linux. The QMK one is easy to configure with VIA once the device permissions are sorted out.

that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.

Please don’t bring webusb to firefox. It’s just a security liability. only use is for tools made out of mistakes. the web should never have direct access to usb devices and the filesystem.

They already brought webserial.

yes and I don’t like it.

If it’s open source, there’s roughly a 100% chance someone will make it work on Linux.

You can configure Keychron peripherals via their website - Keychron Launcher.

It works on Linux, but there are two caveats:

1. Requires Chromium web browser. I’ve tested it with Ungoogled Chromium and it worked fine.
2. In some Linux distributions you will have to set up udev rules, to allow access to USB devices

I’ve tested it with my Keychain K3 keyboard and M4 mouse and it works.

I agree a compatibility with ex. Piper would be neat though

I REALLY fucking wish people would stop targeting Chromium for their apps.

I agree, but at least it’s not an app you have to download, which turns out to be Electron/CEF/etc.

Be careful with this. These udev rules usually grant uaccess to your entire keyboard. uaccess is explicitly disabled for keyboards by default because it presents the event device to all of userspace, which allows any unprivileged app to log all key presses. This includes any malicious scripts running in a browser. If you do want to set up these rules, use them only for the single session you’re setting up your device and don’t type any passwords with it active, or change them immediately after (you won’t be able to remove them without your sudo password).

For the same reason, stop using OpenRGB for devices that don’t have kernel drivers.

You’re right, one of the guides I’ve found explicitly mentioned that, and recommended toggling the rules on only when you need it.

If I’m not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a “Link” device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.

Could you elaborate on the OpenRGB thing? I’ve used it a few times but never paid attention to the rules it asks for

If I’m not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a “Link” device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.

That’s great, just be sure your rules are specific enough for that device but didn’t rely on some randomness for detection. I.e. Matching on the current evdev or hidraw devnode is bad because it can shift with more devices being added, changing ports, or some randomness in enumeration speed. Instead, do an attribute walk on the devnode to find specific unique attributes for that node, such as VID + PID + subsystem + bInterfaceNunber should be unique. Things like names and phys patch aren’t guaranteed to be unique or consistent in different operating modes. You’ll also want to check the devnodes of the other interfaces to be sure they won’t match by doing a test.

The commands for those things are: udevadm info -a /path/to/devnode udevadm test /path/to/devnode

Could you elaborate on the OpenRGB thing? I’ve used it a few times but never paid attention to the rules it asks for

Sure. While not technically necessary for some devices, they have pretty open blanket udev rules. This is because most keyboard devices require the use of hid reports directly to the device to make changes.

From their page:

On Linux, OpenRGB needs permission to access the hardware interfaces used for RGB control. These include USB and I2C interfaces. To make accessing these interfaces easier, OpenRGB provides a udev rules file that tells your operating system to allow your user account control over these hardware interfaces, allowing OpenRGB to run without root access while still controlling the hardware.

Notice the complete lack of warning about any security issue from doing this.

If they wanted to be secure they could make a root level daemon that does all the hardware interfacing, and provide a dbus interface managed through polkit to allow making those changes from the userspace UI.

It’s a fucking USB HID mouse? OS agnostic. In an ideal world, the buttons should just be really big number scancodes that aren’t mapped to anything. You can then do something like this (says sway but runs on basically everything X and Wayland). Research before buying a mouse. Actually, no, just buy it from a local store, and if the buttons aren’t functioning as buttons without OEM bullshit, return as defective.

Make more fully metal mice like the magnesium pwnage stormbreaker 8k

This is good. I want them to succeed with this. This way it could tell Elecom to open-source their mouse firmware and that could make their trackballs more accessible. Come on, Elecom, I need an improved Deft Pro, with open-source firmware!

Sick, my next mouse is probably going to be a Keychron instead of another Logitech.

I’d like to avoid Logitech as well, but Keychron mice seem to be Logitech hardware?

That’s fine by me: All my Logitech stuff has been pretty solid.

I got one of those crazy looking ones from gravastar, after owning one of those super expensive razer mice’s that came with a big ass acrylic show cases like you bought the queen’s crown. After that I owned one similar from Corsair and before those I owned a mad catz rat 9.

I actually really like the gravastar one, but I don’t game competitively.

I just use an MX Vertical at home and an MX Anywhere with my laptop.

Not the first

I checked the repo but there’s no code? Just some HTML etc.
It seems like they just plan for this thing to exist but it doesn’t actually exist yet?

EDIT: Their explanation:

This repository is currently in its early setup phase.

At the moment, the repository mainly contains project scaffolding, policy files, and the initial project direction. Firmware sources, board support, build instructions, and flashing guidance are still being prepared.

That means zgm is early, but it is intentionally early in public. The goal is not to wait until everything is finished before opening the door. The goal is to make the long-term direction visible and let the project grow into a useful open firmware platform in the open.

I’m not sure if that means that they still have to make it, or that they just have to finish it before publishing it?

Waiting for an agentic LLM to magically pick it up and start working on it /j

Yay, more corporate openwashed software. Also yay, more markdown only repos.

If only they made mice that weren’t shit. I love their keyboards, but they do not know how to make quality mice.