View previous topic :: View next topic |
Author |
Message |
zetsumei n00b
Joined: 20 Dec 2006 Posts: 13
|
Posted: Fri Jan 11, 2013 6:52 am Post subject: Can get x to start, but keyboard stops work - log included |
|
|
I've finally got x to actually start and I see the xterm windows and all, but I'm not able to type anything nor use the mouse. My second monitor turns on as well. Only way I can get out of X is by using ctrl-alt-2 then back to ctrl-alt-1 and ctrl-c to end it.
http://bpaste.net/show/69464/ - Xorg.0.log
http://bpaste.net/show/69466 - xorg.conf
I'm using the nvidia-drivers package and nvidia-xconfig to generate my xorg.conf file. |
|
Back to top |
|
|
v_andal Guru
Joined: 26 Aug 2008 Posts: 541 Location: Germany
|
Posted: Fri Jan 11, 2013 8:24 am Post subject: |
|
|
Try to remove the Keyboard0 section and add the following
Code: |
Section "InputClass"
Identifier "other keyboards"
MatchIsKeyboard "On"
Option "Ignore" "on"
EndSection
Section "InputClass"
Identifier "my keyboard"
Driver "evdev"
MatchProduct "Razer Razer BlackWidow Ultimate 2013"
MatchIsKeyboard "On"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "SendCoreEvents" "on"
Option "Ignore" "off"
EndSection
|
It's well known problem of automatic keyboard recognition in xorg. It picks up power button and configures it to be keyboard because there's well button
Well, I'm not sure if this Razer is your keyboard, but I couldn't find anything else in the log that would look like keyboard. |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9679 Location: almost Mile High in the USA
|
Posted: Fri Jan 11, 2013 8:26 am Post subject: |
|
|
What if you have no xorg.conf, does the keyboard work?
Typically Xorg is now set up to autoconfig the keyboard/mouse and it should auto work with no keyboard/mouse section and EVDEV is used. Kernel support is needed - you need to make sure keyboard/mouse INPUT devices are setup for the generic kernel event driver input interface.
To actually use the legacy "keyboard" and "mouse" driver there's a directive I can't remember off the top of my head to disable autoconfiguration of input devices - and this needs to be explicitly specified in xorg.conf to disable.
You have a PS/2 keyboard (guessed) versus a USB keyboard? Looking at the logs a USB keyboard should work... if it really is a USB keyboard, the mystery thickens... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
zetsumei n00b
Joined: 20 Dec 2006 Posts: 13
|
Posted: Fri Jan 11, 2013 8:49 am Post subject: |
|
|
log file - http://bpaste.net/show/69472
xorg.conf - http://bpaste.net/show/69473
Added what you said to add v_andal, I get undefined keyboard0 referenced error then.
My keyboard is the razer and is a usb keyboard. I also tried emerging xf86-input-evdev as well. |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Fri Jan 11, 2013 10:02 am Post subject: |
|
|
You need to cleanup ServerLayout section after you change the identifiers.
But that's not the real problem - the first xorg.conf (your own), while a bit noisy, should have worked.
You need to figure out what part of your keyboard /dev/input/event2 refers to ('udevadm info' should help with that) and either disable/skip that part or figure out why is it a problem in the first place. |
|
Back to top |
|
|
Gusar Advocate
Joined: 09 Apr 2005 Posts: 2665 Location: Slovenia
|
Posted: Fri Jan 11, 2013 10:06 am Post subject: |
|
|
That xorg.conf can be reduced to just the Device section, everything else does nothing. Beyond that, I have the feeling your X is not suid root. Check your USE flags. If "suid" is not set for xorg-server, do so. If it is set, make sure the X binary actually does have the suid bit. |
|
Back to top |
|
|
zetsumei n00b
Joined: 20 Dec 2006 Posts: 13
|
Posted: Fri Jan 11, 2013 1:20 pm Post subject: |
|
|
Gusar wrote: | That xorg.conf can be reduced to just the Device section, everything else does nothing. Beyond that, I have the feeling your X is not suid root. Check your USE flags. If "suid" is not set for xorg-server, do so. If it is set, make sure the X binary actually does have the suid bit. |
That would be in my /etc/portage/make.conf file correct? Or is that where the USE flags are that effect virtually everything I build?
EDIT: I just found something about it and if I'm able to run startx with my regular user I should be good then right? Because I can run it as a regular user just can't type or move the mouse. Only way to get out of it is the ctrl-alt-1. That would mean the suid use flag was set or no?
VoidMage wrote: | You need to cleanup ServerLayout section after you change the identifiers.
But that's not the real problem - the first xorg.conf (your own), while a bit noisy, should have worked.
You need to figure out what part of your keyboard /dev/input/event2 refers to ('udevadm info' should help with that) and either disable/skip that part or figure out why is it a problem in the first place. |
And udevadm info returns missing options and looking at man udevadm I'm trying to figure out what option would allow me to do what you're asking. |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Fri Jan 11, 2013 7:59 pm Post subject: |
|
|
Well, obviously I'm asking for info about input device nodes - reread that man section, it's quite obvious in the hindsight. |
|
Back to top |
|
|
frigger n00b
Joined: 01 Apr 2009 Posts: 15 Location: Norway
|
Posted: Sat Jan 12, 2013 12:27 am Post subject: |
|
|
It's seems that udev-197 breaks some pakages
emerge -C =sys-fs/udev-197
emerge -av =sys-fs/udev-196-r1
You may want to add it to package.mask, but I think it'll be fixed soon.
Worked for me |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Sat Jan 12, 2013 3:00 am Post subject: |
|
|
frigger wrote: | It's seems that udev-197 breaks some pakages
emerge -C =sys-fs/udev-197
emerge -av =sys-fs/udev-196-r1
You may want to add it to package.mask, but I think it'll be fixed soon.
Worked for me |
Going by the bug reports, the problems come from people not reading elog warnings about the need to reemerge a few packages and those are unrelated to the problem here. |
|
Back to top |
|
|
|