F5F Stay Refreshed Software Operating Systems Mouse issue with CPS on Manjaro GNOME Linux

Mouse issue with CPS on Manjaro GNOME Linux

Mouse issue with CPS on Manjaro GNOME Linux

A
angel856
Junior Member
34
01-16-2016, 06:23 PM
#1
I bought the Bloody a70 Matte Black mouse with drag clicking functionality. It works smoothly on Windows, Mac OS, and Chrome OS. On Manjaro it only registers around 4 clicks per second, whereas it should be 25-50. I suspect a kernel or driver problem, similar to what happens in pop!_OS. I don’t know how to fix it. This issue appears with kernel versions 5.10.41 and 4.19.19. Thanks for your assistance.
A
angel856
01-16-2016, 06:23 PM #1

I bought the Bloody a70 Matte Black mouse with drag clicking functionality. It works smoothly on Windows, Mac OS, and Chrome OS. On Manjaro it only registers around 4 clicks per second, whereas it should be 25-50. I suspect a kernel or driver problem, similar to what happens in pop!_OS. I don’t know how to fix it. This issue appears with kernel versions 5.10.41 and 4.19.19. Thanks for your assistance.

K
KARLEISHAK
Member
197
01-17-2016, 03:00 AM
#2
It seems the mouse isn't officially recognized and is only identified as a standard generic mouse. Consider using the AUR package for Manjaro at the provided link.
K
KARLEISHAK
01-17-2016, 03:00 AM #2

It seems the mouse isn't officially recognized and is only identified as a standard generic mouse. Consider using the AUR package for Manjaro at the provided link.

F
FyrewallPlayz
Junior Member
29
02-04-2016, 11:31 PM
#3
I'm facing issues while installing the package. The command `makepkg -si` triggers an error: "Any ideas?" When I run it, it shows warnings about dependencies and build problems. After some steps, it fails to write the package due to permissions on the build directory. It seems the CMake setup isn't working correctly.
F
FyrewallPlayz
02-04-2016, 11:31 PM #3

I'm facing issues while installing the package. The command `makepkg -si` triggers an error: "Any ideas?" When I run it, it shows warnings about dependencies and build problems. After some steps, it fails to write the package due to permissions on the build directory. It seems the CMake setup isn't working correctly.

M
MonsterCrewBR
Member
62
02-07-2016, 05:46 AM
#4
Install the base-devel package group and check if the issue is fixed.
M
MonsterCrewBR
02-07-2016, 05:46 AM #4

Install the base-devel package group and check if the issue is fixed.

M
MrZxs
Junior Member
6
02-07-2016, 06:28 AM
#5
The problem remains unresolved. I searched for additional drivers on the aur and elsewhere. Could there be a method to obtain the Windows drivers and transfer them to Linux?
M
MrZxs
02-07-2016, 06:28 AM #5

The problem remains unresolved. I searched for additional drivers on the aur and elsewhere. Could there be a method to obtain the Windows drivers and transfer them to Linux?

H
hawk5strike
Member
55
02-07-2016, 09:51 AM
#6
Windows and Linux differ significantly at the driver level, making it unlikely they are fundamentally the same.
H
hawk5strike
02-07-2016, 09:51 AM #6

Windows and Linux differ significantly at the driver level, making it unlikely they are fundamentally the same.

C
chkm8te
Junior Member
8
02-10-2016, 12:12 PM
#7
The Driver source must already exist as open-source. Linux provides one compatibility layer for drivers, ndiswrapper, but it is limited to network devices and has caused many issues since its release. It seems your build setup might be faulty—possibly due to the file at "/home/jackb/Downloads/a4tech-bloody-driver-git/CMakeFiles/CMakeOutput.log". In the meantime, the Driver code appears to be under maintenance, so I've prepared an AUR package for you. Be aware of the installation steps: download the file, open a terminal in the downloaded folder, run sudo pacman -U a4tech-bloody-driver-git-r159.37be7d6-1-any.pkg.tar.zst, then uninstall with sudo pacman -R a4tech-bloody-driver-git. Use it as needed.
C
chkm8te
02-10-2016, 12:12 PM #7

The Driver source must already exist as open-source. Linux provides one compatibility layer for drivers, ndiswrapper, but it is limited to network devices and has caused many issues since its release. It seems your build setup might be faulty—possibly due to the file at "/home/jackb/Downloads/a4tech-bloody-driver-git/CMakeFiles/CMakeOutput.log". In the meantime, the Driver code appears to be under maintenance, so I've prepared an AUR package for you. Be aware of the installation steps: download the file, open a terminal in the downloaded folder, run sudo pacman -U a4tech-bloody-driver-git-r159.37be7d6-1-any.pkg.tar.zst, then uninstall with sudo pacman -R a4tech-bloody-driver-git. Use it as needed.

A
AmazinglyCool
Senior Member
695
02-17-2016, 08:37 PM
#8
can any1 tell me how to do it on pop os
A
AmazinglyCool
02-17-2016, 08:37 PM #8

can any1 tell me how to do it on pop os