From: switch <switch@attrition.jp>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test1] on a vaio GR laptop (one more)
Date: Wed, 16 Jul 2003 12:00:30 +0900 [thread overview]
Message-ID: <20030716030030.GB12397@suisho.attrition.jp> (raw)
In-Reply-To: <20030715140354.GB3365@inferi.kami.home>
On Tue, Jul 15, 2003 at 04:03:54PM +0200, Mattia Dongili wrote:
> > hi, here's some problems running the 1st 2.6 test kernel on this vaio
> > gr7k, a japanese model.
> >
> > 1. I've lost the '|' (pipe) keystroke in console, showkey reports the
> > following:
> > 0 press
> > 1 release
> > 55 release
> > 0 relesase
> > 1 release
> > 55 release
> > This laptop is equipped with a japanese keyboard so the | key is just
> > above the Yen key. This problem was already here in 2.5.7X (haven't
> > tested previous kernels).
> > Using an xterm give me the | key back using this config option:
> > Option "XkbModel" "jp106"
> > Option "XkbLayout" "jp"
hello,
i recall having this happen in 2.5 (although i think it also occured under X).
afaik this has to do with the new input system (check atkbd.c). im not sure if
this is the correct fix, but i simply modified my jp106 keymap:
--- jp106.map.orig 2003-07-16 11:40:25.000000000 +0900
+++ jp106.map 2003-07-16 11:40:00.000000000 +0900
@@ -64,3 +64,6 @@
keycode 97 = Control
keycode 124 = backslash bar
control keycode 124 = Control_backslash
+keycode 183 = backslash bar
+ control keycode 183 = Control_backslash
+
(i left the 124 there because i sometimes go back into 2.4 kernels)
and i think i needed to recompile my loadkeys (from kbd-1.08) as
addkey didnt like the 183 index (due to KEY_MAX, iirc).
hope that works/is the correct way to deal with this issue.
prev parent reply other threads:[~2003-07-16 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 13:38 [2.6.0-test1] on a vaio GR laptop Mattia Dongili
2003-07-15 14:03 ` [2.6.0-test1] on a vaio GR laptop (one more) Mattia Dongili
2003-07-16 3:00 ` switch [this message]
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=20030716030030.GB12397@suisho.attrition.jp \
--to=switch@attrition.jp \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).