Hello, would appreciate some help with this. Right from install stage , almost half of alphabet on keyboard come out as numbers. The letter 'o' always comes out as a 6 etc. And yet typing from the on screen keyboard comes out as expected? I have had Deepin and Manjaro previously installed on the same system without any issues at all. Diagnosis and solution appreciated. TIA
Is there anything you’ve already tried? What is your keyboard layout normally set to // supposed to be? Also, could you show the output of the locale command and printenv | grep LANG? This might shed some light if a variable is getting set wrong and telling something else to use the wrong locale for input, not sure.
I’m noticing:
This unit, I believe, calls loadkeys during boot which sets the at least the console keymap, so could be related. Could you share the output of cat /etc/vconsole.conf and sudo systemctl status systemd-vconsole-setup.service as well?
Next I’d try just running sudo systemctl restart systemd-vconsole-setup.service from your terminal, then check if the keyboard behavior has changed, and include anything that command spits outs when you run it.
Also relevant are the systemd logs. I’m not really a journalctl wizard so this may not be the optimum way to do this, but the output of journalctl -b --no-pager --no-hostname | grep vconsole will show all the logs since last boot containing the relevant vconsole. If it’s long, put it in a pastebin instead of pasting it into the thread.
For future reference, do try to do a little digging before coming to the forums with an issue. I personally wanted to show a lil hospitality first but generally speaking just describing an issue and dropping your inxi with no indication that you’ve done anything is going to get you hit with significantly less helpful comments than this one. No shade, just saying - it’s the nature of both small Linux communities and Arch-based communities.
Thanks very much for your response. Having explored many of your suggestions, it seems that changing language and locale was just close to impossible.
I tried the dragonized version for a minute, but even at setup, it was impossible to enter user name or password due to garbled text.
I am typing this in Garuda Cinnamon ,having done the following differently.
At partition stage of install I now chose Erase disk and not manual partition. Also, I have not used a separate home partition. A step or two later I have selected en_US_utf8 ignoring suggestions for my locale/language (en_NG).
You certainly helped point me in the right direction. What I wanted was a problem free installation not one i had to start hacking at from the get go.
Oh, that's odd. I guess since you've kinda sorted it out it may not be relevant, but did you save any of those outputs I mentioned? I'm curious if they could shed a little light on what was going on.
The partitioning schema shouldn't have an impact on this, but I will say that one of the really great things about Garuda is the default filesystem configuration.
I get the desire to not want to, but if you did want to hack at it a little more for future reference/posterity - What is your physical keyboard layout? (if you're not sure, instead: is it QWERTY or something else, and what is the currency symbol and its positioning?) and, what did you select on the 1st, 2nd, and 3rd installer screens (system language, timezone, and keyboard layout) with each install?
If nothing else, glad I could at least point ya in the right direction!
Check your laptop user manual and don’t make us looking for a ghost, please.
This is a familiar case where a laptop does not have a separate full numpad, so there is a key combination or other way to swap this behavior.
PEBKAC issue.
```
FONT=ter-220n
KEYMAP=ng
systemd-vconsole-setup.service - Setup Virtual Console
Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static)
Active: failed (Result: exit-code) since Thu 2022-04-14 16:14:38 WAT; 19min ago
Docs: man:systemd-vconsole-setup.service(8)
man:vconsole.conf(5)
Process: 276 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=1/FAILURE)
Main PID: 276 (code=exited, status=1/FAILURE)
CPU: 21ms
sudo systemctl restart systemd-vconsole-setup.service
Job for systemd-vconsole-setup.service failed because the control process exited with error code.
```
It is a US Keyboard layout but on most distributions even when locale comes up as en_NG it is still basically the US layout and in most distributions it has never been a problem. Even changing locale.conf did not have any effect, and I saw a couple of posts indicating as much.
The service fails normally, since the keymap you set does not exist.
(Arch)Linux is not exactly responsible for the correctness of the used keymap, because they just use international standards. The user (in need) has to declare/find and set the desired proper keymap, which will work as designed (following ISO standards).
For keyboard layout, if your keyboard is an US/English standard keyboard, you should use en_US.UTF-8 for Xorg/GUI and us for console. For a secondary keyboard layout, follow Archwiki instructions to (first) find your proper one and then apply it as instructed in Archwiki.
Use localectl for Xorg kbd layout and, for console, add KEYMAP_TOGGLE= in vconsole.conf.
Read manuals and wikis for all the above. Sometimes GUI installers are not as smart as they declare they are.
If you have difficulties, post what you have done and failed and any questions.
I believe the issue arises from accepting the defaults associated with my Location/TZ setting (Lagos,NG). Accepting those defaults causes problems I have not experienced in Manjaro, Deepin or Mint.
