Displaying 20 results from an estimated 80000 matches similar to: "SYSLINUX 1.75-pre9 released"
2004 Dec 29
2
SYSLINUX 3.00-pre9 released
I have just released SYSLINUX 3.00-pre9. The only change versus
3.00-pre8 is that the MEMDISK query API now reports the boot loader ID
byte, per Bernd's suggestion.
This is a release candidate, and I plan to release it as 3.00
*tomorrow*, unless I hear back anything bad.
-hpa
2008 Apr 10
0
SYSLINUX 3.63 released (and 3.70-pre9)
Hello everyone,
I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX,
which would get confused by directories with deleted file entries.
Special thanks to Stas Kysel of rPath, Inc. for spotting this problem
and giving me an excellent test case; and of course to rPath, Inc. in
general for being my employer and being extremely supportive of my
SYSLINUX work!
I have also
2002 Oct 22
2
PXELINUX memory overwrite bug - SYSLINUX 2.00-pre9 released
Hi everyone,
Kevin Tran of Broadcom just identified a very serious bug in PXELINUX
where random parts of the PXE stack would get overwritten by PXELINUX.
As a result, I have release SYSLINUX 2.00-pre9 for testing; if you have
had problems with PXELINUX **PLEASE** test this version. I will try to
make a SYSLINUX 2.00 some time this week if this tests out OK.
I will also hunt for similar bugs
2005 Sep 13
2
Fw: Issue with pxelinux
I've been working with Matt Burgess here on this problem, and have found
the following:
syslinux 3.08-pre10 ? broken
>>> config.inc:max_cmd_len=255
syslinux 3.08-pre11 ? works
>>> config.inc:max_cmd_len=1023
syslinux 3.08 ? works
>>> config.inc:max_cmd_len=1023
syslinux 3.09-pre1 ? works
>>> config.inc:max_cmd_len=1023
syslinux 3.09-pre2 ? broken
2005 Aug 16
8
SYSLINUX 3.10-pre9
I have just pushed out SYSLINUX 3.10-pre9. Please test it out,
especially everyone who has been working with me on various systems
trying to get them to work, or have had recent breakage.
-hpa
2005 Aug 29
1
SYSLINUX 3.11-pre9 -- release candidate; release delayed
Based on a few reports I've gotten today, I have make a new release
candidate, 3.11-pre9, and am pushing out the release target to Friday,
September 2.
New in this release candidate:
- Change to MEMDISK, which hopefully will work right both on machines
with and without physical floppies.
- Try to enable the 16550A FIFO for serial console. I'm hoping this
will help eliminate dropped
2002 Jun 15
0
SYSLINUX 1.75 released
I have released SYSLINUX 1.75 -- this one is identical to 1.75-pre9
except the version number. I have gotten enough testing done that I
feel it's time to release...
Changes in 1.75:
* ALL: NASM 0.98.32 or later is now required to build
SYSLINUX from sources.
* SYSLINUX: put back in the workaround for the BIOS floppy
table. This seems to be a
2007 Feb 09
6
syslinux-3.36-pre8 feedback
Tested floppy boot on two machines (one PII 350, one 486DX4)
Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux
kernel from floppy on the 2 machines.
Tested with 3 different disquettes that were know to work, boot is reached
after this very long time.
Noise from floppy head make think floppy wait approximatly one minute
between each read.
No problem with pxe boot with
2003 Nov 21
0
Success!!
Hello...
I put pre9 in place and it works great. Thank you very much! This
really was The Very Last Problem in a pretty complex system.
-Chris
-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Friday, November 21, 2003 1:13 AM
To: H. Peter Anvin
Cc: McMahon, Chris; 'syslinux at zytor.com'; 'mike at flux.utah.edu'
Subject: Re: [syslinux]
2014 Jun 08
2
How to use --once? Does it work?
>
> To be clear, I am not saying there is no bug - there might be.
>
I performed the following test with several versions of Syslinux:
1_ Execute:
'extlinux --once=non_default_label --install /mnt/sda1' ;
2_ In first reboot, the "non_default_label" should be executed;
3_ In second reboot, the default label should be executed.
Results:
_ 4.05 to 4.07: OK.
_
2012 Oct 31
1
Syslinux-5.00-pre9
Folks,
I've just pushed out another prerelease for the 5.00 branch. The idea
behind this -pre was to merge in the final 4.06 release.
I'm aiming for a final 5.00 release next week, but as we saw with the
4.06 branch, anything can happen and these deadlines can get pushed
backwards. Please, test if you can.
One thing that is going to happen next week is a Syslinux-6.00-pre1,
which will
2006 Aug 07
1
"sector read error" with 3.20-pre8 syslinux.com
Hi All,
A colleague of mine is using syslinux-3.20-pre8, syslinux.com, under
DOS to install syslinux loader. It gives "sector read error". He
re-compiled syslinux.com under a linux box, and used it successfully
to install the loader from DOS. He is installing it on a hard drive (C:)
He booted from a floppy and ran: "syslinux.com C:" at A:\ prompt
He tried with
2014 Jun 09
3
How to use --once? Does it work?
> On 06/08/2014 02:58 PM, Ady wrote:
> >>
> >> To be clear, I am not saying there is no bug - there might be.
> >>
> >
> > I performed the following test with several versions of Syslinux:
> >
> > 1_ Execute:
> > 'extlinux --once=non_default_label --install /mnt/sda1' ;
> > 2_ In first reboot, the
2005 Aug 29
1
SYSLINUX 3.11-pre8 -- release candidate
I have released SYSLINUX 3.11-pre8; this is a release candidate.
The differences versus -pre6 is that I have reverted the PXELINUX stack
changes I did in SYSLINUX 3.10 since there are confirmed reports that
they break at least one platform.
As before, I hope to release 3.11 on Tuesday unless I get objections.
ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/
-hpa
2004 Dec 30
2
bug / incompatibility with USB booting in Syslinux 3.00 pre9 ?
Hi,
I'm Florent BERANGER, from Flonix ( http://www.flonix.com ).
After several tests, we have found that Syslinux 3.00 pre9 is no longer
compatible with USB stick booting.
Syslinux 2.13 works fine with this feature.
Error infos :
Syslinux 3.00 pre9 only displays its version and a new line with a "a"
character and then hangs.
Tests configuration :
Syslinux applied from : Linux
2008 Mar 31
4
SYSLINUX 3.70-pre8
I have just pushed out SYSLINUX 3.70-pre8. The two main differences is
that I have updated the gPXE source base, and added a sanboot module
(sanboot.c32). sanboot.c32 *should* be capable of initiating an iSCSI
or AoE boot, but I haven't actually tested it.
The other main difference is that gPXE now advertises HTTP/1.0 instead
of HTTP/1.1, since the code was not actually HTTP/1.1
2006 Aug 26
2
SYSLINUX 3.20 released
Hi all,
I have officially released SYSLINUX 3.20:
Changes in 3.20:
* EXTLINUX: New options --install (-i) and --update (-U), to
make it clear if a boot loader should be installed or
updated. For now, defaults to --install for compatibility;
a future version will require one of these options.
* New library functions to load and place files in
2002 Jun 01
0
SYSLINUX 1.74 released -- bug fix release
I tracked down the source of the "invalid kernel image" in 1.73 -- it
turns out that in two different places I was accessing word-sized
variables as dwords :(
Consequently, SYSLINUX would reject valid kernels. PXELINUX/ISOLINUX
are unaffected.
Thus, SYSLINUX 1.74 is out.
Expect a 1.75-pre1 quite soon. I'm working on a rewrite using 32-bit
code from the very beginning, which
2012 Nov 03
1
A Few Syslinux 5.00-pre9 Bugs
Just a few bug-reports, before I forget:
- A Windows installer bug for 4.06 and presumably 5.00-pre9 whereby the ADV
contains backslashes. Reproduced with: syslinux.exe --directory \two\dirs
e:
- An open() (?) bug for 4.06 and presumably 5.00-pre9 whereby the filename
/ubcd/custom/syslinux-5.00-pre9/com32/gplinclude/acpi/facs.h fails to open()
after 134 iterations in a loop where it's
2014 Mar 27
1
Any hints about compiling syslinux 6.03-pre9 on AMD64?
Dear all,
I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem
is, I have problem to use it for PXE booting (BIOS mode).
It always gives me "Failed to load COM32 file vesamenu.c32".
I am sure all the settings are correct because if I switch to the
prebuilt syslinux downloaded from