similar to: Boot prompt ignored

On Sat, May 07, 2016 at 09:56:59PM +0300, Ady via Syslinux wrote: > On Sun, May 01, 2016 at 11:58:41AM +0200, Alexander Freudenberg via Syslinux wrote: > > Using a boot prompt without a menu makes Syslinux 6.03-6 booting the > > default label only, ignoring the label that was entered. Auto completion > > of the defined labels works, though. Can anyone confirm this? > >

And apparently the original poster had bad headers. Delivery to the following recipient failed permanently: ml.afb at mailbox.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain mailbox.org by mx2.mailbox.org. [80.241.60.215]. The error that the other server returned was: 577 5.1.1 <ml.afb at

I'd suggest fixing your mail. ml.afb at mailbox.org still doesn't work. -- -Gene On Sun, May 1, 2016 at 6:55 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, May 1, 2016 at 5:58 AM, Alexander Freudenberg via Syslinux > <syslinux at zytor.com> wrote: >> Using a boot prompt without a menu makes Syslinux 6.03-6 booting the default > > The version

> On Sat, May 07, 2016 at 09:56:59PM +0300, Ady via Syslinux wrote: > > On Sun, May 01, 2016 at 11:58:41AM +0200, Alexander Freudenberg via Syslinux wrote: > > > Using a boot prompt without a menu makes Syslinux 6.03-6 booting the > > > default label only, ignoring the label that was entered. Auto completion > > > of the defined labels works, though. Can anyone

> Using a boot prompt without a menu makes Syslinux 6.03-6 booting the > default label only, ignoring the label that was entered. Auto completion > of the defined labels works, though. Can anyone confirm this? > I compiled binaries from the (hopefully, temporarily) "revert-9acbffd" branch from GeneC. The building environment is using old dependencies (i.e. not recent

> I also sent (off-list) a bootable floppy image to GeneC, using binaries > from Fedora 24, package version "6.03-6" (coincidentally), and a simple > syslinux.cfg, replicating the behavior. > Testing with: _ 6.03-8.fc24 : still the same unwanted behavior as 6.03-6.fc24; _ 6.04-0.1.fc25: works correctly (regarding this matter). I still think that distributions using

On 03/08/2016 02:53 PM, Gene Cumm wrote: > > Poma, in my opinion, this behavior means it's your/Fedora's responsibility > to propose a change that distinguishes between broken and working NASM > 2.11.06 or revert the commit in your/Fedora's build. > Yes, it is highly problematic to have especially build tools with version numbers that don't match upstream having

On 07/11/15 19:38, Ady via Syslinux wrote: > >> >> Just a heads up that syslinux is broken in the current Ubuntu, syslinux >> just shows "Boot error". Downgrading to syslinux from 15.04 works perfectly. >> >> Ubuntu bug is here: >> https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1499746 >> >> This is mostly in case anyone

Just a heads up that syslinux is broken in the current Ubuntu, syslinux just shows "Boot error". Downgrading to syslinux from 15.04 works perfectly. Ubuntu bug is here: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1499746 This is mostly in case anyone shows up on the mailing list with a mystery broken syslinux from latest Ubuntu. -------------- next part -------------- A

gcc-4.6.real (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 GNU ld (GNU Binutils for Ubuntu) 2.22 Regards, Terry On Tue, Oct 4, 2016 at 6:35 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 10/04/16 14:48, Terry Hardie via Syslinux wrote: >> I know this is an old thread, but since I ran into this problem and spun my >> wheels on it for a few hours, I want to point out something

That's what I'm failing with. What version of GCC works? On Wed, Oct 5, 2016 at 3:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > I've only had failures on gcc-4.6 with EFI builds. > > > On Oct 5, 2016 4:03 PM, "Terry Hardie via Syslinux" <syslinux at zytor.com> > wrote: >> >> gcc-4.6.real (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3

2015-10-08 12:58 UTC+02:00, Gene Cumm <gene.cumm at gmail.com>: > On Mon, Oct 5, 2015 at 2:15 PM, celelibi--- via Syslinux > <syslinux at zytor.com> wrote: >> From: Sylvain Gault <sylvain.gault at gmail.com> >> >> These patches basically remove unused linker scripts and port a change >> that was >> made to an unused script. >> >>

I know this is an old thread, but since I ran into this problem and spun my wheels on it for a few hours, I want to point out something subtle in this thread I missed: You must use the pre-compiled binaries in the tarball for this to work. I downloaded the tarball for syslinux 6.03 release and also tried 6.04-pre and 6.03-pre7, and did a make, and the resulting EFI binary still exhibited the

> > > I also sent (off-list) a bootable floppy image to GeneC, using binaries > > from Fedora 24, package version "6.03-6" (coincidentally), and a simple > > syslinux.cfg, replicating the behavior. > > > > Testing with: > _ 6.03-8.fc24 : still the same unwanted behavior as 6.03-6.fc24; > _ 6.04-0.1.fc25: works correctly (regarding this

Hi Ady, On Sun, 22 Oct 2017 22:49:53 +0000 Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Let's not forget that upstream Syslinux FTBFS when building with > binutils 2.27+: > > "ldlinux.elf: Not enough room for program headers" > > Workaround in Debian's package: > _ Add --no-dynamic-linker to link lines > _

On Sun, May 1, 2016 at 5:58 AM, Alexander Freudenberg via Syslinux <syslinux at zytor.com> wrote: > Using a boot prompt without a menu makes Syslinux 6.03-6 booting the default The version appears to be a distribution-specific number. > label only, ignoring the label that was entered. Auto completion of the Using the official builds (documented at

https://bugs.freedesktop.org/show_bug.cgi?id=75985 Priority: medium Bug ID: 75985 Assignee: nouveau at lists.freedesktop.org Summary: HDMI audio device only visible after rescan QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jean-louis at

> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/>

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

Am 02.12.2014 schrieb Ady: > ( ... ) > > Since we are in the Syslinux Mailing List, please let me rephrase the > most relevant part of this case: syslinux.efi 6.03 is incapable of > booting some kernel, whereas syslinux.efi 6.01 can successfully boot it > under the same conditions. > I can now confirm that this can be replicated on hardware, a ThinkCentre M93 will reboot