[solved] Bug 1200983 - mouse & keyboard not available after a reboot (needs replug the devices)
Hi @all, perhaps this can help others too: For a few months now I had Bug 1200983 "mouse & keyboard not available after a reboot (needs replug the devices)" (https://bugzilla.suse.com/show_bug.cgi? id=1200983) on my Tumblewed installation: I first thought, it only would affect mouse & keyboard in KDE, but after a while I saw, that it also happened in the Linux console. The behaviour was like this: 1. During boot the keyboard was usable as expected - one could chose the kernel to boot, enter the LUKS passphrase and so on. 2. As soon as the system was up, the keyboard lights went off. 3. The next, and only the next keypress in the console was ignored then. 4. After the second keypress the keyboard lights went on and one could use the keyboard again. 5. After a few seconds without keyboard usage the lights were switched off again and everything restarted at no 3. 6. When switching to the sddm login screen, the mouse also was "paralyzed". 7. Unplugging the keyboard and plugging it in again solved this problem. From then on keyboard and mouse worked as expected. In the last few days I found enough time to analyze the problem thoroughly. I installed a second Tumbleweed system. This one didn't show the problem. So I compared /etc, running services and so on. After disabling powertop, mouse and keyboard worked as expected after a reboot. So: The culprit was powertop! I don't understand fully, what was going on there. The pitfall is, that now my fans are running more often, so I suspect the system is using more power, which in turn will cause a lower battery runtime. Bye. Michael.
On Sonntag, 25. Juni 2023 13:30:43 CEST mh@mike.franken.de wrote:
Hi @all,
perhaps this can help others too:
For a few months now I had Bug 1200983 "mouse & keyboard not available after a reboot (needs replug the devices)" (https://bugzilla.suse.com/show_bug.cgi? id=1200983) on my Tumblewed installation: I first thought, it only would affect mouse & keyboard in KDE, but after a while I saw, that it also happened in the Linux console.
The behaviour was like this:
1. During boot the keyboard was usable as expected - one could chose the kernel to boot, enter the LUKS passphrase and so on. 2. As soon as the system was up, the keyboard lights went off. 3. The next, and only the next keypress in the console was ignored then. 4. After the second keypress the keyboard lights went on and one could use the keyboard again. 5. After a few seconds without keyboard usage the lights were switched off again and everything restarted at no 3. 6. When switching to the sddm login screen, the mouse also was "paralyzed". 7. Unplugging the keyboard and plugging it in again solved this problem. From then on keyboard and mouse worked as expected.
In the last few days I found enough time to analyze the problem thoroughly. I installed a second Tumbleweed system. This one didn't show the problem. So I compared /etc, running services and so on. After disabling powertop, mouse and keyboard worked as expected after a reboot. So: The culprit was powertop!
I don't understand fully, what was going on there. The pitfall is, that now my fans are running more often, so I suspect the system is using more power, which in turn will cause a lower battery runtime.
Bye. Michael.
I also tested with powertop running, but disabled tunables for mouse, keyboard and the usb hub, they are connected - to no avail.
participants (1)
-
mh＠mike.franken.de