Displaying 20 results from an estimated 9000 matches similar to: "Upcoming Syslinux 6.01 release"
2013 Jun 28
1
Upcoming Syslinux 6.01 release
On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote:
> Am 27.06.2013 22:08, schrieb Matt Fleming:
> > I'm planning on releasing 6.01 next week. The list of changes (so far)
> > are appended below. This is going to be a quick bug fix release, mainly
> > because of the rather embarrassing bug in the 6.00 that prevents booting
> > a Linux kernel on BIOS. The idea is to
2013 Jun 27
2
Upcoming Syslinux 6.01 release
On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote:
> Am 27.06.2013 22:08, schrieb Matt Fleming:
> > I'm planning on releasing 6.01 next week. The list of changes (so far)
> > are appended below. This is going to be a quick bug fix release, mainly
> > because of the rather embarrassing bug in the 6.00 that prevents booting
> > a Linux kernel on BIOS. The idea is to
2013 Jun 27
0
Upcoming Syslinux 6.01 release
Am 27.06.2013 22:08, schrieb Matt Fleming:
> I'm planning on releasing 6.01 next week. The list of changes (so far)
> are appended below. This is going to be a quick bug fix release, mainly
> because of the rather embarrassing bug in the 6.00 that prevents booting
> a Linux kernel on BIOS. The idea is to get a fixed release into
> everyone's hands ASAP.
Any chance for a fix
2013 Jun 27
0
Upcoming Syslinux 6.01 release
> On Thu, 27 Jun, at 11:02:51PM, Thomas B?chler wrote:
> > Am 27.06.2013 22:08, schrieb Matt Fleming:
> > > I'm planning on releasing 6.01 next week. The list of changes (so far)
> > > are appended below. This is going to be a quick bug fix release, mainly
> > > because of the rather embarrassing bug in the 6.00 that prevents booting
> > > a Linux
2013 Jul 05
3
[5.xx-6.01] broken PXE with HTTP
Hello
With 4.06 this works fine all times. But with versions 5.1x-preX and
6.0x-preX, 6.01) does not work, random errors or nothing shows
(netconn_write error -5), random behaviour. Only few times works
(1/50...). Note that retriving files via TFTP works perfect in all cases.
This happens using pre-compiled files in tarball and building for source.
# dnsmasq --port=0 \
2013 Jun 24
4
[bug] 6.00: No linux boot function
On Mon, 24 Jun, at 10:27:52AM, Thomas B?chler wrote:
> Am 24.06.2013 04:10, schrieb Gene Cumm:
> > In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got"
> >
> > "No linux boot function registered for firmware
> > Booting kernel failed: Bad file number"
> >
> > Using Syslinux-5.10, the same kernel/initrd succeeds.
> >
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 22:42, schrieb H. Peter Anvin:
> On 06/06/2013 01:25 AM, Thomas B?chler wrote:
>> Am 06.06.2013 07:00, schrieb Gene Cumm:
>>> iPXE details. My testing was with an Intel PXE OROM in a VMware
>>> hosted platform with 0 issues.
>>>
>>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0"
>>>> 200 26813
2013 Jun 20
9
Syslinux 6.00 released
Finally, the Syslinux 6.00 release is out. This release includes support
for booting from EFI, both from disk-based media and over the network
via PXE. Thanks to everyone who has been testing this out.
There are some EFI bugs that I'm aware of,
* booting Linux kernels without CONFIG_RELOCATABLE doesn't work
* 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa
*
2013 Jul 04
0
Syslinux 6.01 released
OK, 6.01 is now out.
The main intention of this release was to fix the terrible bug in
Syslinux 6.00 which made it impossible to boot kernels from BIOS. This
resulted in a way shorter than usual release cycle, and it does mean
that there are some bugs that have been reported that haven't yet been
fixed. Shortlog appended below.
Thanks to everyone who helped test things out.
---
Gene Cumm
2013 Jul 08
3
[5.xx-6.01] broken PXE with HTTP
On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote:
>
> 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1
> [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0]
> BAD (freeze, no error messages, 100% CPU used)
>
> 5.10-pre1 [pxelinux.0] BAD (freeze, no error messages, 100% CPU
> used) 5.10-pre2 [pxelinux.0] BAD (Failed to load: ldlinux.c32,
2013 Jun 24
2
[bug] 6.00: No linux boot function
In trying Syslinux-6.00 bios/core/pxelinux.0 with a 3.0.21 kernel, I got"
"No linux boot function registered for firmware
Booting kernel failed: Bad file number"
Using Syslinux-5.10, the same kernel/initrd succeeds.
Screenshot, kernel and initrd available but I'm figuring this is an
issue in the BIOS loader not handling things as it should.
--
-Gene
2013 Jun 04
3
Syslinux 5.10 released
Folks,
Finally, Syslinux 5.10 has been released. This release includes a merge
of the 4.10 development branch, which means that there's a new network
stack availble, based on the lwIP embedded TCP/IP stack. The jump from
the previous 5.01 release to 5.10 may be a little confusing, but a new
network stack is such a large change that it deserved a significant bump
in the version minor number.
2013 Jun 28
2
Upcoming Syslinux 6.01 release
On Fri, 28 Jun, at 01:44:56AM, Ady wrote:
> 2_ If relevant, fixing the [MENU] INCLUDE directive in 6.xx (which
> might be the same fix applied just before the release of 5.11-pre3; I
> don't know).
Yes, this fix is applicable to the 6.xx releases and will be merged
before the final 6.01.
--
Matt Fleming, Intel Open Source Technology Center
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote:
> On 06/11/2013 01:03 AM, Matt Fleming wrote:
> > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote:
> >> Either that or make the path a list rather than a string, using the
> >> normal word separators when entered on the command line, a bit like the
> >> (t)csh does. That is a bigger change but is probably
2013 Jun 12
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote:
> Cool thanks!. Now looks better, but still not work.
>
> For some reason, "ldlinux.c32" is apparently sent but "Failed to load"
> by PXELINUX and few seconds later, dnsmasq shows an error message
> "failed sending":
Did you reinstall ldlinux.c32 after rebuilding? Did you do 'make
2013 Jun 27
3
Syslinux 6.00 released
On Thu, 27 Jun, at 11:45:28AM, Matt Fleming wrote:
> I'll bisect to see why this broke after 5.01.
Which is...
commit 5447ef821c24b526079ef785d2454ed0efff3e2b
Author: Matt Fleming <matt.fleming at intel.com>
Date: Thu Feb 28 17:44:54 2013 +0000
ldlinux: Always update ConfigName when opening a config file
With the introduction of commit aa7dd29db684 ("ldlinux:
2013 Feb 01
2
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times
Hello
Booting with 4.06 cmdline looks like:
# cat /proc/cmdline
archisobasedir=arch archisolabel=ARCH_201301
initrd=boot/i686/archiso.img console=ttyS0 BOOT_IMAGE=boot/i686/vmlinuz
while using 5.01:
# cat /proc/cmdline
boot/i686/vmlinuz boot/i686/vmlinuz archisobasedir=arch
archisolabel=ARCH_201302 initrd=boot/i686/archiso.img console=ttyS0
And this cause some issues for cmdline parsing, I
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 07:00, schrieb Gene Cumm:
> iPXE details. My testing was with an Intel PXE OROM in a VMware
> hosted platform with 0 issues.
>
>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813
>> "" "iPXE/1.0.0+ (09c5)"
This is the iPXE version that comes bundled with qemu as the default
qemu boot rom.
-------------- next
2013 Jun 06
7
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Hello,
First, this setup works fine without any error in syslinux 4.06 as show
below.
For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2]
directories (~2MB each) are uploaded ready for test.
As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch
Linux @ 64-bit.
If more info is needed, please let me know.
Good luck!
Relevant directory structure is at
2013 Jul 22
2
Chaining with chain.c32 from syslinux 6.01 error
On Mon, 22 Jul, at 12:07:34PM, Matt Fleming wrote:
> On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote:
> > Hi,
> > ?
> > ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok.
> > ??? LABEL -
> > ?? MENU LABEL GRUB LEGACY
> > ?? MENU INDENT 1
> > ???? COM32 chain.c32
> > ???? APPEND boot fs