Date: Wed, 04 Feb 2009 17:43:03 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: dikshie <dikshie@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: japanese keyboard after xorg upgrade Message-ID: <4989D3A7.6040701@infracaninophile.co.uk> In-Reply-To: <910e60e80902040643x13f6db8bs6a3db93e85ddf679@mail.gmail.com> References: <910e60e80902040643x13f6db8bs6a3db93e85ddf679@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
dikshie wrote:
> Hi,
> any explanation why my japanese keyboard
> does not work after xorg upgrade?
>
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "kbd"
> Option "XkbRules" "xorg"
> Option "XkbModel" "jp106"
> Option "XkbLayout" "jp"
> EndSection
>
> any solutions?
Is it hald that's detecting your keyboard for the X server? You can
tell this by reading Xorg.0.log -- something like this indicates hal
involvement:
(II) config/hal: Adding input device AT Keyboard
(**) AT Keyboard: always reports core events
(**) Option "Protocol" "standard"
(**) AT Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) AT Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) AT Keyboard: XkbModel: "pc105"
(**) Option "XkbLayout" "gb"
(**) AT Keyboard: XkbLayout: "gb"
(**) Option "CustomKeycodes" "off"
(**) AT Keyboard: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "AT Keyboard" (type: KEYBOARD)
Now, hal has no way of telling what sort of layout a keyboard has
automatically[*]. You can tell it what to use by creating a file
/usr/local/etc/hal/fdi/policy/x11-input.fdi with contents similar to
this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keyboard">
<merge key="input.xkb.layout" type="string">gb</merge>
</match>
</device>
</deviceinfo>
Obviously, you'ld want 'jp' in ther rather than 'gb'.
[Not certain exactly what you'ld need to add to override the default
XkbModel setting (pc105) -- but I suspect analogy and guesswork will
serve you well enough in this instance]
Note that there is a race condition on system reboot between xdm(1) or
whatever display manager you use starting up and hald(8) having fully
initialised -- there have been a number of workarounds posted in this
list.
Alternatively you can use the following setting in the ServerLayout
section of xorg.conf:
Option "AllowEmptyInput" "off"
This essentially tells X to just use the values from xorg.conf.
Cheers,
Matthew
[*] As far as I know. It seems like a pretty odd omission to me and
I'd love to be proved wrong.
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkmJ060ACgkQ8Mjk52CukIxWgQCdFQ/id+iqJCM44es8Y64DDrof
pmUAoIjhz2Din2SsYCch7ivZAShnIkNP
=wq7y
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4989D3A7.6040701>