Re: [9fans] Trying to make 9front work on QWERTZ

Re: [9fans] Trying to make 9front work on QWERTZ

[Jonas Amoson]

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

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?

.


[-- Attachment #2: Type: text/html, Size: 2031 bytes --]

Re: [9fans] Trying to make 9front work on QWERTZ

[Jens K. Loewe]

> 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 <cinap_lenrek@felloff.net>:
>
> 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
>

Re: [9fans] Trying to make 9front work on QWERTZ

[cinap_lenrek]

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

Re: [9fans] Trying to make 9front work on QWERTZ

[Jens K. Loewe]

Does 9front also do that?

> Am 26.07.2019 um 07:59 schrieb Lucio De Re <lucio.dere@gmail.com>:
>
>> On 7/25/19, Jens K. Loewe <jens.k.loewe@gmail.com> 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.
>

Re: [9fans] Trying to make 9front work on QWERTZ

[Lucio De Re]

On 7/25/19, Jens K. Loewe <jens.k.loewe@gmail.com> 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.

Re: [9fans] Trying to make 9front work on QWERTZ

[Jens K. Loewe]

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

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 to 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ópez <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 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 <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?
>>> 

[-- Attachment #2: Type: text/html, Size: 2894 bytes --]

Re: [9fans] Trying to make 9front work on QWERTZ

[Rodrigo G. López]

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

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 <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?
>>
>>

[-- Attachment #2: Type: text/html, Size: 2210 bytes --]

Re: [9fans] Trying to make 9front work on QWERTZ

[Ole-Hjalmar Kristensen]

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

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 <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?
>
>

[-- Attachment #2: Type: text/html, Size: 1142 bytes --]

[9fans] Trying to make 9front work on QWERTZ

[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?