I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when booting from a PXE server in EFI mode. Is this a feature that is currently supported? If not, is there a known time frame for which support will be added? Thanks. -Bryan
On Wed, Mar 5, 2014 at 11:30 AM, Bryan Romine <bromine1027 at gmail.com> wrote:> I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when > booting from a PXE server in EFI mode. Is this a feature that is currently > supported? If not, is there a known time frame for which support will be > added? Thanks.1) 6.03 isn't out yet. 6.03-pre7 is the closest. 2) Yes, I've booted several EFI64 systems wwith x86-64 kernels successfully. Which architecture? Does your kernel match your architecture? -- -Gene
Yes. It is supported. Works just like bios for the most part, except that you must load 32bit kernel with 32bit efi and 64bit kernel with 64bit efi. You must then direct your client to the correct efi and kernel based on it's arch. On Wednesday, March 5, 2014 12:02 PM, Bryan Romine <bromine1027 at gmail.com> wrote: I am currently unable to get Syslinux v6.03 to load kernel + ramdisk when booting from a PXE server in EFI mode. Is this a feature that is currently supported? If not, is there a known time frame for which support will be added? Thanks. -Bryan _______________________________________________ Syslinux mailing list Submissions to Syslinux at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote:> Sorry for the confusion, I am actually using 6.02. It turns out that I was > trying to use the 32-bit efi binary to load 64-bit kernels. I switched to > using "syslinux64.efi" but it hangs during boot, just before loading the > menu. I have not been able to get it to load the menu successfully. Here are > the debug messages:Do you mean efi64/efi/syslinux.efi? Any chance you can try the precompiled binaries from 6.03-pre7 from kernel.org? What exact make and model of your CPU and system/motherboard? What BIOS/firmware version? There's a significant chance you only have EFI32 services so EFI64 syslinux.efi isn't an option. -- -Gene A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing? _______________________________________________ Syslinux mailing list Submissions to Syslinux at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.> Client: > ... > NBP filename is efimenu/syslinux64.efi > NBP filesize is xxxx Bytes > Downloading NBP file... > > Succeed to download NBP file > Getting cached packet > My IP is xxxx > (client hangs here) > > > PXE server log: > Last line shows RRQ for filename "efimenu/ldlinux.e64" > > > It looks like the client is hanging after receiving the ldlinux.e64 file > from the PXE server.> On Wed, Mar 5, 2014 at 2:04 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Wed, Mar 5, 2014 at 11:30 AM, Bryan Romine <bromine1027 at gmail.com> >> wrote: >> > I am currently unable to get Syslinux v6.03 to load kernel + ramdisk >> > when >> > booting from a PXE server in EFI mode. Is this a feature that is >> > currently >> > supported? If not, is there a known time frame for which support will be >> > added? Thanks. >> >> 1) 6.03 isn't out yet. 6.03-pre7 is the closest. >> >> 2) Yes, I've booted several EFI64 systems wwith x86-64 kernels >> successfully. Which architecture? Does your kernel match your >> architecture?
On 2014/3/7 ?? 05:23, Gene Cumm wrote:> On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the >> menu. I have not been able to get it to load the menu successfully. Here are >> the debug messages: > > Do you mean efi64/efi/syslinux.efi? Any chance you can try the > precompiled binaries from 6.03-pre7 from kernel.org? > > What exact make and model of your CPU and system/motherboard? What > BIOS/firmware version? There's a significant chance you only have > EFI32 services so EFI64 syslinux.efi isn't an option. >I'd like to test the syslinux 6.03-pre7 EFI network booting. Is there any doc which I can follow? Basically I can test as this doc describes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html Just need to know how to replace grub with syslinux efi64/syslinux.efi and those c32/e64 modules in the tftpboot dir. Thank you very much. Steven. -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C
On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> wrote:> Yes, I am using efi64/efi/syslinux.efi and > efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from 6.03-pre7 and > it gets farther along but brings up the error "Default boot device missing > or boot failed". Maybe I am not installing all of the required dependencies? > Are there any other files I need to include from the newer 6.03-pre7 build? > > This is a reference board and the BIOS is by InsydeH20. I am pretty sure it > is EFI64 as I have successfully done manual Windows and Linux 64-bit EFI > installs using the DVDs.Intel's CPUs codenamed "Bay Trail" are an excellent example of an x86-64 CPU that commonly only has EFI32 services.> On Thu, Mar 6, 2014 at 3:23 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> >> wrote: >> > Sorry for the confusion, I am actually using 6.02. It turns out that I >> > was >> > trying to use the 32-bit efi binary to load 64-bit kernels. I switched >> > to >> > using "syslinux64.efi" but it hangs during boot, just before loading the >> > menu. I have not been able to get it to load the menu successfully. Here >> > are >> > the debug messages: >> >> Do you mean efi64/efi/syslinux.efi? Any chance you can try the >> precompiled binaries from 6.03-pre7 from kernel.org? >> >> What exact make and model of your CPU and system/motherboard? What >> BIOS/firmware version? There's a significant chance you only have >> EFI32 services so EFI64 syslinux.efi isn't an option.So is the CPU also some item that has no retail availability and perhaps is a next-generation chip? Are there any details that we might be able to use to attempt to reproduce this hardware-specific behavior? -- -Gene A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing?
On Fri, Mar 7, 2014 at 12:34 PM, Bryan Romine <bromine1027 at gmail.com> wrote:> I'm convinced that my Syslinux install may be broken with all the hacking > around and testing I have been doing. If I were to install fresh from the > syslinux-6.03-pre7 archive, what would I need to do. I do not see any > documentation on installation other than "make installer" in > docs/building.txt.EFI* is very different. You only copy files around (just like PXELINUX use). No make should be needed at all.> On Fri, Mar 7, 2014 at 10:53 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> >> Yes, this is an AMD reference platform that is not available in retail. I >> did try a Fujitsu tablet which is UEFI only and I get the same error. Here >> is the tablet I am using: >> http://www.fujitsu.com/fts/products/computing/pc/notebooks-tablets/advanced/stylistic-q572/This sounds like the AMD system won't be so nice to deal with however you should check what EFI type it truly is. The tablet sounds a bit more encouraging. The AMD Z60 CPU sounds like a likely system that would have EFI32 services on an x86-64 CPU. If anyone knows a way to tell this information, it'd be nice to hear. -- -Gene A: Because it messes up the order in which people normally read text, especially the archives of mailing lists. Q: Why is Top-posting such a bad thing?>> On Fri, Mar 7, 2014 at 4:54 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >>> On Thu, Mar 6, 2014 at 6:45 PM, Bryan Romine <bromine1027 at gmail.com> >>> wrote: >>> > Yes, I am using efi64/efi/syslinux.efi and >>> > efi64/com32/elflink/ldlinux/ldlinux.e64. I tried binaries from >>> > 6.03-pre7 and >>> > it gets farther along but brings up the error "Default boot device >>> > missing >>> > or boot failed". Maybe I am not installing all of the required >>> > dependencies? >>> > Are there any other files I need to include from the newer 6.03-pre7 >>> > build? >>> > >>> > This is a reference board and the BIOS is by InsydeH20. I am pretty >>> > sure it >>> > is EFI64 as I have successfully done manual Windows and Linux 64-bit >>> > EFI >>> > installs using the DVDs. >>> >>> Intel's CPUs codenamed "Bay Trail" are an excellent example of an >>> x86-64 CPU that commonly only has EFI32 services. >>> >>> > On Thu, Mar 6, 2014 at 3:23 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> >> >>> >> On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> >>> >> wrote: >>> >> > Sorry for the confusion, I am actually using 6.02. It turns out that >>> >> > I >>> >> > was >>> >> > trying to use the 32-bit efi binary to load 64-bit kernels. I >>> >> > switched >>> >> > to >>> >> > using "syslinux64.efi" but it hangs during boot, just before loading >>> >> > the >>> >> > menu. I have not been able to get it to load the menu successfully. >>> >> > Here >>> >> > are >>> >> > the debug messages: >>> >> >>> >> Do you mean efi64/efi/syslinux.efi? Any chance you can try the >>> >> precompiled binaries from 6.03-pre7 from kernel.org? >>> >> >>> >> What exact make and model of your CPU and system/motherboard? What >>> >> BIOS/firmware version? There's a significant chance you only have >>> >> EFI32 services so EFI64 syslinux.efi isn't an option. >>> >>> So is the CPU also some item that has no retail availability and >>> perhaps is a next-generation chip? Are there any details that we >>> might be able to use to attempt to reproduce this hardware-specific >>> behavior?