libratbag: Trying to add support for Logitech Performance MX but ratbagd --verbose=raw hangs permanently
Following the wiki over at https://github.com/libratbag/libratbag/wiki/Adding-a-new-device I added a logitech-performance-mx.device file to /usr/share/libratbag/devices/ after running lsusb. Which resulted in the following:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 10c4:8a2a Cygnal Integrated Products, Inc. HubZ Smart Home Controller
**Bus 003 Device 017: ID 046d:c52b Logitech, Inc. Unifying Receiver**
Bus 003 Device 014: ID cb10:1133
Bus 003 Device 013: ID feed:2260
Bus 003 Device 012: ID 1908:2220 GEMBIRD
Bus 003 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So the logitech unifying receiver is at 046d:c52b. My .device file looks like this:
# Logitech Performance MX - unifying
[Device]
Name=Performance MX
DeviceMatch=usb:046d:c52b
Driver=hidpp20
But the part about running sudo /usr/bin/ratbagd.disabled --verbose=raw never outputs anything. No error, no empty result, nothing. It just continues to run infinitely with a blinking cursor.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 20 (10 by maintainers)
Commits related to this issue
- hidpp10: if we can't fetch the current profile, error out Right now we initialize any hidpp10 device with one profile and then go and fetch the data. But we never check for return codes, so it always... — committed to whot/libratbag by whot 5 years ago
- hidpp10: if we can't fetch the current profile, error out Right now we initialize any hidpp10 device with one profile and then go and fetch the data. But we never check for return codes, so it always... — committed to libratbag/libratbag by whot 5 years ago
I’ll probably replace this mouse soon. I like it a lot but unfortunately its a huge battery drainer and I am starting to lose my patience charging it every 2 days. I’ll make sure to get one of the devices on the supported list.