Displaying 20 results from an estimated 402 matches for "6.02".
Did you mean:
1.02
2013 Jul 19
2
FW: pxelinux 5.x, 6.x memtest problem
Hi,
> Are you positive that the menu works with 6.02-pre5? There are two
> changes between 6.02-pre5 and 6.02-pre6 and those two commits are
> unlikely to have caused any regressions.
Yep, I very sure.
I compiled 6.02-pre6 again (made sure, that I really copy the files
from 6.02-pre6 to the tftp-host) and this isn't working. Now menu will
appear.
I re-compiled 6.02-pre5 again
2013 Jul 19
3
FW: pxelinux 5.x, 6.x memtest problem
Hi,
> What steps are you using to recompile the releases? Are you working from
> git?
No, not git.
See http://www.syslinux.org/archives/2013-July/020543.html and the
f'up from Ady and my response regarding re-compiling.
So actual I think I don't re-compile everything. I think I am using
the pre-build modules from your provided archives (if 'make installer
&& make
2013 Dec 10
0
PXELINUX [BIOS] 6.02 - Upgrade to 6.02 from 4.07 introduces local boot regression
> upgraded from version 4.07 to version 6.02 and, without making any edits to
> my default menu, immediately noticed a regression. I use vesamenu.c32 to
> present a menu to the user which starts with something like this:
>
> default vesamenu.c32
> prompt 0
>
> menu title Host Provisioning Tool
> menu INCLUDE pxelinux.cfg/graphics.conf
> MENU AUTOBOOT
2013 Dec 09
4
PXELINUX [BIOS] 6.02 - Upgrade to 6.02 from 4.07 introduces local boot regression
Hello All, this is my first post so I'll try to be as verbose as possible.
We have a PXE deployment server serving mostly fujitsu RX300 rack mount
servers with Intel 82575EB Gigabit Ethernet Controllers onboard. I recently
upgraded from version 4.07 to version 6.02 and, without making any edits to
my default menu, immediately noticed a regression. I use vesamenu.c32 to
present a menu to the
2013 Jul 19
2
FW: pxelinux 5.x, 6.x memtest problem
Hi,
- syslinux-6.01-pre6 -> Working
- syslinux-6.02-pre5 -> Working
- syslinux-6.02-pre6 -> NOT WORKING
With working I mean that I get my expected menu and I am able to boot
systemrescuecd.
Memtest doesn't boot on any mentioned versions.
Please tell me how I can help you debugging memtest or if you need
anything else.
--
Regards,
Igor
2013 Jul 18
3
Efi64 boot fail during download from kernel and initrd via http
On Sat, 13 Jul, at 07:58:21PM, Michael Szerencsits wrote:
> I use VMWare Player 5.02 build 1031769 on Win2k8 R2 64bit.
> I found that the last working version is 6.02-pre1 but beginning
> with pre2 and also latest version 6.02-pre5 it fail to boot.
Are you sure that 6.02-pre1 worked? There was only one commit between
6.02-pre1 and 6.02-pre2 and it shouldn't have affected anything at
2013 Jul 11
2
make efi64 install in syslinux-6.02-pre3 fail
Hello,
I tried to make my own binary with 'make efi64 install' but it fail with
make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop.
make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64'
make[1]: ***
2013 Jul 18
4
FW: pxelinux 5.x, 6.x memtest problem
Hi,
OK. I build syslinux-6.02-pre6 from
https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
on a Debian jessie/sid system (with gnu-efi_3.0u+debian-2 from
experimental):
root at jessie: ~# cd /tmp
root at jessie:/tmp# wget
https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
root at jessie:/tmp# tar xfz
2013 Dec 10
3
PXELINUX [BIOS] 6.02 - Upgrade to 6.02 from 4.07 introduces local boot regression
Gene, Ady thanks for your suggestions.
>> What if you dropped the timeout to 0.8-2.0 seconds or even 0.2 seconds?
I tried setting the delay to 2 seconds and 0.2 with no change in behavior.
>> First, please be sure you are using all C32 modules from the exact same
Syslinux version, including ldlinux.c32 and all lib*.c32 library modules,
all located somewhere under the
2013 Dec 10
0
PXELINUX [BIOS] 6.02 - Upgrade to 6.02 from 4.07 introduces local boot regression
On Mon, Dec 9, 2013 at 3:27 PM, Cory Fair <cory.fair at gmail.com> wrote:
> Hello All, this is my first post so I'll try to be as verbose as possible.
>
> We have a PXE deployment server serving mostly fujitsu RX300 rack mount
> servers with Intel 82575EB Gigabit Ethernet Controllers onboard. I recently
> upgraded from version 4.07 to version 6.02 and, without making any
2013 Dec 10
0
PXELINUX [BIOS] 6.02 - Upgrade to 6.02 from 4.07 introduces local boot regression
> Tried this out as follows:
>
> UI vesamenu.c32
> DEFAULT bootlocal
> prompt 0
>
> menu title Host Provisioning Tool
> menu INCLUDE pxelinux.cfg/graphics.conf
> MENU AUTOBOOT Starting Local System in # seconds
> MENU BACKGROUND splash.jpg
>
> label bootlocal
> menu label ^Boot This Host
> KERNEL localboot.c32
>
2014 Feb 20
2
[PATCH] core: Incorrect detection of EDD in /core/fs/diskio_bios.c
DL register is not set to drive number when detecting EDD for drive, so detection may fail.
Signed-off-by: Andy Alex<andy at r-tt.com>
---
diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c
--- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400
+++ syslinux-6.02/core/fs/diskio_bios.c 2014-02-20 12:15:08.000000000 +0400
@@ -337,7
2013 Oct 15
2
syslinux.com 6.02 Invalid Opcode under FreeDOS
_ Vbox 4.2.18 VM booted with FreeDOS floppy, kernel 2041, no
config.sys, no autoexec.bat, no TSR's, no memory managers.
_ The booting floppy includes syslinux.com 6.02.
_ Two HDD images attached to the VM, MBR + 1 FAT16 formatted
partition each.
Executing syslinux.com -i c: (or "d:") results in the following
error:
"Invalid Opcode at AD04 5080 0206 5080 2021 3666 FFFD 0083
2013 Nov 23
4
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
It occured with every BIOS system I tested on (none of them Dell):
1. HP G62 laptop (i3)
2. Samsung RV520 (i3)
Don't know what system Philip Muller uses; have copied him in as he has far
more technical knowledge than I do. Syslinux tested from Arch and Manjaro
(an Arch derivative). Basically found then when creating latest ISO images.
I may be missing something as well about the FMs. Just
2013 Jul 18
2
FW: pxelinux 5.x, 6.x memtest problem
Hi,
if you can provide a prepared src tarball like you do for releases, I can test.
But I still cannot build from git source (as you may remember).
--
Regards,
Igor
2013 Oct 31
2
Syslinux 6.02 BIOS - issue on physical devices
Hi
Thanks for confirmation about syslinux 6.02 requirements.
I see small misunderstanding. A used word "Syslinux 6.02 BIOS" mean the
respective syslinux binary files from "/bios" subdirectory for PC's with
Legacy PXE or PC's with PXE where CSM mode is enabled.
Some idea where is the issue?
Do the syslinux 6.02 working well from PXE on multiple PC's in your place?
2013 Jul 12
0
make efi64 install in syslinux-6.02-pre3 fail
On Thu, 11 Jul, at 01:55:12PM, Michael Szerencsits wrote:
> Hello,
>
> I tried to make my own binary with 'make efi64 install' but it fail with
>
> make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop.
> make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi'
> make[2]: ***
2013 Jul 18
0
FW: pxelinux 5.x, 6.x memtest problem
> Hi,
>
> OK. I build syslinux-6.02-pre6 from
> https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz
> on a Debian jessie/sid system (with gnu-efi_3.0u+debian-2 from
> experimental):
>
> root at jessie: ~# cd /tmp
> root at jessie:/tmp# wget
>
2013 Jul 13
3
efi64 boot fail during download from kernel and initrd via http
Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com:
> Reason: Message body is too big: 1780404 bytes with a limit of 512 KB
So previous not on the mailinglist.
> Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST)
> From: Michael Szerencsits <szerencsits.michael at gmx.at>
> To: syslinux at zytor.com
> Subject: efi64 boot fail during download from kernel and initrd
2014 Feb 10
1
pxechn.c32 halting
On Thu, Sep 19, 2013 at 5:13 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Wed, Sep 18, 2013 at 4:09 PM, Chris Valentino
> <chris.valentino at 1010data.com> wrote:
>> I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with
>> pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The