We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I can't solve the problem....LIBUSB_ERROR_TIMEOUT sudo ./bloody Available devices: 2:Bloody P91 Enter device address: 2 Current backlight level: LIBUSB_ERROR_TIMEOUT 239 Select backlight level(0-3):0 LIBUSB_ERROR_TIMEOUT Select backlight level(0-3)
Mouse.cpp case BLOODY_J95S_PID: name = "Bloody J95S"; break; case BLOODY_P91_PID: name = "Bloody P91"; break; default: name = "Unknown";
Mouse.h static const int BLOODY_A9_PID = 0x1003; static const int BLOODY_P91_PID = 0x7ccf; . . . ...BLOODY_A9_PID, BLOODY_P91_PID};
lsusb -d 09da: | cut -d ' ' -f6 | cut -d ':' -f2 7ccf Mouse: Bloody P91 PRO OS: Arch Linux x64 libusb 1.0.26-1 What could be the problem?
The text was updated successfully, but these errors were encountered:
This repo is dead, since you're on Arch, use aur/a4tech-bloody-driver-git
Still a dead repo(it is mine), but less dead than that and should work with your mouse.
Sorry, something went wrong.
No branches or pull requests
I can't solve the problem....LIBUSB_ERROR_TIMEOUT
sudo ./bloody
Available devices:
2:Bloody P91
Enter device address: 2
Current backlight level: LIBUSB_ERROR_TIMEOUT
239
Select backlight level(0-3):0
LIBUSB_ERROR_TIMEOUT
Select backlight level(0-3)
Mouse.cpp
case BLOODY_J95S_PID:
name = "Bloody J95S";
break;
case BLOODY_P91_PID:
name = "Bloody P91";
break;
default:
name = "Unknown";
Mouse.h
static const int BLOODY_A9_PID = 0x1003;
static const int BLOODY_P91_PID = 0x7ccf;
.
.
.
...BLOODY_A9_PID, BLOODY_P91_PID};
lsusb -d 09da: | cut -d ' ' -f6 | cut -d ':' -f2
7ccf
Mouse: Bloody P91 PRO
OS: Arch Linux x64
libusb 1.0.26-1
What could be the problem?
The text was updated successfully, but these errors were encountered: