similar to: syslinux 6.01 boot into GPT EFI hdd

So what about this topic? 2013/8/5 Jonas Keidel <jonas at jonas-keidel.de> > 2013/8/5 Matt Fleming <matt at console-pimps.org> > >> On Mon, 05 Aug, at 01:45:27PM, Jonas Keidel wrote: >> > I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in >> > EFI-mode on SSD and booted after that in EFI-PXE with syslinux >> 6.02-pre16.

On Tue, 30 Jul, at 02:51:03PM, Jonas Keidel wrote: > How to boot from syslinux 6.01 over PXE (syslinux.efi) into an EFI > installed GPT system on a hdd? > Via localboot 0 it doesn't work. (no output) > > Also via chain.c32 hd0 1 it doesn't work. > Errormessage: > Can not find MBR magic, treat hdd as raw disk. > Stop booting. chain.c32 doesn't currently

On Fri, 02 Aug, at 07:51:12PM, Jonas Keidel wrote: > So will the patch be applied in 6.02? It's in 6.02-pre16. -- Matt Fleming, Intel Open Source Technology Center

Yes, I think so. The integer really means the same as EFI's ExitBootServices. Matt Fleming <matt at console-pimps.org> wrote: >On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: >> I don't know if there is a meaningful difference between "localboot >-1" >> and "localboot 0" on EFI... they are really two different ways to ask >> the BIOS

On 08/01/2013 01:13 AM, Matt Fleming wrote: > > I've got a patch to support LOCALBOOT -1 on EFI, which will boot the > next entry in the EFI Boot Manager (the thing configured with > efibootmgr), and which I'll commit shortly, but it doesn't support > LOCALBOOT 0. > > I'm not actually convinced that we should support LOCALBOOT 0 under EFI. > Even on BIOS,

Code doesn't just write itself... Jonas Keidel <jonas at jonas-keidel.de> wrote: >I like to reactivate this topic because i don't see any changes at the >last >time... >So what about the topic? > > >2013/8/9 Jonas Keidel <jonas at jonas-keidel.de> > >> 2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> >> >>> >>>

I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in EFI-mode on SSD and booted after that in EFI-PXE with syslinux 6.02-pre16. I do: LOCALBOOT and then the system doesn't start, just the bios-screen is shown up. Any thought about that? 2013/8/5 Matt Fleming <matt at console-pimps.org> > On Fri, 02 Aug, at 07:51:12PM, Jonas Keidel wrote: > > So will the

2013/8/5 Matt Fleming <matt at console-pimps.org> > On Mon, 05 Aug, at 01:45:27PM, Jonas Keidel wrote: > > I've tested it with the ASUS P9D-WS board. I installed Fedora 19 in > > EFI-mode on SSD and booted after that in EFI-PXE with syslinux > 6.02-pre16. > > I do: LOCALBOOT and then the system doesn't start, just the bios-screen > is > > shown up.

2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 05:37 AM, Jonas Keidel wrote: > > I have problems with the current syslinux (6.02-pre16) booting CentOS 6.4 > > 64bit via LOCALBOOT 0 with the Intel DX79TO. > > Did it work in previous versions? > As i have written, in every previous syslinux version it didn't work. > > Also in every previous

2013/8/7 Jonas Keidel <jonas at jonas-keidel.de> > > > 2013/8/6 H. Peter Anvin <hpa at zytor.com> > >> On 08/05/2013 11:29 PM, Jonas Keidel wrote: >> > 2013/8/6 H. Peter Anvin <hpa at zytor.com> >> > >> >> What about "chain.c32 hd1" or "chain.c32 hd1 swap"? >> >> >> > >> >

On 08/05/2013 11:29 PM, Jonas Keidel wrote: > 2013/8/6 H. Peter Anvin <hpa at zytor.com> > >> What about "chain.c32 hd1" or "chain.c32 hd1 swap"? >> > > That's right, but due to our pxe environment we need a static entry which > handles both, booting from first and second hdd if one fails. localboot > does so. > Actually this does

On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: > I don't know if there is a meaningful difference between "localboot -1" > and "localboot 0" on EFI... they are really two different ways to ask > the BIOS to do the same thing. That's fine, it was just that I couldn't figure out what LOCALBOOT 0 should do on EFI. Should we just ignore the integer

So will the patch be applied in 6.02? Am 02.08.2013 17:30 schrieb "H. Peter Anvin" <hpa at zytor.com>: > Yes, I think so. The integer really means the same as EFI's > ExitBootServices. > > Matt Fleming <matt at console-pimps.org> wrote: > >On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: > >> I don't know if there is a meaningful

2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 07:04 AM, Jonas Keidel wrote: > > > > So i've also tried to use chain.c32, but there are also some problems. > > For example FreeBSD doesn't boot with chain.c32, so we've decided to use > > localboot, because it works in 90%, except with that board. > > Maybe you have an idea how to fix

What about "chain.c32 hd1" or "chain.c32 hd1 swap"? Jonas Keidel <jonas at jonas-keidel.de> wrote: >2013/8/5 Jonas Keidel <jonas at jonas-keidel.de> > >> >> >> 2013/8/5 H. Peter Anvin <hpa at zytor.com> >> >>> On 08/05/2013 07:04 AM, Jonas Keidel wrote: >>> >>> > >>> > So i've also

2013/8/6 Gene Cumm <gene.cumm at gmail.com> > On Mon, Aug 5, 2013 at 9:04 AM, Jonas Keidel <jonas at jonas-keidel.de> > wrote: > > 2013/8/5 H. Peter Anvin <hpa at zytor.com> > > > >> On 08/05/2013 05:37 AM, Jonas Keidel wrote: > >> > I have problems with the current syslinux (6.02-pre16) booting CentOS > 6.4 > >> > 64bit via

On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>> Test #2: if you unplug the USB and reboot the system, can you >>> successfully boot directly to the HDD's OS? >>> >> Yes. The only HDD, NTFS, WindowsXP native boot loader ntldr. > > > Let me rephrase my question. It was/is clear that you used to be able > to boot Windows when the first boot

2013/8/5 H. Peter Anvin <hpa at zytor.com> > On 08/05/2013 06:04 AM, Jonas Keidel wrote: > > 2013/8/5 H. Peter Anvin <hpa at zytor.com> > > > >> On 08/05/2013 05:37 AM, Jonas Keidel wrote: > >>> I have problems with the current syslinux (6.02-pre16) booting CentOS > 6.4 > >>> 64bit via LOCALBOOT 0 with the Intel DX79TO. > >>

On Wed, Sep 14, 2016 at 9:06 AM, Gary Stainburn <gary at ringways.co.uk> wrote: > I don't know if this additional information helps. Looking at he efibootmgr > output, is the centos entry pointing to the right place? > > Also, any idea why the update isn't being make permenant? Probably because the specified file wasn't found by the firmware on partition 1, so it

I have just pushed out SYSLINUX 3.10-pre11. This version hopefully should fix Curtis' bug (display file garbage) as well as the NOESCAPE problem. Curtis, Alex and Paul, could you try this version out, please? -hpa