similar to: Recommend verification

On Sun, Jul 23, 2017 at 11:16 AM, <mikezb at softhome.net> wrote: > Gene Cumm: > ______________________________________________________________________ >> >> On Sun, Jul 23, 2017 at 9:30 AM, <mikezb at softhome.net> wrote: >>> >>> Gene Cumm: >>>> Please use reply all. OP is a non-subscriber. >>>>

On Sun, Jul 23, 2017 at 9:30 AM, <mikezb at softhome.net> wrote: > Gene Cumm: >> >> Please use reply all. OP is a non-subscriber. >> ______________________________________________________________________ >> Sun, Jul 23, 2017 at 3:26 AM, mikezb (via Syslinux <syslinux at zytor.com>) >> wrote: >>> >>> I recommend someone verify that

On Sun, Jul 23, 2017 at 7:22 PM, <mikezb at softhome.net> wrote: > Gene Cumm: > ? >>>>>> >>>>>> ______________________________________________________________________ >>>>> >>>>> ? >>>>> I ? tried a more flexible script, but it had trouble unpacking >>>>> syslinux-6.04-pre1.tar.xz for

Was seeing it I could get any closer with the efi boot using the 6.0.4, and didn't have any more luck. Did a test with it in bios mode and it works for the regular kernels, but when I tried the hdt.c32 I get the following error? Undef symbol FAIL: parse_url Failed to load COM32 file hdt.c32 Only find urlparce.c in the PXE directory, and no reference to it in any files in the hdt

So there seem to be some shortcomings in NTFS, still. 1. Symlinks are not supported. Proper symlinks exist in NTFS since Vista, so we should support them. 2. readdir() seems to be broken. I have been using the following test load to generate disk images: http://www.zytor.com/~hpa/syslinux/exttest-20140521.tar.xz Anyone who has been involved with the NTFS code who has a chance to take a

Why no mention of versions 4.06, 4.10, or 5.xx on the SysLinux Wiki?

Greetings, all... Hoping someone can point me in the right direction. I've set up a Linux PXE host with a menu choice to install Windows. This option boots a WinPE image, which then uses \\net use... to mount the appropriate ISO image. Works fine. However, I would like to pass the iso name and directory into WinPE from the menu via append= arguments. Thus, I can set up a separate menu option

There seem to be a bunch of bug fixes in the 6.04 branch that people really need. Do we know of any current regressions? Otherwise we really ought to just push the button... -hpa

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

... > 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 \ >

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

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 >>>

> Thank you all. > > It looks like -mno-red-zone flag is already in master branch since > commit 7d70885d, but it seems it is applied to all EFI builds. Finally we are on the same page. > > IIUC, the problem only affects efi64 builds. Have you actually tested efi32 (ia32) builds? > > So here's the modification of my patch to only apply -mno-red-zone >

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

> >> Let me double check what the status of 6.04-pre1 is. Maybe this patch > >> is not necessary at all! > > OK, I have verified beyond doubt that 6.04-pre1 (prebuilt from > kernel.org) indeed does fix the issue on the affected systems. > > Again, sorry for the churn! > > Best Regards, > - Chris OK, so, from the user's point of view, the

> Let me double check what the status of 6.04-pre1 is. Maybe this patch > is not necessary at all! Just a reminder: _ 6.04-pre1 can be downloaded from kernel.org, and it includes pre-built binaries, so no "make" anything is needed (and to some degree, not always recommended). _ In many cases, testing with pre-built official binaries is desired, so others can attempt to

On 6/6/19 8:16 AM, Ady Ady via Syslinux wrote: > >> the PXELINUX log line is >> printed (PXELINUX 6.04 lwIP 6.04-pre3 Copyright (C) 1994-2015 H. Peter >> Anvin et al), > > (snip) > > FWIW, the official binaries from 6.04-pre2 and 6.04-pre3 are not good > for troubleshooting. > > Is the same behavior present when testing with other versions? I would

On 07/14/16 05:56, Ady Ady via Syslinux wrote: > > @Peter, Erwan, Gene, Michal, (and anyone else interested)... > > Although I haven't actually tested Erwan's patch, would it be > acceptable by you (all) if I were to send a patch to this Syslinux > Mailing List with the same code while changing the wording as I > previously suggested in a prior email? Would it be

On Fri, Jul 3, 2015 at 2:28 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, I am still against releasing 6.04-pre1 yet. Why? A pre-release is not a full release. It means we're getting ready and have something that we want more people to test, especially those who can't reliably build test binaries, especially those who can't build any. Yes there are open

Hi, I'm trying to make Syslinux, OSTree and Qemu work together. So I've made an image, installed Syslinux v. 6.0.3 on it with extlinux and try to boot it. Unfortunately it stops on the stage of loading the kernel with Loading /boot/ostree/agl-17980142f6d5ef5e82153aa533ffb9775181f93248e62a4821f925cdf1b81c34/vmlinuz... failed: I/O error The vmlinuz file is just a normal bzImage (v.