Tiny Core Linux

Tiny Core Extensions => TCE Bugs => Topic started by: SamK on January 14, 2013, 04:56:36 AM

Title: Kmaps Works With Xvesa Fails with Xorg
Post by: SamK on January 14, 2013, 04:56:36 AM
TC v4.7.3

Boot Codes
Code: [Select]
quiet norestore noswap kmap=qwerty/uk showapps pause waitusb=5:UUID="e1250876-d731-45a8-abd9-3e1d402b652f" tce=UUID="e1250876-d731-45a8-abd9-3e1d402b652f"
onboot.lst-xvesa-kmaps-working
Code: [Select]
Xlibs.tcz
Xprogs.tcz
Xvesa.tcz
fltk-1.1.10.tcz
wbar.tcz
flwm_topside.tcz
kmaps.tcz
onboot.lst-xorg-kmaps-failing
Code: [Select]
Xlibs.tcz
Xprogs.tcz
Xorg-7.6.tcz
fltk-1.1.10.tcz
wbar.tcz
flwm_topside.tcz
kmaps.tcz
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: curaga on January 14, 2013, 07:09:51 AM
Yes, Xorg uses its own keymaps, not the console keymap. It defaults to US, you need to set your own in xorg.conf or by using the setxkbmap tool.

See /etc/X11/README.xorg.conf for an example.
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: SamK on January 14, 2013, 11:31:20 AM
Quote from: curaga on January 14, 2013, 07:09:51 AM
Yes, Xorg uses its own keymaps, not the console keymap. It defaults to US, you need to set your own in xorg.conf or by using the setxkbmap tool.

See /etc/X11/README.xorg.conf for an example.
OK, got it thanks.

Rather than create a new xorg.conf, setxkbmap seemed simpler.  With the help of this:
http://www.x.org/releases/X11R7.5/doc/input/XKB-Config.html
a working setup has been added in ~/.X.d. 

Although the official advice is to specify multiple parameters, it works OK with just the country as follows:
Code: [Select]
setxkbmap gbThe country code sets up a British keyboard layout but I could not find a list of country codes for reference.


Edit
Afterthought, might this be a candidate for a boot code in order to allow both Xvesa and Xorg to be specified via boot loader?
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: curaga on January 14, 2013, 02:16:51 PM
Not really, since the names don't match.
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: SamK on January 15, 2013, 02:20:44 AM
Quote from: curaga on January 14, 2013, 02:16:51 PM
Not really, since the names don't match.
I was thinking of an additional code for Xorg.  In this way the different names might be less of an issue.  Also it provides parity for both as each can then be specified as a boot code or started with a command post bootup.

Perhaps something along these lines (examples based on British keyboard)
kmaps=qwerty/uk  (as currently specified)
kbxorg=gb  (suggested for consideration)
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: tinypoodle on January 15, 2013, 02:32:02 AM
I think that might open a more general subject if boot codes could/should refer to extensions (or not).

I wouldn't even know offhand if there are any such at current without first going through whole boot code list :P

If the conclusion was affirmative, sure there would be other candidates as well.
Title: Re: Kmaps Works With Xvesa Fails with Xorg
Post by: SamK on January 15, 2013, 02:57:25 AM
Quote from: tinypoodle on January 15, 2013, 02:32:02 AM
I think that might open a more general subject if boot codes could/should refer to extensions (or not).

I wouldn't even know offhand if there are any such at current without first going through whole boot code list :P
The idea is not intended to be interpreted as establishing policy for Core.

Extensions are required for at least two current boot codes: