similar to: Problem with cascading configurations

Displaying 20 results from an estimated 6000 matches similar to: "Problem with cascading configurations"

2019 Sep 05
2
Problem with cascading configurations
Am 04.09.2019 um 22:18 schrieb Ady Ady via Syslinux: >> I am trying to setup a PXE server for two Debian releases (stretch and >> buster) using their respective network boot images (netboot.tar.gz), >> which I extracted into subdirectories of the TFTP server's root directory: >> >> ??? ??? debian >> ??? ??? ??? buster >> ??? ??? ??? ???
2019 Sep 04
0
Problem with cascading configurations
> I am trying to setup a PXE server for two Debian releases (stretch and > buster) using their respective network boot images (netboot.tar.gz), > which I extracted into subdirectories of the TFTP server's root directory: > > ??? ??? debian > ??? ??? ??? buster > ??? ??? ??? ??? debian-installer > ??? ??? ??? ??? ldlinux.c32 -> >
2014 Jun 16
5
Chainload pxelinux from pxelinux and pass parameters or change root dir?
On 06/16/2014 10:41 AM, Gene Cumm wrote: > [...] Initially I wrote pxechn.c32 to allow further > modifications of the DHCP data [...] Awesome! In fact, this might allow us to install an automatic 'http' prefix on all subsequent requests, to avoid slow tftp --- or is that a bad idea, and/or is there a way to default all transfers to http without using pxechn and
2009 Aug 05
6
Could not find kernel image : vmlinuz
hello list, I am trying to setup a PXE boot server. Below are the details of the server: OS : Fedora Core 5 32-bit DHCP : dhcp 4.1 TFTP : tftp-hpa-5.0 Number of NIC : 2 eth0 : IP : 192.168.100.17, Subnet : 255.255.255.0, Gateway : 192.168.100.1 eth1 : IP : 192.168.1.1, Subnet : 255.255.255.0, Gateway : 192.168.1.1 Client: OS : None, fresh machine Number of NIC : 2 Intel Gigabit eth0 of server
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
2013 Jun 17
1
Cisco SSCP to SIP
Hi all, I'm trying to convers some Cisco SSCP phones to the SIP formware. The phone boots, I see it tries to fetch a bunch of files on my TFTP: Jun 17 09:37:45 firewall dnsmasq-dhcp[21202]: DHCPACK(eth2) 192.168.10.103 6c:50:4d:da:f0:67 SEP6C504DDAF067 Jun 17 09:38:10 firewall in.tftpd[22666]: RRQ from 192.168.10.103 filename CTLSEP6C504DDAF067.tlv Jun 17 09:38:10 firewall in.tftpd[22666]:
2002 Aug 17
1
Pxelinux: File not found during boot, HELP
Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz
2007 Oct 20
1
kernel stops booting process
Hi I have a problem with our pxelinux server, the server works for month without any problems. We use syslinux-3.51 version on an FC2 with in.tftp. Today I want to install a new server, but it fails after loading the kernel and booting stopped with this message ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered
2009 Jun 12
4
tftp open timeout but with no server side errors
Background, Client - realtek rtl8111c tftpd version is 5.0 options on use -l -v Client: PXE-EX32 TFTP Open Timeout Server: Jun 12 10:48:38 damar in.tftpd[30132]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:48:48 damar in.tftpd[30133]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:49:24 damar in.tftpd[30134]: RRQ from 192.168.1.107 filename gpxelinux.0 Jun 12 10:50:36 damar
2015 Oct 11
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
On Oct 11, 2015 1:26 AM, "Michael Glasgow" <glasgow at beer.net> wrote: > > Gene Cumm wrote: > > >> My test x86-64 binaries: > > >> > > >> https://sites.google.com/site/genecsyslinux/sl604p0g17-x64.tgz?attredirects=0&d=1 > > > > On Fri, Oct 2, 2015 at 4:46 PM, Derrick M <derrick.martinez at
2015 Oct 07
4
UEFI: Failed to load ldlinux.e64/ldlinux.e32
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,
2013 Dec 20
3
syslinux.efi hangs during PXE boot
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
2006 Mar 17
3
TFTP problems on FC4
Greetings to all. I am hoping someone can help me out with a problem I am having getting my Cisco phones, 7960s and 7940s, to download the appropriate files from our TFTP server. The TFTP server is running on Fedora Core 4. The TFTP server appears to be setup properly: service tftp { socket_type = dgram protocol = udp wait =
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
On 2014/3/7 ?? 05:23, Gene Cumm wrote: > On Thu, Mar 6, 2014 at 10:55 AM, Bryan Romine <bromine1027 at gmail.com> wrote: >> Sorry for the confusion, I am actually using 6.02. It turns out that I was >> trying to use the 32-bit efi binary to load 64-bit kernels. I switched to >> using "syslinux64.efi" but it hangs during boot, just before loading the
2002 Oct 29
2
wierd problem concerning directory, symlinks, chroot
hello, i'm having a wierd problem with 0.31 tftpd-hpa. i'm using xinetd, with this config: service tftp { disable = no socket_type = dgram wait = yes user = root log_on_failure += USERID bind = 10.13.0.254 server =
2005 Jun 05
2
pxelinux and DISPLAY
I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from
2004 Oct 18
1
Display file problem with PXELINUX
Hi All, I am having trouble with pxelinux display file not calling the correct name to retrieve the graphic image. I guess the filename length is determained the first time ^X is used, and doesnt re-size the field name on next call. For example when cycling through F1 - F2 - F3 the f1 image displays fine, and its the longer name f2 & f3 just display the text and no image, output from
2006 May 17
1
Weird Error When upgrading 7960G to 8.2
Hello All, I just picked up 10 new 7960G's and having a hardtime upgrading the firmware on them. We already have 30 or 40 of these phones in production. Typically when I get a new phone, I just plug it into the voice vlan and it auto grades to the firmware in OS79XX.txt. Now whats happening is im getting a weird error during the reading of that file. Here's the output from the TFTP
2015 Jul 02
1
UEFI/EFI booting and constantly asking for ldlinux.e64
On 7/2/2015 3:42 AM, Gene Cumm wrote: > This has me thinking your build system has a negative interaction. > There should be at least 2 lines of output prior to loading > ldlinux.e64. gcc less than 4.7 is one problem for the EFI binaries. This could be my problem. I'm using gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC). I will attempt from a new version of gcc and
2007 May 28
5
Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned.
Hi ALL Has anyone any insight as to why RedHat Enterprise Level 5 is broken as far as PXE booting is concerned. Is there a Protocol communication problem ???????? Are there alternative tftp-severs that work for the RHEL5.. It seems: the PXE CLIENT when booting cannot access files in the "pxelinux.cfg" dir RHEL4 works just fine !! ( kernel 2.6.9-22.EL) with