similar to: intermittent pxe failure

On Thu, Feb 05, 2015 at 11:06:36PM +0100, Geert Stappers via Syslinux wrote: > On Thu, Feb 05, 2015 at 02:27:57PM -0600, Lane via Syslinux wrote: > > When trying to boot, the 1950 node displays (though both diskless types > > having same issue): > > --- > > > > CLIENT MAC ADDR: 00 13 72 F9 54 41 GUID: 44454C4C 4A00 104D 8058 > > B4C04F534231 > > CLIENT

Sorry for makeing a new post, but I already erased my old mails. In the following I describe my Server-Situation (Sorry for my bad english) * I have a eisfair server http://www.eisfair.org with version 1.6.1 (newest) * I have a ISC-DHCPD 3 Server running * I have a TFTP Server running http://www.kernel.org/pub/software/network/tftp/ * I have Samba installed and a DNS Server is running My

I am having a problem while trying to download anything from a recently configured tftp boot server. Here are the configuration for the dhcpd.conf option domain-name="domain.com"; default-lease-time 900; max-lease-time 1800; ddns-update-style none; authoritative; allow bootp; allow booting; option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2

On Thu, Feb 05, 2015 at 02:27:57PM -0600, Lane via Syslinux wrote: > When trying to boot, the 1950 node displays (though both diskless types > having same issue): > --- > > CLIENT MAC ADDR: 00 13 72 F9 54 41 GUID: 44454C4C 4A00 104D 8058 > B4C04F534231 > CLIENT IP: 10.0.1.1 MASK: 255.255.0.0 DHCP IP: 10.0.0.11 > GATEWAY IP: 10.0.0.1 > PXE-E32: TFTP open timeout >

I'm currently using Microsoft DHCP to enable PXE booting. I've set options 66 and 67 for the relevant scopes and it's all fine and dandy. However, UEFI machines won't initiate PXE boot, they don't seem to recognize the options. Is there another setting that need to be set? And how to I filter UEFI clients so I set option 67 to the right value (lpxelinux.efi)? -- Alexandre

I'm replacing the master node in a cluster and having issues PXE booting the diskless nodes. The current master works fine, but the new node to replace the current node which has the same setup is having the issues. The hardware is: Dell r920 (new master node, UEFI) Dell r620's (diskless, BIOS) Dell 1950's (diskless, BIOS) When trying to boot, the 1950 node displays (though both

Hello, On Sat, Dec 21, 2013 at 6:07 PM, Geert Stappers <stappers at stappers.nl>wrote: > Op 2013-12-20 om 12:05 schreef Roman: > > Hi, > > > > I'm trying to boot 64bit version of syslinux.efi through network. But > > booting is freezes with following message: > > Getting cached packets > > My IP is X.X.X.X > > That is a very strange IPv4

Hi, I'm trying to boot 64bit version of syslinux.efi through network. But booting is freezes with following message: Getting cached packets My IP is X.X.X.X the last file that was requested through tftp is syslinux.efi. I'm using precompiled binary from official syslinux-6.02.tar.gz. Here is the dump in ASCII - http://brom.in/dumps/syslinux-20131220.txt Any help is appreciated.

On Thu, Feb 05, 2015 at 07:02:07PM +0100, Holger Baust wrote: > Hello. > > We are using pxelinux for years to boot Linux via PXE since years. > Since EFI is spreading, I changed configuration to be able to boot EFI > systems. > > The "Client": > - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available > - NIC used for booting: HP Embedded LOM 331i

Hello. We are using pxelinux for years to boot Linux via PXE since years. Since EFI is spreading, I changed configuration to be able to boot EFI systems. The "Client": - HP Proliant DL380Gen9 System FW: 1.21 11/03/2014, latest available - NIC used for booting: HP Embedded LOM 331i (Broadcom BCM 5719/ tg3), FW: 5719-v1.38 The Server: - ISC-DHCP with tfpd-hpa running on Debian 6.x -

>> Hi, >> >> We have some problems while network booting thin clients. The type is T5540. >> >> At this moment we are using pxe linux 6.03. >> >> The systems are booting correctly with pxe linux version 6.03-pre14. >> We have seen the same error with version 6.03-pre9. >> >> The error message: >> >> Failed to load ldlinux.c32

On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > Sounds like it's losing lots of packets. > > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > It is TCP to port 80, but that

On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 06:18 schreef upen: > > On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > > > The tcpdump[1] shows strang HTTP

Hello, On my previous TFTP server I had logging. I did see all requests in logfiles. On my current TFTP server I have also added the options '-v -v -v', but nog logging. At least I can't find it them in /var/log/*/* Where does tftpd-hpa writes it's logging? Groeten Geert Stappers -- Leven en laten leven

On Sun, Jun 21, 2015 at 11:12:07AM -0700, syslinux-bot wrote: > Commit-ID: 38e861ebf45a804bc5fbd74d9c19292822c84487 > Gitweb: http://www.syslinux.org/commit/38e861ebf45a804bc5fbd74d9c19292822c84487 > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sat, 20 Jun 2015 21:17:18 -0400 > Committer: Gene Cumm <gene.cumm at gmail.com> > CommitDate: Sat, 20

Op 2013-11-08 om 10:48 schreef H. Peter Anvin: > Thank you for posting the pcap files, by the way. Analyzing them in > Wireshark is so much nicer than reading the text output of tcpdump. Fetch the new capture with wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi, but nothing after that. As if

Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > On 06/06/2013 02:40 PM, upen wrote: > > > > Some odd things I observed just now. > > 1. Since yesterday, I have been reseting the client box from Virtualbox VM > > menu (Reset option). This always showed me com32 vesamenu.c32 > > message. > > 2. Some time ago, I decided I power off the client VM(

Hi, my client pc hangs on pxelinux before starting to fetch the linux kernel. It hangs after printing the ip information row. No traffic is observed at this point on the network. The pxelinux is transferred to the client through a tftp server and with no problems. What options do I have to proceed from this point and try to find out where the problem is? Thanks, Firas. -- Firas Swidan, PhD

On Sat, Sep 30, 2017 at 08:53:09PM -0400, Gene Cumm wrote: > On Sep 30, 2017 8:47 PM, Bruce Ferrell wrote: > > > > I've recently seen something to the effect that the pxelinux.0 boot loader > > has some limit of 45MB. Is this correct or some misunderstanding? > > No, I've loaded 90MB files. The catch is often TFTP block number rollover. My first thought was:

--- On Thu, 5/31/12, Geert Stappers <stappers at stappers.nl> wrote: > > P.S. > > As usual, eagerly (and patiently) waiting for the HTTP > bits to start > > working properly! ;) :) > > How should I read that??.? Does it mean "I'm waiting to > get time to test" > or do you mean "tested, it doesn't work yet"??? > Anyway, please