When the GUI is started OS reacts very slowly with a huge lag
(usually >3s) to mouse and keyboard. This happens only in the GUI. On a console or via ssh reaction to mouse and keyboard is as expected, IOW:
fast. This happens even if CPU is idleing.
Hi *.*,
I've got a Compute Modul 4 (2GB RAM) on a Waveshare CM4-IO-BASE-A board (https://www.waveshare.com/wiki/CM4-IO-BASE-A).
I installed a fresh Raspberry OS (bookworm) on it.
Keyboard and mouse are wireless Logitech MK-250 connected with a
dongle to USB.
When the GUI is started OS reacts very slowly with a huge lag
(usually >3s) to mouse and keyboard. This happens only in the GUI. On a console or via ssh reaction to mouse and keyboard is as expected, IOW:
fast. This happens even if CPU is idleing.
Does anyone have an idea what could be the reason for that slow reaction?
Or how I can find out?
One more thing: I use a 4K LCD display connected via HDMI. The graphics driver is wayland. But the same issue occurs using X11.
TIA, Stefan
Try usbhib.kbpoll=0 (or some other low number)
from https://patchwork.kernel.org/project/linux-input/patch/20180321162825.2709-1-filipalac@gmail.com/
(It's long been a problem with erratic keyboard behaviour on some keyboards due to the Pi's dwc2 USB 2 controller. I guess on the CM4 you don't have a USB 3
controller which should be better)
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 16/10/2023 07:00, Stefan Kaintoch wrote:
When the GUI is started OS reacts very slowly with a huge lagFWIW I've noticed this on my *86 laptop as well.
(usually >3s) to mouse and keyboard. This happens only in the GUI. On a
console or via ssh reaction to mouse and keyboard is as expected, IOW:
fast. This happens even if CPU is idleing.
Trying to log in a freshly booted Mint 20 the password cannot
immediately be entered.
Since its a boot issue I naturally blame Poettering and systemd.
I'm tempted to blame Poettering, too ;-)
But this cannot be the reason. Slow keyboard reaction happens only on
GUI, not on console or ssh. But it would happen on both if systemd was
the reason. Furthermore it happens *all the time*, even after login.
Bye, Stefan
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 140:33:59 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,239 |