Jump to content

Bloody a70 gaming mouse not regestering cps on Manjaro Gnome Linux

penguin1
 Share
Posted

My original post form Manjaro Forums

I recently purchased the Bloody a70 Matte Black mouse for a certain clicking method called drag clicking. To put it simply you drag your finger down the mouse to register multiple clicks. On Windows, Mac OS, and chrome OS, there are no issues with the mouse. On Manjaro, it only registers about 4 cps when it should be 25-50. I assume it is a kernel or driver issue, as it happens on pop!_OS. I have no idea how to fix it. This happens Happens on kernel 5.10.41 & 4.19.19.

Thanks for the help.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
20 hours ago, Nayr438 said:

From what I can tell, the mouse isn't officially supported and it's just detected as a generic mouse.

You could try this AUR package on Manjaro, https://aur.archlinux.org/packages/a4tech-bloody-driver-git/

I am trying to install the package, but when I type in makepkg -si i get this error: Any ideas?

 

==> Making package: a4tech-bloody-driver-git r155.2beb8fe-1 (Thu 10 Jun 2021 05:54:42 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Cloning a4tech-bloody-driver-git git repo...
Cloning into bare repository '/home/jackb/Downloads/a4tech-bloody-driver-git/a4tech-bloody-driver-git'...
warning: redirecting to https://gitlab.com/C0rn3j/a4tech_bloody_p85_driver.git/
remote: Enumerating objects: 600, done.
remote: Counting objects: 100% (199/199), done.
remote: Compressing objects: 100% (100/100), done.
remote: Total 600 (delta 125), reused 169 (delta 98), pack-reused 401
Receiving objects: 100% (600/600), 324.51 KiB | 4.92 MiB/s, done.
Resolving deltas: 100% (387/387), done.
  -> Found 60-bloody.rules
==> Validating source files with sha256sums...
    a4tech-bloody-driver-git ... Skipped
    60-bloody.rules ... Passed
==> Extracting sources...
  -> Creating working copy of a4tech-bloody-driver-git git repo...
Cloning into 'a4tech-bloody-driver-git'...
done.
==> Starting pkgver()...
==> WARNING: /home/jackb/Downloads/a4tech-bloody-driver-git/PKGBUILD is not writeable -- pkgver will not be updated
==> Starting build()...
CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
See also "/home/jackb/Downloads/a4tech-bloody-driver-git/src/a4tech-bloody-driver-git/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
    Aborting...

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Try installing the base-devel package group and see if it resolves it.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
On 6/9/2021 at 9:28 PM, Nayr438 said:

From what I can tell, the mouse isn't officially supported and it's just detected as a generic mouse.

You could try this AUR package on Manjaro, https://aur.archlinux.org/packages/a4tech-bloody-driver-git/

Still doesn't fix the issue. I looked for more drivers on the aur and other places. Do you think that there might be a way to get the windows drivers and port them over to Linux?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
On 6/10/2021 at 10:38 PM, penguin1 said:

Still doesn't fix the issue. I looked for more drivers on the aur and other places. Do you think that there might be a way to get the windows drivers and port them over to Linux?

Windows and Linux are quite fundementally different on the driver level so I doubt that.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
On 6/10/2021 at 9:38 PM, penguin1 said:

Do you think that there might be a way to get the windows drivers and port them over to Linux?

No. The Driver source would need to already be open-source.

Linux has 1 compatibility wrapper for drivers, ndiswrapper, but it is solely for Network Devices and has been a nightmare ever since it's introduction.

 

For some reason your build environment is broken, the reason as to why might be located in  

"/home/jackb/Downloads/a4tech-bloody-driver-git/src/a4tech-bloody-driver-git/CMakeFiles/CMakeOutput.log"

 

In the meantime, this Driver implementation seems to be unmaintained so I have built the AUR Package for you if you would like to use it.

 

Spoiler

 

  • Install
    • Download the below file
    • Open a terminal in the directory you downloaded it to
    • sudo pacman -U a4tech-bloody-driver-git-r159.37be7d6-1-any.pkg.tar.zst
  • Uninstall
    • sudo pacman -R a4tech-bloody-driver-git
  • Usage
    • In a terminal
      • For Graphical Interface
        • bloody
      • For Cli interface
        • bloody-cli
    • May need to restart your system or re-attach your bloody mouse before usage. May need to be run with sudo.

a4tech-bloody-driver-git-r159.37be7d6-1-any.pkg.tar.zst

 

Link to comment
Share on other sites
Link to post
Share on other sites
  • 10 months later...
Posted

can any1 tell me how to do it on pop os

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Linux, macOS and Everything Not-Windows

×