All, I have scoured the mailing list and the web and I can't seem to find any help on this issue. I am attempting to have EFI machines boot over PXE and then load various Linux Live distributions. I have a similar setup over standard BIOS machines and all is well on that end. First I have tried SysLinux 6.0, 6.1, and 6.2 for various EFI enabled machines and thus far 6.1 gets me to the furthest point. My clients successfully boot over PXE and grab the relevant files over TFTP to get me to a simple selection menu. I have watched the interaction in the TFTP logs and over tcpdump. All is well until I attempt to select a kernel (Ubuntu 13.10 vmlinuz.efi). Regardless of where the kernel is located, nested in a sub-directory of /tftpboot or not, the client always responds with "File not found." It is odd since all other support files (syslinux64.efi, pxelinux.cfg/default, vesamenu.c32, and so forth) have no issue. Any guidance or assistance is greatly appreciated. Adam
On Wed, Dec 4, 2013 at 12:02 PM, Adam Sawyer <acsawyer at gmail.com> wrote:> All, > > I have scoured the mailing list and the web and I can't seem to find any > help on this issue. I am attempting to have EFI machines boot over PXE and > then load various Linux Live distributions. I have a similar setup over > standard BIOS machines and all is well on that end. First I have tried > SysLinux 6.0, 6.1, and 6.2 for various EFI enabled machines and thus far > 6.1 gets me to the furthest point. > > My clients successfully boot over PXE and grab the relevant files over TFTP > to get me to a simple selection menu. I have watched the interaction in the > TFTP logs and over tcpdump. All is well until I attempt to select a kernel > (Ubuntu 13.10 vmlinuz.efi). Regardless of where the kernel is located, > nested in a sub-directory of /tftpboot or not, the client always responds > with "File not found." It is odd since all other support files > (syslinux64.efi, pxelinux.cfg/default, vesamenu.c32, and so forth) have no > issue.What exact kernel? This almost sounds familiar to some errors I've seen in the last two months. What do you observe in the packet capture? -- -Gene
On 12/04/2013 02:58 PM, Gene Cumm wrote:> On Wed, Dec 4, 2013 at 12:02 PM, Adam Sawyer <acsawyer at gmail.com> wrote: >> All, >> >> I have scoured the mailing list and the web and I can't seem to find any >> help on this issue. I am attempting to have EFI machines boot over PXE and >> then load various Linux Live distributions. I have a similar setup over >> standard BIOS machines and all is well on that end. First I have tried >> SysLinux 6.0, 6.1, and 6.2 for various EFI enabled machines and thus far >> 6.1 gets me to the furthest point. >> >> My clients successfully boot over PXE and grab the relevant files over TFTP >> to get me to a simple selection menu. I have watched the interaction in the >> TFTP logs and over tcpdump. All is well until I attempt to select a kernel >> (Ubuntu 13.10 vmlinuz.efi). Regardless of where the kernel is located, >> nested in a sub-directory of /tftpboot or not, the client always responds >> with "File not found." It is odd since all other support files >> (syslinux64.efi, pxelinux.cfg/default, vesamenu.c32, and so forth) have no >> issue. > > What exact kernel? This almost sounds familiar to some errors I've > seen in the last two months. What do you observe in the packet > capture? >I believe this is exactly the TFTP port number bug. -hpa