similar to: recompiling syslinux 4.00pre31

Hi, Is anyone compiled a new pxelinux.0 with syslinux code 4.03? right now, I got a error in compiling this version code, objdump -h pxelinux.elf > pxelinux.sec perl lstadjust.pl pxelinux.lsr pxelinux.sec pxelinux.lst objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore pxelinux.raw pxelinux.bin ../lzo/prepcore: pxelinux.raw: output too big (30197, max 0) make[1]: *** [pxelinux.bin]

Sorry Gene, I got the version of binutils is 2.17. I download the latest Binutils to make the *objdump* and *objcopy*. with both of these utilities to create new pxelinux.raw. then, the error message shows me that, objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore pxelinux.raw pxelinux.bin ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0) make[1]: *** [pxelinux.bin] Error 1

Hi, I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below. 1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31 LABEL local MENU DEFAULT MENU LABEL Local Boot ... (skip PXE boot) KERNEL chain.c32 APPEND hd0 0 2) works on all three. LABEL local

When i build syslinux.4.02 i get an error like this. I haven't been able to figure out what could be wrong. My gcc version is 4.1.2 and nasm is 2.10.07. Binutils is 2.17.50 I am compiling on xenserver 6.0 Thanks Alakesh 31186 bytes (31 kB) copied, 0.000315067 seconds, 99.0 MB/s nasm -f elf -Ox -g -F dwarf -DDATE_STR="'0x5110300a'" \

> 2015-11-20 8:15 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> > > >> > I don't like the idea of changing "UI" (e.g. command line options that > >> > might be used by some users) without very well-thought reasoning. > >> > >> This is not an UI. AFAIK, this script is not shipped to the user. I > >>

Hi Fi $ rpm --query --file /usr/bin/objcopy binutils-2.25.1-9.fc24.x86_64 $ cd syslinux-7cd1ed6/ $ make bios ... make[3]: Leaving directory '/tmp/syslinux-7cd1ed6/bios/gpxe' make[2]: Leaving directory '/tmp/syslinux-7cd1ed6/bios' make[1]: Leaving directory '/tmp/syslinux-7cd1ed6' $ file bios/core/*.bin bios/core/isolinux.bin: data bios/core/isolinux-debug.bin:

Thanks to debugging information from Thomas Mieslinger, I have root-caused the failure of chain.c32 in Syslinux 3.85. I have put out Syslinux 3.86-pre1 and Syslinux 4.00-pre33 which fix the problem. I expect to release a Syslinux 3.86 relatively shortly (ideally in the next two weeks), with bug fixes only. I would like to figure out if there are other bug fixes we can get in in reasonable time,

The prescription for Boot Info Table says that checksumming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +

Hi All! It''s been a while since I had to ask for help, but I''m back! I''ve finished beta testing my big app and started the transition to production. Everything went fine and the production version was working till I was asked to add another model :-( (Almost a year of beta testing and they only come up with it after moving to production :-D ) I successfully

Hi, The internal Gnu-EFI build gives me grief: * efi/check-gnu-efi.sh: uses realpath, which is not available on my Debian wheezy system. I now use readlink -f, but wonder if it's needed at all. * efi/build-gnu-efi.sh: uses realpath, like above, and also pushd/popd, which is not built into a standard Bourne shell invoked by #!/bin/sh. Again I wonder what's the point of it, as

I think I have tracked this down... it's a bug in GNU make 3.82. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

> Hi, > > Ady wrote: > > During May 2009, a commit by Peter deleted the checksumiso.pl file. The > > commit is: > > core: LZO compress the PM part of the core > > repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 > > And so, since version 4.00, the 'code/checksumiso.pl' file is no longer > > included. > > How is

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at

PXELINUX 3.85 pre13-1-gee43a6e* Copyright (C) 1994-2010 H. Peter Anvin et al !PXE entry point found (we hope) at 9F00:0680 via plan A UNDI code segment at 9F00 len 0AB0 UNDI data segment at 9E00 len 1000 Getting cached packet 01 02 03 My IP address seems to be C0A80168 192.168.1.104 ip=192.168.1.104:192.168.1.99:192.168.1.1:255.255.255.0 TFTP prefix: Trying to load:

> > > > I don't like the idea of changing "UI" (e.g. command line options that > > might be used by some users) without very well-thought reasoning. > > This is not an UI. AFAIK, this script is not shipped to the user. I > don't even see what a user could do with it. > > Well, the Perl script _is_ shipped in the official release, and the

Hi, Ady wrote: > This is a quote from Wonko/Jaclaz, who has also been investigation this > issue and deserves credit for it: > Ok, not that I understand the code, but what *somehow* happens is that > the "embedded" checksum in Isolinux.bin (starting from 4.00) is the > checksum of the WHOLE file (i.e. starting from offset 0 instead of 64) > at a time when: > 1)

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

2015-11-20 8:15 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: >> > >> > I don't like the idea of changing "UI" (e.g. command line options that >> > might be used by some users) without very well-thought reasoning. >> >> This is not an UI. AFAIK, this script is not shipped to the user. I >> don't even see what a user could

2015-11-20 12:50 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> 2015-11-20 8:15 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: >> >> > >> >> > I don't like the idea of changing "UI" (e.g. command line options >> >> > that >> >> > might be used by some users) without very well-thought