Hide Forgot
in /etc/sysconfig/keyboard I have the line KEYTABLE=uk This fails to map to a UK keyboard. (not in X) Also X key maps are OK the "|" (pipe) symbol comes out as a ">" The "|" (pipe) symbol is found on the shift-# (shift-hash) key
I'm having this problem also, but only on systems that I've upgraded from 5.2. With fresh installs the key mapping is correct.
clemons@atm.ox.ac.uk, could you see if there is a difference in the KEYTABLE entry in /etc/sysconfig/keyboard on your 5.2 vs. 6.0 systems? There is only one uk keytable installed on a 6.0 system. Thanks!
closed, lack of input
Has anyone worked out why the keytable fails yet? I am still waiting for a solution. Is there any extra info I can supply? I upgraded from 5.0 to 5.2 to 6.0 Please just tell me what file is missing/wrongly configured.
1) does this happen only in X, or also at the console? 2) if it happens in both, what happens if you type 'loadkeys uk'?
I found out what has gone wrong. I ran "rpm --verify -a" after reading other bug lists, and found that the upgrade from 5.2 to 6.0 does not upgrade all the files properly, some files are deleted and not replaced. After searching the output, I found that the following files were missing, together with 100s more. /etc/rc.d/rc2.d/S75keytable /etc/rc.d/rc3.d/S75keytable /etc/rc.d/rc5.d/S75keytable Once I did a symbolic link from /etc/rc.d/init.d/keytable to these files and rebooted, all is now fine. 1) X in fine, console bad. 2) loadkeys uk works fine. Obviously, some files got deleted during the upgrade. Has REDHAT found out which packages they are, and told us users how to fix them? If so, can someone please tell me.
OK, you ran into an RPM problem. The 'kbd' package was replaced with the console-tools package, however, this (because of an RPM problem) caused the keytable links to be removed. Once they were remade, is the keyboard working OK in the console?
The packages are fine, the problem was in rpm itself. Install the errata rpm-3.0.2 release, and reinstall the rpm's with missing files. Please reopen this bug if the above does not remedy your problem.