On 2017-06-10 05:25, Edgar Pettijohn wrote:
>
>
> On 06/09/17 11:18, Tommy Nevtelen wrote:
>> On 2017-06-09 17:46, Tommy Nevtelen wrote:
>>
>>> Hello misc!
>>>
>>> I'm chain-loading pxeboot symlinked to auto_install from ipxe.
>> So I tried to remove ipxe and specify pxeboot directly in the dhcp
>> filename, that worked.
>> But with that said I still don't understand why it works on a VM but not
>> on my hardware.
>>
>> Could somebody clarify what that error means?
>>
> It is an issue with the reply packet from the DHCP server. It delves
> into assembly from there and I'd rather not purposefully give myself a
> headache, so thats the best I can do for you.
>
Thanks for looking!
It helped a little when I read the second forum post here
http://forum.ipxe.org/showthread.php?tid=6989
Quoting Sedorox for completeness:
- .pxe is an image designed to be chain loaded, unloading both the
underlying PXE and UNDI code sections
- .kpxe is a PXE image that keeps UNDI loaded and unloads PXE
- .kkpxe is a PXE image that keeps PXE+UNDI loaded and return to PXE
(instead of int 18h)
Most often, you will want either .pxe, .kkpxe (for when you are
using cached credentials, iirc), and .kkkpxe (usually the last two are
in combination with pxelinux).
I managed to make the error go away by using the undionly.kpxe.
But pxeboot still stops at, just before when it's supposed to get the
network up.
disk: fd0 fd1 hd0+
I will try undionly.kkpxe and that might help since it's used for
pxelinux there might be some similarities.
--
Tommy Nevtelen
