From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Can't log in: blank login screen after reconfigure Date: Wed, 24 Oct 2018 16:19:27 +0200 Message-ID: <87efcf1l74.fsf@gnu.org> References: <87ftx0qv8w.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFK0Z-0006Ok-ES for help-guix@gnu.org; Wed, 24 Oct 2018 10:19:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFK0W-0006qd-7U for help-guix@gnu.org; Wed, 24 Oct 2018 10:19:39 -0400 In-Reply-To: <87ftx0qv8w.fsf@gmail.com> (Chris Marusich's message of "Sat, 20 Oct 2018 12:21:51 -0700") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: help-guix@gnu.org Hello, Chris Marusich skribis: > * I tried pressing control+alt+F2 etc. to switch to different virtual > tty, but it didn't work. The blank screen remained. That sounds bad, like perhaps a KMS (=E2=80=9CKernel Mode Setting=E2=80=9D)= driver issue or something. Is the machine entirely dead at that point, or can you still log in via SSH for instance? > * I examined various system logs, but I could not find anything that > jumped out at me as causing the problem. It's entirely possible I > missed something important, though; I just checked a few places. Do /var/log/messages and /var/log/Xorg.0.log provide any useful hints? As an aside, I=E2=80=99d recommend using QEMU (VirtualBox now requires a sm= all piece of non-free software to be built). QEMU is known to work well with Xorg and all (e.g., =E2=80=98guix system vm gnu/system/example/desktop= .tmpl=E2=80=99). HTH! Ludo=E2=80=99.