M801 Mammoth compatibility

Question

M801 Mammoth compatibility

NonMeme opened this issue 4 years ago · 11 comments

The M801 Mammoth is my main mouse. What can I do to help it be compatible with this software?

Answer 1 · 2021-01-10T02:52:36.000Z

The first step would be to run lsusb, mouse_m908 -D - and mouse_m908 -R - and post the output. That would allow the creation of an experimental backend where features can be added or implemented. The second step would then be for you to test the features as they are implemented, and capture the USB traffic of the official software with wireshark if features are not working.
I hope this answers your question, feel free to ask if anything is unclear.

Answer 2 · 2021-01-10T14:11:16.000Z

I cloned the repository, but I have no idea what to do from there.

Answer 3 · 2021-01-10T15:28:23.000Z

Build and install as described in the README, then run lsusb, mouse_m908 -R - and mouse_m908 -D - and attach the output to your comment. If you have problems with compiling, the basic steps are:

install the dependencies: libusb (dev package on Debian based distros), make, pkgconf, gcc/g++
cd /path/to/mouse_m908
make
sudo make install

Answer 4 · 2021-01-17T20:00:46.000Z

When I run "mouse_m908 -R -" and "mouse_m908 -D -", I get a Couldn't detect mouse error message. What am I missing?

Answer 5 · 2021-01-17T21:07:41.000Z

You could run lsusb to check if the USB IDs are different from 04d9:fc56, then use the --bus and --device options, or try running the program as root. If you post the output of lsusb i might be able to give you more information.

Answer 6 · 2021-01-17T21:28:58.000Z

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 007: ID 04d9:fa56 Holtek Semiconductor, Inc. USB Laser Game Mouse
Bus 001 Device 005: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
Bus 001 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub
Bus 001 Device 002: ID 1038:12ad SteelSeries ApS SteelSeries Arctis 7
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I believe my mouse is 7.

Answer 7 · 2021-01-17T21:36:57.000Z

Thanks that helped, the USB PID was indeed wrong. I have fixed it in the master branch.

Answer 8 · 2021-01-18T22:28:28.000Z

How do I update it? And what commands do I run afterwards to get the mouse info you need?

Answer 9 · 2021-01-18T22:36:37.000Z

Assuming that you still have the repositrory cloned, if not clone this repository first (git clone https://github.com/dokutan/mouse_m908):

cd path/to/mouse_m908
git pull
make clean
make
sudo make install

Afterwards running mouse_m908 -D - and mouse_m908 -R - should work (it could be that you need root permissions).

Answer 10 · 2021-01-19T22:02:24.000Z

OK, it seems to have worked. Here are the outputs.
D Output.txt
R Output.txt

Answer 11 · 2021-01-19T22:45:31.000Z

I'm glad that worked, unfortunately from what i can tell now is this mouse is using a different data format, maybe similar to the M990 (#5). This means it would be neccessary to install the official software in a VM with USB passthrough or on bare metal and use wireshark to capture the USB data when changing settings.

In case that is something you want to try, here are a few links to explain the process (you don't have to do the reverse engineering part, only the capture), or feel free to ask here.
https://bytepunk.wordpress.com/2017/03/25/reverse-engineering-a-usb-mouse/
https://github.com/pez2001/razer_chroma_drivers/wiki/Reverse-Engineering-USB-Protocol
https://github.com/dokutan/rgb_keyboard/tree/master/doc (from my other usb reverse engineering project)

I'm sorry i couldn't be of much help, but please let me know if you want to continue to work on this or not.