You are not logged in.
Pages: 1
Hi,
For some time I've experiencing lagginess when moving the mouse across the screen. I even bought a new one since I had thought the previous one was faulty. After some googling I came across the term USB autosuspend, which may cause lagging.
So I created the file /etc/udev/rules.d/50-usb_power_save.rules with the content:
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="c52b", ATTR{power/autosuspend}="-1"
and restarted the computer. After restarting I'm still expercing lagging.
When the cursor freezes, I move the mouse, click several times and usually the mouse is starting to work. In such a situation, dmesg shows:
[ 34.295551] audit: type=1334 audit(1644394309.881:147): prog-id=0 op=UNLOAD
[ 34.295564] audit: type=1334 audit(1644394309.881:148): prog-id=0 op=UNLOAD
[ 34.295570] audit: type=1334 audit(1644394309.881:149): prog-id=0 op=UNLOAD
[ 34.785589] logitech-hidpp-device 0003:046D:4094.0007: HID++ 4.5 device connected.
It seems that udev fails to work.
Here's the output of lsusb:
Bus 002 Device 002: ID 2537:1068 Norelsys NS1068/NS1068X SATA Bridge Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey]
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Note that I have two USB receivers: one for mouse, the other for keyboard. The keyboard works fine, however, a few months ago I also experienced problems with it, namely at some occasions it completely failed to work or the keys lagged. I used Debian back then. Now with Arch the keyboard is working properly.
The mouse is not faulty. I connected it to a different computer with Windows and it worked without any issues. I used the LTS kernel and the latest (non-lts). There is no difference as to the mouse lagginess.
Please help.
Last edited by menteith (2022-02-09 11:12:28)
Long time Debian user who switched to Arch.
Offline
The disconnect isn't from the dongle - the mouse powers down when idle to save battery. The question is why this causes lags.
If you track "dmesg -w", does the logitech-hidpp-device register the connect immediately when you start moving the mouse?
If you rest the mouse, the press a button, the move it - does it respond immediately or is there still a lag?
Online
Seth,
Many thanks for your help.
On LTS kernel many times when I started using the mouse, the the logitech-hidpp-device register entry was in dmesg. However, on non-LTS kernel it doesn't seem to occur every time.
One thing just happened. I started my computer and the mouse was almost completely non-responding. Restarting computer didn't change anything. But when I disconnected my SDD disk connected to a USB port the mouse is working flawlessly.
After disconnecting dmesg -w showed:
[ 212.312266] usb 2-1: USB disconnect, device number 2 ,
Perhaps it is not the kernel itself. It may have always been always SDD disk connected to USB port. This is only a guess. I can test whether connecting the disk causes the mouse lagging.
Last edited by menteith (2022-02-10 10:46:48)
Long time Debian user who switched to Arch.
Offline
I'm experiencing the same issue. It began not so long ago.
- It happens to me no matter what is connected via USB (I use hub at home, no hub at work)
- I use another mouse (both A4tech wireless mouse of the same type) at work - both started having this issue at the same time (most likely a software issue)
@menteith Did you manage to solve it? The problem persists?
I'm not the sharpest tool in the shed. Say it to me like I'm 5, please!
Arch | ZFS | systemd | XFCE | ASUS S435 | CPU: Intel 11th gen | GPU: Intel Iris Xe Graphics
Offline
Thread 2040240 seems to be about the same thing.
I'm not the sharpest tool in the shed. Say it to me like I'm 5, please!
Arch | ZFS | systemd | XFCE | ASUS S435 | CPU: Intel 11th gen | GPU: Intel Iris Xe Graphics
Offline
It stopped, now everything is OK. I don't know what caused it or why everything is OK now.
Long time Debian user who switched to Arch.
Offline
Pages: 1