Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: floppy on December 26, 2010, 01:24:07 PM
-
Ladies and Gentlemen,
I had a bit time between 2 Christmas lunches and 20cm new snow for making an update at my old good pc.
I updated the 3.3 official release with the 4.4 official release (making a new install) and patched with the RC2 (copied the bzImage as per nice advice in this forum). So, it is now modern (4.4RC2: good mounting menu recognizing in an easy way an USB memory stick etc. fine work!). And added a second HDD.
My PC go now to a first HDD 10GB with antiX Linux on it: it goes into a menu.lst where I have to choose
a) antiX boot (on the same HDD); antiX is for genetical diversity and for my wife not going too mad with the changes from her ubuntu laptop.
b) goes to the second HDD (6GB) with TC4.4RC2 on it.
Both choices runs well (and access via WLAN and LAN).
Unfortunately the kmaps is not setting up correctly anymore.
1. I tried with the boot option kmap=de-latin1 in the TC boot option (I have a german keyboard..).. not working
2. I tried on root in TC4.4 loadkmap </usr/share/qwertz/de-latin1 .. but no effect
If somebody has an Idea how to solve this issue?
In the time, before the solution comes up, I use the How to.. (tip the sign on the german keyboard = appear on the screen)
shift ö = : (: for the vi editor for :quit!)
z = y
y = z
ß = - (- for de-latin1)
- = / (for directories)
/ = = (for kmap=de-latin1)
( = * (for seraching *.* files in the terminal)
? = _ (for wpa_supplicant.conf changes)
\ = +
§ = # (for commenting the lines in menue.lst)
Thanks.
Pascal
-
de-latin1 works for me on TC 3.4. Please update the kmaps extension to the latest, and check the bootcode (it was changed to include the dir, ie "kmap=qwertz/de-latin1").
BTW, there's no 4.4, and 3.4 is the latest version available. 3.4rc2 is an earlier development version.
-
thanks curaga.. the bordeaux 2005 I had made changing the 3.4 in a very nice looking 4.4.. I will try it later with this bootcode.
Does it mean I should re-install the 3.4 official bzImage because I overwrited it with the bzImage from rc2?
The loadkmap </usr/share/qwertz/de-latin1 .. should have been working, too.
-
... I should re-install the 3.4 official bzImage because I overwrited it with the bzImage from rc2?
The 'bzImage' (i.e. our Linux kernel) has AFAIK not changed in the TC 3.x phase. Hence when upgrading from a RC to the official release, or from TC 3.x to TC 3.x+1 release it is sufficient to change the initrd (i.e. 'tinycore.gz').
NOTE: This information is valid at least up to now (i.e. TC 3.4), but would not be correct if the Core team releases an updated kernel during the TC 3.x phase as has happened once IIRC during the TC 2.x phase.
-
de-latin1 works for me on TC 3.4. Please update the kmaps extension to the latest, and check the bootcode (it was changed to include the dir, ie "kmap=qwertz/de-latin1").
BTW, there's no 4.4, and 3.4 is the latest version available. 3.4rc2 is an earlier development version.
Its working fine with the boot code "kmap=qwertz/de-latin1"
Thanks.
Instead of loading kmaps "on boot", it is perhaps better to
put /usr/share/kmap/qwertz/de-latin1.kmap into .filetool.lst
then to include
loadkmap </usr/share/kmap/qwertz/de-latin1.kmap
to
bootlocal.sh?
for a RAM saving and boot speed point of view ?
-
Instead of loading kmaps "on boot", it is perhaps better to
put /usr/share/kmap/qwertz/de-latin1.kmap into .filetool.lst
then to include
loadkmap </usr/share/kmap/qwertz/de-latin1.kmap
to
bootlocal.sh?
for a RAM saving and boot speed point of view ?
Yes, it should be better for both angles, but not that much.
-
I've also been having problems with kmaps since V 3.4. I had all this working in 3.3 by installing kmaps.tcz and setting the bootcode 'kmap=uk'. With 3.4 I cannot get TC to recognise my UK keyboard, whatever I do. I've tried:
- Putting 'loadkmap < /usr/share/kmap/qwerty/uk.kmap' into bootlocal.sh and then rebooting.
- Issuing 'sudo loadkmap < /usr/share/kmap/qwerty/uk.kmap' in a shell.
None of this seems to work.
Anyone know what I'm missing?
-
Issuing 'sudo loadkmap < /usr/share/kmap/qwerty/uk.kmap' in a shell.
Works for me. Is your kmaps extension up to date?
-
Issuing 'sudo loadkmap < /usr/share/kmap/qwerty/uk.kmap' in a shell.
Works for me. Is your kmaps extension up to date?
I'm not sure why that didn't work. However, I posted a slightly different query at http://forum.tinycorelinux.net/index.php?topic=8305.msg44821#msg44821 and the response has shown me how to fix it.