From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: "Jens K. Loewe" Date: Wed, 24 Jul 2019 21:01:27 +0200 Message-ID: To: 9fans@9fans.net Content-Type: text/plain; charset="UTF-8" Subject: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 0202d67e-eada-11e9-9d60-3106f5b1d025 Ahoy, I've been trying to give 9front a test ride for a while now, and I'm stuck with one specific problem. So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the key seems to be dead on all of my keyboards. I tried quite a lot of them, both inside QEMU on two different computers and on a dedicated ThinkPad. Also, using the de layout does not fix that. Is that a known problem or a configuration error? From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Ole-Hjalmar Kristensen Date: Wed, 24 Jul 2019 23:04:44 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000005116cc058e73a90f" Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 020bb1b8-eada-11e9-9d60-3106f5b1d025 --0000000000005116cc058e73a90f Content-Type: text/plain; charset="UTF-8" Can't give a definitive answer, but it works fine on my Norwegian keyboard which also has a rather different layout from the US keyboard. Unless the key code is simply not handled, I can't imagine why you get nothing at all. ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe : > Ahoy, > > I've been trying to give 9front a test ride for a while now, and I'm > stuck with one specific problem. > > So I have a German keyboard layout where <, > and | are on the same > key. However, while I have no problems with these keys, in 9front the > key seems to be dead on all of my keyboards. I tried quite a lot of > them, both inside QEMU on two different computers and on a dedicated > ThinkPad. Also, using the de layout does not fix that. > > Is that a known problem or a configuration error? > > --0000000000005116cc058e73a90f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can't give a definitive answer, but it works fine on = my Norwegian keyboard which also has a rather different layout from the US = keyboard. Unless the key code is simply not handled, I can't imagine wh= y you get nothing at all.

ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe <= jens.k.loewe@gmail.com>:
Ahoy,

I've been trying to give 9front a test ride for a while now, and I'= m
stuck with one specific problem.

So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the
key seems to be dead on all of my keyboards. I tried quite a lot of
them, both inside QEMU on two different computers and on a dedicated
ThinkPad. Also, using the de layout does not fix that.

Is that a known problem or a configuration error?

--0000000000005116cc058e73a90f-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Rodrigo_G=2E_L=C3=B3pez?= Date: Thu, 25 Jul 2019 09:17:51 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000000cddf0058e7c3ae7" Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 0222e1d0-eada-11e9-9d60-3106f5b1d025 --0000000000000cddf0058e7c3ae7 Content-Type: text/plain; charset="UTF-8" i have a qwertz but i use it with the us layout (any other layout sucks for programming). i think you can change the layout with kbmap(1), and set it to de or whatever, although i don't have a 9 machine with me right now so can't tell for sure. if the default map doesn't work, read it, ask on #cat-v@freenode and write a new, fixed kbmap you can fling into kbdfs(8). you should also ask this in the 9front ml. good luck. -rodri On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen < ole.hjalmar.kristensen@gmail.com> wrote: > Can't give a definitive answer, but it works fine on my Norwegian keyboard > which also has a rather different layout from the US keyboard. Unless the > key code is simply not handled, I can't imagine why you get nothing at all. > > ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe : > >> Ahoy, >> >> I've been trying to give 9front a test ride for a while now, and I'm >> stuck with one specific problem. >> >> So I have a German keyboard layout where <, > and | are on the same >> key. However, while I have no problems with these keys, in 9front the >> key seems to be dead on all of my keyboards. I tried quite a lot of >> them, both inside QEMU on two different computers and on a dedicated >> ThinkPad. Also, using the de layout does not fix that. >> >> Is that a known problem or a configuration error? >> >> --0000000000000cddf0058e7c3ae7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
i have a qwertz but i use it with the us layout (any= other layout sucks for programming). i think you can change the layout wit= h kbmap(1), and set it to de or whatever, although i don't have a 9 mac= hine with me right now so can't tell for sure.
<= br>
if the default map doesn't work, read it, as= k on #cat-v@freenode and write a new, fixed kbmap you can fling into kbdfs(= 8).

you should also ask = this in the 9front ml.

good luck.

-rodri=

On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.= com> wrote:
Can't give a definitive answer, but it works fine on my Norwegian key= board which also has a rather different layout from the US keyboard. Unless= the key code is simply not handled, I can't imagine why you get nothin= g at all.

ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe <jens.k.loewe= @gmail.com>:
Ahoy,

I've been trying to give 9front a test ride for a while now, and I'= m
stuck with one specific problem.

So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the
key seems to be dead on all of my keyboards. I tried quite a lot of
them, both inside QEMU on two different computers and on a dedicated
ThinkPad. Also, using the de layout does not fix that.

Is that a known problem or a configuration error?

--0000000000000cddf0058e7c3ae7-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jens K. Loewe" Content-Type: multipart/alternative; boundary=Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Thu, 25 Jul 2019 13:40:52 +0200 Message-Id: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> References: In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 02ccdae6-eada-11e9-9d60-3106f5b1d025 --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I tried using kbmap (which is not that easy without < and > on the keyboard)= , but the key still has no function for me. Weird, honestly. :-/ Thank you for the information that a 9front mailing list exists. I may want t= o look for that, although I guess that most of them are here as well. > Am 25.07.2019 um 09:17 schrieb Rodrigo G. L=C3=B3pez : >=20 > i have a qwertz but i use it with the us layout (any other layout sucks fo= r programming). i think you can change the layout with kbmap(1), and set it t= o de or whatever, although i don't have a 9 machine with me right now so can= 't tell for sure. >=20 > if the default map doesn't work, read it, ask on #cat-v@freenode and write= a new, fixed kbmap you can fling into kbdfs(8). >=20 > you should also ask this in the 9front ml. >=20 >=20 > good luck. >=20 > -rodri >=20 >> On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen wrote: >> Can't give a definitive answer, but it works fine on my Norwegian keyboar= d which also has a rather different layout from the US keyboard. Unless the k= ey code is simply not handled, I can't imagine why you get nothing at all. >>=20 >> ons. 24. jul. 2019, 21.03 skrev Jens K. Loewe : >>> Ahoy, >>>=20 >>> I've been trying to give 9front a test ride for a while now, and I'm >>> stuck with one specific problem. >>>=20 >>> So I have a German keyboard layout where <, > and | are on the same >>> key. However, while I have no problems with these keys, in 9front the >>> key seems to be dead on all of my keyboards. I tried quite a lot of >>> them, both inside QEMU on two different computers and on a dedicated >>> ThinkPad. Also, using the de layout does not fix that. >>>=20 >>> Is that a known problem or a configuration error? >>>=20 --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I t= ried using kbmap (which is not that easy without < and > on the keyboa= rd), but the key still has no function for me. Weird, honestly. :-/

Thank you for the information that a= 9front mailing list exists. I may want to look for that, although I guess t= hat most of them are here as well.

Am 25.07.2019 u= m 09:17 schrieb Rodrigo G. L=C3=B3pez <rodrigosloop@gmail.com>:

i have a qwertz but i use it with= the us layout (any other layout sucks for programming). i think you can cha= nge the layout with kbmap(1), and set it to de or whatever, although i don't= have a 9 machine with me right now so can't tell for sure.

if the default map doesn't work, read it,= ask on #cat-v@freenode and write a new, fixed kbmap you can fling into kbdf= s(8).

you should also ask= this in the 9front ml.

good luck.

-rodri<= br>
On Wed, Jul 24, 2019, 11:06 PM Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:

<= div class=3D"gmail_quote">
ons. 24. jul= . 2019, 21.03 skrev Jens K. Loewe <jens.k.loewe@gmail.com>:
=
Ahoy,

I've been trying to give 9front a test ride for a while now, and I'm
stuck with one specific problem.

So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the
key seems to be dead on all of my keyboards. I tried quite a lot of
them, both inside QEMU on two different computers and on a dedicated
ThinkPad. Also, using the de layout does not fix that.

Is that a known problem or a configuration error?

= --Apple-Mail-91C4B2BE-2C93-4D24-83D4-E9B9E56507C6-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> References: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> From: Lucio De Re Date: Fri, 26 Jul 2019 07:59:38 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 02fb7c20-eada-11e9-9d60-3106f5b1d025 On 7/25/19, Jens K. Loewe wrote: > I tried using kbmap (which is not that easy without < and > on the > keyboard), but the key still has no function for me. Weird, honestly. :-/ > Legacy Plan 9, with /dev/kbmap device driver, uses F11 and F12 to trigger monitoring keystrokes. Maybe that will help you debug the problem? Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jens K. Loewe" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Fri, 26 Jul 2019 18:10:36 +0200 Message-Id: References: <6DD95854-3117-4907-BB8E-C8A04A5C2BAF@gmail.com> In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 03231e10-eada-11e9-9d60-3106f5b1d025 Does 9front also do that? > Am 26.07.2019 um 07:59 schrieb Lucio De Re : > >> On 7/25/19, Jens K. Loewe wrote: >> I tried using kbmap (which is not that easy without < and > on the >> keyboard), but the key still has no function for me. Weird, honestly. :-/ >> > > Legacy Plan 9, with /dev/kbmap device driver, uses F11 and F12 to > trigger monitoring keystrokes. Maybe that will help you debug the > problem? > > Lucio. > From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jonas Amoson" To: <9fans@9fans.net> Date: Fri, 26 Jul 2019 12:54:34 -0700 Message-ID: <8235E58DF88046E2A94BF3C789690B2A@mail2world.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_74BC_01D543B1.46472E00" Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 0327b2c2-eada-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. ------=_NextPart_000_74BC_01D543B1.46472E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I am not sure I will solve your problem, but maybe give some input. I had a similar problem (That the '<' key to the right of the left shift key on ISO-style keyboards didn't work) on a Bell Labs Plan 9 on my Raspberry PI (though it might nowadays, it is an old installation on that sdcard). It does however work on 9front on my Pi. If I remember correctly, I had the key working on a PC running Bell Labs Plan 9 if I connected the keyboard to PS/2, but not when connected to USB using a converter. But again, on 9front it works both on PS/2 and USB on that PC for me. Jonas <-----Ursprungligt Meddelande-----> From: Jens K. Loewe [jens.k.loewe@gmail.com] Sent: 24/7/2019 9:57:27 PM To: 9fans@9fans.net Subject: [9fans] Trying to make 9front work on QWERTZ Ahoy, I've been trying to give 9front a test ride for a while now, and I'm stuck with one specific problem. So I have a German keyboard layout where <, > and | are on the same key. However, while I have no problems with these keys, in 9front the key seems to be dead on all of my keyboards. I tried quite a lot of them, both inside QEMU on two different computers and on a dedicated ThinkPad. Also, using the de layout does not fix that. Is that a known problem or a configuration error? . ------=_NextPart_000_74BC_01D543B1.46472E00 Content-Type: text/html Content-Transfer-Encoding: 7bit I am not sure I will solve your problem, but maybe give some
input. I had a similar problem (That the ‘<‘ key to the right of
the left shift key on ISO-style keyboards didn’t work) on a Bell
Labs Plan 9 on my Raspberry PI (though it might nowadays, it is
an old installation on that sdcard). It does however work on 9front
on my Pi. If I remember correctly, I had the key working on a PC
running Bell Labs Plan 9 if I connected the keyboard to PS/2, but
not when connected to USB using a converter. But again, on 9front
it works both on PS/2 and USB on that PC for me.

Jonas


<-----Ursprungligt Meddelande----->
  From: Jens K. Loewe [jens.k.loewe@gmail.com]
Sent: 24/7/2019 9:57:27 PM
To: 9fans@9fans.net
Subject: [9fans] Trying to make 9front work on QWERTZ 

Ahoy,

I've been trying to give 9front a test ride for a while now, and I'm
stuck with one specific problem.

So I have a German keyboard layout where <, > and | are on the same
key. However, while I have no problems with these keys, in 9front the
key seems to be dead on all of my keyboards. I tried quite a lot of
them, both inside QEMU on two different computers and on a dedicated
ThinkPad. Also, using the de layout does not fix that.

Is that a known problem or a configuration error?

.
------=_NextPart_000_74BC_01D543B1.46472E00-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 27 Jul 2019 11:21:19 +0200 From: cinap_lenrek@felloff.net To: 9fans@9fans.net In-Reply-To: AF69836B-E208-44B4-9CE0-6304BD7BEDCD@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 0332b0e6-eada-11e9-9d60-3106f5b1d025 on my t23, which has physical german keyboard layout, the scancode for the [<>|] key left to the [Y] key is 0x56 (86 decimal), which is not mapped with us layout. tho this is mapped in german keyboard layout: term% grep ' 86' /sys/lib/kbmap/de 0 86 '< 1 86 '> 2 86 0 3 86 '| 4 86 0 running the following on my t23 maps it. term% echo '0 0x56 ''<' > /dev/kbmap term% echo '1 0x56 ''>' > /dev/kbmap term% echo '3 0x56 ''|' > /dev/kbmap maybe your keyboard produces a different scancode? you can attach ratrace to kbdfs [scanproc] pid and look what it reads back from /dev/scancode for a ps2 keyboard. usb keyboards work differently. you can bring back that scancode debug thing with F11/F12 with the following patch which should work for both ps2 and usb keyboards. --- a/sys/src/cmd/aux/kbdfs/kbdfs.c Thu Jul 25 17:44:47 2019 +0200 +++ b/sys/src/cmd/aux/kbdfs/kbdfs.c Sat Jul 27 11:12:20 2019 +0200 @@ -43,6 +43,7 @@ int alt; int altgr; int leds; + int debug; }; struct Qtab { @@ -337,6 +338,9 @@ { Key key; + if(scan->debug) + fprint(2, "kbdputsc %#p sc %x esc1 %d esc2 %d\n", scan, c, scan->esc1, scan->esc2); + /* * e0's is the first of a 2 character sequence, e1 and e2 the first * of a 3 character sequence (on the safari) @@ -390,6 +394,13 @@ if(scan->ctl && scan->alt && key.r == Kdel) reboot(); + if(key.down){ + if(key.b == (KF|11)) + scan->debug = 1; + if(key.b == (KF|12)) + scan->debug = 0; + } + if(key.b) send(keychan, &key); after applying that change, run mk install in /sys/src/cmd/aux/kbdfs and then rebuild the kernel (as kbdfs gets included into the kernel image). -- cinap From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: "Jens K. Loewe" Date: Sat, 27 Jul 2019 21:18:38 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Trying to make 9front work on QWERTZ Topicbox-Message-UUID: 0343aa86-eada-11e9-9d60-3106f5b1d025 > maybe your keyboard produces a different scancode? The internal T60 keyboard, a native USB keyboard and a DIN-to-USB converted keyboard all produce the wrong scancodes on different hardware? That sounds unreasonable. But I'll try to test that next week ... thank you. Am Sa., 27. Juli 2019 um 11:22 Uhr schrieb : > > on my t23, which has physical german keyboard layout, the scancode > for the [<>|] key left to the [Y] key is 0x56 (86 decimal), which > is not mapped with us layout. > > tho this is mapped in german keyboard layout: > > term% grep ' 86' /sys/lib/kbmap/de > 0 86 '< > 1 86 '> > 2 86 0 > 3 86 '| > 4 86 0 > > running the following on my t23 maps it. > > term% echo '0 0x56 ''<' > /dev/kbmap > term% echo '1 0x56 ''>' > /dev/kbmap > term% echo '3 0x56 ''|' > /dev/kbmap > > maybe your keyboard produces a different scancode? > > you can attach ratrace to kbdfs [scanproc] pid and look what > it reads back from /dev/scancode for a ps2 keyboard. > usb keyboards work differently. > > you can bring back that scancode debug thing with F11/F12 > with the following patch which should work for both ps2 and usb > keyboards. > > --- a/sys/src/cmd/aux/kbdfs/kbdfs.c Thu Jul 25 17:44:47 2019 +0200 > +++ b/sys/src/cmd/aux/kbdfs/kbdfs.c Sat Jul 27 11:12:20 2019 +0200 > @@ -43,6 +43,7 @@ > int alt; > int altgr; > int leds; > + int debug; > }; > > struct Qtab { > @@ -337,6 +338,9 @@ > { > Key key; > > + if(scan->debug) > + fprint(2, "kbdputsc %#p sc %x esc1 %d esc2 %d\n", scan, c, scan->esc1, scan->esc2); > + > /* > * e0's is the first of a 2 character sequence, e1 and e2 the first > * of a 3 character sequence (on the safari) > @@ -390,6 +394,13 @@ > if(scan->ctl && scan->alt && key.r == Kdel) > reboot(); > > + if(key.down){ > + if(key.b == (KF|11)) > + scan->debug = 1; > + if(key.b == (KF|12)) > + scan->debug = 0; > + } > + > if(key.b) > send(keychan, &key); > > after applying that change, run mk install in /sys/src/cmd/aux/kbdfs > and then rebuild the kernel (as kbdfs gets included into the kernel image). > > -- > cinap >