From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35875: Guix won't boot after installation with fully encrypted disk Date: Fri, 24 May 2019 19:00:48 +0200 Message-ID: <87pno7rdmn.fsf@gnu.org> References: <138779ab-830b-32a9-e64a-e1fccabf90ab@disroot.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:49031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hUDc7-0000v2-4n for bug-guix@gnu.org; Fri, 24 May 2019 13:04:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hUDZ1-0004pB-5E for bug-guix@gnu.org; Fri, 24 May 2019 13:01:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:33671) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hUDZ1-0004p2-0X for bug-guix@gnu.org; Fri, 24 May 2019 13:01:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hUDZ0-00037G-2e for bug-guix@gnu.org; Fri, 24 May 2019 13:01:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <138779ab-830b-32a9-e64a-e1fccabf90ab@disroot.org> (reg@disroot.org's message of "Thu, 23 May 2019 23:41:40 +0200") 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: Reg Cc: 35875@debbugs.gnu.org Hello, Reg skribis: > Note: There was some discussion about this on IRC a couple of weeks ago. > > Guix won't boot on my ThinkPad T430 after an installation with fully encr= ypted disk: > > * First, at the end of the installation, I'm getting the following error = message multiple times: "device-mapper: remove ioctl on cryptroot failed: D= evice or resource busy" These messages are annoying but really harmless. > * On boot, I am being prompted for the encryption key. So far so good. Th= e Grub menu is then displayed and disappears after a few seconds =E2=80=93 = as it should =E2=80=93 after which the computer is stuck on the Grub Weird. Does your compute have an AMD graphics card that could lead the kernel (KMS) to wreck havoc during initialization? Did you have hardware-related problems with other free GNU/Linux distros on this machine before? Thanks, Ludo=E2=80=99.