a4tech-bloody-linux-driver icon indicating copy to clipboard operation
a4tech-bloody-linux-driver copied to clipboard

Ubuntu 17.10 and a4Tech v5: No suitable device found.

Open lotarbo opened this issue 6 years ago • 8 comments

Hi, i run sudo ./bloody and have message

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

What i need to do?

lotarbo avatar Dec 28 '17 09:12 lotarbo

You need to hack your mouse in like so

https://github.com/maxmati/a4tech-bloody-linux-driver/pull/21/commits/8ac3427281e42ae98212bcf3229f2c4753108d8c

you can get the IDs from lsusb

C0rn3j avatar Feb 06 '18 15:02 C0rn3j

@C0rn3j Thank you, this is work)

lotarbo avatar Feb 06 '18 15:02 lotarbo

@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

C0rn3j avatar Feb 06 '18 19:02 C0rn3j

18c7

Mouse - A4Tech Bloody V5

lotarbo avatar Feb 07 '18 09:02 lotarbo

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 ^^

C0rn3j avatar Feb 09 '18 07:02 C0rn3j

If you say how -> i do this)

lotarbo avatar Feb 09 '18 09:02 lotarbo

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

C0rn3j avatar Feb 09 '18 09:02 C0rn3j

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)

lotarbo avatar Feb 09 '18 09:02 lotarbo