From: Helge Deller <deller@gmx.de>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] SOLVED: HIL keyboard problems
Date: Sun, 3 Feb 2002 20:15:13 +0100 [thread overview]
Message-ID: <200202032015.13091.deller@gmx.de> (raw)
Hi list,
I've found a solution for the problem with the not-working "i" and "o"
keys on HIL keyboards and X11.
Just grab the files
ftp://ftp.parisc-linux.org/XFree86/HILkeyb/hp
ftp://ftp.parisc-linux.org/XFree86/HILkeyb/hp.lst
and store both to /etc/X11/xkb/rules
Then change your keyboard definition section in
/etc/X11/XF86Config-4 to contain the following lines
Option "XkbRules" "hp"
Option "XkbModel" "hphil"
Option "CustomKeycodes" "yes"
and maybe:
Option "XkbLayout" "de"
with "de" replaced for your language in case you have
a non-US keyboard.
btw, the CustomKeycodes = yes option does the real trick here.
Alternately you may also fetch my XF86Config-4
from ftp://ftp.parisc-linux.org/XFree86/HILkeyb/XF86Config-4
and just change the Screen-section to match your display.
Please note: My XF86Config-4 is configured to use a Microsoft
compatible serial mouse on /dev/ttyS1 (serial port 2).
The HIL mouse is still not supported!
Regards,
Helge
reply other threads:[~2002-02-03 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202032015.13091.deller@gmx.de \
--to=deller@gmx.de \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox