From: myglc2 <myglc2@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: How do I make GuixSD boot screens appear on TTY?
Date: Sun, 29 Jan 2017 11:03:11 -0500 [thread overview]
Message-ID: <86k29ddfb4.fsf@gmail.com> (raw)
In-Reply-To: <20170128221418.GA4671@jasmine> (Leo Famulari's message of "Sat, 28 Jan 2017 17:14:19 -0500")
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
prev parent reply other threads:[~2017-01-29 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 15:44 How do I make GuixSD boot screens appear on TTY? myglc2
2017-01-28 22:14 ` Leo Famulari
2017-01-29 16:03 ` myglc2 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k29ddfb4.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).