similar to: Unable to PXE boot

Displaying 20 results from an estimated 1000 matches similar to: "Unable to PXE boot"

2015 Feb 05
0
Unable to PXE boot (on new setup)
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 >
2015 Feb 05
1
Unable to PXE boot (on new setup)
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
2015 Feb 05
0
Unable to PXE boot
> /diskless/pxelinux.cfg/default > --- > DEFAULT /gentoo-x86_64/boot/kernel-3.14.14-gentoo > APPEND ip=dhcp ro rootfstype=nfs root=/dev/nfs > nfsroot=10.0.0.11:/diskless/gentoo-x86_64 > init=/linuxrc That pxelinux.cfg/default seems "tolerable" for older versions, but not for Syslinux 5+. Is this an inadequate copy of the actual content? Or is it really a
2010 Feb 08
2
Proposals for making configure_from_network function works in f13
Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's
2004 Jun 10
0
TFTP: error code 2 received - Only absolute filenames allowed
Hey ppl, This is probably something very basic i'm doing wrong but I can't seem to get aorund it after reading the man page, it goes between error 2 and 1, im trying to tftp from a cisco router to my linux box. my in.tftpd.conf file looks like this: INTFTPD_PATH="/usr/tftp" INTFTPD_OPTS="-l ${INTFTPD_PATH}" and ive done a chmod 777 on the above path just to be 100%
2015 Feb 05
0
Problems with EFI PXE boot on Hp DL380p Gen9
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
2015 Feb 05
4
Problems with EFI PXE boot on Hp DL380p Gen9
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 -
2002 Feb 04
3
Allwell doesn't respond to OACK with ACK in TFTP
I'm trying to network-boot a GCT Allwell set-top box without success. My frustration level is high. The problem seems to be that the Allwell is sending a RRQ with an option. tftp-hpa responds with an OACK, and waits for the corresponding ACK from the Allwell. The Allwell never sends that ACK, but instead continues with the same RRQ until timeout. Having read RFC1782, this makes me think
2014 Jun 25
2
testing out 6.03 network booting...
On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to
2004 Jun 07
2
run-init warning
Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa
2014 Jun 19
5
testing out 6.03 network booting...
Hi all, wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. below are results of me testing - i did each a few times to make sure they are valid results. hope it helps identify something that's gone awry ? so far, 6.03 pre11 and pre13 (excluding efi32) seem most
2014 Jun 25
3
testing out 6.03 network booting...
> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be
2023 Apr 03
1
pxelinux takes too long trying all the config file options
Hi All, I have a situation where I want to netboot and ONLY use pxelinux.cfg/default. It seems to take FOREVER for pxelinux to try all of the config file file options before falling through to default .... trying each possible combination multiple times ... increasing the wait time everytime it doesn't get a response. >From my log: Apr 2 19:53:17 helium tftpd[3372124]: tftpd: trying to
2015 Oct 02
6
UEFI: Failed to load ldlinux.e64/ldlinux.e32
I have a patch that I think may help your situation of syslinux.efi being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if any of you are using an EFI ia32 platform). The basics are that we try to enable UseDefaultAddress as it helps certain clients with routing and works on numerous other clients. If we timeout on receiving a packet and have never received any packets, disable
2015 Feb 26
2
Re: Broken OS when booting rootfs from 9p share
On Tue, Feb 24, 2015 at 11:56:50PM +0100, Olivier Mauras wrote: > > > On Tue, 2015-02-24 at 16:05 -0500, Laine Stump wrote: > > On 02/24/2015 03:37 PM, Olivier Mauras wrote: > > >> Hello, > > >> > > >> I've been trying to boot a VM with the rootfs being a 9P share from > > >> the host. The VM OS is centos 7. > > >>
2006 Sep 06
3
Intel Boot Agent: PXE-E32: TFTP open timeout for correctly configured tftp-hpa
Hello. In my case I can successfully boot up my Thinkpad X32, but the same configuration doesn't work for my desktop computer with Intel network card, with Intel Boot Agent 2.2 DHCP server is 10.0.0.1, tftpd (used tftp-hpa) runs on 10.0.0.32. netstat told me the daemon listen to 69 UDP port just fine. running tftp in commandline also shows it works (retrieve pxelinux.0 less then 1 second).
2014 Aug 27
1
[PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >
2014 Aug 27
1
[PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
On Wed, Aug 27, 2014 at 10:34 AM, Christopher Covington <cov at codeaurora.org> wrote: > On 08/27/2014 12:19 PM, Andy Lutomirski wrote: >> On Wed, Aug 27, 2014 at 9:13 AM, Christopher Covington >> <cov at codeaurora.org> wrote: > > Virtme looks interesting. If it's any use, here is my modest QEMU command line > collection. > >
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Wed, Oct 7, 2015 at 2:33 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Tue, Oct 06, 2015 at 10:27:15PM -0400, Gene Cumm via Syslinux wrote: >> > On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> >> >> I have a patch that I think may help your situation of syslinux.efi >> >> being unable to load
2015 Oct 07
5
UEFI: Failed to load ldlinux.e64/ldlinux.e32
> On Fri, Oct 2, 2015 at 4:07 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> I have a patch that I think may help your situation of syslinux.efi >> being unable to load ldlinux.e64/ldlinux.e32 (though I don't know if >> any of you are using an EFI ia32 platform). >> >> The basics are that we try to enable UseDefaultAddress as it helps >>