similar to: Installing image via PXE

Hi All, My PXE configurations works fine for a bios PXE (the server in legacy mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi but not the next one ldlinux.e64 Any ideas? Thanks Software> syslinux ver 6.3 atftp 7.1 Log server side >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over

On Thu, Mar 5, 2015 at 2:03 PM, Jorge Cisneros via Syslinux <syslinux at zytor.com> wrote: > Hi All, > > My PXE configurations works fine for a bios PXE (the server in legacy > mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi > but not the next one ldlinux.e64 > > > Any ideas? My latest personally-published binaries.

Hi, i'm trying to get my VIA Epia with VIA Rhine ethernet device to boot PXELinux. I have done this before, but now i can't get it to work. The machine loads pxelinux.0, i see some messages. But it fails just after trying reading the first config file (the one with the mac address). It kinda says this (transcribed): CLIENT IP: 192.168.1.23 MASK: 255.255.255.0 DHCP IP: 192.168.1.93

Hi, I am trying to setup my own PXE boot server. I tried several PXE bootable Linux-Distributions. For example if I use the ubuntu netboot image from [1] it works quit well but there are a few other images they do not work in my case e.g.: RIPLinuX [2]. A friend tested this image on his PXE boot server with success. I also checked the download with md5sum. In my case I can see the boot menu [3].

Hello, we have a problem with pxelinux and a specific hardware. In short: PXE starts, get and start the pxelinux.0 but can't get the configuration file. This problem belongs only to one new client. Other clients work in this environment with out any problem. The client is a HP xw4300 with the networkcard: ------------ vendor = "Broadcom Corporation" name = "NetXtreme BCM5752

I'm trying to network boot a thin client using pxelinux. I had this working about a year ago but have since reinstalled my OS (went from RH9 to FC2). I'm using atftpd. The thin client gets the dhcp address fine and requests pxelinux.0. Eventually, it just times out. Here's the relevant info from /var/log/messages: Oct 7 23:14:36 home atftpd[4717]: Advanced Trivial FTP server started

On 2014/3/10 ?? 05:48, Gene Cumm wrote: > 1) My assumption would be that the VMware virtualized AMD 79C970A > (PCNet32 driver; vlance virtualDev) lacks proper EFI64 support. > > 2) I have 0 speed issues using your VMX. If you only have two real > cores for this 2vCPU VM, you're choking it as the host needs time to > run. If you choke it, you mess with timers. If you mess

On 21.09.2015 12:06, Gene Cumm wrote: > On Mon, Sep 21, 2015 at 2:38 AM, Mathias Radtke <m.radtke at uib.de> wrote: >> >> On 18.09.2015 16:35, Gene Cumm wrote: >>> 1) This is actually a critical cusp size. Watch what tftpd you use or >>> you'll never get it all. The tftpd needs to support rollover. >>> Consider HTTP as it should be more capable

On Sat, Mar 8, 2014 at 2:05 AM, Steven Shiau <steven at nchc.org.tw> wrote: > Hi Gene, > Thanks. As you mentioned, atftpd has better logging, and my files are > smaller than 92 MB, so I switched to atftpd for testing. Now I could > find that somehow after bootx64.efi is downloaded by client, the next > ldlinux.e64 has never been fetched by client: > ====================

On 2014?03?08? 05:56, Gene Cumm wrote: > In /etc/vmware/vmnet8/dhcpd/dhcpd.conf I added the following: > > host 7x { > hardware ethernet 00:0C:29:38:6B:6E; > filename "e6/bootx64.efi"; > next-server 172.21.1.1; > # option vendor-encapsulated-options >

Hello SysLinux Team, I have recently installed version 5.0of SysLinuxwhat may be I should not have done so. Now my problem is, that everytime I start via PXE (gpxe) I only get the boot: prompt and not the menu as expected (all was working fine with previous versions incl 4.06) In the server log I can see atftpd serving some files to the workstation but not as before where it tried to find the

Hello, we have the following problem: - a new Dell Optiplex 740 boots pxelinux.0 - loads the kernel - start to load the miniroot.gz and crashs after loading about 1/5 of the miniroot The tftpd messages are: Feb 21 14:48:32 srv006 atftpd[26225]: Advanced Trivial FTP server started (0.7) Feb 21 14:48:32 srv006 atftpd[26225]: Serving /linux/pxelinux.0 to 10.10.100.113:2070 Feb 21 14:48:32 srv006

Hi, I've been struggling with this problem for the last couple of hours and am nowhere near solving the problem. I am trying to run a tftp server in a chroot jail. Now perhaps I am being paranoid, but I would like to have it launched from within its own jail even if it supposedly does a chroot itself and runs with a parameterizable user. I downloaded the atftp-server package and tried

On 2014?03?08? 20:57, Gene Cumm wrote: > Please try 6.03-pre6. I see a regression on 6.03-pre7 with EFI64 netboot > >> > Another thing you I'd like to mentioned is, after bootx64.efi was >> > downloaded, the next download for ldlinux.e64 was about 15 secs later. >> > Is that normal? > When it's successful for me, it takes 0.2s from the beginning of >

I am trying to install Debian GNU/Linux onto a floppy-less CD-ROM-less Shuttle XPC SS40G with an AMD Athlon installed. This machine has an on-board ethernet controller (RealTek 8139), but I had also added an Intel Pro/100 Ethernet card, and I am trying to boot via that additional Ethernet card. Following the instructions at: http://www.debianplanet.org/node.php?id=818 I obtained the stock

Hello Andreas, Andreas Gruenbacher wrote: > Hi, > > On 01/17/2015 12:57 AM, Sebastian Herbszt wrote: > >> On 01/16/2015 12:19 AM, Sebastian Herbszt wrote: > >>> Andreas Gruenbacher wrote: > >>>> "Loading <FILE>... failed: No such file or directory" when the TFTP > >>>> server replies with "Permission denied"

Hello I recently get a Cisco 7940G IP Phone and I try to make several things with it and I en counted many difficulties: 1.) I tried to unlock the phone and to set manually IP Address, Netmask, Gateway etc. I don't get any luck. 2.) I tried to upgrade firmware like they said with tftp server... I downloaded: P0S3-08-11-00.zip and I uncompressed the files in tftpboot directory. I don't get

It seems that tftpd-hpa is more suitable at serving arbitrarily large files (greater than 65535 blocks long; with pxelinux.0 using a default block size of 1408 this is 92,273,280 bytes) as atftpd will complain in the log stating "Requested file to big, increase BLKSIZE". I saw that a while back HPA mentioned that atftpd was probably more scalable (number of clients) while tftpd-hpa is

I'm interested to find out how many people are running tftp-hpa versus atftpd. I'm almost a bit surprised in how many people seem to be using tftp-hpa; for modern Unix systems (including Linux), I would in general assume atftpd to be a better choice. If you have tried both and specifically chosen (as opposed to "it was already installed", etc.) I'd be interested in

Hi... I''m interested to find out how many people are running tftp-hpa versus atftpd. I''m almost a bit surprised in how many people seem to be using tftp-hpa; for modern Unix systems (including Linux), I would in general assume atftpd to be a better choice. If you have tried both and specifically chosen (as opposed to "it was already installed", etc.) I''d