Le lundi 23 octobre 2006 23:35, Davide Viti a écrit : > I see; you can use the very same iso and boot using "install > DEBIAN_FRONTEND=newt" and > eventually append also "priority=medium"
I just had to hit Return because it makes use of newt by default. > > BTW, I can help debugging that VT issue if you tell me where > > I shall look into. > > well, it's not yet clear what is going on; > I've noticed the following : > > when loading the keymap using the graphical frontend, you get the > following warnings: > > INFO: kbd_chooser: setting keymap fr-latin9 > WARNING **: : assuming iso-8859-1 cedilla > WARNING **: : assuming iso-8859-1 acute > WARNING **: : assuming iso-8859-1 diaeresis > WARNING **: : assuming iso-8859-1 brokenbar > WARNING **: : assuming iso-8859-1 threequarters > WARNING **: : assuming iso-8859-1 currency > WARNING **: : assuming iso-8859-1 onehalf > WARNING **: : assuming iso-8859-1 onequarter > > and those are printed only if kbd_mode is different from "3" > (K_UNICODE, from <linux/kd.h>); using some extra logs I noticed that > kbd_mode is "2" (K_MEDIUMRAW) when running the graphical frontend > and looking at the directfb sources (inputdrivers/keyboard/keyboard.c) > > if (ioctl( dfb_fbdev->vt->fd, KDSKBMODE, K_MEDIUMRAW ) < 0) { > D_PERROR( "DirectFB/Keyboard: K_MEDIUMRAW failed!\n" ); > > ... > > info->desc.max_keycode = 127; > > I've tried to change that into K_UNICODE and s/127/255/ > > the warnings disappear, but I can't get the accented letters I get on VT2 > (for example "["+"e" give me "ê" when I use fr-latin9 on my italian keyboard) Whenever you change something, you regenerate th udeb then the mini iso and boot it, right? -- Jérôme Marant