On Sun, Feb 01, 2015 at 11:16:59PM +0100, Marco Gamberoni wrote: > I see this same at_keyboard behaviour: working in VirtualBox, delivering > garbage on this real hardware: > - an HP Proliant DL380 Gen5 machine > - with a Compaq PS/2 keyboard italian layout attached > - booted from an iso image made with grub-mkrescue (GRUB) 2.02~beta2-15, > containing a keyboard layout file made with > ckbcomp -model pc105 -layout it | grub-mklayout -o pc105-it.gkb [...] > Having read > > http://web.archive.org/web/20040604041507/http://panda.cs.ndsu.nodak.edu/~achapwes/PICmicro/keyboard/atkeyboard.html > it is obvious what's going on: at_keyboard is using scankey set 1 but the > keyboard is using set 2 and the keyboard controller is not translating.
Sorry for the long delay. Are you still in a position to test this? I just ran across this upstream commit: https://git.savannah.gnu.org/cgit/grub.git/commit/?id=c4b8bec5fee4e30a165fd14a188cf3ab8eccd095 Ignoring the specific hardware mentioned here, it seems like this could be a plausible cause: if GRUB manages to get out of sync with the keyboard controller on the command/data sequence, then it could easily end up confused about which is the current scan code set (see the changes to query_mode in particular) and so end up using the wrong set, or possibly even send a nonsense command somehow. It seems worth testing if you can. -- Colin Watson [cjwat...@debian.org]