From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How do I find out what module is needed for a command?
Date: Fri, 05 Apr 2013 13:45:00 +0200 [thread overview]
Message-ID: <515EB93C.6040304@gmail.com> (raw)
In-Reply-To: <1365157717.20168.24.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On 05.04.2013 12:28, Paul Menzel wrote:
> Dear GRUB developers,
>
>
> is there a program/script, which module I need to load to get a certain
> command? Using my distribution `/boot/grub/grub.cfg`
>
> $ more /boot/grub/grub.cfg
> […]
> if [ -s $prefix/grubenv ]; then
> load_env
> fi
> set default="1>Debian GNU/Linux, with Linux 3.2.0-4-686-pae"
>
> if [ x"${feature_menuentry_id}" = xy ]; then
> menuentry_id_option="--id"
> else
> menuentry_id_option=""
> fi
> […]
>
> in my GRUB payload for coreboot, created with
>
> src/grub/grub-core $ ../grub-mkimage -d . -c grub.cfg -O i386-coreboot -o ../../grub2.elf memdisk tar ehci ohci uhci usb_keyboard serial all_video terminal -m ../memdisk.tar
>
Don't use -c, put grub.cfg on memdisk and add normal.
> I currently get the following (excerpt) printed to the monitor/serial
> line
>
> Unknown command `if'.
> Unknown command `load_env'.
> Unknown command `fi'.
> Unknown command `if'.
> Unknown command `else'.
> Unknown command `fi'.
>
>
> Thanks,
>
> Paul
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2013-04-05 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:28 How do I find out what module is needed for a command? Paul Menzel
2013-04-05 11:08 ` Andrey Borzenkov
2013-04-05 11:45 ` Vladimir 'φ-coder/phcoder' Serbinenko [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515EB93C.6040304@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.