similar to: lpxelinux.0 problems with CentOS 7.6

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

Hello all, I think I may have found a bug with the way lpxelinux.0 sends http requests. Specifically when I trace the requests I notice that the Host: header does not contain the port that was used to make the request. Here's my scenario. I have a python Flask app that dynamically generates the PXE menu for kickstarts. When I request a URL the server responds with a file containing more

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

> > 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 am using lpxelinux.0 (latest stable version 6.03, using the official binaries from kernel.org) to kickstart servers as http transfers really helps over links with poor latencies... These servers are being booted in legacy mode, not in UEFI. This has worked very well until recently. Starting with RHEL 7.5, on some servers, we would see the machine rebooting while pxelinux is in the

> What can I do to further diagnose this issue? The email thread you linked to (still) continues; it does not finish in May 2019. Reading the whole set of emails in that email thread, you will notice that the other email thread is slightly different than yours (and actually that email thread has not finished yet). In spite of the differences, the suggestions that were already given in

On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu> wrote: > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some

On this list in early July 2014 I reported that on certain hardware one cannot chain from ipxe to lpxelinux.0 . My report at the time was about 6.03-pre17. I've repeated the tests with the release version of 6.03 and here is an updated report with more details. I boot to a USB stick with iPXE, which then is told to "dhcp" and then "chain http://xxx.xxx.xxx.xxx/pxe.0".

On Sat, Oct 26, 2013 at 4:08 AM, Petry Roman, SHS-S IT-TS <Roman.Petry at shsservices.org> wrote: > Hello Geert > Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. You're right. Since you can't

Op 2014-07-01 om 22:55 schreef Gene Cumm: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" wrote: > > > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some > > advice on how to isolate and troubleshoot this. (I can't try pre18 > > at the moment, but did try 4.07 and 5.10 and saw similar behavior, > > also with pxelinux.0, so

On 07/10/2014 04:07 PM, Alexander Perlis wrote: > Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel > Boot Agent 1.3.81 (2.1 build 089). It gets network and launches > lpxelinux.0, I see the PXELINUX banner line, but there it hangs. > > I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead > use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >> lpxelinux.0, I see the PXELINUX banner line, but there it hangs. >> >> I tried both 6.03-pre18

Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to

Hi Gene, Am 05.07.2016 um 12:42 schrieb Gene Cumm: > Version 6.03. Is this a distribution build or fresh from the > binary/source archive from kernel.org without any running of 'make'? it's actually a freshly downloaded lpxelinux.0 from kernel.org. I get: $ md5sum lpxelinux.0 d77a175ea1a0a8c05b315d179992e1bd lpxelinux.0 >> nothing more. Sniffing revealed that there are

On 07/10/2014 06:39 PM, Gene Cumm wrote: > On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 07/10/2014 04:07 PM, Alexander Perlis wrote: >>> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >>> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >>> lpxelinux.0, I see the PXELINUX banner line,

On Tue, Jul 5, 2016 at 2:16 AM, Christof B?ckler <syslinux at zytor.com> wrote: > Hi all, > > I try to switch from pxelinux.0 to lpxelinux.0 as a PXE boot loader. With > pxelinux.0 I am able to boot my Linux kernel and initrd without any > problems. > > When I change DHCP option 67 to lpxelinux.0 this file gets loaded via TFTP. > On the client screen I see the welcome

I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some isolation/troubleshooting advice will be a good education no matter what.) To get to our PXE-launched tools from

Hello, after spending some time searching the mailing list and chatting via irc with some nice people i have to come to the list to ask for help. First thanks again to some IRC guys: genec for taking some time and to Ady2.. First some background. I need to boot a 250mb initrd to some(later all) of our thinclients , at the moment i?m using tftp but as we all know performance is bad. I

On Fri, Jul 11, 2014 at 5:49 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 04:31 PM, H. Peter Anvin wrote: >> >> On 07/11/2014 10:17 AM, Alexander Perlis wrote: >>> >>> >>> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that >>> there is only ARP traffic: a "gratuitous" ARP announcement by

Once upon a time, isdtor <isdtor at gmail.com> said: > We have a working PXE setup. I've tried to adapt it to UEFI as per > RHEL6 manual, but the client won't boot. I have BIOS+UEFI PXE boot set up, although it took some doing. I still use SYSLINUX for BIOS, but GRUB2 plus Red Hat's secure boot shim for UEFI. I never could get SYSLINUX's UEFI support working very