From: Guillaume Laures <guillaume.laures@noos.fr>
To: mlan@cpu.lu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Keyboard trouble with XF 4.0.1
Date: Mon, 30 Oct 2000 10:43:27 +0100 [thread overview]
Message-ID: <39FD42BF.3623CD9D@noos.fr> (raw)
In-Reply-To: 200010292159.WAA02769@piglet.grunz.lu
Michel Lanners wrote:
> Hi Guillaume,
>
> On 29 Oct, this message from Guillaume Laures echoed through cyberspace:
> > - fr-mac.kmap.gz: a map to use at console (place in
> > /usr/lib/kbd/keymaps/mac/ and run kbdconfig)
>
> I'll have a look, but as long as I stay in ADB keycodes, my console
> works ok. I have yet to check why this is so ;-)
Installed initscripts-5.35-1a ?
It will switch you to linux keycodes in conole, I guess by sending a 1 in the
appropriate location in /proc
> > 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...
>
> Any solution for MOL? It doesn't work for me with Linux keycodes...
I didn't used mol for a while, have enough to do in the linux side...
>
> That's the way I'm going as well: just reverse engineer the stuff.
> Change somthing and see what happens ;-) So far I've successfully made X
> load some XKB stuff, but the result is totally messed up keys. Maybe
> some old xmodmap setting is getting in my way...
XKBModel = macintosh_old may be useful to you...
>
>
> > 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...
>
> Hehehehe.... For this sort of thing, I always first make backups of
> config files (my xdm directory has been deleted only once by an RPM
> install...), then I keep the old RPMs handy, and then I have a second
> machine to telnet into the DUU (Device Under Upgrade ;-).
I made regularly a complete .tbz of all my stuff, since upgrading a rpm may be
easy & messy, but downgrading is really a pain.
--
GoM
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-30 9:43 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
2000-10-29 21:59 ` Michel Lanners
2000-10-30 9:43 ` Guillaume Laures [this message]
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=39FD42BF.3623CD9D@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.