libinput doesn't recognise any devices

[zinstack]

So my problem is I want to use libinput, but libinput-list-devices shows none and libinput-debug-events shows "Expected device added events on startup but got none. Maybe you don't have the right permissions?". But, in fact, i use root with all these commands. All the devices show up in dmesg and, using cat, I managed to find needed devices in /dev/input/event*, and currently I have keyboard mapped to /dev/input/event5 and touchpad mapped to /dev/input/event9. GPM works just perfectly. I have a synaptics touchpad, some "general" ps/2 keyboard, a laptop and a lot of time. I have all drivers incompiled, run without initrd and have absolutely no modules. EVDEV, PS2_SYNAPTICS and PS2_SYNAPTICS_SMBUS were set to yes. Maybe that's because I messed up with use flags? I tried not to edit them and in /etc/portage/make.conf only have alsa and input_devices_libinput. After switching to kde profile it didn't help either (before there was a clean default/linux/amd64/13.0 one). More than that, X doesn't recognise my keyboard. So what am I doing wrong? How do I fix this?

[LIsLinuxIsSogood]

Do you have an Xorg log, the best advice I can give you is to include in your post some of the basic troubleshooting information and then let someone help steer you over to victory! For what you described, I would think that an X log should show an error regarding the keyboard. Also, depending on the Xorg configuration file, kernel settings, etc. there's a lot of potential things that could be an issue so it is helpful to see the output from your system.

If you like post back using wgetpaste or similar pastebin tool with emerge --info, and any relevant logs (the Xorg.log is important) that are stored in the folder /var/log and you should be able to catch the attention of some good answers from adding some more of that type of information here to the picture!

[zinstack]

[url=https://1drv.ms/f/s!As_1mBvrdwF7hKcnhthvDMZ7cYXdjw]Here[/url] are my settings and logs. The problem is not in Xorg, its libinput. And, I think the keyboard problem has the same cause as a touchpad, so it will probably be easy to solve, just as we know why doesn't libinput work as intended.

[mir3x]

You don't have even anything related to libinput in logs.
Something like:

[zinstack]

[mir3x]

Your problem is xorg doesnt even try to use libinput.
And I meant xorg.conf
_________________
Sent from Windows

[Myu]

For what it's worth, I've this file in /etc/X11/xorg.conf.d/40-libinput.conf

[LIsLinuxIsSogood]

Something I just realized about my own similar issue with using libinput on my laptop as a replacemet for evdev and synaptics, is that while the wiki says the following:

[LIsLinuxIsSogood]

If you are sticking with libinput as your driver (not sure if that's a good idea), but here is what the wiki desribesto make sure that X can be aware of libinput.
In other words, it is not enough to simply compile it with the use flag, but you actually have to go the extra step of configuring, as mentioned in the wiki here:

[zinstack]

Do you even guys read my messages? Even with 40-libinput.conf in xorg.conf.d and libinput in INPUT_DEVICES, xorg won't use the keyboard or touchpad, because if libinput doesn't have a basic idea of input devices in my system, the xorg won't as well. I'm telling again: the main problem is in libinput, not xorg, if xorg doesn't use libinput it's just another story and has a very easy fix of editing some config files and maybe recompiling xserver, but, mainly I was surprised by that libinput doesn't recognise any devices. It's no surprise that xinput won't show anything useful. Yes, I had problems with X not using libinput, but this is just above the water. As I already texted in my latest message, I already have everything set up, just as needed, but neither the keybord, nor the touchpad are having no effect, though in logs it does show that it loads libinput.

[Ant P.]

You're right, this isn't anything to do with Xorg (so far). Besides, most of the suggestions above to change xorg.conf are wrong and misleading. Xorg loads files from /usr/share/X11/xorg.conf.d automatically, copying or linking things from there does nothing at best and more likely makes things worse. But that can wait until later.


It would help to figure out what's going on if we could see the full output from the following:

[zinstack]

[mir3x]

So maybe you installed xorg with 'minimal' flag enabled ? If yes then disable it.

[zinstack]

[LIsLinuxIsSogood]

Edit: I didn't see the response from Ant P. requesting more info, so I retract all of this below.



zinstack, I realize you are frustrated because it is not a quick answer or the one you want, but in fairness to everyone else, since you have not yet posted the result of emerge --info xorg-server or xorg anything-else, not only is it hard to say what may be the problem, but also concerning is you've provided no support to the problem being outside or not within Xorg. Personally, I think if you are not against sharing it, then you should bypass your own beliefs and then share that information about xorg, since that is what is being asked. It seems like a critical component here, since regardless whether you are running Wayland or whatever libinput is a requirement and has to work with both of those systems (or either one). Do you catch my drift?

I will stick to my initial suggestion for you to bypass libinput drivers in favor of the slowly deprecated ones (evdev and synaptics) but that is because you are so concerned with the use of drivers, when in reality it really doesn't matter as long as things work.

But, just so you have some faith in my answer as well, there is no reason to think that evdev is going to be at least any time in the near future an obsolete tool.

[LIsLinuxIsSogood]

[krinn]

[zinstack]

[Jaglover]

Despite repeated requests there is no emerge --info. Thus we do not know what init system is used and anything else about this system. Anyhow, there is a udev rule responsible for assigning input group, /etc/udev/rules.d/99-dev-input-group.rules.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!

[LIsLinuxIsSogood]

Providing emerge—info dev-libs/libinput and x11-drivers/xf86-input-libinput, please if possible..

Those permission bits as krinn mentioned and as pointed to earlier are probably not right, so lets check into that.

[zinstack]

Ok, sorry. I always forget. Here is "emerge --info", "emerge --info libinput", and "emerge --info xf86-input-libinput". Oh, and I've found that dhcpcd is also having trouble finding interfaces, even though wlan0 is up and connected. Guess that may be useful.

[Jaglover]

[zinstack]

[Ant P.]

[Melunlina]

Thanks guys, starting the udev and udev-trigger services manually solved the same problem with my new Logitech G413 keyboard. Curious, why these services were stopped.