linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Laures <guillaume.laures@noos.fr>
To: mlan@cpu.lu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Keyboard trouble with XF 4.0.1
Date: Sun, 29 Oct 2000 22:40:02 +0100	[thread overview]
Message-ID: <39FC9932.6041E947@noos.fr> (raw)
In-Reply-To: 200010291647.RAA01482@piglet.grunz.lu

[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]

Michel Lanners wrote:

> Hi all,
>
> On  22 Oct, this message from Martin Costabel echoed through cyberspace:
> > I can tell you what is working for me. I have been using Franz's XF4
> > RPMs for quite a while without major problems (some minor ones still
> > persist, but since the RPMs are 3 months old, I won't repeat them here).
> > I am not using, however, the "linux" keycodes. Only the ADB codes.

You have attached my answer to the problem we seem to have in France
regarding the new input layer, since no good azerty keymap exists in the
standard distrib.
 - fr-mac.kmap.gz: a map to use at console (place in
/usr/lib/kbd/keymaps/mac/ and run kbdconfig)
 - xf86_nil_fr.diff.gz: a diff to stuff I modified in the xkb directory. (do
not try to apply it, but inspect it and see what should be included in the
distribution, test it)
Basically both are last Marc Shapiros's production, with various enhancements
(not much...) and with keycodes # completely redesigned regarding the new
input layer.
Note: you'd _rather_ use linux keycodes if you setup this...

I have only one problem so far: I can't switch from X to console. Otherwise
it's very neat.

>
> I still don't see how those Xkb options relate to anything in the files
> below /usr/lib/X11/xkb. Anybody can explain this?

I've yet to find some doc about it, but starting to play with rules/xfree86
made me learn what you can see in xf86_nil_fr.

Last but not least:
Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "keyboard"
#        Option      "XkbDisable"
        Option "XkbRules" "xfree86"
        Option "XkbModel"  "macintosh"
        Option "XkbLayout"  "fr"
EndSection

All using XFree86-4.0.1-0.36a and happy (so faster with r128).

And an advice: if you plan to move from XFree 4.0 to 4.0.1, have a clean
linuxppc install not far (other partition) to recover things once your
keyboard is completely screwed...

Later,

--
GoM



[-- Attachment #2: xf86_nil_fr.diff.gz --]
[-- Type: application/x-gzip, Size: 3783 bytes --]

[-- Attachment #3: fr-mac.kmap.gz --]
[-- Type: application/x-gzip, Size: 2414 bytes --]

  parent reply	other threads:[~2000-10-29 21:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 16:30 Keyboard trouble with XF 4.0.1 Michel Lanners
2000-10-22 18:45 ` Benjamin Herrenschmidt
2000-10-22 19:05 ` Martin Costabel
2000-10-22 20:53   ` Benjamin Herrenschmidt
2000-10-22 22:13     ` Martin Costabel
2000-10-23 12:32       ` Benjamin Herrenschmidt
2000-10-29 16:47   ` Michel Lanners
2000-10-29 18:57     ` Martin Costabel
2000-10-29 22:04       ` Michel Lanners
2000-10-29 21:40     ` Guillaume Laures [this message]
2000-10-29 21:59       ` Michel Lanners
2000-10-30  9:43         ` Guillaume Laures
2000-11-02  7:12   ` Michel Lanners
2000-10-29 22:09 ` Michel Lanners
2000-10-30 21:22   ` Keyboard trouble with XF 4.0.1R Guillaume Laures

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=39FC9932.6041E947@noos.fr \
    --to=guillaume.laures@noos.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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;
as well as URLs for NNTP newsgroup(s).