Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
This is old, but maybe helpful: https://bbs.archlinux.org/viewtopic.php?id=292996
My thinking is you may have gotten an update, restarted, and now you're seeing this issue. What's the specific model of keyboard?
Logi MX Keys S.
I had an update available today(after this issue). Ran it but it didn’t fix the issue sadly.
Okay, so let's try connectit via BT as a test at least. You said it wasn't showing up in your BT menu, check this out.
The other thing here is that this is a wireless-only key card, so you've got a potential HID configuration problem because of that receiver. The fact that you can actually login first, THEN it stops working tells me it's something like this. The fact it works fine on LiveUSB screams settings/config issue. You may need that LiveUSB again to go in and chroot some stuff away.
It just works again after the computer being shut off for a few hours. I did quite a few restarts earlier today that didn’t help so something isn’t right. I’m thinking there’s something broken with the HID config myself.
If I was on Windows I’d reinstall the driver, check chipset driver etc. maybe check if there’s something wrong with Logitech’s software. I’ll do some digging now that I have a keyboard again to see how if I find anything.
Interesting.
Yeah, all my settings are the same as when it didn’t work.
Does linux do any driver check or something when booting?
Every boot, but it won't automatically change any settings by interacting with any of them. Gotta be something in userspace, or just the hardware acting up. Maybe change the batteries 😂
I’m almost scared of my computer now. This is the weirdest thing I have seen so far on Linux.
I’m guessing something crashed or whatever. Settings are just like they were with no changes.
Maybe I should just get a wired keyboard 😂
At least as a standby in case it happens again 😂