View previous topic :: View next topic |
Author |
Message |
bms n00b

Joined: 30 Dec 2016 Posts: 11
|
Posted: Fri Dec 30, 2016 8:40 pm Post subject: [SOLVED] xorg keyboard: X won't start |
|
|
Hello all,
I've just installed Gentoo. I've followed the Gentoo Wiki to install both the Xorg server as well as the proprietary Nvidia Drivers. Both installed fine, but now I seem to have a problem with my Logitech G610 Gaming Keyboard. Whenever I try to "startx", I manage to see the nVidia logo for about one second, after that the X server start fails. The following lines from Xorg.log draw some attention:
Code: |
[ 2255.929] (II) config/udev: Adding input device Logitech Gaming Keyboard G610 (/dev/input/event5)
[ 2255.929] (**) Logitech Gaming Keyboard G610: Applying InputClass "evdev keyboard catchall"
[ 2255.929] (II) Using input driver 'evdev' for 'Logitech Gaming Keyboard G610'
[ 2255.929] (**) Logitech Gaming Keyboard G610: always reports core events
[ 2255.929] (**) evdev: Logitech Gaming Keyboard G610: Device: "/dev/input/event5"
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Vendor 0x46d Product 0xc333
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Found keys
[ 2255.929] (II) evdev: Logitech Gaming Keyboard G610: Configuring as keyboard
[ 2255.929] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:046D:C333.0001/input/input8/event5"
[ 2255.929] (II) XINPUT: Adding extended input device "Logitech Gaming Keyboard G610" (type: KEYBOARD, id 9)
[ 2255.929] (**) Option "xkb_rules" "evdev"
[ 2255.929] (II) config/udev: Adding input device Logitech Gaming Keyboard G610 (/dev/input/event6)
[ 2255.929] (**) Logitech Gaming Keyboard G610: Applying InputClass "evdev keyboard catchall"
[ 2255.929] (II) Using input driver 'evdev' for 'Logitech Gaming Keyboard G610'
[ 2255.929] (**) Logitech Gaming Keyboard G610: always reports core events
[ 2255.929] (**) evdev: Logitech Gaming Keyboard G610: Device: "/dev/input/event6"
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Vendor 0x46d Product 0xc333
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Found absolute axes
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Found absolute multitouch axes
[ 2255.929] (II) evdev: Logitech Gaming Keyboard G610: No buttons found, faking one.
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Fake MT device detected
[ 2255.929] (--) evdev: Logitech Gaming Keyboard G610: Found keys
[ 2255.929] (II) evdev: Logitech Gaming Keyboard G610: Forcing relative x/y axes to exist.
[ 2255.929] (II) evdev: Logitech Gaming Keyboard G610: Configuring as mouse
[ 2255.929] (II) evdev: Logitech Gaming Keyboard G610: Configuring as keyboard
[ 2255.929] (**) evdev: Logitech Gaming Keyboard G610: YAxisMapping: buttons 4 and 5
[ 2255.929] (**) evdev: Logitech Gaming Keyboard G610: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2255.929] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:046D:C333.0002/input/input9/event6"
[ 2255.929] (II) XINPUT: Adding extended input device "Logitech Gaming Keyboard G610" (type: KEYBOARD, id 10)
[ 2255.929] (**) Option "xkb_rules" "evdev"
[ 2255.929] (EE) BUG: triggered 'if (axnum >= dev->valuator->numAxes)'
[ 2255.929] (EE) BUG: /var/tmp/portage/x11-base/xorg-server-1.18.4/work/xorg-server-1.18.4/Xi/exevents.c:2103 in InitValuatorAxisStruct()
[ 2255.929] (EE)
[ 2255.929] (EE) Backtrace:
[ 2255.929] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58acf6]
[ 2255.929] (EE) 1: /usr/bin/X (InitValuatorAxisStruct+0x67) [0x51c317]
[ 2255.929] (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f674ef5e000+0x53c5) [0x7f674ef633c5]
[ 2255.929] (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f674ef5e000+0x58af) [0x7f674ef638af]
[ 2255.929] (EE) 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f674ef5e000+0x7653) [0x7f674ef65653]
[ 2255.929] (EE) 5: /usr/bin/X (ActivateDevice+0x4a) [0x42a6fa]
[ 2255.929] (EE) 6: /usr/bin/X (0x400000+0x838f9) [0x4838f9]
[ 2255.929] (EE) 7: /usr/bin/X (0x400000+0x9583b) [0x49583b]
[ 2255.929] (EE) 8: /usr/bin/X (0x400000+0x95e23) [0x495e23]
[ 2255.929] (EE) 9: /usr/bin/X (config_init+0x9) [0x494cb9]
[ 2255.929] (EE) 10: /usr/bin/X (InitInput+0xbb) [0x477ecb]
[ 2255.929] (EE) 11: /usr/bin/X (0x400000+0x39761) [0x439761]
[ 2255.929] (EE) 12: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f6754753630]
[ 2255.929] (EE) 13: /usr/bin/X (_start+0x29) [0x423aa9]
|
I've tried starting X without a xorg.conf file, and with the xorg.conf file that was generated by the nvidia settings tool: both attempts yielded the same result seen above. I'm at a bit of a loss as to what to do next, so any help is appreciated!
Last edited by bms on Sun Jan 01, 2017 8:55 am; edited 1 time in total |
|
Back to top |
|
 |
Keruskerfuerst Advocate


Joined: 01 Feb 2006 Posts: 2289 Location: near Augsburg, Germany
|
|
Back to top |
|
 |
bms n00b

Joined: 30 Dec 2016 Posts: 11
|
Posted: Fri Dec 30, 2016 9:24 pm Post subject: |
|
|
Thanks for bringing this to my attention. The Keyboard indeed does have a wheel (to control the audio volume). After reading through the bug, I unmasked both libevdev and xf86-input-evdev and upgraded them to their newest versions (1.5.5 and 2.10.4). Alas, the same result: I still get the same error message. According to the bug report, the problem should be fixed in the 2.10.x branch.
Any other ideas? Can I somehow force Xorg to treat the Keyboard as a "standard" Keyboard without any fancy controls and all? |
|
Back to top |
|
 |
Jaglover Watchman


Joined: 29 May 2005 Posts: 7799 Location: Saint Amant, Acadiana
|
|
Back to top |
|
 |
bms n00b

Joined: 30 Dec 2016 Posts: 11
|
Posted: Fri Dec 30, 2016 10:12 pm Post subject: |
|
|
Hello there,
I'm not sure I understand you: both libraries were already installed (in slightly older versions). My guess is they were pulled in as dependencies by "xorg-server". All i did was upgrading both libraries to their newest versions (by unmasking them). I tried upgrading both libraries at the same time, and only one of them at a time - always the same result  |
|
Back to top |
|
 |
Jaglover Watchman


Joined: 29 May 2005 Posts: 7799 Location: Saint Amant, Acadiana
|
|
Back to top |
|
 |
bms n00b

Joined: 30 Dec 2016 Posts: 11
|
Posted: Sun Jan 01, 2017 8:54 am Post subject: |
|
|
Happy new year to you all!
Turns out that despite the error message in Xorg.log (which is still there), everything works! Here is what I did:
I attached an old Keyboard and managed to finally install my Desktop environment + window manager. Turns out I mistook the X server falling back to the command-line for an abort, whereas it probably only was a short test cycle (displaying the logo and exiting). After i could boot into the desktop I switched Keyboards again and voila: it works, no additional Kernel modules needed
Thanks for all your help! |
|
Back to top |
|
 |
|