View previous topic :: View next topic |
Author |
Message |
HandlingThrowback n00b
Joined: 11 Dec 2020 Posts: 2
|
Posted: Sat Dec 12, 2020 1:15 am Post subject: libinput not recognizing devices |
|
|
Hi all. New gentoo user here. I'm having trouble getting my keyboard+mouse working.
`libinput list-devices` doesn't list several devices. Unplugging+replugging usb devices sometimes works, but that's not a solution (it's a laptop). If I unplug+replug a working keyboard, it stops working until I reboot.
My init system is OpenRC. I'm running sway(wayland) as a window manager and don't have X installed. All keyboards work fine in the tty.
Here's the dmesg
Other system information:
profile: default/linux/amd64/17.1/no-multilib/hardened/selinux (stable)
groups: wheel audio video input me
USE="dbus peer_perms open_perms wayland -X alsa pulseaudio"
I don't have a login manager such as consolekit or elogind. [/url]
Last edited by HandlingThrowback on Sat Dec 12, 2020 2:53 am; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54824 Location: 56N 3W
|
Posted: Sat Dec 12, 2020 2:19 am Post subject: |
|
|
HandlingThrowback,
Welcome to Gentoo.
We need all of dmesg. What should be there but is missing is just as important as what in actually there.
When its filtered, its not possible to pick up missing entries.
Make friends with wgetpaste because dmesg is too big for a post.
Put dmesg onto a pastebin and post the link. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
HandlingThrowback n00b
Joined: 11 Dec 2020 Posts: 2
|
Posted: Sat Dec 12, 2020 2:57 am Post subject: |
|
|
NeddySeagoon: I updated my original post with a link to the full dmesg |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54824 Location: 56N 3W
|
Posted: Sat Dec 12, 2020 12:24 pm Post subject: |
|
|
HandlingThrowback,
Your dmesg looks OK. I've seen problems with your touchpad as its an i2c_designware device.
Detection of i2c devices is difficult.
Getting back to USB devices and intermittent problems, I'm aware of several sources of pain.
Loading modules in the wrong order.
Loading modules for USB root hubs you don't have, interfering with the drives you do need.
USB bus powered devices overloading the bus.
We can investigate this by analysis.
Please put your kernel .config file onto a pastebin.
Put the output of
Before you post that make sure all your usb devices appear in
The -vvv gives enough information to reconstruct the bus power distribution tree.
Please post the output of It can go to a pastebin if you prefer.
Lastly, the module load order when its working and not working.
will show that. So that's two lsmod outputs.
Kernel modules come and go dynamically. The first loaded module is at the bottom of the output.
The USB modules may be reordered as a result of unplugging the device, then reconnecting it. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Sat Dec 12, 2020 3:22 pm Post subject: |
|
|
First, the info requested by NeddySeagoon is very important.
Second, I note (don't have the link handy) that a forum poster had trouble with libinput and went back to evdev, I did a new install last week and the mouse didn't work. I also got error messages "Your LiteOn USB keyboard is too slow >75ns". I had to power button out of the install. I re-entered the install via chroot, changed INPUT_DEVICES to "evdev", updated world and sure enough it works now. I provide this as information and potential fallback, but it is best if you can get libinput working. BTW, The keyboard is Microsoft branded, apparently really made by LiteOn. (It was the only one I could find in beige to match the old PS/2 leyboard).
OK, back to solving your problem the right way. |
|
Back to top |
|
|
|