Displaying 4 results from an estimated 4 matches for "git87981".
2015 Jul 31
2
EFI: ipxe + syslinux = Failed to read blocks: 0xC
...by doing what?
Some magic in dhcpd.conf:
if option architecture-type = 00:09 {
filename "efi64/syslinux-87020-or.efi";
option pxelinux.pathprefix "http://bla/efi64/";
} elsif option architecture-type = 00:07 {
filename "efi64/ipxe-git87981.efi";
} else {
filename "pxelinux.0";
}
2015 Jul 31
0
EFI: ipxe + syslinux = Failed to read blocks: 0xC
...ng what?
Some magic in dhcpd.conf:
? ? ???if option architecture-type = 00:09 { ? ? ?
???filename "efi64/syslinux-87020-or.efi";
? ? ???option pxelinux.pathprefix "http://bla/efi64/";
? ? ???} elsif option
architecture-type = 00:07 { ? ? ?
???filename "efi64/ipxe-git87981.efi";
???} else { ? ? ?
???filename "pxelinux.0"; ? ?
???}
<<<
I "think" in this case ipxe.efi probably "did not" chainload to pxelinux.efi
When your HP booted arch=07 retrieved ipxe.efi
ipxe.efi performs a new pxe "session" declaring arch=...
2015 Jul 31
2
EFI: ipxe + syslinux = Failed to read blocks: 0xC
...hcpd.conf:
>
> if option architecture-type = 00:09 {
> filename "efi64/syslinux-87020-or.efi";
> option pxelinux.pathprefix "http://bla/efi64/";
> } elsif option
> architecture-type = 00:07 {
> filename "efi64/ipxe-git87981.efi";
> } else {
> filename "pxelinux.0";
> }
> <<<
>
> I "think" in this case ipxe.efi probably "did not" chainload to pxelinux.efi
>
> When your HP booted arch=07 retrieved ipxe.efi
> ipxe.efi performs a new pxe...
2015 Jul 31
5
EFI: ipxe + syslinux = Failed to read blocks: 0xC
Hello dear list,
Using VMware I built a test setup of a server with dhcp, tftp and a
http-server and several pxe-clients with EFI mode turned on. This setup
worked, albeit with the exponential-like decay of IO rate I described
earlier. The work-around of using HTTP works beautifully though.
So it was time for the next step. Migrate this setup to our automated
testing environment that runs