<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 24, 2016 at 8:39 PM, Dreamcat4 <span dir="ltr"><<a href="mailto:dreamcat4@gmail.com" target="_blank">dreamcat4@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Fri, Sep 23, 2016 at 10:39 PM, Christian Nilsson <span dir="ltr"><<a href="mailto:nikize@gmail.com" target="_blank">nikize@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><span style="font-size:12.8px">net0: 34:97:f6:5a:fe:e8 using undionly on UNI-PCI04:00.0 (open)</span><br style="font-size:12.8px"><span style="font-size:12.8px"> [Link:up, TX:0 TXE:1 RX:0 RXE:0]</span><br style="font-size:12.8px"><span style="font-size:12.8px"> [TXE: 1 x "Network unreachable (</span><a href="http://ipxe.org/28086011" style="font-size:12.8px" target="_blank">http://ipxe.org/28086011</a><span style="font-size:12.8px">"]</span><br style="font-size:12.8px"><span style="font-size:12.8px">Configuring (net0 34:97:f6:5a:fe:e8)............</span><span style="font-size:12.8px"><wbr>........ No configuration methods succeeded (</span><a href="http://ipxe.org/040ee119" style="font-size:12.8px" target="_blank">http://ipxe.org/040ee119</a><span style="font-size:12.8px">)</span><br style="font-size:12.8px"></span></div></blockquote><div><br></div></span><div>Hey liking these instructions for debugging. However I'm not really sure or understand why the first 2 situations can be a possible reason?<br></div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><div><span style="font-size:12.8px">DHCP fails.</span></div></span><div><span style="font-size:12.8px">* Cable problems, or switch having STP or similar causing not getting link up before iPXE dhcp times out.</span></div></div></blockquote><div><br></div></span><div>So if its the cable a problem, then why does it get past that point in EFI mode. It gets the menu and I can boot for example into ubuntu 16.04.1 live CD iso file. Everything else (apart from undionly file vs ipxe.efi) is the same, just execpt I change the motherboard's bios setting (on this device, asus p10s-m) into EFI mode for the intel NIC's pxe boot to identify other with other packet signature, and get given to download the other filename.<br><br></div></div></div></div></blockquote><div>Did you check STP settings on the switch ?</div><div>It is likely that the motherboards efi driver does something differently, or that you are using another port in the switch.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> <br></div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="font-size:12.8px">* DHCP server not responding, it does respond to the initial PXE request but maybe not to iPXE</span></div></div></blockquote><div><br></div></span><div>The same DHCP server works all fine for the 2 other computers I have tested in my LAN.<br><br></div><div>One is a broadwell chip (Gigabyte BRIX) NUC. With a realtek NIC and can work in both mode (efi and pc-bios). Both modes work.<br><br></div><div>Other one is a Z170 Gigabyte Gaming 3 motherboard. Again, both modes worked. It has a Killer NIC (qualcomm - atheros).<br></div><div><br></div></div></div></div></blockquote><div> </div><div>Great then we can rule that one out.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>This ASUS board has C323 chipset and intel NICs.<br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="font-size:12.8px">* undionly uses the UNDI PXE driver, maybe it is bad for your BIOS.</span></div></div></blockquote><div><br></div></span><div>Ah maybe! Don't really know what to do about it though.<br></div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="font-size:12.8px">Only the first of these seems likely, you could try pressing Ctrl-B and then typing out autoboot and pressing enter, and maybe retrying that if it fails the first time.</span></div></div></blockquote><div><br></div></span><div>Yeah sorry I put my new toy away for now. But whenever it flashed up 'Press Ctrl-B' there was never enough time to actually press Ctrl-B. Like only 1 second. Or else it just didnt work (the Ctrl+B).<br><br></div></div></div></div></blockquote><div>1 sec is plenty, however some EFI implementations does not support Ctrl keypresses, as a workaround there is the ESC quickly followed by B hack implemented in iPXE for efi</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div><div class="h5"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Please remember to follow the recommendation at the error url that is printed in the error message (<a href="http://ipxe.org/040ee119" target="_blank">http://ipxe.org/040ee119</a>)</span></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Fri, Sep 23, 2016 at 5:58 PM, Dreamcat4 <span dir="ltr"><<a href="mailto:dreamcat4@gmail.com" target="_blank">dreamcat4@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Updated undionly.kpxe to 827dd to the latest version, (aug 30th). Unfortunately its still the same error message.<br><br><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 23, 2016 at 4:10 PM, Dreamcat4 <span dir="ltr"><<a href="mailto:dreamcat4@gmail.com" target="_blank">dreamcat4@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi,<br></div>Got some new hardware today: asus p10s-m motherboard.<br><br><a href="https://www.asus.com/Commercial-Servers-Workstations/P10S-M/" target="_blank">https://www.asus.com/Commercia<wbr>l-Servers-Workstations/P10S-M/</a><br><br><br></div>It seems to have intel NICs, and legacy CSM mode. UEFI pxe booting works OK. However UEFI does not work chaining into <a href="http://boot.salstar.sk" target="_blank">boot.salstar.sk</a>, with some message about bad or incorrect executable format.<br><br><br><br></div>As for legacy BIOS mode, here is the output where it fails:<br><br>Intel(R) Boot Agent GE v1.5.72<br>Copyright (C) 1997-2014, Intel Corporation<br><br>CLIENT MAC ADDR: 34 97 F6 5A FE E8 GUID: 2098D402 E642 9B81 83D0 3497F65AFEE7<br>CLIENT IP: 192.168.1.221 MASK: 255.255.0.0<br>DHCP IP: 192.168.1.1 PROXY IP: 192.168.69.69<br>GATEWAY IP: 192.168.1.1<br><br>Auto-select:<br> PC-DOS: Chainload Boot - iPXE<br><br>BOOT SERVER IP: 192.168.69.69<br><br>PXE->EB: !PXE at 97B4:0070, entry point at 97B4:0106<br> UNDI code segment 7EB4:5F30, data segment 787C:6380 (481-531kB)<br> UNDI device is PCI 04:00.0, type DIX+802.3<br> 531kB free base memory after PXE unload<br> iPXE initialising devices...ok<br><br><br><br>iPXE 1.0.0+ (2afd6) -- Open Source Network Boot Firmware -- <a href="http://ipxe.org" target="_blank">http://ipxe.org</a><br>Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT<br><br>net0: 34:97:f6:5a:fe:e8 using undionly on UNI-PCI04:00.0 (open)<br> [Link:up, TX:0 TXE:1 RX:0 RXE:0]<br> [TXE: 1 x "Network unreachable (<a href="http://ipxe.org/28086011" target="_blank">http://ipxe.org/28086011</a>"]<br>Configuring (net0 34:97:f6:5a:fe:e8)............<wbr>........ No configuration methods succeeded (<a href="http://ipxe.org/040ee119" target="_blank">http://ipxe.org/040ee119</a>)<br><br>Press Ctrl+B for iPXE cmdline<br><br><br><br></div>Not seem to matter at all whether have plugged into NIC 1 or NIC 2, it always reports the same thing about 'net0', and with same error message. Any help appreciated.<br><div><br><br><br><br></div></div>
</blockquote></div><br></div>
</div></div><br></div></div>______________________________<wbr>_________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" rel="noreferrer" target="_blank">https://lists.ipxe.org/mailman<wbr>/listinfo.cgi/ipxe-devel</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div>