[SOLVED] evdev issue: no Input w/ Mouse or Keyboard in X -current

slugman · 03-12-2016, 01:37 PM

Hey everyone,

I just installed the latest current (I rsync'ed with rackspaces rsync mirror 3/10--the last update). The install went smooth. Everything was working great until I tried booting into X.

Background: I have a Nvidia GT310. I started by blacklisting nouveau, rebooted, and installed the latest nvidia blob. The Nvidia installation went smoothly w/ the latest current(I allowed the nvidia installer to configure my xorg.config).

The prolbem is when after I start X. I can launch the x-server just fine, however shortly after that I lose all input. I can't use my mouse or keyboard. The messed up thing is I can't even switch to another terminal nor can I exit x (ctrl+alt+del). I have to force a reboot.

Looking at my Xorg log, It looks like my problem starts shortly after x attempts to load evdev:

Code:

[   988.292] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event2)
[   988.824] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   988.824] (**) Power Button: Applying InputClass "keyboard-all"
[   988.824] (II) LoadModule: "evdev"
[   988.825] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[   988.853] (II) Module evdev: vendor="X.Org Foundation"
[   988.853]    compiled for 1.17.2, module version = 2.9.2
[   988.853]    Module class: X.Org XInput Driver
[   988.853]    ABI class: X.Org XInput driver, version 21.0
[   988.853] (EE) module ABI major version (21) doesn't match the server's version (22)
[   988.853] (II) UnloadModule: "evdev"
[   988.853] (II) Unloading evdev
[   988.853] (EE) Failed to load module "evdev" (module requirement mismatch, 0)
[   988.853] (EE) No input driver matching `evdev'

So, its saying there is no input driver matching evdev, but when I look at lsmod, I see:

Code:

root@darkstar:/home/slugman# lsmod | grep evdev
evdev                  11690  8

.. which leads me to believe that evdev is in fact loaded.

If evdev is in fact loading, then we have to look at previous message, indicating a version mismatch:

Code:

[   988.853] (II) Module evdev: vendor="X.Org Foundation"
[   988.853]    compiled for 1.17.2, module version = 2.9.2
[   988.853]    Module class: X.Org XInput Driver
[   988.853]    ABI class: X.Org XInput driver, version 21.0

According to the current changelog, current is on xorg 1.18.1. It looks like I need to rebuild evdev for the current version of xorg current is useing.

Does anyone have any suggestions? I don't mind compiling evdev for the current xorg version. I immagine I'd have to grab the sources first, but I'm not sure how to proceed.

Any help is appreciated!

orbea · 03-12-2016, 01:46 PM

For me in Slackware64-current.

Code:

[    74.278] (II) Module evdev: vendor="X.Org Foundation"
[    74.278]    compiled for 1.18.0, module version = 2.10.1
[    74.278]    Module class: X.Org XInput Driver
[    74.278]    ABI class: X.Org XInput driver, version 22.1

Tonus · 03-12-2016, 02:05 PM

Might be a bad rsync. You could try to run it once more or try slackpkg, current is moving quite fast these days...

kjhambrick · 03-12-2016, 02:50 PM

slugman --

I just now did an upgrade for this week's current package updates.

I am running xf86-input-evdev-2.10.1-x86_64-1

What's odd about your evdev-2.9.x is that mine was installed on Feb 09 when my Laptop was installed new.

Code:

# cd /home/dld/slackware
# ls -lad $(find slackware-current-32 slackware-current-64 -type f -iname "*evdev*t?z")

-rw-r--r-- 1 4015 4015 65776 Apr 19  2015 slackware-current-32/slackware/x/libevdev-1.4.1-i486-1.txz
-rw-r--r-- 1 4015 4015 46444 Jan 12 15:27 slackware-current-32/slackware/x/xf86-input-evdev-2.10.1-i586-1.txz
-rw-r--r-- 1 4015 4015 62196 Apr 18  2015 slackware-current-64/slackware64/x/libevdev-1.4.1-x86_64-1.txz
-rw-r--r-- 1 4015 4015 45804 Jan 12 13:54 slackware-current-64/slackware64/x/xf86-input-evdev-2.10.1-x86_64-1.txz

That looks like the culprit.

But where did you get it ?

-- kjh

My `ver` command is a handy package query tool ( I've got one for Slackware and another for RPM-Based Systems )
so `ver` works on all 'my' boxes.

ver evdev` returns these packages

Code:

# ver evdev

-rw-r--r-- 1 root root 1199 Feb  8 07:14 /var/log/packages/libevdev-1.4.1-x86_64-1
-rw-r--r-- 1 root root 1351 Feb  8 07:14 /var/log/packages/xf86-input-evdev-2.10.1-x86_64-1

This is the `ver` command

Code:

#!/bin/sh
#
# ver command for slackware packages
#
for i in $*
do
   j="`2regex $i`"                                                                                  
   ls -la /var/log/packages/*${j}* 2>/dev/null                                                      
done                                                                                                
                                                                                                    
exit 0

This is the sub-referenced `2regex` command:

Code:

#!/bin/sh
#
# 2regex command turns alpha to case-insensitive for ls
#
echo $@ |
gawk '
BEGIN {
   # 
   # portable ... runs on nawk or gawk
   #
   Lower = "abcdefghijklmnopqrstuvwxyz"
   Upper = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"

   for ( i = 1 ; i <= length( Lower ) ; i ++ )
   {
      L = substr( Lower, i, 1 )
      U = substr( Upper, i, 1 )

      LoAry [L] = i
      UpAry [U] = i
      REAry [i] = "[" U L "]"
   }
}
{
   for ( i = 1 ; i <= length( $0 ) ; i ++ )
   {
      if (( c = substr( $0, i, 1 )) in LoAry )
         printf( "%s", REAry [LoAry [c]] )
      else if ( c in UpAry )
         printf( "%s", REAry [UpAry [c]] )
      else
         printf( "%s", c )
   }
   print ""
}'

slugman · 03-12-2016, 03:01 PM

thanks for the quick reply guys. So, I don't believe there was an issue w/ the rsync. Here is what I see when I check /var/log/packages:

Code:

root@darkstar:/home/slugman# ls /var/log/packages/ | grep -i xf86-input-evdev
xf86-input-evdev-2.10.0-x86_64-3
xf86-input-evdev-2.10.1-x86_64-1
xf86-input-evdev-2.9.2-x86_64-1
xf86-input-evdev-2.9.2-x86_64-2

So, it looks like I do have the latest package for evdev installed: xf86-input-evdev-2.10.1-x86_64-1. However, I don't know why X is defaulting back to evdev 2.9.2.

I'll try uninstalling the old evdev packages (xf86-input-evdev-2.9.2-x86_64-1), and see if that makes a difference.

slugman · 03-12-2016, 03:17 PM

Those are some cool scripts kjhambrick, I went ahead and ahead and saved them.

Orbea and Tonus, I believe I spoke too soon. I don't think I'm rsyncing properly. Apparently, xf86-input-evdev was one of the packages that was updated. This is why I have 2.9.2, 2.10.0, and 2.10.1 in my local rsync directory. However, the older versions should have been removed.

A quick refresher on the rsync, this is the last command I used:

Code:

rsync -avuP mirror directory

I always thought that the -u switch is what performed the "update". Is that not true? I guess I should just delete the whole directory, and rsync again to make sure I have only the new files, and the old ones left out.

I'm glad you guys pointed this out. It looks like I may have been installing a bunch of old packages along side new ones. I'll have to re-install once I've deleted the old directory, and ensured the directory contains only the latest rsync.

kjhambrick · 03-12-2016, 03:28 PM

Slugman --

Check out Eric's ( alien's ) mirror-slackware-current.sh script at:

http://www.slackware.com/~alien/

If you're mirroring the slackware repository, you definitely want a --delete somewhere in the rsync line.

I typically use:

Code:

rsync -avz --delete <<source>> <<target>>

Eric's Script has something similar, I think.

-- kjh

speck · 03-12-2016, 04:27 PM

Quote:

root@darkstar:/home/slugman# ls /var/log/packages/ | grep -i xf86-input-evdev
xf86-input-evdev-2.10.0-x86_64-3
xf86-input-evdev-2.10.1-x86_64-1
xf86-input-evdev-2.9.2-x86_64-1
xf86-input-evdev-2.9.2-x86_64-2

I'm not sure if it's the cause of your issue, but it looks like you're installing (installpkg) package updates instead of upgrading (upgradepkg) package updates. You should really only have xf86-input-evdev-2.10.1-x86_64-1 in the /var/log/packages/ directory.

slugman · 03-13-2016, 12:55 AM

Thanks guys, it was as Tonus and Orbea suspected earlier, I messed up my rsync. The install worked fine after installing from a clean--and correct--rsync.

I had some issue w/ amd-vi iommu (I had to set a kernel boot parameter "iommu=soft"), after that I was good to go!

kjhambrick, thanks for sharing that mirror script!