Broken KVM keyboard mapping

[bthebaudeau]

Using an fr-fr keyboard with MeshCommander v0.8.2, some keys are correctly mapped, some other keys are mapped as en-us, some other keys are mapped otherwise, and some keys are not mapped at all. I get the same behavior whether the AMT host is running the BIOS UI, Windows 10 Pro with an fr-fr keyboard or Ubuntu with an en-us mapping.

I don't know if this can help, but with MDTK, in order to get an acceptable keyboard mapping, I had to select "Japanese keyboard" in the connection options of UltraVNC and to switch my Windows keyboard mapping to en-us for the KVM window.

Here is the exact mapping that I get with MeshCommander v0.8.2:

• a-z → a-z (no issues)
• ² → '
• Shift+² → "
• &é"'(-è_çà → 1234567890 (as if en-us)
• 1234567890 → !@#$%^&*() (as if en-us)
• )°=+^¨$£ù%*µ,?;.:/ → [{=+]};:`~\|,<.>/?
• !§<> and AltGr combinations → not mapped at all
• numpad: no issues

AMT host: Lenovo ThinkServer TS140, BIOS version: FBKTD9AUS, Intel ME v9.1.45 activated in Admin Control Mode (ACM). Client: Windows 10 Pro 1909, 64-bit, fully updated, RLE8.

MeshCommander was installed using the MSI installer.

Tell me if you need more information.

[bthebaudeau]

The mapping above was for Ubuntu as the host OS with an en-us mapping.

With Windows Server 2019 Standard and an fr-fr mapping, I get:

• azertyuiop → qwertyuiop
• qsdfghjklmM → asdfghjkl,?
• wxcvbn → zxcvbn
• ² → ù
• Shift+² → %
• &é"'(-è_çà → &é"'(-è_çà (no issues)
• 1234567890 → 1234567890 (no issues)
• ~#{[|`\^@ → ~#{[|`\^@ (no issues)
• )°=+}^¨$£ù*µ,?;.:/ → ^"=+}$£mM²*µ;.:/!§
• ]¤%!§<> → not mapped at all
• 0.123456789/*-+ (numpad) → à:&é"'(-è_ç!8)+

[Horgster]

Hi @Ylianst

Confirm we are having the same issue with MeshCommander version 0.9.0. We are using NO-NB Keyboard Layout

Some keys are correct and some keys are EN-US keyboard layout.

Is this something that you please can fix ?

Best Regards Horgster

[trondkk]

I can confirm that we are also experiencing issues with norwegian keyboard layout.

Regards Trond

[Horgster]

Hi again!

This is how the Norwegian Keyboard Layout looks like including scancodes

I have testet all the keys of the keyboard in this is the result:

Keyboard → Result in Remote Desktop screen 1234567890 → 1234567890 (no issues) abcdefghjiklmnopqrstuvwxyz → abcdefghjiklmnopqrstuvwxyz (no issues) øæå → |æ (should have been øæå) ØÆÅ → §Æ (should have been ØÆÅ) | → ' (not working) \ → å (not working)
<> → not mapped at all + → \ (not working)

Keyboard combination = how it should be → Result in Remote Desktop screen ALTGR+2 = @ → @ (working) SHIFT+§ = § → * (not working) SHIFT+1234567890 = !"#¤%&/()= → !"#¤%&/()= (working) SHIFT+> = > → not mapped at all ALTGR+7890 = {[]} → {[]} (working)

SHIFT+ = ? → ``` (not working) SHIFT+\ = ` → Å (not working)

Please fix this as Norwegians can't us this product if this is not fixed.

[Monsurd]

Great tool @Ylianst.

Got same issues as Horgster posted with the Norwegian keyboard.

Very much appricated if you could look into the issue.

Keep up the good work!

brgds Monsurd

[Horgster]

Hi @Ylianst

Any status or progress here?

Cheers Thanks!

[rgl]

@Ylianst should this issue be opened somewhere else? Do you have any pointer about this? How can we help?

[ensingerphilipp]

Can confirm - Using German keyboard and set german keyboard layout in ubuntu. Is broken have to use it like an englisch keyboard and some keys like / dont work altogether