Closed jacksonbaxter closed 8 months ago
Same output, and config not works at all $ sudo logid -v [sudo] password for mariusz: [DEBUG] Unsupported device /dev/hidraw1 ignored [DEBUG] Unsupported device /dev/hidraw2 ignored [DEBUG] Unsupported device /dev/hidraw3 ignored [INFO] Detected receiver at /dev/hidraw4 [DEBUG] Unsupported device /dev/hidraw5 ignored [DEBUG] Unsupported device /dev/hidraw6 ignored [DEBUG] Unsupported device /dev/hidraw0 ignored
$ sudo systemctl status logid.service ● logid.service - Logitech Configuration Daemon Loaded: loaded (/lib/systemd/system/logid.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2024-02-19 22:04:01 CET; 5min ago Main PID: 2647 (logid) Tasks: 8 (limit: 37710) Memory: 4.9M CPU: 31ms CGroup: /system.slice/logid.service └─2647 /usr/local/bin/logid
lut 19 22:04:01 mariusz-laptop systemd[1]: Started Logitech Configuration Daemon. lut 19 22:04:01 mariusz-laptop logid[2647]: [INFO] Detected receiver at /dev/hidraw4 lut 19 22:07:49 mariusz-laptop logid[2647]: [INFO] Device found: MX Master 3S on /dev/hidraw4:2 lut 19 22:08:05 mariusz-laptop logid[2647]: [INFO] /dev/hidraw4:2 fell asleep. lut 19 22:08:22 mariusz-laptop logid[2647]: [WARN] Failed to add device /dev/hidraw7 after 5 tries. Treating as failure. lut 19 22:08:22 mariusz-laptop logid[2647]: [WARN] Failed to add device /dev/hidraw7 after 5 tries. Treating as failure. lut 19 22:09:59 mariusz-laptop logid[2647]: [INFO] /dev/hidraw4:2 woke up.
I cannot make mine to work using logi bolt as well
I was having this problem when running the compiled binary directly; when I installed it, the problem went away
I was having this problem when running the compiled binary directly; when I installed it, the problem went away
It worked when you built it directly from the install? I can't it to work correctly whether I install it to arch using pacman or when I build the installation directly with my MX Master 3s.
Hi! I was troubleshooting with this problem aswell, I managed to fix it by:
sudo logid --config abcdefg
(set the config an unexisting one to force logid to read the default one at /etc/logid.cfg)systemctl restart logid
Restart the daemonAnd now checking with status we see the mouse.
And then it was working as expected. Had to change a couple of default settings to fix high resolution scrolling but I'm happy with having it fixed on my machine.
Kudos to Michael Verschoof on his amazing post on Medium about this specific problem.
Hi! I was troubleshooting with this problem aswell, I managed to fix it by:
- Compiling the binaries. (I'm working on a Manjaro Linux, but some people recommended building the binaries)
- Copying the default configuration on the default config file at /etc/logid.cfg
- Fixing the device configuration name to "MX Master 3S" on /etc/logid.cfg Link to my logid.cfg
sudo logid --config abcdefg
(set the config an unexisting one to force logid to read the default one at /etc/logid.cfg)systemctl restart logid
Restart the daemonAnd now checking with status we see the mouse.
And then it was working as expected. Had to change a couple of default settings to fix high resolution scrolling but I'm happy with having it fixed on my machine.
Kudos to Michael Verschoof on his amazing post on Medium about this specific problem.
Thank you for making clear steps. I am using Ubuntu, and I installed logiops by compiling source code, and then followed your steps. However, logiops detects only receiver, not my mouse. Any idea what to troubleshoot?
EDIT: FIXED IT! Turns out, I still had Solaar installed. Not running, but installed, and instantly after uninstalling, my mouse was detected by logiops.
Hi! I was troubleshooting with this problem aswell, I managed to fix it by:
- Compiling the binaries. (I'm working on a Manjaro Linux, but some people recommended building the binaries)
- Copying the default configuration on the default config file at /etc/logid.cfg
- Fixing the device configuration name to "MX Master 3S" on /etc/logid.cfg Link to my logid.cfg
sudo logid --config abcdefg
(set the config an unexisting one to force logid to read the default one at /etc/logid.cfg)systemctl restart logid
Restart the daemonAnd now checking with status we see the mouse.
And then it was working as expected. Had to change a couple of default settings to fix high resolution scrolling but I'm happy with having it fixed on my machine.
Kudos to Michael Verschoof on his amazing post on Medium about this specific problem.
This finally worked for me. Thanks so much! Only things I may have done different:
sudo logid --config abcdefg
sudo systemctl restart logid
sudo logid --config /etc/logid.cfg
after correcting the config file.sudo systemctl restart logid
I have my Logitech MX Master 3S connected to my computer via the Bolt Receiver. When I run logid -v I only get this with no connected device.
Does anyone have a solution to this?