On Tue, 10 Sep 2019 at 13:25, Felix Jacobi wrote:
>
> Hi Christian,
>
> > My guess is that your server returns something other than what you
> > expect it to - maybe because it is ipxe, and not a browser, and your
> > server detects this. or something similar which "corrupts" the data.
>
> I check
On 10-09-2019 16:25, Felix Jacobi wrote:
> Mailing list subscriber wrote
>
> > The original posting, IIRC, had || at the end of each line in the
> > iPXE script.
> > I did read the || as "or" and did ignore it.
>
> Yeah, that's correct. I don't remember the exact reason why I added the
> || , but
Hi Geert,
> The original posting, IIRC, had || at the end of each line in the
iPXE script.
> I did read the || as "or" and did ignore it.
Yeah, that's correct. I don't remember the exact reason why I added the
|| , but it seems to prevent iPXE from exiting immediately if an error
like the "Exec
On 10-09-2019 15:40, Felix Jacobi wrote:
> Geert wrote:
>
>>
>> So back to Error "Could not select: Exec format error (2e008081)" while
>> loading EFI images via HTTP/TFTP
>>
>> My educated guess is with Christian Nilssons posting from yesterday
>> the file gets damaged during transport
>>
>> Ple
Hi Geert,
>
> So back to Error "Could not select: Exec format error (2e008081)" while
> loading EFI images via HTTP/TFTP
>
> My educated guess is with Christian Nilssons posting from yesterday
> the file gets damaged during transport
>
> Please pursuit this interresting problem
I compiled an
On 10-09-2019 13:36, Felix Jacobi wrote:
> On 10.09.19 at 13:25, Felix Jacobi wrote:
>> > http://ipxe.org/err/2e0080
>
>> Yeah, I will try to research on that point. As already mentioned before
>> there is no such option in the firmware. That either implies that there
>> is no support for secure bo
On 10.09.19 at 13:25, Felix Jacobi wrote:
> Yeah, I will try to research on that point. As already mentioned before
> there is no such option in the firmware. That either implies that there
> is no support for secure boot or secure boot is always active. I am not
> sure if the latter case is even p
Hi Christian,
> My guess is that your server returns something other than what you
> expect it to - maybe because it is ipxe, and not a browser, and your
> server detects this. or something similar which "corrupts" the data.
I checked that the URL is correct, it definitely serves a Linux kernel
i
When building the x86_64 gdbidt with newer gcc it fails recognizing
the segment registers FS/GS being too short for pushq/popq.
arch/x86_64/core/gdbidt.S:109: Error: operand type mismatch for `push'
arch/x86_64/core/gdbidt.S:110: Error: operand type mismatch for `push'
arch/x86_64/core/gdbidt
9 matches
Mail list logo
