You are not logged in.
Hi!
After installing Arch I have a working console based system (no X).
However, my console keymap is broken. Some examples of keypress → output:
F1 → A
F2 → B
F3 → C
I am unable to scroll the console by Shift + Fn + Up Arrow (as Fn + Up Arrow should result in PageUp if I look at the keyboard). I am able to PageUp and PageDown in nano using Fn + Up/Down Arrow.
All the lowercase characters work as intended (it is a Swedish keyboard, but I prefer running it en US layout), and also the arrow keys and colon and semicolon.
I haven't stumbled over this problem before and feeling a bit confused.
How would I go about troubleshooting it? Do I count the keys? Is that enough? And then what?
Photo of keyboard: https://imgur.com/a/PuKUULq
Last edited by tnek (2020-10-12 07:58:34)
Offline
echo $SHELLOnline
It's
/bin/bashOffline
Does it happen w/
env -i bash --noprofile --norc?
Online
Yes, unfortunately.
Personally I don't think it has anything to do with Bash, but the keymap being used. Also this is a newly installed system so something in the Bash profile making it behave this way seems unlikely. But I haven't experienced this before so I might be wrong.
I don't really know which kind of keyboard I am using (except how it looks, from the image in the OP) or how to configure the console accordingly. My personal theory is that the problem has something to do with that?
Last edited by tnek (2020-10-11 17:32:20)
Offline
FWIW that you don't have a console scrollback buffer was changed in one of the recent kernel releases to fix a security issue, so while I'm not sure about the general button detection, you will want to use screen or tmux or so for a properly working scrollback regardless of how your buttons are detected otherwise.
Offline
If we rule the scrollback buffer out, what's the output if you run "od" and press F1/2/3?
Online
FWIW that you don't have a console scrollback buffer was changed in one of the recent kernel releases to fix a security issue, so while I'm not sure about the general button detection, you will want to use screen or tmux or so for a properly working scrollback regardless of how your buttons are detected otherwise.
Super interesting and a bit saddling to learn! I used to have a nice big scroll back buffer.
If we rule the scrollback buffer out, what's the output if you run "od" and press F1/2/3?
First if I press F1, F2, F3 the output is: ^[[[A ^[[[B ^[[[C
Then if I then press Ctrl + D twice (one time didn't work, hm) the output is: 0000000 055433 040533 055433 041133 041533 0000014
Offline
First if I press F1, F2, F3 the output is: ^[[[A ^[[[B ^[[[C
That's normal, do the F-keys work as expected in eg. mc?
Online
Same issue here, framebuffer scrollback with fn+shift up/down does not work anymore on my Dell Ultrabook with the recent kernel update. It works on the previous kernels.
Offline
Unless you have any other input issues, that's https://bbs.archlinux.org/viewtopic.php?id=259359 - for the thread at hand we're not sure whether it's limited to that.
Online
First if I press F1, F2, F3 the output is: ^[[[A ^[[[B ^[[[C
That's normal, do the F-keys work as expected in eg. mc?
Yes, I tried in nano. F1 displays help text, F11 displays character position.
Trying it more now (temporarily switched using loadkeys se-latin1 so I easily can compare symbols on physical keyboard to output). Then I guess it works as expected (now that the scroll back buffer is a goner), except for the F keys outputting letters in the console.
That part is weird, but I guess I can live with it. Would be interesting to find out why though.
Trying F2 with od again, comparing it with actually typing a B. I get the same first output in both cases (after closing the input "file" (stdin)), B0000000.
Last edited by tnek (2020-10-11 20:41:36)
Offline
The "^[[[A ^[[[B ^[[[C" are the (escaped) keycodes the kernel generates for the input. Bash doesn't do anything w/ them and just prints the printable part.
You should be able to https://stackoverflow.com/questions/420 … -a-command
Online
Thanks for your help! Much appreciated!
Last edited by tnek (2020-10-12 05:56:24)
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online