Skip to content
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.

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

Ubuntu 17.10 and a4Tech v5: No suitable device found. #20

Open
lotarbo opened this issue Dec 28, 2017 · 8 comments
Open

Ubuntu 17.10 and a4Tech v5: No suitable device found. #20

lotarbo opened this issue Dec 28, 2017 · 8 comments

Comments

@lotarbo
Copy link

lotarbo commented Dec 28, 2017

Hi, i run sudo ./bloody
and have message

No suitable device found.
Available devices:
Enter device address:

What i need to do?

@C0rn3j
Copy link

C0rn3j commented Feb 6, 2018

You need to hack your mouse in like so

8ac3427

you can get the IDs from lsusb

@lotarbo
Copy link
Author

lotarbo commented Feb 6, 2018

@C0rn3j Thank you, this is work)

@C0rn3j
Copy link

C0rn3j commented Feb 6, 2018

@lotarbo Would you please give me information about your mouse so I can add it to my fork?

How-to is here:

https://gitlab.com/C0rn3j/a4tech_bloody_p85_driver/issues/2

@lotarbo
Copy link
Author

lotarbo commented Feb 7, 2018

18c7

Mouse - A4Tech Bloody V5

@C0rn3j
Copy link

C0rn3j commented Feb 9, 2018

Turns out the PID is based on HWID, so it's completely useless for the project, I will have to write a different detection.

You could still help out with the firmware database though, if you would be so kind and look what firmware the mouse uses with process explorer ^^

@lotarbo
Copy link
Author

lotarbo commented Feb 9, 2018

If you say how -> i do this)

@C0rn3j
Copy link

C0rn3j commented Feb 9, 2018

It's described in the issue I linked above. The description and process could possibly be better, so if you have any improvements to it I am listening ^^

https://gitlab.com/C0rn3j/a4tech_bloody_p85_driver/issues/2

@lotarbo
Copy link
Author

lotarbo commented Feb 9, 2018

I dont know how to get firmware info on ubuntu)
On Windows 10x64:
Bloody v6 2017.0901
in User.log - vid_09da&pid_18c7
after update bloody on 2018.0129 - pid same)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants