search for: 8702009f

...: stalling on configure with no mapping core_tcp_connect: stalling on configure with no mapping core_tcp_connect: aborting on no mapping tcp close failed: 17 So... this is EFI_NO_MAPPING. Is this very different from the EFI_NO_MEDIA I get when booting via iPXE? Testing with commit 8702009f yields worse results: >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over IPv4. Station IP address is 10.141.166.254 Server IP address is 10.141.255.254 NBP filename is efi64/syslinux-87020-or.ef...

...54 ? ? Filename: efi64/syslinux-87020-debug.efi ? ? tftp://10.X.255.254/efi64/syslinux-87020-debug.efi... ok ? ? efi_rdwr_sectors: read 1 bytes ? ? Failed to read blocks: 0xC In this screenshot the iPXE version is 87981 for commit 87981bb6. The syslinux version here is 87020-or for commit 8702009f plus one extra printf I added, that shows me the error happens on the very first call to efi_rdwr_sectors while reading one byte. This iPXE comes from git://git.kraxel.org/ipxe, but I also tried stock version 1.0.0+ and 2b15ae55 and the newest ae7f22eb2? from git://git.ipxe.org/ipxe.git....

....X.255.254 Filename: efi64/syslinux-87020-debug.efi tftp://10.X.255.254/efi64/syslinux-87020-debug.efi... ok efi_rdwr_sectors: read 1 bytes Failed to read blocks: 0xC In this screenshot the iPXE version is 87981 for commit 87981bb6. The syslinux version here is 87020-or for commit 8702009f plus one extra printf I added, that shows me the error happens on the very first call to efi_rdwr_sectors while reading one byte. This iPXE comes from git://git.kraxel.org/ipxe, but I also tried stock version 1.0.0+ and 2b15ae55 and the newest ae7f22eb2 from git://git.ipxe.org/ipxe.git. For s...

...te wireshark traffic capture would be handy. Are you trying to retrieve anything using http? >>> Now I upgrade the System ROM to version 1.40 and the NIC Firmware to version 2.15.10. The results: Version 6.0.3 just reboots shortly after printing "My IP is %s". Version 8702009f still throws around various exceptions. <<< Does it print "My IP is %s" ?? with that ending %s ? >>> Quoting from a blog post the support site for HP: http://h30507.www3.hp.com/t5/Reality-Check-Server-Insights/Learn-how-to-modify-a-Linux-based-PXE-server-to-sup...

Update: I added my debugging stuff (just a bunch of Print()s and dprintf()s) to the branch without the multinic fix to see if I could find a common cause somewhere. This is based on commit 8702009f. Where I expected the machine to crash again, it just exited back to the bootloader without crashing. So.. somehow adding this debug code solved the crashing problem? Or did it? Then I went back to the latest branch (e466d249) and lo and behold... It did not crash! Not even with the vesamenu.c3...

>>> > On 05-08-15 12:05, Gene Cumm wrote: >> >>? > I recompiled with this in mk/devel.mk <http://devel.mk>: >>? >? GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 >> >> 0x2f8 is a BIOSism. > Is this a problem? The example in the comments said 0x3f8 which is COM1. It means that a BIOS IO port for a UART won't work for EFI.? No