From mboxrd@z Thu Jan 1 00:00:00 1970 From: myglc2 Subject: Re: How do I make GuixSD boot screens appear on TTY? Date: Sun, 29 Jan 2017 11:03:11 -0500 Message-ID: <86k29ddfb4.fsf@gmail.com> References: <86ziib6vex.fsf@gmail.com> <20170128221418.GA4671@jasmine> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60328) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXrwl-0008VG-C6 for help-guix@gnu.org; Sun, 29 Jan 2017 11:03:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXrwi-00083s-1z for help-guix@gnu.org; Sun, 29 Jan 2017 11:03:19 -0500 Received: from mail-qk0-x241.google.com ([2607:f8b0:400d:c09::241]:36458) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cXrwh-00082T-TS for help-guix@gnu.org; Sun, 29 Jan 2017 11:03:15 -0500 Received: by mail-qk0-x241.google.com with SMTP id i34so12937194qkh.3 for ; Sun, 29 Jan 2017 08:03:14 -0800 (PST) In-Reply-To: <20170128221418.GA4671@jasmine> (Leo Famulari's message of "Sat, 28 Jan 2017 17:14:19 -0500") 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: Leo Famulari Cc: help-guix@gnu.org On 01/28/2017 at 17:14 Leo Famulari writes: > On Sat, Jan 28, 2017 at 10:44:54AM -0500, myglc2 wrote: >> I am remotely managing headless GuixSD servers using IPMI Serial over >> LAN (SOL). The BIOS, linux messages, and REPL work great. >> >> I also see ... >> >> GRUB loading. >> Welcome to GRUB! >> >> ... but I don't see the GuixSD boot menu ;-( >> >> Is there a way to make GuixSD boot screens appear on TTY? > > One of my machines is unable to show the graphical menu, so I crudely > make it use the console menu with the attached diff. Thank you Leo, this was really helpful. > We should make it smarter so it can be set properly in the OS > declaration, or even choose automatically. Agreed. To provide a basis for that, here are some example configurations that I have verified on an ASROCK MT-C224 IPMI SOL + FreeIPMI. Note: code examples below are substitute for "terminal_output gfxterm" in (gnu system grub) 1) local GRUB console, no GRUB on SOL (the current default) terminal_output gfxterm 2) local GRUB console + VT100 GRUB on SOL serial --unit=0 --speed=115200 terminal_input serial console; terminal_output serial gfxterm 3) local _character_ GRUB console + VT100 GRUB on SOL serial --unit=0 --speed=115200 terminal_input serial console; terminal_output console Note: On the ASROCK, the form that might seem more logical ... terminal_input serial console; terminal_output serial console ... produces undesirable "double lines" on VT100 GRUB on SOL. In terms of adding OS declarations, a simple approach might be to specify the three GRUB configuration options shown above. 1) and 2) probably cover 80% of users. I believe 3) covers your situation. Other options to consider ... A) provide a "GRUB" console argument into which a user can plug GRUB syntax B) provide guile wrappers for the GRUB options A) has in its favor the fact that the grub doc is beautifully written, and it may be more helpful to a user, particularly if their needs are unique, to let them read that and plug in GRUB syntax. - George