search for: mybiginitrd

...ug 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 mybiginitrd APPEND myoptions ### Maybe a packet capture might reveal something about the network setup? Maybe it is not the size of the initrd file but rather a time limitation (which gets triggered by a big-enough file)? What about trying with 6.04-pre1, and/or (even better) with Debian Sid's package...

...nd 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 mybiginitrd > APPEND myoptions > ### I will try that. > Maybe a packet capture might reveal something about the network setup? > > Maybe it is not the size of the initrd file but rather a time > limitation (which gets triggered by a big-enough file)? If it's a timing difference it...

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

...g.c32 > > APPEND -e pxe_call,malloc > > # Additional functions for debug might be of interest. > > > > > > # After debug.c32 returns to the boot prompt, > > # press "1" and "Enter". > > LABEL 1 > > LINUX mykernel > > INITRD mybiginitrd > > APPEND myoptions > > ### > > > > > > Once the label named "1" is launched, is there any info (that could > > help)? > > > > Please avoid using boot menus for these tests; use the boot prompt. > > I'll give that a shot as w...