Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Xorg/libinput No input driver specified, ignoring this dev
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sun Jan 07, 2018 6:33 pm    Post subject: Xorg/libinput No input driver specified, ignoring this dev Reply with quote

I'm tiring to bring up a new install of my box.
When I 'startx' I have no keyboard or mouse.
Googling and reading the forms haven't got me any closer as I don't see this type of error mentioned:

"[ 912.639] (II) No input driver specified, ignoring this device."

I started out following a X11 install guide that used evdev.
When that didn't work I found instructions that said things have moved to libinput.

INPUT_DEVICES is set to only "libinput" in make.conf.
Cleared out all of the old evdev and related xf86 modules with emerge -C. Rebuilt xorg and xorg drivers.

libinput-debug-events shows all my devices are active.

Yet when I startx I STILL have no keyboard and mouse! :-(

The log below shows the devices are found then ignored.
Why are they being ignored???

The stuff at the end about being removed is from when I killed the process via ssh.


Code:

...

[   912.241] (II) AMDGPU(0): Set up textured video (glamor)
[   912.241] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[   912.347] (--) RandR disabled
[   912.348] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[   912.348] (II) AIGLX: enabled GLX_ARB_create_context
[   912.348] (II) AIGLX: enabled GLX_ARB_create_context_profile
[   912.348] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[   912.348] (II) AIGLX: enabled GLX_INTEL_swap_event
[   912.348] (II) AIGLX: enabled GLX_SGI_swap_control
[   912.348] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[   912.349] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[   912.349] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[   912.349] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[   912.349] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[   912.349] (II) AIGLX: Loaded and initialized radeonsi
[   912.349] (II) GLX: Initialized DRI2 GL provider for screen 0
[   912.353] (II) modeset(G0): Damage tracking initialized
[   912.357] (II) AMDGPU(0): Setting screen physical size to 1524 x 285
[   912.466] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   912.466] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   912.466] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   912.466] (II) LoadModule: "libinput"
[   912.466] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[   912.468] (II) Module libinput: vendor="X.Org Foundation"
[   912.468]    compiled for 1.19.5, module version = 0.25.1
[   912.468]    Module class: X.Org XInput Driver
[   912.468]    ABI class: X.Org XInput driver, version 24.1
[   912.468] (II) Using input driver 'libinput' for 'Power Button'
[   912.468] (**) Power Button: always reports core events
[   912.468] (**) Option "Device" "/dev/input/event1"
[   912.468] (**) Option "_source" "server/udev"
[   912.468] (II) event1  - (II) Power Button: (II) is tagged by udev as: Keyboard
[   912.468] (II) event1  - (II) Power Button: (II) device is a keyboard
[   912.468] (II) event1  - (II) Power Button: (II) device removed
[   912.491] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[   912.491] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   912.491] (II) event1  - (II) Power Button: (II) is tagged by udev as: Keyboard
[   912.491] (II) event1  - (II) Power Button: (II) device is a keyboard
[   912.491] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
[   912.491] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[   912.491] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[   912.492] (II) Using input driver 'libinput' for 'Video Bus'
[   912.492] (**) Video Bus: always reports core events
[   912.492] (**) Option "Device" "/dev/input/event5"
[   912.492] (**) Option "_source" "server/udev"
[   912.492] (II) event5  - (II) Video Bus: (II) is tagged by udev as: Keyboard
[   912.492] (II) event5  - (II) Video Bus: (II) device is a keyboard
[   912.492] (II) event5  - (II) Video Bus: (II) device removed
[   912.503] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5/event5"
[   912.503] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[   912.503] (II) event5  - (II) Video Bus: (II) is tagged by udev as: Keyboard
[   912.503] (II) event5  - (II) Video Bus: (II) device is a keyboard
[   912.503] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[   912.503] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   912.503] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   912.503] (II) Using input driver 'libinput' for 'Power Button'
[   912.504] (**) Power Button: always reports core events
[   912.504] (**) Option "Device" "/dev/input/event0"
[   912.504] (**) Option "_source" "server/udev"
[   912.504] (II) event0  - (II) Power Button: (II) is tagged by udev as: Keyboard
[   912.504] (II) event0  - (II) Power Button: (II) device is a keyboard
[   912.504] (II) event0  - (II) Power Button: (II) device removed
[   912.515] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[   912.515] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[   912.515] (II) event0  - (II) Power Button: (II) is tagged by udev as: Keyboard
[   912.515] (II) event0  - (II) Power Button: (II) device is a keyboard
[   912.516] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event10)
[   912.516] (II) No input driver specified, ignoring this device.
[   912.516] (II) This device may have been added with another device file.
[   912.516] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event11)
[   912.516] (II) No input driver specified, ignoring this device.
[   912.516] (II) This device may have been added with another device file.
[   912.516] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event12)
[   912.516] (II) No input driver specified, ignoring this device.
[   912.516] (II) This device may have been added with another device file.
[   912.517] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event13)
[   912.517] (II) No input driver specified, ignoring this device.
[   912.517] (II) This device may have been added with another device file.
[   912.517] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event14)
[   912.517] (II) No input driver specified, ignoring this device.
[   912.517] (II) This device may have been added with another device file.
[   912.517] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event9)
[   912.517] (II) No input driver specified, ignoring this device.
[   912.517] (II) This device may have been added with another device file.
[   912.518] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event15)
[   912.518] (II) No input driver specified, ignoring this device.
[   912.518] (II) This device may have been added with another device file.
[   912.518] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event16)
[   912.518] (II) No input driver specified, ignoring this device.
[   912.518] (II) This device may have been added with another device file.
[   912.519] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event17)
[   912.519] (II) No input driver specified, ignoring this device.
[   912.519] (II) This device may have been added with another device file.
[   912.519] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event18)
[   912.519] (II) No input driver specified, ignoring this device.
[   912.519] (II) This device may have been added with another device file.
[   912.519] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event19)
[   912.519] (II) No input driver specified, ignoring this device.
[   912.519] (II) This device may have been added with another device file.
[   912.520] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event20)
[   912.520] (II) No input driver specified, ignoring this device.
[   912.520] (II) This device may have been added with another device file.
[   912.520] (II) config/udev: Adding input device Xonar DS Headphone (/dev/input/event7)
[   912.520] (II) No input driver specified, ignoring this device.
[   912.520] (II) This device may have been added with another device file.
[   912.520] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event4)
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (II) Using input driver 'libinput' for 'Logitech USB-PS/2 Optical Mouse'
[   912.521] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[   912.521] (**) Option "Device" "/dev/input/event4"
[   912.521] (**) Option "_source" "server/udev"
[   912.573] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) is tagged by udev as: Mouse
[   912.573] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device set to 400 DPI
[   912.573] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device is a pointer
[   912.573] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device removed
[   912.587] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7.4/2-1.7.4:1.0/0003:046D:C00E.0003/input/input4/event4"
[   912.587] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
[   912.587] (**) Option "AccelerationScheme" "none"
[   912.587] (**) Logitech USB-PS/2 Optical Mouse: (accel) selected scheme none/0
[   912.587] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[   912.587] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[   912.639] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) is tagged by udev as: Mouse
[   912.639] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device set to 400 DPI
[   912.639] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device is a pointer
[   912.639] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse1)
[   912.639] (II) No input driver specified, ignoring this device.
[   912.639] (II) This device may have been added with another device file.
[   912.640] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/event2)
[   912.640] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.640] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.640] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[   912.640] (**) HOLTEK USB Keyboard: always reports core events
[   912.640] (**) Option "Device" "/dev/input/event2"
[   912.640] (**) Option "_source" "server/udev"
[   912.640] (II) event2  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard
[   912.640] (II) event2  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[   912.640] (II) event2  - (II) HOLTEK USB Keyboard: (II) device removed
[   912.651] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:04D9:A01C.0001/input/input2/event2"
[   912.651] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: KEYBOARD, id 10)
[   912.651] (II) event2  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard
[   912.651] (II) event2  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[   912.652] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/event3)
[   912.652] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[   912.652] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.652] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[   912.652] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.652] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[   912.652] (**) HOLTEK USB Keyboard: always reports core events
[   912.652] (**) Option "Device" "/dev/input/event3"
[   912.652] (**) Option "_source" "server/udev"
[   912.652] (II) event3  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard Mouse
[   912.652] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a pointer
[   912.653] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[   912.653] (II) event3  - (II) HOLTEK USB Keyboard: (II) device removed
[   912.663] (II) libinput: HOLTEK USB Keyboard: needs a virtual subdevice
[   912.663] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/0003:04D9:A01C.0002/input/input3/event3"
[   912.663] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: MOUSE, id 11)
[   912.663] (**) Option "AccelerationScheme" "none"
[   912.663] (**) HOLTEK USB Keyboard: (accel) selected scheme none/0
[   912.663] (**) HOLTEK USB Keyboard: (accel) acceleration factor: 2.000
[   912.663] (**) HOLTEK USB Keyboard: (accel) acceleration threshold: 4
[   912.663] (II) event3  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard Mouse
[   912.664] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a pointer
[   912.664] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[   912.664] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/mouse0)
[   912.664] (II) No input driver specified, ignoring this device.
[   912.664] (II) This device may have been added with another device file.
[   912.664] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event8)
[   912.664] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[   912.664] (**) Eee PC WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[   912.664] (II) Using input driver 'libinput' for 'Eee PC WMI hotkeys'
[   912.664] (**) Eee PC WMI hotkeys: always reports core events
[   912.664] (**) Option "Device" "/dev/input/event8"
[   912.665] (**) Option "_source" "server/udev"
[   912.665] (II) event8  - (II) Eee PC WMI hotkeys: (II) is tagged by udev as: Keyboard
[   912.665] (II) event8  - (II) Eee PC WMI hotkeys: (II) device is a keyboard
[   912.665] (II) event8  - (II) Eee PC WMI hotkeys: (II) device removed
[   912.675] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input8/event8"
[   912.675] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[   912.675] (II) event8  - (II) Eee PC WMI hotkeys: (II) is tagged by udev as: Keyboard
[   912.675] (II) event8  - (II) Eee PC WMI hotkeys: (II) device is a keyboard
[   912.676] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[   912.676] (II) No input driver specified, ignoring this device.
[   912.676] (II) This device may have been added with another device file.
[   912.680] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[   912.680] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.680] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[   912.680] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[   912.680] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[   912.680] (**) HOLTEK USB Keyboard: always reports core events
[   912.680] (**) Option "Device" "/dev/input/event3"
[   912.680] (**) Option "_source" "_driver/libinput"
[   912.680] (II) libinput: HOLTEK USB Keyboard: is a virtual subdevice
[   912.680] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/0003:04D9:A01C.0002/input/input3/event3"
[   912.681] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: KEYBOARD, id 13)
[  1414.354] (II) event1  - (II) Power Button: (II) device removed
[  1414.380] (II) event5  - (II) Video Bus: (II) device removed
[  1414.396] (II) event0  - (II) Power Button: (II) device removed
[  1414.408] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device removed
[  1414.422] (II) event2  - (II) HOLTEK USB Keyboard: (II) device removed
[  1414.434] (II) event8  - (II) Eee PC WMI hotkeys: (II) device removed
[  1414.446] (II) event3  - (II) HOLTEK USB Keyboard: (II) device removed
[  1414.458] (II) UnloadModule: "libinput"
[  1414.458] (II) UnloadModule: "libinput"
[  1414.458] (II) UnloadModule: "libinput"
[  1414.459] (II) UnloadModule: "libinput"
[  1414.459] (II) UnloadModule: "libinput"
[  1414.459] (II) UnloadModule: "libinput"
[  1414.459] (II) UnloadModule: "libinput"
[  1414.459] (II) UnloadModule: "libinput"
[  1414.473] (II) Server terminated successfully (0). Closing log file.

Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 6960

PostPosted: Sun Jan 07, 2018 7:11 pm    Post subject: Reply with quote

the general rule for libinput or evdev is that the driver only work with the xorg XInput ABI it was made for
i don't use libinput myself, but if i assume libinput try in its version to hint about the ABI to use, your libinput was made for ABI 25.1
and your xorg is using ABI 24.1
Code:
[   912.468]    ABI class: X.Org XInput driver, version 24.1
[   912.468]    compiled for 1.19.5, module version = 0.25.1

If it's that, you either downgrade libinput to a version that handle ABI 24.1 (seek some xf86-libinput-0.24.1) or you upgrade xorg to a version using ABI 25.1 which by the hint "compiled for" should be xorg-1.19.5

Normally portage should handle that for you, when you emerge -u xorg-server, portage should pull the correct dependency for libinput.
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sun Jan 07, 2018 8:43 pm    Post subject: Reply with quote

krinn wrote:
the general rule for libinput or evdev is that the driver only work with the xorg XInput ABI it was made for
i don't use libinput myself, but if i assume libinput try in its version to hint about the ABI to use, your libinput was made for ABI 25.1
and your xorg is using ABI 24.1
Code:
[   912.468]    ABI class: X.Org XInput driver, version 24.1
[   912.468]    compiled for 1.19.5, module version = 0.25.1

If it's that, you either downgrade libinput to a version that handle ABI 24.1 (seek some xf86-libinput-0.24.1) or you upgrade xorg to a version using ABI 25.1 which by the hint "compiled for" should be xorg-1.19.5

Normally portage should handle that for you, when you emerge -u xorg-server, portage should pull the correct dependency for libinput.


I just went with what Portage offered during the install.
Currently xf86-input-libinput has both 24.0 and 25.1 unmasked in portage.
I masked 25.1 and did emerge @x11-rebuild-modules, which also rebuilt xorg-server.

Sadly still the same results, no mouse or keyboard.
They are removed for lack of driver.
What driver are they taking about here as it does not seem to be xf86-input-libinput?


Code:

[ 18516.797] (II) LoadModule: "libinput"
[ 18516.797] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[ 18516.798] (II) Module libinput: vendor="X.Org Foundation"
[ 18516.798]    compiled for 1.19.5, module version = 0.24.0
[ 18516.798]    Module class: X.Org XInput Driver
[ 18516.798]    ABI class: X.Org XInput driver, version 24.1
[ 18516.798] (II) Using input driver 'libinput' for 'Power Button'
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 5584

PostPosted: Mon Jan 08, 2018 12:41 pm    Post subject: Re: Xorg/libinput No input driver specified, ignoring this d Reply with quote

bpaddock wrote:
I'm tiring to bring up a new install of my box.
When I 'startx' I have no keyboard or mouse.
Googling and reading the forms haven't got me any closer as I don't see this type of error mentioned:

"[ 912.639] (II) No input driver specified, ignoring this device."

Line directly below that one says:
Quote:
Code:
[   912.639] (II) This device may have been added with another device file.

Which is correct, unless you have two identical mice using different kernel drivers:
Quote:
Code:
[   912.520] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event4)
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (II) Using input driver 'libinput' for 'Logitech USB-PS/2 Optical Mouse'


What DE/WM are you running?
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Tue Jan 09, 2018 3:17 am    Post subject: Re: Xorg/libinput No input driver specified, ignoring this d Reply with quote

Quote:

Which is correct, unless you have two identical mice using different kernel drivers:
Quote:
Code:
[   912.520] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event4)
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[   912.520] (II) Using input driver 'libinput' for 'Logitech USB-PS/2 Optical Mouse'


What DE/WM are you running?


I'm simply working my way through the install documents.
Started with

https://wiki.gentoo.org/wiki/User:Fearedbliss/Installing_Gentoo_Linux_On_ZFS

in conjunction with the AMD64 handbook.

https://wiki.gentoo.org/wiki/Handbook:AMD64

Then the AMDGPU:

https://wiki.gentoo.org/wiki/AMDGPU

Then Xorg

https://wiki.gentoo.org/wiki/Xorg/Guide

With the unexpected detour to libinput:

https://wiki.gentoo.org/wiki/Libinput

Then back to Xorg Guide.
Following the that I installed twm and xterm.
That is where there is no keyboard and mouse.

Saw no point in installing XFCE4 until twm was working.

I've been running Gentoo for years.
I have never had so many problems with an install as I'm having with this one. :-(

I did note this in the Xorg.0.log near the start of the log:

"The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices."

So libinput and udev are fighting each other?
As I said I'm just following along the documentation path I listed above.
Can't this crap just simply work? :-( Sorry, just very frustrated at the amount of time I'm spending.

Currently I have no xorg.conf. Looks like the next step is to make one with AudoAddDevices set to False?
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sat Jan 13, 2018 9:46 pm    Post subject: Reply with quote

I had Gentoo working on this box for a long time, for various reasons I wiped everything and did a fresh install.

Now I have no Keyboard or Mouse in XOrg. I've goggled and looked over the forms for FAR too long trying to figure out why they are being actively ignored.

There is a keyboard with a mouse pad and a single Logitech USB mouse.
However in the XOrg log it appears that EVERY device is being ignored. WHY?

I've been following the instructions here: https://wiki.gentoo.org/wiki/Xorg/Guide

There is no desktop or window manager outside of twm as per the above Guide to test things.
All versions of packages are what was installed via portage. I've not made any attempts to upgrade nor downgrade anything yet.

In make.conf is:
INPUT_DEVICES="libinput"

libinput-debug-events shows that the keyboard and mouse work and as I said in the old install they also worked with XOrg.

Full XOrg.0.log here:

https://pastebin.com/Mz6Qsjwk

Kernel .config here:

https://pastebin.com/MdYbyiDM

emerge --info here:

https://pastebin.com/C2XUNP4i


Help! Please. Thank You.

Code:

...
[    56.237] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event18)
[    56.237] (II) No input driver specified, ignoring this device.
[    56.237] (II) This device may have been added with another device file.
[    56.237] (II) config/udev: Adding input device Xonar DS Headphone (/dev/input/event20)
[    56.237] (II) No input driver specified, ignoring this device.
[    56.237] (II) This device may have been added with another device file.

[    56.237] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event4)
[    56.237] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "libinput pointer catchall"
[    56.237] (II) Using input driver 'libinput' for 'Logitech USB-PS/2 Optical Mouse'
[    56.237] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[    56.237] (**) Option "Device" "/dev/input/event4"
[    56.237] (**) Option "_source" "server/udev"
[    56.290] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) is tagged by udev as: Mouse
[    56.290] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device set to 400 DPI
[    56.290] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device is a pointer
[    56.290] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device removed
[    56.304] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7.4/2-1.7.4:1.0/0003:046D:C00E.0003/input/input7/event4"
[    56.304] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
[    56.304] (**) Option "AccelerationScheme" "none"
[    56.304] (**) Logitech USB-PS/2 Optical Mouse: (accel) selected scheme none/0
[    56.304] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[    56.304] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[    56.356] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) is tagged by udev as: Mouse
[    56.356] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device set to 400 DPI
[    56.356] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device is a pointer
[    56.356] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse1)
[    56.356] (II) No input driver specified, ignoring this device.
[    56.356] (II) This device may have been added with another device file.

[    56.357] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/event2)
[    56.357] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    56.357] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[    56.357] (**) HOLTEK USB Keyboard: always reports core events
[    56.357] (**) Option "Device" "/dev/input/event2"
[    56.357] (**) Option "_source" "server/udev"
[    56.357] (II) event2  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard
[    56.357] (II) event2  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[    56.358] (II) event2  - (II) HOLTEK USB Keyboard: (II) device removed
[    56.368] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:04D9:A01C.0001/input/input5/event2"
[    56.368] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: KEYBOARD, id 10)
[    56.368] (II) event2  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard
[    56.368] (II) event2  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[    56.369] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/event3)
[    56.369] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[    56.369] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    56.369] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[    56.369] (**) HOLTEK USB Keyboard: always reports core events
[    56.369] (**) Option "Device" "/dev/input/event3"
[    56.369] (**) Option "_source" "server/udev"
[    56.369] (II) event3  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard Mouse
[    56.369] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a pointer
[    56.369] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[    56.370] (II) event3  - (II) HOLTEK USB Keyboard: (II) device removed
[    56.380] (II) libinput: HOLTEK USB Keyboard: needs a virtual subdevice
[    56.380] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/0003:04D9:A01C.0002/input/input6/event3"
[    56.380] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: MOUSE, id 11)
[    56.380] (**) Option "AccelerationScheme" "none"
[    56.380] (**) HOLTEK USB Keyboard: (accel) selected scheme none/0
[    56.380] (**) HOLTEK USB Keyboard: (accel) acceleration factor: 2.000
[    56.380] (**) HOLTEK USB Keyboard: (accel) acceleration threshold: 4
[    56.380] (II) event3  - (II) HOLTEK USB Keyboard: (II) is tagged by udev as: Keyboard Mouse
[    56.380] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a pointer
[    56.381] (II) event3  - (II) HOLTEK USB Keyboard: (II) device is a keyboard
[    56.381] (II) config/udev: Adding input device HOLTEK USB Keyboard (/dev/input/mouse0)
[    56.381] (II) No input driver specified, ignoring this device.
[    56.381] (II) This device may have been added with another device file.
[    56.381] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event19)

...

[    56.393] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[    56.393] (II) No input driver specified, ignoring this device.
[    56.393] (II) This device may have been added with another device file.

[    56.397] (**) HOLTEK USB Keyboard: Applying InputClass "libinput pointer catchall"
[    56.397] (**) HOLTEK USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    56.397] (II) Using input driver 'libinput' for 'HOLTEK USB Keyboard'
[    56.397] (**) HOLTEK USB Keyboard: always reports core events
[    56.397] (**) Option "Device" "/dev/input/event3"
[    56.397] (**) Option "_source" "_driver/libinput"
[    56.397] (II) libinput: HOLTEK USB Keyboard: is a virtual subdevice
[    56.397] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/0003:04D9:A01C.0002/input/input6/event3"
[    56.397] (II) XINPUT: Adding extended input device "HOLTEK USB Keyboard" (type: KEYBOARD, id 13)

[WHY????:]

[    63.412] (II) event1  - (II) Power Button: (II) device removed
[    63.424] (II) event5  - (II) Video Bus: (II) device removed
[    63.436] (II) event0  - (II) Power Button: (II) device removed
[    63.448] (II) event4  - (II) Logitech USB-PS/2 Optical Mouse: (II) device removed
[    63.462] (II) event2  - (II) HOLTEK USB Keyboard: (II) device removed
[    63.474] (II) event19 - (II) Eee PC WMI hotkeys: (II) device removed
[    63.486] (II) event3  - (II) HOLTEK USB Keyboard: (II) device removed

[    63.498] (II) AIGLX: Suspending AIGLX clients for VT switch

Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2583

PostPosted: Sun Jan 14, 2018 10:14 am    Post subject: Reply with quote

Have you tried with CONFIG_HID_HOLTEK=y?
And, did you already show the keyboard setting in your /etc/X11/xorg.conf.d/ directory?
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sun Jan 14, 2018 1:56 pm    Post subject: Reply with quote

charles17 wrote:
Have you tried with CONFIG_HID_HOLTEK=y?
And, did you already show the keyboard setting in your /etc/X11/xorg.conf.d/ directory?


Setting HOLTEK did get a X keyboard working. Doing same for the mouse got it working.
I had no keyboard settings in /etc/X11/xorg.conf.d why would I?

Still seems like there is something wrong here.
Isn't the point of libinput to make this stuff transparent?
At the libinput level everything was working as expected as shown by libinput-debug-events.

Should I really have to track down every single device in the kernel and make sure it is built in and not a module?
What changed, as I never had to do this in past installs of Gentoo?

Thank you for your suggestion. Now I can move along with the install. Still do think something is not right...
Back to top
View user's profile Send private message
charles17
Advocate
Advocate


Joined: 02 Mar 2008
Posts: 2583

PostPosted: Sun Jan 14, 2018 2:23 pm    Post subject: Reply with quote

bpaddock wrote:
Should I really have to track down every single device in the kernel and make sure it is built in and not a module?

Otherwise you would have to take care to have the modules loaded
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sun Jan 14, 2018 2:31 pm    Post subject: Reply with quote

charles17 wrote:
bpaddock wrote:
Should I really have to track down every single device in the kernel and make sure it is built in and not a module?

Otherwise you would have to take care to have the modules loaded


Yes I understand that.

Still doesn't explain why libinput-debug-event works and X doesn't.
Back to top
View user's profile Send private message
ct85711
Veteran
Veteran


Joined: 27 Sep 2005
Posts: 1691

PostPosted: Sun Jan 14, 2018 4:07 pm    Post subject: Reply with quote

You are more of missing what libinput is, it is only a common interface for all of the inputs to use in front of other interfaces that talks to the kernel. In the end, the kernel has to know how to speak to the devices. Libinput simply needs to see that the input is there (which is does), but it doesn't talk with the devices. In the end, the kernel is the true device that does the communications, everything else software wise is more of a interface layer between the kernel and user.
Back to top
View user's profile Send private message
bpaddock
Apprentice
Apprentice


Joined: 04 Nov 2005
Posts: 195
Location: Franklin, PA

PostPosted: Sun Jan 14, 2018 5:04 pm    Post subject: Reply with quote

ct85711 wrote:
You are more of missing what libinput is, it is only a common interface for all of the inputs to use in front of other interfaces that talks to the kernel. In the end, the kernel has to know how to speak to the devices. Libinput simply needs to see that the input is there (which is does), but it doesn't talk with the devices. In the end, the kernel is the true device that does the communications, everything else software wise is more of a interface layer between the kernel and user.


Yes, I really don't understand how libinput-debug-events can show the actual keycode of the key I'm pressing without configuring a specific keyboard, which is what it was doing. Nor how the keyboard worked at the terminal without a specific keyboard in the kernel. Yet X doesn't get it. Clearly neither do I.

Perhaps it should be mentioned in the Xorg Guide that following it, using libinput as it recommends, will not result in a working system.

https://wiki.gentoo.org/wiki/Xorg/Guide

All seems like a significant regression from the last time I installed Gentoo a couple of years ago.
Following the Guides 'Just Worked' back then.

Thank you for your help.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum