My native keyboard layout is "dk" (Danish).

I am running Tiny Core Linux in a virtual machine (Bochs). The virtual machine is booting the bootloader where I have the possibility of giving the keyboard map as a argument to the kernel. An example is "kmap=qwerty/dk". If I change the keyboard layout to "us" on the host, I can input the "=" in Bochs' X11 GUI. But then I can't input the "/". If I change keyboard layout after inputting anything, Bochs won't let me input more.

I have to keep using the X11 GUI because using i.e. the SDL GUI, CPU utilization is always 100%.

After booting TCL with the default keymap (as I can't change it in the bootloader), I can change keymap with "loadkmap". It reads from STDIN. The keymap is located in /usr/share/kmaps/qwerty/dk. I figured out I can go to the directory using "cd .." without having to use the key "/". But how do I load it into "loadkmap" without using "|" or "<"?

  • How about figuring out where those keys are in the other layout? – DevSolar Jul 27 '12 at 19:05
  • if you mean dk by other layout, that doesnt work because the linux kernel running inside thinks im using a us layout. if you mean us by other layout, that doesnt work because then im stuck with us layout outside the vm too because bochs crashes if i change it while running – Janus Troelsen Jul 27 '12 at 19:10
  • How about a script someplace: Can you make modifications to the filesystem to write a script to do what you want? Possibly on bootup? – Rich Homolka Jul 27 '12 at 19:10
  • What happens if you press / on the US layout (right next to .)? I don't know Bochs, but wouldn't copy & paste work? – Dennis Jul 27 '12 at 19:11
  • @RichHomolka: good idea, Ill try that if theres no other way to do this. this would mean id have to patch every single tcl image i used... – Janus Troelsen Jul 27 '12 at 19:11

I found out that using the US as host layout and booting with the default layout would get me a machine that worked well unless I pressed arrow left. If I pressed arrow left, backspace would delete whole words at a time. It was very hard for me to configure the network interfaces in this state. To get out of the mode I found out that I only needed to press L_ALT. This situation is not the "crash" I talked about, the crash was related to Bochs I believe, as it happened in the bootloader too. The arrow problem only occurred in the guest Linux.

After figuring out that L_ALT would get me out of this mode, I successfully configured the network interfaces. Now then I saved the VM's state, changed host keyboard to DK, restored state and connected over SSH. I now have access to the VM over SSH with my native layout configured on the host and the native layout being "used" (no layout actually used since it's over SSH and SSH does not send key codes AFAIK), which is pretty much what I wanted.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.