Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

N900: ssh -X to maemo loads keyboard map on PC #60

Closed
pavelmachek opened this issue Feb 6, 2018 · 14 comments
Assignees
Labels

Comments

@pavelmachek
Copy link

@pavelmachek pavelmachek commented Feb 6, 2018

...which results in unusable PC where many characters can not be typed. For example numbers. Nice trap.

@parazyd parazyd added the N900 label Feb 6, 2018
@parazyd parazyd self-assigned this Feb 6, 2018
@parazyd

This comment has been minimized.

Copy link
Member

@parazyd parazyd commented Feb 6, 2018

You can temporarily disable it in /etc/profile.d/nokia-n900-keymap.sh. Let us know if you know of a better way to load these keymaps.

#34 is relevant to this.

@parazyd parazyd changed the title N nine hundred: ssh minus X to maemo loads keyboard map on PC N900: ssh -X to maemo loads keyboard map on PC Feb 6, 2018
@pavelmachek

This comment has been minimized.

Copy link
Author

@pavelmachek pavelmachek commented Feb 6, 2018

Thanks for pointer. Better solution would be to have configuration in /etc/X11/xorg.conf.d/40-xkb.conf ; see postmarketOS/pmbootstrap#735 for working example.

@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 23, 2018

@parazyd - shall we see if can fix this soon? It does seem to be rather annoying, and the fix shouldn't be too hard, I think.

@parazyd

This comment has been minimized.

Copy link
Member

@parazyd parazyd commented Feb 24, 2018

I'll try out @pavelmachek 's fix for Xorg.

@MerlijnWajer Does the busybox keymap cause issues as well?

@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 25, 2018

How would I test this? I don't think I follow your question. If you ask if loadkeys() affects my host machine, then that's a no.

@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Feb 26, 2018

This should be configured in /etc/default/keyboard rather than create another xorg.conf.d file. Example:
https://github.com/dderby/debian900/blob/master/install_debian.sh#L264-L267

@parazyd

This comment has been minimized.

Copy link
Member

@parazyd parazyd commented Mar 1, 2018

@dderby It seems to me that is for the console keyboard layout. This issue is about the Xorg one.

@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Mar 1, 2018

@parazyd, I believe it's for both console and Xorg keyboard configuration (sorry, the comment in my script is misleading). It's been a while since I've touched this so I may be mistaken but I am fairly certain that I did not need to configure the X11 keyboard in xorg.conf(.d). The keyboard(5) manual states:

In Debian systems the default keyboard layout is described in /etc/default/keyboard and it is shared between X and the console.

The variables that start with XKB should configure X keyboard extensions. Further reading of that manual suggests that I may not have needed to set the KMAP variable as I had been doing for console keyboard configuration. I'll see if I get a chance to test this tonight and come up with what I think the correct keyboard configuration should be.

dderby added a commit to dderby/arm-sdk that referenced this issue Mar 2, 2018
@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Mar 2, 2018

I've verified that /etc/default/keyboard will configure both X11 and console keymaps so we don't need to have a separate console keymap. I had to run setupcon manually to get the console keyboard to use what was defined in /etc/default/keyboard. It does persist reboots but I don't know if there is already anything that ensures that this set up on first boot. We may need to add /etc/default/console-setup to the root overlay.

@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Mar 12, 2018

The setupcon command requires the console-setup package which is not installed by default. @parazyd, can we place this in extra_pacakges in image-builder/leste.config or do you have a better suggestion?

@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Mar 20, 2018

The setupcon command is called automatically by a postinst script when console-setup is installed. So we just need to install this package ensuring that /etc/default/keyboard from parazyd/arm-sdk#2 is already overlayed at the time the package installed and we'll have a nice, clean configuration of both the X11 and console keymaps.

@dderby

This comment has been minimized.

Copy link
Member

@dderby dderby commented Mar 20, 2018

We can do even better than this. This can be set up automatically in the package config. I'm going to create a patch to detect RX-51 hardware and set XKBMODEL. I'll submit it upstream and hopefully it will land in buster/beowulf.

@dderby

This comment has been minimized.

@parazyd

This comment has been minimized.

Copy link
Member

@parazyd parazyd commented Mar 31, 2018

@dderby We will still have to backport it for Ascii. Should I add console-setup to the default package array then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.