grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: UEFI/PXE and emulating grub-legacy-uefi-hacked behaviour


From: Vladimir 'φ-coder/phcoder' Serbinenko
Subject: Re: RFC: UEFI/PXE and emulating grub-legacy-uefi-hacked behaviour
Date: Wed, 25 Apr 2012 22:38:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120329 Icedove/10.0.3

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: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]