Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: archivista on March 15, 2009, 06:27:24 PM

Title: Non us keyboard does not work
Post by: archivista on March 15, 2009, 06:27:24 PM
I like tinycorelinux very well. But my keyboard is de_CH, does mean I need umlauts and y is there where z should be. So I installed

kmaps.tce and opened a terminal

sudo loadkmap < /usr/share/kmap/fi-latin9.kmap

I don-t geht any error but also not the Swiss German keyboard layout. I also tried other keyboards *i.e. de), but could not get any results. What could the problem?
Title: Re: Non us keyboard does not work
Post by: ^thehatsrule^ on March 15, 2009, 06:37:26 PM
See http://tinycorelinux.com/faq.html#keyboard

You'll probably need to use your own kmap instead of fi-latin9
Title: Re: Non us keyboard does not work
Post by: archivista on March 15, 2009, 07:03:47 PM
Sorry, I did not inform right, I loaded

sudo loadkmap < /usr/share/kmap/de_CH-latin1.kmap

and nothing happened. When I have an ls in /usr/share/kmap/de_*, I get the following:

 4 -rw-r--r--    1 root     root         2823 Jul  5  2008 de-latin1.kmap
 4 -rw-r--r--    1 root     root         2823 Jul  5  2008 de.kmap
 4 -rw-r--r--    1 root     root         2823 Jul  5  2008 de_CH-latin1.kmap
 4 -rw-r--r--    1 root     root         2823 Jul  5  2008 defkeymap.kmap8
 4 -rw-r--r--    1 root     root         2823 Jul  5  2008 defkeymap_V1.0.kmap

So it looks that the keyboard files are there. But when I load one, I see no change in the keyboard. Do I have to reset x server?


Title: Re: Non us keyboard does not work
Post by: archivista on March 15, 2009, 07:17:44 PM
I just got it working. I had to add

loadkmap < /usr/share/kmap/de_CH-latin1.kmap

to /opt/bootlocal.sh and after I rebooted, I got the correct keyboard.

Title: Re: Non us keyboard does not work
Post by: tobiaus on March 16, 2009, 12:41:24 AM
i guess if english isn't your primary language, that faq is confusing. perhaps it ought to say "where 'filatin9.kmap' is the name of your keyboard map."
Title: Re: Non us keyboard does not work
Post by: mikshaw on March 16, 2009, 08:45:21 AM
It appears that the issue was actually overlooking the part that says to either exit to the console before running the command, or run it from bootlocal.sh
Title: Re: Non us keyboard does not work
Post by: nickispeaki on April 18, 2009, 01:10:47 PM
I just got it working. I had to add

loadkmap < /usr/share/kmap/de_CH-latin1.kmap

to /opt/bootlocal.sh and after I rebooted, I got the correct keyboard.
sh: can't open /usr/share/kmap/de_CH-latin1.kmap: no such file
!
 ???   :-\

how it can be?! i read a lot of articles about fbxkb, xkb, russification of Freebsd, linux and it DOESN'T work!
Terrible!
Title: Re: Non us keyboard does not work
Post by: nickispeaki on April 18, 2009, 01:13:55 PM
when i start to use something ua in console:
sudo loadkmap < /usr/share/kmap/ua.kmap
then my X will became BLACK! and windows are without upper bar = without max-minimaze and close buttons and mouse point is cross!

Title: Re: Non us keyboard does not work
Post by: alu on April 20, 2009, 09:17:57 AM
@ nickispeaki

try the following:

1. open a console and write as you did:

sudo loadkmap < /usr/share/kmap/de_CH-latin1.kmap

or

sudo loadkmap < /usr/share/kmap/ua.kmap

2. ctrl+alt+backspace in order to exit to a console;
3. then write at the prompt: startx

it should work; obviously, you have to mount your kmaps.tce in order for tc to find the kmaps file.
Title: Re: Non us keyboard does not work
Post by: nickispeaki on April 20, 2009, 09:50:17 AM
sudo loadkmap < /usr/share/kmap/de_CH-latin1.kmap
2. ctrl+alt+backspace in order to exit to a console;
3. then write at the prompt: startx
it should work; obviously, you have to mount your kmaps.tce in order for tc to find the kmaps file.
thanks, alu!
it works great! But.....
Quote
sudo loadkmap < /usr/share/kmap/ua.kmap
doesn't works! any combinations of ua*.kmap!  ???

may be there is not cyrilic support in tcl? may be is just need to any cyrilic fonts?
and then:
Code: [Select]
tc@box:~$ startx
error opening security policy file /usr/lib//xserver/SecurityPolicy
Could not init font path element /usr/lib/X11/fonts/TTF/, removing from list!
Could not init font path element /usr/lib/X11/fonts/OTF, removing from list!
Could not init font path element /usr/lib/X11/fonts/Type1/, removing from list!
Could not init font path element /usr/lib/X11/fonts/100dpi/, removing from list!
..
..
tc@box:~$ FreeFontPath: FPE "/usr/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing.

what is does mean?
what fonts? where i can get it and then where i must put in?  :-\