--Signature_Thu__22_Dec_2005_08_43_25_-0500_lyOxxhWeeURRhQB.
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> Oddly enough though the keyboard isn't quite right.  Only the down
> arrow sends something recognized as down arrow.  The up arror, for
> example, sends an '=3D'.

In 3.0 use something like this:
Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option  "XkbRules" "xfree86"
        Option  "XkbModel" "pc105"
        Option  "XkbLayout" "us"
        Option      "Protocol" "wskbd"
        Option      "Device" "/dev/wskbd0"
EndSection

Yes, it's a blatant lie but XFree translates everything to some PCish
set of scancodes anyway before doing any further processing. This should
make most keys work without any xmodmap stunts ( and "XkbLayout" "de"
should Just Work )

The point is - there are two keyboard drivers in XFree - 'keyboard' and
'kbd'. The former is a horrible mess that only works properly with
PS/2-ish keyboards, the latter is a module that works just fine with
USB, Sun and ADB keyboards but has problems with PS/2 ones ( apparently
some of the scancode mangling done in 'keyboard' doesn't work in 'kbd' -
didn't have time to investigate further yet )
The error you describe sounds like you're either using 'keyboard' or
some outdated xmodmap hack.

have fun
Michael

--Signature_Thu__22_Dec_2005_08_43_25_-0500_lyOxxhWeeURRhQB.
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQ6qtfcpnzkX8Yg2nAQL0BggAvQTn6CHdjZoJ9HsRj0Q3fmXbX3WgP9Pe
EWfqaLH5+8Ns+n9OhrvHeMY4OH9SWzZhSOG6ssf9YE9KXVwfMON3NTVbEg0zm/pE
YNvsC+MDOIzprUtoClqmDiN3km4SezdaEYRYqgZMqxwTJOe6oDVtXo39P4qC3Ka3
+4M+sa/7Fs1nEDHVgb7u0oBb36jyoBh3stopvFfcvMBDtVK15W2idbbSKjICwpMK
zAyihZhO4p+KuvwKACnxeGVLUwcqpZFLbI9suyqBhIAY5G7axBniZAoVfZ+KHzm8
yIxU1MbMb1N93tdsPO3r7u3By/3dpOtl0TuaRJZ725O2+byj9PuL8g==
=Z6Rz
-----END PGP SIGNATURE-----

--Signature_Thu__22_Dec_2005_08_43_25_-0500_lyOxxhWeeURRhQB.--