similar to: lpxelinux.0 issues with larger initrd.img files from RHEL >= 7.5 on UCS servers?

On June 19, 2019 12:21:05 PM PDT, Mathieu Chouquet-Stringer <m+syslinux at thi.eu.com> wrote: > Hello, > >On Tue, Jun 18, 2019 at 05:31:17PM -0700, hpa at zytor.com wrote: >> Which servers, what threshold, what clients, what about pxelinux.0? > >All affected servers so far are Cisco UCS B200 M3 blade servers. > >The threshold seems to be around 50MB, I haven't

> Is there something I could do A_ Instead of 6.03, try 6.04-pre1 (not pre2 and not pre3, but pre1). Please remember to change _all_ related files to the same version, not just lpxelinux.0. Alternatively (and in many cases, even better) you could try current Debian's "Unstable" packages, which are "more up-to-date" than 6.04-pre1. B_ In the configuration file,

Hello Ady, thanks for getting back to me. On Wed, May 22, 2019 at 01:33:50AM +0000, Ady Ady via Syslinux wrote: > > Is there something I could do > > A_ Instead of 6.03, try 6.04-pre1 (not pre2 and not pre3, but pre1). > Please remember to change _all_ related files to the same version, not > just lpxelinux.0. > > Alternatively (and in many cases, even better) you

> > Sounds like you may want to contact Cisco... > > And tell them what? There's a bug in their PXE/BIOS stack somewhere? Just some random and humble thoughts... Perhaps it would be worth some additional tests? Maybe a test with pxelinux.0 version 4.07? And using "LINUX", not "KERNEL": ### DEFAULT biginitrd PROMPT 0 LABEL biginitrd LINUX mykernel INITRD

Hello, i would like create a bootdisk , that can be boot from Old BIOS, EFI32 and EFI64. But for EFI Boot there is only one directory /EFI/BOOT/ In this directory I can copy BOOTia32.EFI and BOOTx64.EFI. But the *.c32 files for EFI32 & EFI64 , I can install to this directory at the same time. Is there a way to load the *.c32 from different directory ? Or is there a other solution ?

Hello, On Wed, Jun 19, 2019 at 11:15:36PM +0000, Ady Ady via Syslinux wrote: > Just some random and humble thoughts... > > Perhaps it would be worth some additional tests? > > Maybe a test with pxelinux.0 version 4.07? And using "LINUX", not > "KERNEL": > > ### > DEFAULT biginitrd > PROMPT 0 > LABEL biginitrd > LINUX mykernel > INITRD

Hello, At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad. Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to

Hi, I tried more syslinux/pxelinux versions and I can report the following while using pxelinux.0: 4.03 OK (server boots fine) 4.07 OK (server boots fine) 5.00 KO (server reboots) 5.01 KO (server reboots) 5.10 KO (server reboots) 6.0* KO (server reboots) Next step is to try the debug.c32 stuff I guess... On Thu, Jun 20, 2019 at 08:52:44PM +0200, Mathieu Chouquet-Stringer wrote: > > Maybe

Hello, On Tue, Jun 18, 2019 at 05:31:17PM -0700, hpa at zytor.com wrote: > Which servers, what threshold, what clients, what about pxelinux.0? All affected servers so far are Cisco UCS B200 M3 blade servers. The threshold seems to be around 50MB, I haven't tested precisely but 54525200 bytes is enough to trigger the reboot while 49812292 isn't (what I did was to recompress the initrd

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's

> I downloaded pxelinux and syslinux 6.04 from sid You also need (at least) the "syslinux-common" package of the same version, in order to obtain the core module (ldlinux.c32) and the other *.c32 modules under the "bios" directory tree (Beware: all platforms are included in the same binary package; make sure not to use c32 modules from UEFI platforms when you are

On Wed, May 22, 2019 at 03:18:25PM +0000, Ady Ady via Syslinux wrote: > You also need (at least) the "syslinux-common" package of the same > version Yeah my bad, that's what I used, I had all the c32 files... > I don't know how much relevant debug info you could actually get when > using the "-dhcpinfo" option of linux.c32 (see the wiki for details).

Hello Hans Peter, Any idea on how I could debug this problem? Basically lpxelinux 6.03 reboots while loading the initrd if its size is above a certain threshold. It only happens on certain servers and there's not output when it happens. I can trigger it reliably on affected hardware. On Wed, May 22, 2019 at 05:45:20PM +0200, Mathieu Chouquet-Stringer via Syslinux wrote: > > I don't

On Wed, Jun 19, 2019 at 01:05:50PM -0700, hpa at zytor.com wrote: > Sounds like you may want to contact Cisco... And tell them what? There's a bug in their PXE/BIOS stack somewhere? -- Mathieu Chouquet-Stringer m+syslonux at thi.eu.com The sun itself sees not till heaven clears. -- William Shakespeare --

On June 18, 2019 12:34:35 PM PDT, Mathieu Chouquet-Stringer <m+syslinux at thi.eu.com> wrote: > Hello Hans Peter, > >Any idea on how I could debug this problem? Basically lpxelinux 6.03 >reboots while loading the initrd if its size is above a certain >threshold. It only happens on certain servers and there's not output >when it happens. I can trigger it reliably on

Hello, I saw this in the release notes for 4.00: "PXELINUX: TFTP URL syntax (tftp://) supported even when not running gPXE/gpxelinux" I can't find any info describing this new functionality (searched wiki and mailing list), I'm guessing you can now use tftp:// in the paths, e g: LABEL mylabel KERNEL tftp://servername/path/to/mykernel APPEND myoptions Correct? I've

In Syslinux 5-6.02, the "global append" directive is being (unintentionally) ignored in some cases. Updating Syslinux from prior versions, when using a "global append" directive, will cause unexpected results. For example, take the following simple configuration file: *** DEFAULT mykernel APPEND root=/dev/sda2 *** Note that the 'append' line is a global

Hello, Thank you, for this information. This is, what I need. So I will switch from 6.03 to the last 6.04 pre. Regards Johann > -----Urspr?ngliche Nachricht----- > Von: Syslinux <syslinux-bounces at syslinux.org> Im Auftrag von Ady Ady via > Syslinux > Gesendet: Montag, 15. April 2019 18:53 > An: syslinux at syslinux.org > Betreff: Re: [syslinux] EFI32, EFI64 on one

> On Thu, 4 Dec 2014, Ady wrote: > > > Perhaps there should be a new MENU-type directive, so to force the > > screen to text mode (as opposed to leaving it in graphics mode for as > > long as it can be)? Perhaps this could also be useful when exiting a > > vesamenu to Syslinux CLI? > > Yes, please. To make this dependent *only* on the configuration of >

On 01.07.2015 12:10, Gene Cumm wrote: > On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >> >> To remind you once again. >> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >> This relates specifically to the use of the vesamenu.c32, >> menu.c32 works without problemos. > > isolinux-debug.bin is not for