search for: keidel

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

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 "ch...

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

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

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

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

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

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 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 LOCALBOOT 0 with the Intel DX79TO....

.... 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 jonas-keidel.de> > > > >> > >> > >> 2013/8/5 H. Peter Anvin <hpa at zytor.com> > >> > >>> On 08/05/2013 07:04 AM, Jonas Keidel wrote: > >>>...

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

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/6 H. Peter Anvin <hpa at zytor...

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

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

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

Hey, i'm using latest Syslinx 6.01 and try to get the linux kernel booted via tftp in EFI mode. My menu entry: LABEL rescue64 MENU LABEL ^1. 64-Bit Rescue-System - wheezy - 3.10.2 LINUX /rescue/dev-64/vmlinuz INITRD /rescue/dev-64/initramfs.cpio.gz APPEND ... If i select the entry i get: "Bad file number!". Over http it works like a charm. With the pxelinux.0 it works via

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?

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

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.

I've tried the pre version, also the today's pre15. Also not working. I've checked it with wireshark, here is the output: No. Time Source Destination Protocol Length Info 1 0.000000 192.168.3.13 192.168.3.1 TFTP 97 Read Request, File: rescue/dev-64/vmlinuz, Transfer type: octet, tsize\000=0\000,