From: Tomas Volf <~@wolfsden.cz>
To: Zack Weinberg <zack@owlfolio.org>
Cc: help-guix@gnu.org
Subject: Re: How do I set kernel command line arguments for all bootloader menu entries?
Date: Tue, 23 Jul 2024 16:25:58 +0200 [thread overview]
Message-ID: <Zp-9diL_AL8D-lKq@ws> (raw)
In-Reply-To: <75ed7503-2b9f-473e-b356-d0d5f773b648@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On 2024-07-23 10:17:51 -0400, Zack Weinberg wrote:
> On Mon, Jul 22, 2024, at 5:33 PM, Tomas Volf wrote:
> > Hi,
> >
> > On 2024-07-22 16:18:41 -0400, Zack Weinberg wrote:
> >> Suppose I want to append "console=ttyS0,115200n8" to every GRUB
> >> bootloader menu entry. I can't figure out how to do that with a
> >> (bootloader-configuration) recipe. The manual talks about writing
> >> *extra* menu entries, but not about tweaking the automatically
> >> generated ones. Is it possible, and if so, how?
> >
> > I believe the kernel-arguments field can be of use. For example I have this in
> > my configuration:
> >
> > (kernel-arguments (delete "quiet"
> > %default-kernel-arguments))
>
> Thanks, but kernel-arguments isn't recognized as a valid field of
> bootloader-configuration.
Ah, sorry, should have been more explicit. In my case it is a field of
operating-system. So in your case try something like
(operating-system
...
(host-name "foo")
...
(kernel-arguments (cons* "console=ttyS0,115200n8"
%default-kernel-arguments))
...)
From there it should automatically propagate into all auto-generated boot menu
entries.
Hope it helps this time,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-23 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 20:18 How do I set kernel command line arguments for all bootloader menu entries? Zack Weinberg
2024-07-22 21:33 ` Tomas Volf
2024-07-23 14:17 ` Zack Weinberg
2024-07-23 14:25 ` Tomas Volf [this message]
2024-07-23 14:46 ` Zack Weinberg
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=Zp-9diL_AL8D-lKq@ws \
--to=~@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=zack@owlfolio.org \
/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).