Why does X (on Sarge) ignore my keyboard selection?

From: John Winters (newstmp_at_sinodun.org.uk)
Date: 08/25/04


Date: Wed, 25 Aug 2004 16:21:00 +0100 (BST)

I've just done a fresh Sarge installation with XFree86 4.3.0. All seems
well except for the fact that it insists on behaving as if I had an
American keyboard, even though I have set it for a UK keyboard.

I originally had the following for my keyboard clause, which works on
all my other similar boxes.

Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "keyboard"
        Option "CoreKeyboard"
        Option "XkbRules" "xfree86"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "gb"
EndSection

On the advice of several people I've tried variations and I now have:

Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "keyboard"
        Option "CoreKeyboard"
        Option "XkbRules" "xfree86"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "en-GB"
        Option "XkbVariant" "gb"
EndSection

but the effect is exactly the same - American keyboard layout.
Examining the log file I can see it's definitely using this file
and seeing the clauses, but it just seems to be ignoring them. Can
anyone suggest why this might be please?

(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "en-GB"
(**) XKB: layout: "en-GB"
(**) Option "XkbVariant" "gb"
(**) XKB: variant: "gb"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "Generic Mouse"

TIA,
John

-- 
Wallingford, Oxfordshire, England
i = (free(NULL), i++);


Relevant Pages

  • startx fail after portupgrade Xorg 6.8.2 - (keyboard)
    ... My original XF86Config has not been changed during upgrade to 6.8.2 nor ... have there been any hardware changes. ... Log file entries relating to kb are as follows: ... Keyboard: CustomKeycode disabled ...
    (freebsd-questions)
  • Re: problems with hal in freebsd 7.2 i386
    ... That's what Xorg autodetects, anyway, and it ... Cannot locate a core keyboard device. ... The server relies on HAL to provide the list of input devices. ... the most recent log file, I deleted all the Xorg logs, restarted it, and ...
    (freebsd-questions)
  • Re: problems with hal in freebsd 7.2 i386
    ... That's what Xorg autodetects, anyway, and it ... Cannot locate a core keyboard device. ... The server relies on HAL to provide the list of input devices. ... the most recent log file, I deleted all the Xorg logs, restarted it, and ...
    (freebsd-questions)
  • Re: Keyboard/Mouse Support
    ... Yes I do see both lines in the log file. ... There are a couple of errors for the USB Host controller not loading, ... nothing with the mouse or keyboard. ... >>XPe image. ...
    (microsoft.public.windowsxp.embedded)
  • Compaq Armada m700 - XFree86 Problems.
    ... I am trying ti install FC1 on a Compaq and I am having troubles with the ... What happens is that when it switches to graphics the ... dmesg reports the same amount of "keyboard timed ... In the log file there is nothing about the keyboard beside the ...
    (Fedora)