search for: dx79to

I have problems with the current syslinux (6.02-pre16) booting CentOS 6.4 64bit via LOCALBOOT 0 with the Intel DX79TO. Also in every previous version there is problem exiting the pxe-stack. It boots again from bios. With LOCALBOOT -1 it works, but that is not the target. Can you please advice or look at that?

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 version there is problem exiting the pxe-stack. It > > boots again from bios. > > What do you mean with "exiting the PXE s...

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? > Also in every previous version there is problem exiting the pxe-stack. It > boots again from bios. What do you mean with "exiting the PXE stack" in this context? -hpa

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. >> >> Did it work in previous versions? >> > > As i have written, in every previous syslinux version it didn't work. > > >>> Also in every previous version there is problem exiting the pxe-stack. It >>> boots again from bios. >> >>...

...s 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 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. Could you be specific on what versions you've tried? 3.86, 4.07 and 4.02 would be the first suggest. >> > Also in every previous version there is...

I know that but is there any progress? -----Urspr?ngliche Nachricht----- Von: H. Peter Anvin [mailto:hpa at zytor.com] Gesendet: Donnerstag, 22. August 2013 13:58 An: Jonas Keidel Cc: For discussion of Syslinux and tftp-hpa Betreff: Re: [syslinux] Intel DX79TO localboot problem with CentOS 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 j...

...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. > >> > >> Did it work in previous versions? > >> > > > > As i have written, in every previous syslinux version it didn't work. > > > > > >>> Also in every previous version there is problem exiting the pxe-stack. > It > >&g...

...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 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. > > Could you be specific on what versions you've tried? 3.86, 4.07 and > 4.02 would be the first suggest. > I've tried...

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> >> >>> >>>

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 that? Or what do you think is broken? > It would be a BIOS problem. There

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 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 >> >

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. > > Jonas Keidel <jonas at jonas-keidel.de> wrote: > >2013/8/5 Jonas Keidel <jonas at

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

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"? > >> > > > > That's right, but due to our pxe environment we need a static entry which > > handles both, booting

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> > >> >> >> 2013/8/6 H. Peter Anvin <hpa at zytor.com> >> >>> On 08/05/2013 11:29 PM, Jonas Keidel wrote: >>> >

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/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"? >> >> >> > >> >