[syslinux] Syslinux EFI + TFTPBOOT Support

[Gene Cumm]

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?