On Sat, Sep 24, 2016 at 8:39 PM, Dreamcat4 <dreamc...@gmail.com> wrote:
> > > On Fri, Sep 23, 2016 at 10:39 PM, Christian Nilsson <nik...@gmail.com> > wrote: > >> net0: 34:97:f6:5a:fe:e8 using undionly on UNI-PCI04:00.0 (open) >> [Link:up, TX:0 TXE:1 RX:0 RXE:0] >> [TXE: 1 x "Network unreachable (http://ipxe.org/28086011";] >> Configuring (net0 34:97:f6:5a:fe:e8).................... No >> configuration methods succeeded (http://ipxe.org/040ee119) >> > > Hey liking these instructions for debugging. However I'm not really sure > or understand why the first 2 situations can be a possible reason? > > DHCP fails. >> * Cable problems, or switch having STP or similar causing not getting >> link up before iPXE dhcp times out. >> > > 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. > > Did you check STP settings on the switch ? It is likely that the motherboards efi driver does something differently, or that you are using another port in the switch. > > >> * DHCP server not responding, it does respond to the initial PXE request >> but maybe not to iPXE >> > > The same DHCP server works all fine for the 2 other computers I have > tested in my LAN. > > 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. > > Other one is a Z170 Gigabyte Gaming 3 motherboard. Again, both modes > worked. It has a Killer NIC (qualcomm - atheros). > > Great then we can rule that one out. > This ASUS board has C323 chipset and intel NICs. > > >> * undionly uses the UNDI PXE driver, maybe it is bad for your BIOS. >> > > Ah maybe! Don't really know what to do about it though. > > >> 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. >> > > 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). > > 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 > > >> >> Please remember to follow the recommendation at the error url that is >> printed in the error message (http://ipxe.org/040ee119) >> >> On Fri, Sep 23, 2016 at 5:58 PM, Dreamcat4 <dreamc...@gmail.com> wrote: >> >>> Updated undionly.kpxe to 827dd to the latest version, (aug 30th). >>> Unfortunately its still the same error message. >>> >>> >>> >>> On Fri, Sep 23, 2016 at 4:10 PM, Dreamcat4 <dreamc...@gmail.com> wrote: >>> >>>> Hi, >>>> Got some new hardware today: asus p10s-m motherboard. >>>> >>>> https://www.asus.com/Commercial-Servers-Workstations/P10S-M/ >>>> >>>> >>>> It seems to have intel NICs, and legacy CSM mode. UEFI pxe booting >>>> works OK. However UEFI does not work chaining into boot.salstar.sk, >>>> with some message about bad or incorrect executable format. >>>> >>>> >>>> >>>> As for legacy BIOS mode, here is the output where it fails: >>>> >>>> Intel(R) Boot Agent GE v1.5.72 >>>> Copyright (C) 1997-2014, Intel Corporation >>>> >>>> CLIENT MAC ADDR: 34 97 F6 5A FE E8 GUID: 2098D402 E642 9B81 83D0 >>>> 3497F65AFEE7 >>>> CLIENT IP: 192.168.1.221 MASK: 255.255.0.0 >>>> DHCP IP: 192.168.1.1 PROXY IP: 192.168.69.69 >>>> GATEWAY IP: 192.168.1.1 >>>> >>>> Auto-select: >>>> PC-DOS: Chainload Boot - iPXE >>>> >>>> BOOT SERVER IP: 192.168.69.69 >>>> >>>> PXE->EB: !PXE at 97B4:0070, entry point at 97B4:0106 >>>> UNDI code segment 7EB4:5F30, data segment 787C:6380 (481-531kB) >>>> UNDI device is PCI 04:00.0, type DIX+802.3 >>>> 531kB free base memory after PXE unload >>>> iPXE initialising devices...ok >>>> >>>> >>>> >>>> iPXE 1.0.0+ (2afd6) -- Open Source Network Boot Firmware -- >>>> http://ipxe.org >>>> Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT >>>> >>>> net0: 34:97:f6:5a:fe:e8 using undionly on UNI-PCI04:00.0 (open) >>>> [Link:up, TX:0 TXE:1 RX:0 RXE:0] >>>> [TXE: 1 x "Network unreachable (http://ipxe.org/28086011";] >>>> Configuring (net0 34:97:f6:5a:fe:e8).................... No >>>> configuration methods succeeded (http://ipxe.org/040ee119) >>>> >>>> Press Ctrl+B for iPXE cmdline >>>> >>>> >>>> >>>> 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. >>>> >>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> ipxe-devel mailing list >>> ipxe-devel@lists.ipxe.org >>> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel >>> >>> >> >
_______________________________________________ ipxe-devel mailing list ipxe-devel@lists.ipxe.org https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
