[arch-general] keyboard not working in Xorg after package updates
I upgraded my extremely not-up-to-date server last night (523 packages upgraded). The upgrade generally went well, except for one significant issue: the keyboard is no longer working under Xorg. It works fine in a command line tty though (i.e., ctrl-alt-F1). Not sure what the problem is, as it was working before the upgrade, and I'm fairly certain I've got all the relevant bits installed and loaded, such as: * evdev module loaded * dbus daemon running * hal daemon running * xf86-input-evdev package installed etc. Perhaps related: I saw the following odd sequence of messages in the Xorg.0.log: (II) config/hal: Adding input device Power Button (**) Power Button: always reports core events (**) Power Button: Device: "/dev/input/event2" (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) config/hal: Adding input device Power Button (**) Power Button: always reports core events (**) Power Button: Device: "/dev/input/event3" (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" Certainly sounds like that could be the cause, but I have no idea why that's happening or how to fix. Anyone have any ideas? TIA, DR
On Wed, Apr 7, 2010 at 4:32 PM, David Rosenstrauch <darose@darose.net> wrote:
I upgraded my extremely not-up-to-date server last night (523 packages upgraded). The upgrade generally went well, except for one significant issue: the keyboard is no longer working under Xorg. It works fine in a command line tty though (i.e., ctrl-alt-F1).
Not sure what the problem is, as it was working before the upgrade, and I'm fairly certain I've got all the relevant bits installed and loaded, such as:
* evdev module loaded * dbus daemon running * hal daemon running * xf86-input-evdev package installed etc.
Perhaps related: I saw the following odd sequence of messages in the Xorg.0.log:
(II) config/hal: Adding input device Power Button (**) Power Button: always reports core events (**) Power Button: Device: "/dev/input/event2" (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) config/hal: Adding input device Power Button (**) Power Button: always reports core events (**) Power Button: Device: "/dev/input/event3" (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us"
Certainly sounds like that could be the cause, but I have no idea why that's happening or how to fix.
Anyone have any ideas?
Can you attach full Xorg log and config ? And does it work with xf86-input-keyboard driver ?
On 04/07/2010 10:46 AM, Xavier Chantry wrote:
Can you attach full Xorg log and config ?
I'm not using any xorg config. Log is at: http://www.darose.net/Xorg.0.log
And does it work with xf86-input-keyboard driver ?
I have xf86-input-keyboard installed. I assumed X was just automatically choosing evdev (as I have no xorg config). Thanks, DR
On 04/07/2010 09:55 AM, David Rosenstrauch wrote:
On 04/07/2010 10:46 AM, Xavier Chantry wrote:
Can you attach full Xorg log and config ?
I'm not using any xorg config. Log is at:
http://www.darose.net/Xorg.0.log
And does it work with xf86-input-keyboard driver ?
I have xf86-input-keyboard installed. I assumed X was just automatically choosing evdev (as I have no xorg config).
Thanks,
DR
On the same note, after the latest Xorg update, X (nVidia card) was failing to start on the same xorg.conf I had used with my arch box since I first installed arch. The xorg.conf was generated by the nvidia-xconfig app. The xorg.conf was: http://www.3111skyline.com/dl/dt/X/xorg/xorg.conf.sav Something is not as it should be in the latest X release. (p.s. this is 'in addition to' and not 'in lieu of' the current topic) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, Apr 7, 2010 at 8:35 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On the same note, after the latest Xorg update, X (nVidia card) was failing to start on the same xorg.conf I had used with my arch box since I first installed arch.
Add a ServerFlags section to your xorg.conf and inside that insert: Option "IgnoreABI" "True" When a new driver is released that recognizes the new xorg-server version, you can remove that.
On Wed, 2010-04-07 at 20:56 +0300, Evangelos Foutras wrote:
On Wed, Apr 7, 2010 at 8:35 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
On the same note, after the latest Xorg update, X (nVidia card) was failing to start on the same xorg.conf I had used with my arch box since I first installed arch.
Add a ServerFlags section to your xorg.conf and inside that insert:
Option "IgnoreABI" "True"
When a new driver is released that recognizes the new xorg-server version, you can remove that.
I think that stuff like this belongs more to the forum, where it can be easily accessed by many people
On 04/07/2010 12:56 PM, Evangelos Foutras wrote:
Add a ServerFlags section to your xorg.conf and inside that insert:
Option "IgnoreABI" "True"
When a new driver is released that recognizes the new xorg-server version, you can remove that.
Thank you Evangelos. Hopefully DR's issue will be resolved as well :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 04/07/2010 10:55 AM, David Rosenstrauch wrote:
On 04/07/2010 10:46 AM, Xavier Chantry wrote:
Can you attach full Xorg log and config ?
I'm not using any xorg config. Log is at:
http://www.darose.net/Xorg.0.log
And does it work with xf86-input-keyboard driver ?
I have xf86-input-keyboard installed. I assumed X was just automatically choosing evdev (as I have no xorg config).
Thanks,
DR
Anybody have any ideas on this? GUI is completely unusable on the server until I solve this! :-( I really have zero idea what's going on. And it's a difficult thing to find good specific search terms for, as there's been numerous problems with xorg and keyboards over the years that keep coming up in the search results. TIA, DR
On Wed, Apr 7, 2010 at 7:59 PM, David Rosenstrauch <darose@darose.net> wrote:
Anybody have any ideas on this? GUI is completely unusable on the server until I solve this! :-(
I really have zero idea what's going on. And it's a difficult thing to find good specific search terms for, as there's been numerous problems with xorg and keyboards over the years that keep coming up in the search results.
Well I already suggested a workaround : find a way to use the keyboard driver It should be possible to create a xorg.conf to specify that. Or to edit the hal files, but that's already deprecated with 1.8 Or maybe just removing evdev would work, I am not sure. But you would need mouse too. But in any cases, have a look at http://www.x.org/wiki/ Reporting problems, asking questions and getting help
On Wed, April 7, 2010 2:11 pm, Xavier Chantry wrote:
On Wed, Apr 7, 2010 at 7:59 PM, David Rosenstrauch <darose@darose.net> wrote:
Anybody have any ideas on this? GUI is completely unusable on the server until I solve this! :-(
I really have zero idea what's going on. And it's a difficult thing to find good specific search terms for, as there's been numerous problems with xorg and keyboards over the years that keep coming up in the search results.
Well I already suggested a workaround : find a way to use the keyboard driver It should be possible to create a xorg.conf to specify that. Or to edit the hal files, but that's already deprecated with 1.8 Or maybe just removing evdev would work, I am not sure. But you would need mouse too.
But in any cases, have a look at http://www.x.org/wiki/ Reporting problems, asking questions and getting help
Still trying to get this working, and I'm getting really stumped. Here's what I'm seeing after a debugging session tonight: * can't start an x session by logging into slim (since I have no keyboard) * so I ssh in, and shut down slim * I switch to qingy, which does let me log in (since I have keyboard access when I'm in a console) * qingy logs me into an x session (fluxbox), and again I have no keyboard access. Weirdly, however, the mouse works while in the x session. (WTF?!?!?) * I want to run xev to see if x is registering keyboard events. But I can't launch it since I can't type "xev" since I have no keyboard. Fine. So I ssh in, and launch "xev display :1". Xev launches fine inside the x session. I do mouse clicks on the xev window, and also try pressing keys on the keyboard. AND XEV PICKS UP THE KEYBOARD EVENTS AND ECHOS THEM BACK OUT TO THE SSH SESSION. WTF?!?!?!? Plus I also checked in hal-device, and it see the keyboard fine on /dev/event1 (or whatever it's called). So .... WTF?!?!?!? Hal sees the keyboard. And xev running inside the x session sees the keyboard. SO WHY ON EARTH IS MY KEYBOARD STILL DEAD IN MY X SESSIONS?!?!? ARRRRGGGGHHHHHH!!!! Anyone have *any* ideas what's going on and/or how to fix? I'm totally stumped! TIA, DR
On Thu, April 8, 2010 9:51 pm, David Rosenstrauch wrote:
So .... WTF?!?!?!? Hal sees the keyboard. And xev running inside the x session sees the keyboard. SO WHY ON EARTH IS MY KEYBOARD STILL DEAD IN MY X SESSIONS?!?!? ARRRRGGGGHHHHHH!!!!
Wee hee! It gets weirder! * Bizarrely enough, *some* of the keys on the keyboard actually work (such as / * - + on the numeric keypad). * I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86 W T F ? ! ? DR
On Thu, Apr 8, 2010 at 23:05, David Rosenstrauch <darose@darose.net> wrote:
* Bizarrely enough, *some* of the keys on the keyboard actually work (such as / * - + on the numeric keypad).
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
Is numlock on? Seems like it thinks you have some meta keys pressed
On Thu, April 8, 2010 11:09 pm, Daenyth Blank wrote:
On Thu, Apr 8, 2010 at 23:05, David Rosenstrauch <darose@darose.net> wrote:
* Bizarrely enough, *some* of the keys on the keyboard actually work (such as / * - + on the numeric keypad).
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
Is numlock on? Seems like it thinks you have some meta keys pressed
Yes, numlock is on, so I can enter #'s on the keypad. (Instead of them being arrow keys.) Not sure why that could be a problem though. I've been doing that for ages ... Thanks, DR
On Fri, Apr 9, 2010 at 5:05 AM, David Rosenstrauch <darose@darose.net> wrote:
On Thu, April 8, 2010 9:51 pm, David Rosenstrauch wrote:
So .... WTF?!?!?!? Hal sees the keyboard. And xev running inside the x session sees the keyboard. SO WHY ON EARTH IS MY KEYBOARD STILL DEAD IN MY X SESSIONS?!?!? ARRRRGGGGHHHHHH!!!!
Wee hee! It gets weirder!
* Bizarrely enough, *some* of the keys on the keyboard actually work (such as / * - + on the numeric keypad).
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Did you try googling for that error ? For instance I felt on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364932 which gives many things to check.
On 04/09/2010 06:11 AM, Xavier Chantry wrote:
On Fri, Apr 9, 2010 at 5:05 AM, David Rosenstrauch<darose@darose.net> wrote:
On Thu, April 8, 2010 9:51 pm, David Rosenstrauch wrote:
So .... WTF?!?!?!? Hal sees the keyboard. And xev running inside the x session sees the keyboard. SO WHY ON EARTH IS MY KEYBOARD STILL DEAD IN MY X SESSIONS?!?!? ARRRRGGGGHHHHHH!!!!
Wee hee! It gets weirder!
* Bizarrely enough, *some* of the keys on the keyboard actually work (such as / * - + on the numeric keypad).
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Did you try googling for that error ? For instance I felt on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364932 which gives many things to check.
Yes of course. It came up with many links - none of which provided any useful help. Which is why I'm posting here. DR
2010/4/9 David Rosenstrauch <darose@darose.net>:
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Not sure it's the same problem, but I experienced something similar a while ago... and I couldn't properly use my desktop for months =P Did you install NX or similar lately? Check this one out: http://bugs.archlinux.org/task/15236 HTH, Corrado
On Fri, Apr 9, 2010 at 3:54 PM, bardo <ilbardo@gmail.com> wrote:
2010/4/9 David Rosenstrauch <darose@darose.net>:
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Not sure it's the same problem, but I experienced something similar a while ago... and I couldn't properly use my desktop for months =P Did you install NX or similar lately? Check this one out: http://bugs.archlinux.org/task/15236
And by the way, one of the last comments in the debian bug is the following : "Thank you for your advice. In fact the bogus files were in /opt/lib/NX/lib. So it was an old (1 year ago) and bad installation (from an archive) of NoMachine libraries which mess up my system."
On 04/09/2010 09:54 AM, bardo wrote:
2010/4/9 David Rosenstrauch<darose@darose.net>:
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Not sure it's the same problem, but I experienced something similar a while ago... and I couldn't properly use my desktop for months =P Did you install NX or similar lately? Check this one out: http://bugs.archlinux.org/task/15236
HTH, Corrado
I've had NX installed for a long time. I think it got upgraded with the big upgrade though. I can try uninstalling it temporarily and see if that fixes things. Perhaps coincidentally (or not) NX also isn't working for me on that server right now. DR
On Fri, April 9, 2010 10:18 am, David Rosenstrauch wrote:
On 04/09/2010 09:54 AM, bardo wrote:
2010/4/9 David Rosenstrauch<darose@darose.net>:
* I'm getting a load of errors in the slim.log file that look like this: expected keysym, got XF86_Switch_VT_1 line 8 of xfree86
W T F ? ! ?
Not sure it's the same problem, but I experienced something similar a while ago... and I couldn't properly use my desktop for months =P Did you install NX or similar lately? Check this one out: http://bugs.archlinux.org/task/15236
HTH, Corrado
I've had NX installed for a long time. I think it got upgraded with the big upgrade though. I can try uninstalling it temporarily and see if that fixes things.
Perhaps coincidentally (or not) NX also isn't working for me on that server right now.
DR
Woo hoo! I think I finally just fixed this irritating problem - with a similar solution. Eventual fix (I think) was uninstalling an old copy of neatx (Google's clone of nx) that I had hanging around. Neatx had placed a file in /etc/ld.so.conf.d, which I'm guessing was what was messing things up. What a relief!!! Thanks for the help, all. DR
participants (7)
-
bardo
-
Daenyth Blank
-
David C. Rankin
-
David Rosenstrauch
-
Evangelos Foutras
-
Matěj Týč
-
Xavier Chantry