Displaying 20 results from an estimated 9000 matches similar to: "replacing ldlinux.sys"
2013 Feb 04
1
syslinux 4.02 build problem
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'" \
2016 Mar 06
3
Syslinux 6.04-pre1
...
> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \
> -DHEXDATE="0x56dc3c62" \
> -Di386 \
> -I/tmp/syslinux-6.04-pre1/core/ \
> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm
> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \
> -DHEXDATE="0x56dc3c62" \
> -Di386 \
>
2016 Mar 07
2
Syslinux 6.04-pre1
On 06.03.2016 18:23, poma wrote:
> On 06.03.2016 16:47, poma wrote:
>> ...
>>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \
>>> -DHEXDATE="0x56dc3c62" \
>>> -Di386 \
>>> -I/tmp/syslinux-6.04-pre1/core/ \
>>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm
>>>
2015 Feb 09
0
extlinux installer build failed
On Sun, Feb 8, 2015 at 7:49 PM, Alexey Orishko via Syslinux
<syslinux at zytor.com> wrote:
> Hi guys,
>
> I'm have a pure 64-bit system (Intel based). Due to that I can't use 32-bit ELF
> extlinux binary provided in the syslinux-6.03 package.
>
> Unfortunately building extlinux installer failed...
>
> See error below after these command:
> make bios clean
2015 Feb 09
5
extlinux installer build failed
Hi guys,
I'm have a pure 64-bit system (Intel based). Due to that I can't use 32-bit ELF
extlinux binary provided in the syslinux-6.03 package.
Unfortunately building extlinux installer failed...
See error below after these command:
make bios clean
make bios (failed)
...
ar cq liblpxelinux.a rawcon.o pxeboot.o pxelinux-c.o
fs/pxe/dhcp_option.o fs/pxe/pxe.o fs/pxe/tftp.o
2015 Feb 09
1
extlinux installer build failed
On Sun, 8 Feb 2015 20:21:58 -0500
Gene Cumm via Syslinux <syslinux at zytor.com> wrote:
> On Sun, Feb 8, 2015 at 7:49 PM, Alexey Orishko via Syslinux
> <syslinux at zytor.com> wrote:
> > Hi guys,
> >
> > I'm have a pure 64-bit system (Intel based). Due to that I can't
> > use 32-bit ELF extlinux binary provided in the syslinux-6.03
> >
2012 Nov 02
10
[PATCH 0/9] elflink fixes
From: Matt Fleming <matt.fleming at intel.com>
Here are the patches that I've got queued up based on the very helpful
feedback I received from people testing Syslinux 5.00-pre9. Unless
anyone has any concerns these will make it into Syslinux 5.00-pre10.
Matt Fleming (9):
pxe: Don't call open_config() from the pxe core
ldlinux: Print a warning if no config file is found
2018 Jan 02
3
Structure of VBR in FAT32?
Thanks for the response, Gene. Much appreciated. I didn't get all of it;
mind if I follow on below?
ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code.
>
Makes sense.
> > 1. Where is the code that goes in the VBR or Block Group 0 padding?
>
> diskboot.inc.
>
which appears to be included in diskstart.inc. I will have to dig in and
see how this all gets
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
On Wed, Oct 07, 2015 at 05:58:51PM -0500, Clements, James wrote:
> James Clement
> > Geert Stappers
> > > On Wed, Oct 07, 2015 at 05:06:41PM -0500, Clements, James wrote:
> > > > The screen displays the following:
> > > >
> > > > PXE Network Boot using IPv4
> > > > ....
> > > > Station IP address is 192.168.205.50
2018 Jan 03
2
Structure of VBR in FAT32?
Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in
the loop. Appreciated.
> which appears to be included in diskstart.inc. I will have to dig in and
> see
> > how this all gets compiled (pointers always appreciated :-) ).
>
> Yes.
>
Is the build process documented? Or am I just going to have to plod through
the makefiles?
> As Ady said,
2013 Jul 26
2
[PATCH 1/1] core: Add a check at ldlinux.sys build time.
On 07/26/2013 01:36 PM, Raphael S Carvalho wrote:
>
> Bootsector is installed into the 0-512 range, whereas 2 copies of ADV
> into (65536 - 2 * ADV_SIZE).
> Then basically ldlinux.sys must fit between the bootsector and two
> copies of ADV whose size may vary.
>
> The range 0-64k is laid out something like this, right?!
> [0](bootsector)[512](ldlinux.sys)[65536 - 2 *
2012 Dec 06
1
Proposal for Chain-Loadable LDLINUX.SYS
A proposal for changing the LDLINUX.SYS layout and flow:
The current situation ("old style"):
ldlinux.bin's physical layout:
- VBR
- 512 bytes of padding (never lands in memory)
- ldlinux.sys, which is:
- Sect1 code (494 bytes, leaving enough room for at least one
extent, as planned)
- Extent pointer patch space (1920 bytes)
- The rest of the code
2013 Sep 30
2
[PATCH v2] core: Check size of ldlinux.sys at building time.
From: Raphael S. Carvalho <raphael.scarv at gmail.com>
v2: Extract ADV_SIZE automatically from libinstaller/setadv.h.
Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit.
ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary.
Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit).
Certain file systems
2013 Jul 24
2
[PATCH 1/1] core: Add a check at ldlinux.sys build time.
Check if ldlinux.sys is larger than 64k at build time.
Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com>
---
core/Makefile | 5 +++--
core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++
2 files changed, 34 insertions(+), 2 deletions(-)
create mode 100644 core/ldlinux_limit.pl
diff --git a/core/Makefile b/core/Makefile
index f795a5c..00de331 100644
---
2013 Aug 31
4
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit.
ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary.
Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512.
Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys being installed on the 0-64k range,
thus it can't exceed the limit,
2013 Jul 26
2
[PATCH 1/1] core: Add a check at ldlinux.sys build time.
On 07/26/2013 08:10 AM, Matt Fleming wrote:
> On Wed, 24 Jul, at 08:05:16AM, Raphael S.Carvalho wrote:
>> Check if ldlinux.sys is larger than 64k at build time.
>>
>> Signed-off-by: Raphael S.Carvalho <raphael.scarv at gmail.com>
>> ---
>> core/Makefile | 5 +++--
>> core/ldlinux_limit.pl | 31 +++++++++++++++++++++++++++++++
>> 2
2014 May 27
2
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
> On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote:
> >
> >
> > While going throug old posts found:
> >
> > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho:
> > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds
> the limit.
> > > ldlinux.sys must fit between the bootsector and
2012 May 17
2
Manually copy over ldlinux.sys
Hello,
I am working on a remote upgrade that will utilize a squashfs to boot
off the hard drive.
I have everything worked out and functioning, except I see installing
extlinux as an unecesarry step. The only thing I use the command for
is to install the ldlinux.sys file to the /boot/extlinux/ folder.
The rest of it is just a file copy.
What manual step can I take to avoid the installation of
2014 May 25
4
[PATCH 1/1] core: Check if ldlinux.sys exceeds the limit at its building time.
On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote:
>
>
> While going throug old posts found:
>
> Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho:
> > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds
the limit.
> > ldlinux.sys must fit between the bootsector and two copies of ADV whose
size may vary.
>
2005 May 07
1
SYSLINUX: Cannot read ldlinux.sys
My question is the following:
I need to "syslinux" a harddisk(partition-type is FAT16, size is about
100mb). I created a Dos-Bootdisk with WindowsXP and removed everything
except command.com, io.sys and msdos.sys. Then I copied syslinux.com
(and even ldlinux.sys) to the disk but nothing seems to help, I always
get the "SYSLINUX: Cannot read ldlinux.sys"-error. Should I use