Solved Raspbian-powered SBC and # vs £ question

[Leo_B]

Hello gentlemen,

What a wierd puzzle I've got. Played today with the replacement SBC instance, Raspbian-powered one: restored the backup image to memory card, booted up the device and suddenly realized it doesn't accept the password as I use tty1 physical console. So I ssh'ed SBC and logged in successfuly using pretty the same password. A bit later I realized that culprit is probably # sign which appears in password - for some reason, tty1 input interprets Shift-3 shortcut from physical keyboard as £ (pound) sign.



Could someone explain me what happens and how could it be fixed? Is there a way to enter # on tty1?

Just in case, here's the localectl status output:

System Locale: LANG=en_GB.UTF-8
VC Keymap: n/a
X11 Layout: gb
X11 Model: pc105

I know I am supposed to add SBC version as well, but don't know how retrieve the one via CLI. Suggestions?

 

[Leo_B]

Okay, okay, I figured out, switched to en_US locale and changed the keyboard layout to us instead of gb. You can do this either through raspi-config utility or CLI:

sudo localectl set-locale LANG=en_US.UTF-8
sudo localectl set-keymap us

The only thing that appears a total surprise to me is that 3CX SBC distributive seems to come with en_GB.UTF-8 locale set up by default. Hmmmm...

 

[leejor]

Given that it can be used all over the world, and not everyone uses the US keyboard layout, by default, is it that big of a surprise? Thanks for posting your solution, I'm sure it will help someone else.