You are not logged in.
Pages: 1
Hello,
I'm using a Logitech M510 on my laptop, and yesterday it stopped working. I hadn't used it for a few days prior to that, so I'm not exactly sure when it stopped working. I tried the mouse on another computer, and it worked just fine. I also tried some other mice on my laptop, and those worked fine as well. I checked lsusb, and can see the following for the non functional M510:
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
This is the output from solaar show:
solaar version 1.1.13
Unifying Receiver
Device path : /dev/hidraw0
USB id : 046d:C52B
Serial : (omitting this)
C Pending : ff
Firmware : 12.11.B0032
Bootloader : 04.16
Other : AA.AA
Has 0 paired device(s) out of a maximum of 6.
Notifications: wireless, software present (0x000900)
Device activity counters: (empty)The output was different from this before, but I tried messing around with solaar's un-pair and pair commands to correct the issue. Before the un-pairing there was a message about the device not being on, and when I attempt to pair it still thinks the device isn't on.
I followed along with this other forum post, as well as all the posts it linked to. This was all either not applicable or not successful. I tried to identify the mouse in libinput and evtest and was unable to do so.
I then downgraded systemd as this seemed to have been relevant before, this didn't work. Tried a different kernel and an older version of linux-firmware, also no luck. Here is some relevant output from journalctl:
Dec 30 15:11:08 laptop kernel: usb 3-2: new full-speed USB device number 6 using xhci_hcd
Dec 30 15:11:08 laptop kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.11
Dec 30 15:11:08 laptop kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 30 15:11:08 laptop kernel: usb 3-2: Product: USB Receiver
Dec 30 15:11:08 laptop kernel: usb 3-2: Manufacturer: Logitech
Dec 30 15:11:08 laptop kernel: logitech-djreceiver 0003:046D:C52B.000A: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2
Dec 30 15:11:08 laptop mtp-probe[11431]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Dec 30 15:11:08 laptop mtp-probe[11431]: bus: 3, device: 6 was not an MTP device
Dec 30 15:11:08 laptop mtp-probe[11459]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Dec 30 15:11:08 laptop mtp-probe[11459]: bus: 3, device: 6 was not an MTP deviceAny help or advice greatly appreciated. Thanks.
Last edited by alett (2024-12-31 21:40:25)
Offline
Please use [code][/code] tags. Edit your post in this regard.
Before the un-pairing there was a message about the device not being on, and when I attempt to pair it still thinks the device isn't on.
I tried to identify the mouse in libinput and evtest and was unable to do so.
It does not generate events in "evtest" or "libinput debug-events" or did you quit at permission errors (both need root privileges)?
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855 - post the exact I/O
I tried the mouse on another computer
Same dongle, other dongle or via bluetooth?
I also tried some other mice on my laptop
Likewise logitech va the UR or some BT devices?
Online
When testing the Logitech mouse on another computer, the same dongle it came with was used. For the testing of other mice on the laptop, two random mice that aren't Logitech devices were used. One was wireless and used with its dongle, the other was wired. Both worked without issue.
Regarding evtest and libinput, both were run as root. To be more specific, when running evtest I am provided with a list of devices (/dev/input/event*) and this list is identical when the Logitech dongle is plugged in to when it is not plugged in. The list has new options when the dongle of the other wireless mouse is plugged in. Similarly, when running libinput debug-events no output occurs when I do anything with the Logitech mouse, output occurs with the non Logitech mouse.
Offline
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stDid you try a different usb port?
Do you run some power saving tools (TLP etc.)?
https://wiki.archlinux.org/title/Power_ … utosuspend might be an issue but you'd rather lose the dongle than its contact to your device.
Online
Hello,
I ended up just buying another of the very same mouse I had before. After messing with solaar the problem had gotten worse and I didn't even realize. A few days after my second post I tried connecting the mouse to another computer and that no longer worked. I'm pretty sure I'd disconnected the receiver and mouse and that not even Solaar could reconnect them. Battery life was fine. For $20 a new one seemed like the easier option, and ended up being successful. Thank you for your time and effort helping me, I certainly appreciated it. Not sure if I should mark this as solved, seeing as it wasn't really, but the issue is no longer of concern to me.
Offline
You could tag it as "[replaced broken HW]"
Online
Pages: 1