8000 Support Redragom m601 · Issue #31 · dokutan/mouse_m908 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Support Redragom m601 #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Xfezor opened this issue Oct 21, 2021 · 6 comments
Open

Support Redragom m601 #31

Xfezor opened this issue Oct 21, 2021 · 6 comments
Labels
enhancement New feature or request

Comments

@Xfezor
Copy link
Xfezor commented Oct 21, 2021

pls support redragon m601 :(
@dokutan
Copy link
Owner
dokutan commented Oct 22, 2021

Please start by posting the output of lsusb

@dokutan dokutan added the enhancement New feature or request label Oct 23, 2021
@TheAquabat
Copy link

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
Copy link
Owner
dokutan commented Nov 22, 2022

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
Copy link
TheAquabat commented Nov 23, 2022 •
edited
Loading

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
Copy link
so1der commented Dec 11, 2023

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
Copy link
so1der commented Dec 11, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@TheAquabat @dokutan @Xfezor @so1der
0