I found what seems to be an incompatiblity when GRUB/UEFI bootp is
used with PXE active: you cannot reuse the same IP address. I.e. you
cannot DHCP twice - once by UEFI/PXE and the 2nd time by GRUB/bootp
The 2nd attempt will fail.
Eg., UEFI/PXE has received address 172.31.0.202.
If I try to reuse
On Fri, Apr 27, 2012 at 1:10 AM, Seth Goldberg wrote:
>
>
> On Apr 26, 2012, at 6:46 AM, Bean wrote:
>
>> On Thu, Apr 26, 2012 at 12:59 PM, Seth Goldberg
>> wrote:
>>>
>>>
>>> On Apr 25, 2012, at 11:22 PM, Bean wrote:
>>>
On Thu, Apr 26, 2012 at 12:10 PM, Seth Goldberg
wrote:
>
On Apr 26, 2012, at 6:46 AM, Bean wrote:
> On Thu, Apr 26, 2012 at 12:59 PM, Seth Goldberg
> wrote:
>>
>>
>> On Apr 25, 2012, at 11:22 PM, Bean wrote:
>>
>>> On Thu, Apr 26, 2012 at 12:10 PM, Seth Goldberg
>>> wrote:
How does this work around the issue? I'm not seeing it -- we call
On Thu, Apr 26, 2012 at 12:59 PM, Seth Goldberg
wrote:
>
>
> On Apr 25, 2012, at 11:22 PM, Bean wrote:
>
>> On Thu, Apr 26, 2012 at 12:10 PM, Seth Goldberg
>> wrote:
>>> How does this work around the issue? I'm not seeing it -- we call SNP
>>> directly. We don't go through UDP or any other u
On Apr 25, 2012, at 11:22 PM, Bean wrote:
> On Thu, Apr 26, 2012 at 12:10 PM, Seth Goldberg
> wrote:
>> How does this work around the issue? I'm not seeing it -- we call SNP
>> directly. We don't go through UDP or any other upper layers in efinet.
>> When I did the investigation, I remov
On Thu, Apr 26, 2012 at 12:10 PM, Seth Goldberg
wrote:
> How does this work around the issue? I'm not seeing it -- we call SNP
> directly. We don't go through UDP or any other upper layers in efinet. When
> I did the investigation, I removed ALL other consumers of SNP manually via
> the efi
On Apr 25, 2012, at 7:23 PM, Bean wrote:
> 2012/4/26 Vladimir 'φ-coder/phcoder' Serbinenko :
>> On 25.04.2012 22:21, Bean wrote:
>>> On Thu, Apr 26, 2012 at 1:57 AM, Seth Goldberg
>>> wrote:
Just to chime in here with some data -- I've found numerous UEFI systems'
network functional
2012/4/26 Vladimir 'φ-coder/phcoder' Serbinenko :
> On 25.04.2012 22:21, Bean wrote:
>> On Thu, Apr 26, 2012 at 1:57 AM, Seth Goldberg
>> wrote:
>>> Just to chime in here with some data -- I've found numerous UEFI systems'
>>> network functionality to be buggy (what a shock, right). Specifical
On 25.04.2012 22:21, Bean wrote:
> On Thu, Apr 26, 2012 at 1:57 AM, Seth Goldberg
> wrote:
>> Just to chime in here with some data -- I've found numerous UEFI systems'
>> network functionality to be buggy (what a shock, right). Specifically,
>> using the TFTP APIs allow files to be retrieved,
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 presum
On Thu, Apr 26, 2012 at 1:57 AM, Seth Goldberg wrote:
> Just to chime in here with some data -- I've found numerous UEFI systems'
> network functionality to be buggy (what a shock, right). Specifically, using
> the TFTP APIs allow files to be retrieved, but using GRUB 2's TFTP stack,
> those
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?
Hi,
On Apr 25, 2012, at 8:59 AM, Bean wrote:
> On Wed, Apr 25, 2012 at 8:16 AM, Richard Chan wrote:
>> I am interested in getting UEFI/PXE working using the EFI IP/TFTP
>> stack as hacked versions of grub-legacy (e,g., Fedora 17). Is there
>> any wisdom that the list would like to shed?
>>
>> 1
On Wed, Apr 25, 2012 at 8:16 AM, Richard Chan wrote:
> I am interested in getting UEFI/PXE working using the EFI IP/TFTP
> stack as hacked versions of grub-legacy (e,g., Fedora 17). Is there
> any wisdom that the list would like to shed?
>
> 1. ON EFI platforms grub-legacy directly uses the EFI T
On 25.04.2012 02:16, Richard Chan wrote:
> 5. I have looked at the existing GRUB net+efinet stack. During my
> simple testing I have to be unaable to trigger the code path where
> grub populates the grub_net_structure from the UEFI PXE code. This
> occurs in grub_efi_net_config_real() in
> grub-co
I am interested in getting UEFI/PXE working using the EFI IP/TFTP
stack as hacked versions of grub-legacy (e,g., Fedora 17). Is there
any wisdom that the list would like to shed?
1. ON EFI platforms grub-legacy directly uses the EFI TFTP stack and
not its own i386-pc/TFTP stack.
Network tftp-able
16 matches
Mail list logo
