On 12.08.2015 22:17, Hervé Werner wrote:
As requested I compiled the latest development version of Grub and installed it
on a test laptop. Without any further configuration, Grub works fine, it is
able to boot as intended but the keyboard mapping is us.
I then added the following snippet :
grubdir="`echo "/boot/grub" | sed 's,//*,/,g'`"
grub-kbdcomp -o "${grubdir}"/layout.gkb fr
cat <<EOF
terminal_input at_keyboard
insmod keylayouts
keymap `make_system_path_relative_to_its_root "${grubdir}"/layout.gkb`
EOF
and ran grub-mkconfig which produced the following output in grub.cfg :
terminal_input at_keyboard
insmod keylayouts
keymap /grub/layout.gkb
I checked that the file /boot/grub/layout.gkb (as you have probably figured
out, I have a dedicated partition for Grub's files), it is fine the file has
been successfully created. At last I executed grub-install and rebooted. This
time I'm no longer able to boot : the screen is freezing at Grub's main menu,
the timeout counter isn't even decreasing and I'm not able to enter into Grub's
rescue. Removing the insmod line doesn't change anything.
To be sure - does it hang without at_keyboard as well? keylayouts is
loaded automatically as dependency of at_keyboard anyway, and it is
quite unlikely anything in this module would cause observed effect.
Could you please tell me what I could do to increase debugging output ?
First try to reproduce it without GUI - it is rather hard to see
anything in this case. Just boot grub without any grub.cfg - you will be
left in plain CLI. Now try
insmod at_keyboard
terminal_input at_keyboard
does it still work? If yes, try keymap /grub/layout.gkb; does it still work?
and to be sure - could you send me your gkb file for test?
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
