search for: oroms

Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with one Dell system and pxelinux: The keyboard does not properly work. The computer boots, I press F12 to select the boot device, then I select the network card. Up to that point the keyboard works fine. Then pxelinux is booted, and I use menu.c32 to display a menu (or vesamenu.c32 - same result). Now the keyboard does not

On Jun 6, 2013 5:42 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: > > 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

Shantanu, let's continue here. You first noticed this on a Dell OptiPlex 755. I think it covers all Dell OptiPlex/Latitude/Precision models that are PCIe based with Intel LoM (LAN on motherboard) utilizing the BIOS PXE OROM, based on the similarity of these systems. The symptoms are that PXELINUX requests pxelinux.cfg/<UUID> by TFTP (but it might not strictly be a TFTP issue) when not

On Wed, Jun 5, 2013 at 9:58 PM, upen <upendra.gandhi at gmail.com> wrote: > I copied pxelinux.cfg/default to pxelinux.cfg/<IP to HEX> and it looks this > step resolved the earlier error. Next I get failed to load com32 file > vesamenu.c32 while that file exists in /tftplinux/linux-install. Is vesamenu.c32 from 5.10? -- -Gene

On Wed, Oct 7, 2015 at 6:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> -----Original Message----- >> From: Gene Cumm [mailto:gene.cumm at gmail.com] >> Sent: Wednesday, October 07, 2015 4:43 PM >> To: For discussion of Syslinux and tftp-hpa; Geert Stappers >> Subject: Re: [syslinux] UEFI: Failed to load ldlinux.e64/ldlinux.e32 >> >> On Wed, Oct

On Thu, Jun 6, 2013 at 7:02 PM, upen <upendra.gandhi at gmail.com> wrote: > On Thu, Jun 6, 2013 at 5:38 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Jun 6, 2013 5:42 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: >> > On 06/06/2013 02:40 PM, upen wrote: >> > > >> > > Some odd things I observed just now. >> > >

On 06/06/2013 02:00 AM, Gene Cumm wrote: > On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello, >> >> First, this setup works fine without any error in syslinux 4.06 as show >> below. >> >> For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] >> directories (~2MB each) are uploaded

On Sun, Sep 13, 2015 at 3:46 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Sep 12, 2015 at 06:56:04PM -0400, Gene Cumm via Syslinux wrote: >> On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm wrote: >> > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers wrote: >> >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c >>

On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> This is sounding like dropped/intercepted packets. Could we get some >> details on the client (make/model of computer/motherboard, same for >> NIC, PXE OROM details)? Is it connected to the same physical switch >> as the DHCP/TFTP server? Any chance that the physical switch that the

Ady Ady via Syslinux wrote: > >> However, I have just tested the exact same boot procedure using a Dell >> laptop (Latitude 7480) - and it all worked without a problem - that is, >> syslinux.efi and ldlinux.e64 were downloaded without a problem - and >> from a tcpdump, there was *no* DHCP transaction between downloading >> syslinux.efi and ldlinux.e64 >>

Hi there, We had to setup a pxelinux on a new server (windows 2012) and used the latest release of pxelinux 6.0.2. Everything went ok on my first client test machine : dell optiplex 740. Pxe was really fast (vesamenu with large background image was appearing in less than 3 secondes) But on different client machine i got different results : On optiplex 790 (core i5 with intel 82579 nic) and

Gene wrote: > On Wed, Oct 7, 2015 at 7:58 AM, Ashish, Shivendra <shivendra.ashish at hpe.com> wrote: >> Still getting error >> >> Disable uderdefault address > > 1) I'm presuming this is actually "disable UseDefaultAddress" > >> Core_udp_sento: udp->configure unsuccessful >> >> This message lopping in console > > Not

Gene Cumm wrote: > > > > I am attempting to chainload a file from TFTP. I have the following > > lines in the configuration file: > > > > LABEL WDS1 > > Menu LABEL WDS1 > > kernel pxechn.c32 > > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > > > > The TFTP server at 10.14.141.150 is operational and wdsnbp.com is

Yes on optiplex 790 i upgraded from A07 to A18 (there was a nic upgrade) but it didn't change anything.. On optiplex 380 i upgraded from bios A01 to A07(don't know if upgrade contained pxe or not)... I tried, lpxelinux.0 and it wasn't faster. Only v4.07 helped on these machines. Tomorrow, i will give a try with 6.03pre2. In wireshark, i saw no errors, the packet length was the

Gene Cumm wrote: > >> > > >> > I am attempting to chainload a file from TFTP. I have the following > >> > lines in the configuration file: > >> > > >> > LABEL WDS1 > >> > Menu LABEL WDS1 > >> > kernel pxechn.c32 > >> > append 10.14.141.150::boot\x86\wdsnbp.com -W -o 66.x=0a:0e:8d:96 -S > >>

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at

I've started using pxe servers for OS deployment at my organization and I'm trying to get chainbooting working but I seem to run into an issue that causes a hard lock up of a system. MENU BEGIN ^1. Boot Satellite PXE LABEL Satellite PXE KERNEL pxechain.com APPEND (Server IP Address)::pxelinux.0 Is part of my config file for my main pxe server to boot over to the

On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > Hello, > > First, this setup works fine without any error in syslinux 4.06 as show > below. > > For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] > directories (~2MB each) are uploaded ready for test. > > As said before, this is tested on qemu-1.5.0 +

On Thu, Jun 6, 2013 at 3:48 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Thu, Jun 6, 2013 at 1:01 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> >> >> This is sounding like dropped/intercepted packets. Could we get some >> >>