| Author |
Message |
|
opel70
|
 Posted: Sat Dec 03, 2011 10:23 pm |
|
|
Joined: Tue Apr 11, 2006 7:44 am
Posts: 287
Location:
Los Angeles, CA
|
|
Hello,
After having some problems upgrading from 6.04 to 7.1 I am getting on the right track with a fresh install. I've restored my database and tuners are working. Now the next thing to get figured out before moving forward is the keyboard. The arrow keys are not working. I've done some digging, and it appears this is from a change in driver from the 'kbd' driver to using 'evdev'.
I started up 'xev' and was getting information to create an .Xmodmap, but then I stumbles across the file in /usr/share/X11/xkb/keycodes/evdev, that looked to have all of the correct keycodes already. So, why isn't this working?
Of course, arrow keys seem to work right up until X starts, and then no go. I've got some work ahead of me in getting my ATI Remote Wonder II working and my IR blaster, but I'd like to get my keyboard working first.
Any ideas?
_________________
Tim
LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT
|
|
| Top |
|
 |
|
mattbatt
|
Posted: Sat Dec 03, 2011 10:29 pm |
|
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
|
arrow keys on what device? wired or wireless keyboard? bluetooth ? remote control? the more details the better.
_________________ My System
|
|
| Top |
|
|
|
opel70
|
Posted: Sun Dec 04, 2011 1:02 pm |
|
|
Joined: Tue Apr 11, 2006 7:44 am
Posts: 287
Location:
Los Angeles, CA
|
Sorry, thought keyboard was specific enough. This is with a wired or wireless keyboard. The problem is with the separate arrow keys. The arrow keys in the number pad work correctly.
This site ( http://kb.vmware.com/selfservice/micros ... Id=1007439) talks about the exact same problem. Even showing the same problematic keycode example of 116 returning Win+R.
If I boot to the console instead of the full X system, the keyboard functions normally. However, as soon as X starts, the arrow keys (and all of the keys in that center section of the keyboard, between the letters and the number pad) stop functioning correctly.
As I mentioned, that keycode file in the X11 folder seems to have the correct mappings, but it seems to net be being used. This is probably something I the xorg.conf, but I am just using the one generated by the install system.
So at this point I haven't even tried configuring my remote, and no bluetooth in play. Just a wireless USB keyboard and a wired USB keyboard.
_________________
Tim
LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT
|
|
| Top |
|
|
|
opel70
|
Posted: Mon Dec 05, 2011 3:02 pm |
|
|
Joined: Tue Apr 11, 2006 7:44 am
Posts: 287
Location:
Los Angeles, CA
|
|
And then last night I just wanted to watch the football game, so I pulled out my old PS/2 keyboard with the 20' cord, so that I could use the arrow keys on the number pad while sitting on the couch. Well, I plugged in the keyboard and decided to test the other arrow keys, and they worked. I then went back and tested the arrow keys on the two USB keyboards, and they worked. So tonight I'll try duplicating this experiment when I can reboot the PC, but it LOOKS like the problem only happens with USB keyboards, and is resolved with PS/2 keyboards.
Hmmm.
_________________
Tim
LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT
|
|
| Top |
|
|
|
Martian
|
Posted: Mon Dec 05, 2011 3:36 pm |
|
|
Joined: Wed Feb 08, 2006 6:13 pm
Posts: 480
Location:
IN
|
|
For what it's worth - my USB wireless Logitech keyboard and mouse work fine (including arrow keys) and I don't have anything plugged into the PS/2 port - in fact, I'm not sure I have a PS/2 port...
_________________
ABIT NF-M2 nView | Athlon 64 X2 3800+ | 2GB DDR2 800 | HDHomerun | GeForce 6150 (onboard) | WD 640 GB SATA HD | DVD-RW (sata) | StreamZap IR receiver with Logitech Harmony remote
Vizio 37" LCD HDTV (1080p)
|
|
| Top |
|
|
|
opel70
|
Posted: Mon Dec 05, 2011 8:19 pm |
|
|
Joined: Tue Apr 11, 2006 7:44 am
Posts: 287
Location:
Los Angeles, CA
|
I'm guessing that there is something in the xorg.conf.d directory that is controlling this, but now with the new locations I don't know what is actually controlling the keyboard driver. It looks like it is either the "11-inputs.conf" or the "20-automv.conf". Both of these have "InputDevice" sections of "Keyboard0". The "11-inputs.conf" shows a driver of "kbd" in this section while the "20-automv.conf" shows a driver of "keyboard".
An additional oddity that I noticed after testing a few reboots tonight: The arrow keys on the USB keyboard only start working after I press any key on the PS/2 keyboard.
When I look at the Xorg.0.log, it looks like both the USB keyboard and the PS/2 keyboard are using the same drivers and keymap, so I am at a loss to explain why these keymaps do not work until I press a key on the PS/2 keyboard. I have even double checked with xev that the keycode passed does not change. Where else can I look to see why this isn't working?
Code: [ 24.125] (II) XKB: Reusing cached keymap
[ 24.127] (II) LoadModule: "kbd"
[ 24.127] (WW) Warning, couldn't open module kbd
[ 24.127] (II) UnloadModule: "kbd"
[ 24.127] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 24.127] (EE) No input driver matching `kbd'
[ 24.127] (II) LoadModule: "mouse"
[ 24.128] (WW) Warning, couldn't open module mouse
[ 24.128] (II) UnloadModule: "mouse"
[ 24.128] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 24.128] (EE) No input driver matching `mouse'
[ 24.139] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 24.139] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.139] (II) LoadModule: "evdev"
[ 24.139] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 24.215] (II) Module evdev: vendor="X.Org Foundation"
[ 24.216] compiled for 1.9.2, module version = 2.6.0
[ 24.216] Module class: X.Org XInput Driver
[ 24.216] ABI class: X.Org XInput driver, version 11.0
[ 24.216] (**) Power Button: always reports core events
[ 24.216] (**) Power Button: Device: "/dev/input/event3"
[ 24.221] (--) Power Button: Found keys
[ 24.221] (II) Power Button: Configuring as keyboard
[ 24.221] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 24.221] (**) Option "xkb_rules" "evdev"
[ 24.221] (**) Option "xkb_model" "evdev"
[ 24.221] (**) Option "xkb_layout" "us"
[ 24.316] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 24.316] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.316] (**) Power Button: always reports core events
[ 24.316] (**) Power Button: Device: "/dev/input/event2"
[ 24.320] (--) Power Button: Found keys
[ 24.320] (II) Power Button: Configuring as keyboard
[ 24.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 24.320] (**) Option "xkb_rules" "evdev"
[ 24.320] (**) Option "xkb_model" "evdev"
[ 24.320] (**) Option "xkb_layout" "us"
[ 24.320] (II) XKB: Reusing cached keymap
[ 24.325] (II) config/udev: Adding input device Device USB Device (/dev/input/event0)
[ 24.326] (**) Device USB Device: Applying InputClass "evdev keyboard catchall"
[ 24.326] (**) Device USB Device: always reports core events
[ 24.326] (**) Device USB Device: Device: "/dev/input/event0"
[ 24.333] (--) Device USB Device: Found scroll wheel(s)
[ 24.333] (II) Device USB Device: Forcing buttons for scroll wheel(s)
[ 24.333] (--) Device USB Device: Found relative axes
[ 24.333] (--) Device USB Device: Found absolute axes
[ 24.333] (--) Device USB Device: Found keys
[ 24.333] (II) Device USB Device: Configuring as mouse
[ 24.333] (II) Device USB Device: Configuring as keyboard
[ 24.333] (II) Device USB Device: Adding scrollwheel support
[ 24.333] (**) Device USB Device: YAxisMapping: buttons 4 and 5
[ 24.333] (**) Device USB Device: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 24.333] (II) XINPUT: Adding extended input device "Device USB Device" (type: KEYBOARD)
[ 24.333] (**) Option "xkb_rules" "evdev"
[ 24.333] (**) Option "xkb_model" "evdev"
[ 24.333] (**) Option "xkb_layout" "us"
[ 24.333] (II) XKB: Reusing cached keymap
[ 24.333] (EE) Device USB Device: failed to initialize for relative axes.
[ 24.333] (II) Device USB Device: initialized for absolute axes.
[ 24.334] (II) config/udev: Adding input device Device USB Device (/dev/input/event1)
[ 24.334] (**) Device USB Device: Applying InputClass "evdev pointer catchall"
[ 24.334] (**) Device USB Device: always reports core events
[ 24.334] (**) Device USB Device: Device: "/dev/input/event1"
[ 24.338] (--) Device USB Device: Found 3 mouse buttons
[ 24.338] (--) Device USB Device: Found scroll wheel(s)
[ 24.338] (--) Device USB Device: Found relative axes
[ 24.338] (--) Device USB Device: Found x and y relative axes
[ 24.338] (II) Device USB Device: Configuring as mouse
[ 24.338] (II) Device USB Device: Adding scrollwheel support
[ 24.338] (**) Device USB Device: YAxisMapping: buttons 4 and 5
[ 24.338] (**) Device USB Device: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 24.338] (II) XINPUT: Adding extended input device "Device USB Device" (type: MOUSE)
[ 24.338] (**) Device USB Device: (accel) keeping acceleration scheme 1
[ 24.338] (**) Device USB Device: (accel) acceleration profile 0
[ 24.338] (**) Device USB Device: (accel) acceleration factor: 2.000
[ 24.338] (**) Device USB Device: (accel) acceleration threshold: 4
[ 24.338] (II) Device USB Device: initialized for relative axes.
[ 24.338] (II) config/udev: Adding input device Device USB Device (/dev/input/mouse0)
[ 24.338] (II) No input driver/identifier specified (ignoring)
[ 24.342] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 24.342] (II) No input driver/identifier specified (ignoring)
[ 28.079] GetModeLine - scrn: 0 clock: 84060
[ 28.079] GetModeLine - hdsp: 1360 hbeg: 1392 hend: 1712 httl: 1740
[ 28.079] vdsp: 768 vbeg: 771 vend: 777 vttl: 806 flags: 10
[ 64.550] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event5)
[ 64.550] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 64.550] (**) AT Translated Set 2 keyboard: always reports core events
[ 64.550] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event5"
[ 64.554] (--) AT Translated Set 2 keyboard: Found keys
[ 64.554] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 64.554] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 64.554] (**) Option "xkb_rules" "evdev"
[ 64.554] (**) Option "xkb_model" "evdev"
[ 64.554] (**) Option "xkb_layout" "us"
[ 64.554] (II) XKB: Reusing cached keymap
_________________
Tim
LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT
|
|
| Top |
|
|
|
opel70
|
Posted: Wed Dec 07, 2011 10:05 pm |
|
|
Joined: Tue Apr 11, 2006 7:44 am
Posts: 287
Location:
Los Angeles, CA
|
|
Ok, well after having success with lirc, I figured I'd take another look at this. I wound up just removing all of the "extra" keyboard and mouse config sections in the "20-automv.conf" file and completely removing the "11-inputs.conf" file and all is well with the keyboards now.
I do wonder why those config files had those lines since they wound up just causing problems. But as long as it is now working, I am happy.
_________________
Tim
LinHES 8.4
HDHR3
BioStar A770, AMD X2 4050e, 2GB RAM
GigaByte GeForce 8400, Chaintech AV710
USB-UIRT
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
