From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: RFC: UEFI/PXE and emulating grub-legacy-uefi-hacked behaviour
Date: Wed, 25 Apr 2012 22:38:18 +0200 [thread overview]
Message-ID: <4F9860BA.3040701@gmail.com> (raw)
In-Reply-To: <CAHonLzjMk2eHQBRBMNTwCPf92EyDcF7jMp8rWfDLUKDn=PS=BA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 25.04.2012 22:20, Richard Chan wrote:
> Hi Vladimir and list
>
> "The information from EFI network is used only if efinet is embed in
> grub.efi. Otherwise you have to call net_bootp manually"
>
> 1. How do you "embed" efinet.mod into the image so that
> grub_efi_net_config is called?
> I presume you mean somthing different from preload of module?
No, just preload
> ./grub-core/kern/efi/init.c: if (!*device && grub_efi_net_config)
>
> ./grub-core/net/drivers/efi/efinet.c: grub_efi_net_config =
> grub_efi_net_config_real;
>
> The latter function populates the NIC structure from PXE, but in my case, it is
> not being called.
Network config is started only if root is on network. Otherwise network
config is considered unnecessary and skipped.
>
> 2. For net_bootp, I can see the BOOTP request/reply but GRUB will
> timeout setting the IP address. It is as if it doesn't see the BOOTP
> reply.
Do you have full dumps? It's possible GRUB rejects them for some field
mismatch (not all bootp servers are good).
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2012-04-25 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 0:16 RFC: UEFI/PXE and emulating grub-legacy-uefi-hacked behaviour Richard Chan
2012-04-25 8:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-25 15:59 ` Bean
2012-04-25 17:57 ` Seth Goldberg
2012-04-25 20:20 ` Richard Chan
2012-04-25 20:38 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-04-27 5:41 ` Richard Chan
2012-04-25 20:21 ` Bean
2012-04-25 20:39 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-04-26 2:23 ` Bean
2012-04-26 4:10 ` Seth Goldberg
2012-04-26 4:22 ` Bean
2012-04-26 4:59 ` Seth Goldberg
2012-04-26 11:46 ` Bean
2012-04-26 17:10 ` Seth Goldberg
2012-04-27 1:50 ` Bean
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=4F9860BA.3040701@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.