On 26/12/2009 14:52, Anton Zinoviev wrote:
On Fri, Dec 25, 2009 at 09:35:42PM +0100, Eric Valette wrote:
I had a file system witha date set in the future, and thus entered
single mode. I had then a wrong keyboard
This shouldn't be happening so I need you to make few tests in order to
see what went wrong.
OK.
First, to make it clear - I suppose you you entered single user mode
from the corresponding menu item of grup? If you used 'emergency' mode
(option -b at grub menu) then it would be normal for the keyboard to be
leaven unconfigured.
No I entered this mode because the check of the filesystem failed
(S30checkfs in rcS.d that is after S06keyboard-setup)
Second, while you machine is entering single user mode do you see the
text 'Setting preliminary keymap'?
I do not see it but my screen is full of message because of the various
drivers and file system so I may have missed it.
If you don't, do you have a file
/etc/rcS.d/S06keyboard-setup?
ls -l /etc/rcS.d/S06keyboard-setup
lrwxrwxrwx 1 root root 24 avril 11 2009 /etc/rcS.d/S06keyboard-setup ->
../init.d/keyboard-setup
Third, if you see the text 'Setting preliminary keymap', can you test
that the keyboard is still unconfigured? What is the output of the
command
ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz
ls -l /etc/default/keyboard /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root 4776 déc. 26 09:55 /etc/console-setup/cached.kmap.gz
-rw-r--r-- 1 root root 668 déc. 25 21:23 /etc/default/keyboard
Console-setup uses time-stamps in order to determine whether the
keyboard map needs recompiling. If your date/time was incorrect and
cached.kmap.gz seems newer than /etc/default/keyboard then console-setup
will never recompile the keymap. If this is the case, then you need to
remove /etc/console-setup/cached.kmap.gz.
BTW if I hit ctlr D, and let the boot finish the kerboard on the console
are OK. And I alraedy done dpkg-reconfigure console-setup several times
(2X)