dokutan / mouse_m908

Control various Redragon gaming mice from Linux, BSD and Haiku
GNU General Public License v3.0
206 stars 36 forks source link

Support Redragom m601 #31

Open Xfezor opened 3 years ago

Xfezor commented 3 years ago

pls support redragon m601 :(

dokutan commented 3 years ago

Please start by posting the output of lsusb

TheAquabat commented 1 year ago

I have a 601


Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 062a:5918 MosArt Semiconductor Corp. 2.4G Keyboard Mouse
Bus 003 Device 002: ID 0c45:5204 Microdia USB DEVICE
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 002: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dokutan commented 1 year ago

I assume 062a:5918 MosArt Semiconductor Corp. 2.4G Keyboard Mouse is the M601. The vendor id is different from all other mice (wired and wireless), this makes it unlikely that this mouse has a compatible protocol.

Nonetheless i added the ids in a new branch (https://github.com/dokutan/mouse_m908/tree/m601) to the generic backend, i suggest you try to read the settings/change the active profile to see if the protocol might be compatible.

TheAquabat commented 1 year ago

I assume 062a:5918 MosArt Semiconductor Corp. 2.4G Keyboard Mouse is the M601. The vendor id is different from all other mice (wired and wireless), this makes it unlikely that this mouse has a compatible protocol.

Nonetheless i added the ids in a new branch (https://github.com/dokutan/mouse_m908/tree/m601) to the generic backend, i suggest you try to read the settings/change the active profile to see if the protocol might be compatible.

problem is that the windows utility doesn't work for this mouse .. so if something goes south I cannot fix it. So what you say makes sense since the windows red dragon utility doesn't work with this mouse. but maybe someone more brave than me is willing to try.

so1der commented 10 months ago

Hello there! Im also have a m601, more specifically - M601-RGB (Centrophorus 2), but in my case both PID and VID are different.

Bus 001 Device 006: ID 258a:1007 SINOWEALTH Wired Gaming Mouse

I tried to add those PID:VID into include/generic/data.cpp file and compile it, but I still get a "Couldn't detect mouse" message. It is because I did something wrong, or thats cause mouse doesnt support generic protocol? I also tried a "m601" branch, but ended up with a compilation error, thats why I tried to add PID:VID into default branch.

so1der commented 10 months ago

Yup, thats was problem on my side, After correctly recompile it I have a "Couldn't open mouse" message. After thats mouse stop responding, but simple "unplug-plug" brings it back to action. So as far as it looks like, M601-RGB doesnt support this protocol.