From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: paulepanter@users.sourceforge.net
Subject: Re: How do I find out what module is needed for a command?
Date: Fri, 5 Apr 2013 15:08:08 +0400 [thread overview]
Message-ID: <20130405150808.60383f40@opensuse.site> (raw)
In-Reply-To: <1365157717.20168.24.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
В Fri, 05 Apr 2013 12:28:37 +0200
Paul Menzel <paulepanter@users.sourceforge.net> пишет:
> 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`
>
/usr/lib/grub/i386-pc/command.lst
replace i386-pc with your platform.
> $ 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
>
> 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'.
>
You need to load "normal" module and enter normal mode.
>
> Thanks,
>
> Paul
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-05 11:08 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 [this message]
2013-04-05 11:45 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20130405150808.60383f40@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=paulepanter@users.sourceforge.net \
/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.