From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#25453: Inconsistent keyboard layout affecting encrypted root Date: Tue, 16 Jan 2018 23:05:44 -0800 Message-ID: <87vag1j77b.fsf@gmail.com> References: <87wpdwzuar.fsf@cbaines.net> <87vat9akzj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60700) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ebhnS-0003Je-CX for bug-guix@gnu.org; Wed, 17 Jan 2018 02:06:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ebhnP-00045g-7R for bug-guix@gnu.org; Wed, 17 Jan 2018 02:06:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:51413) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ebhnP-00045Q-3g for bug-guix@gnu.org; Wed, 17 Jan 2018 02:06:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ebhnO-0006av-HZ for bug-guix@gnu.org; Wed, 17 Jan 2018 02:06:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87vat9akzj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 20 Jan 2017 15:01:36 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 25453@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Hi! > > Christopher Baines skribis: > >> I'm using a UK keyboard layout with a computer that I recently installed >> GuixSD on with a encrypted root parition. Immediately after installation >> when I attempted to boot in to the new system for the first time I had >> to enter the passphrase twice, and in doing this, first I had to use the >> keyboard layout under which I carried out the installation (the layout >> which I had intended to use), and then during the early boot stage of >> the system I had to enter the passphrase using a different keyboard >> layout. > > Currently installing a keymap is something done by the =E2=80=98console-k= eymap=E2=80=99 > Shepherd service, which invokes =E2=80=98loadkeys=E2=80=99. That happens= after > =E2=80=9Ccryptsetup --open=E2=80=9D has opened your encrypted root device= , hence the > problem. > > Should we install the keymap right in the initrd, before we=E2=80=99ve mo= unted > the root partition? That would require copying the right keymap(s) and > probably =E2=80=98loadkeys=E2=80=99 to the initrd, which might make it qu= ite big. > > Suggestions? How do others handle it? > > Thanks for your report, > Ludo=E2=80=99. I may be wrong, but keep in mind that Grub and other bootloaders might require their own configuration to set the keyboard layout, also. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlpe9cgACgkQ3UCaFdgi Rp29eg//UlfUyYZkZ/t9LjeIbuJZCUvYtvVdiqdxf+nZS+m0qACMFqDvOJvjkUmL CJ/pATjLV/rVyB7go5QXjkdeRYT29dgrHSWCfdNjc/cuiIHdqZHQvZlJiD48mtt3 GUWu7N68KdObUShwUL4O/rSLY5Hibgid8VbKJMs7H4ZZnpUDx8CrtD3keaeeXB9z 09nGlkEdc5dB5DIh9rsdFhBVM20HeXZwp3NfNM/AKCE5FGRuSKvDpTj8beHT6iVU SpnS3kZmEtB+yK0ndcPbthvn4jDnTaMrKxr0DaVVsgfYOAzfkgPpW5JeMIWP78GT MEHKjecoFIK794MZPfKd7+jlyLKI8m2tVc1l5C1PSZ7gMnneoVHbp3ntusdt98QB tMKKFFfs8vgpGQddPZa3YxbGOrgC6vJqD9OYMVwpBJD5iZg2cXBvVfGsz0vX37P+ IZxRHMg3jV4qA+zIYaE1+DamH3FWMdtPTvD+JlITAy/WyrBZ0iLOZ50dujzoc2Bs b8qFVJNAVv7OJ3HCOxP9guWNZd2/ejFqQ0imdD/DnJZwZvKWDMn0Q+I774oLw2wD R9y/1WP0fO4OUPnylXf9Z8u0gL3looj1B+Wh5VZnpfqUA1yti7+REv0qyl5x2s2R s4sPUJzd0KEYfwmolQX0WyUlk8HJKNlnXMqfsVldvpS+uBCkuTk= =BTf9 -----END PGP SIGNATURE----- --=-=-=--