From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#30467: GuixSD fails to display login prompt on headless server Date: Thu, 15 Feb 2018 16:54:55 +0100 Message-ID: <20180215165455.09a9efa3@scratchpost.org> References: <868tbu9u0r.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39752) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1emLtF-000413-L4 for bug-guix@gnu.org; Thu, 15 Feb 2018 10:56:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1emLtC-0005up-7z for bug-guix@gnu.org; Thu, 15 Feb 2018 10:56:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37103) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1emLtC-0005uj-2k for bug-guix@gnu.org; Thu, 15 Feb 2018 10:56:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1emLtB-0000GF-Md for bug-guix@gnu.org; Thu, 15 Feb 2018 10:56:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <868tbu9u0r.fsf@gmail.com> 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: George myglc2 Clemmer Cc: 30467@debbugs.gnu.org Hi George, Leo added a comment to the services/base.scm code: ;;; FIXME This doesn't work as expected. According to agetty(8), if this option ;;; is not passed, then the default is 'auto'. However, in my tests, when that ;;; option is selected, agetty never presents the login prompt, and the ;;; term-ttyS0 service respawns every few seconds. #$@(if local-line #~(#$(match local-line ('auto "--local-line=auto") ('always "--local-line=always") ('never "-local-line=never"))) #~()) So try specifying local-line ? Also, can you try updating again? I've pushed some agetty consolidation to guix-master (only) today. Also, you have (kernel-arguments '("console=ttyS1,115200")) AND (agetty-service (agetty-configuration (tty "ttyS1") (baud-rate "115200"))) . Starting today, the second one will be automatically configured by %base-services. I wonder whether we can provide a nice upgrade path for users. Can be automatically remove duplicates from the service definitions? Can we warn about duplicates in the final service definition? Does agetty lock the serial port? Or does it happily start two gettys? The latter would be bad. So please keep your config the same and reconfigure and let's see what happens. In the long run please remove your agetty-service, it should automatically appear (it recovers the settings from the "console" kernel-argument). If it doesn't work you can always return to the previous generation so no worries!