Arch Linux

le_grande_castel

Member

Registered: 2022-05-16

Posts: 10

Keyboard and Mouse do not intialize properly after boot

I have an Anne Pro 2 which I keep on wired and a wireless G502 Lightspeed, running on linux-lts-5.15.39-1 with KDE Plasma. After boot, the keyboard and mouse don't initialize. The keyboard usually takes about a minute after the login screen appears to work, whilst the mouse needs plugging and unplugging (I use its own dongle which I plug and unplug), after which it works. The keyboard doesn't work with this method, I simply have to wait, sometimes more, sometimes less. I can't remember when this started to happen. A few weeks ago the keyboard wouldn't have issues, and the mouse took like a minute to connect. Now it's obviously worse. I can't recall what I have been installing in the past few weeks that could cause this issue, the only ones related would be Piper and ObinsKit.

Oh also, related but not as important, whenever i plug/unplug the dongle or if I put the mouse in wired mode, it has its own sensitivity, I have to go into settings, change it and then change it back so that the normal speed is restored.

I will provide any information necessary, I don't even know where to look for this issue. Thank you.

nordkamp

Member

From: Queensland, AU

Registered: 2022-05-17

Posts: 10

Website

Re: Keyboard and Mouse do not intialize properly after boot

Hey, I'm using a G502 Lightspeed as well so maybe I can help you here. As for your keyboard initialising, we should start by finding out whether or not it initialises during boot at all. I see that you can connect it in wired mode, if it's purely acting in wired mode do the lights come on at all during the boot process before the login screen?

In any case I can give you something to check. In your /etc/mkinitcpio.conf you should see whether 'keyboard' and 'keymaps' without quotes is present in the HOOKS variable. You can check this very easily by running the command:

grep keyboard /etc/mkinitcpio.conf
grep keymap /etc/mkinitcpio.conf

and if HOOKS=(.....) gets output to your terminal you know that it's there, and if it's not there you can try editing mkinitcpio.conf, adding keyboard and keymap to your list of hooks and then running:

sudo mkinitcpio -p linux

On your next reboot the kernel should try and initialise your keyboard at boot time.

About your G502's different sensitivity in wired and wireless mode - I have run into this as well. The reason for this occurring is because the wireless dongle emulates a mouse device, so it shows up as a mouse. Also, when the mouse is plugged in in wired mode, it is able to transmit data through the cable as well so the system detects it as a second, separate mouse device. If you plug the mouse in, go into your mouse settings in plasma and click on the Device drop down menu you'll see what I mean. You should then just be able to make the settings identical for both devices, seems to work for me at least.

Last edited by nordkamp (2022-05-17 10:39:37)

---

"Navigating one's life is like being a pathfinding algorithm with no paths to find." - Ghandi, probably