similar to: EFI Clients Unable to Load kernel/initrd Not Stored on PXE Server

On Fri, Apr 6, 2018 at 3:28 PM, Nathan.Wittie--- via Syslinux <syslinux at zytor.com> wrote: > Issue Statement: > PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and

Thanks. That gets me further. Syslinux 4.07 loads from Syslinux 6.04 now. For some reason though it reread D:\syslinux.cfg instead of D:\ESXi\syslinux.cfg . I don't see the directive that tells Syslinux(4) to look in the sub directory for syslinux.cfg instead of the root. The only thing (right now) I can see that is different, is my D:\syslinux.cfg is one file while yours loads other files

Le 18/02/2019 ? 18:58, Tru Huynh a ?crit?: > On Mon, Feb 18, 2019 at 06:36:10PM +0100, Patrick B?gou wrote: > ... >> - PXE boot start and the desktop load the kernel and the inirtd file >> >> - the kernel is booted and at this time the led of the network switch >> goes down for the port used by the desktop. >> >> - then I have a message "no carrier

I'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

Hello Ady, thanks for getting back to me. On Wed, May 22, 2019 at 01:33:50AM +0000, Ady Ady via Syslinux wrote: > > Is there something I could do > > A_ Instead of 6.03, try 6.04-pre1 (not pre2 and not pre3, but pre1). > Please remember to change _all_ related files to the same version, not > just lpxelinux.0. > > Alternatively (and in many cases, even better) you

> Is there something I could do A_ Instead of 6.03, try 6.04-pre1 (not pre2 and not pre3, but pre1). Please remember to change _all_ related files to the same version, not just lpxelinux.0. Alternatively (and in many cases, even better) you could try current Debian's "Unstable" packages, which are "more up-to-date" than 6.04-pre1. B_ In the configuration file,

> > SYSLINUX 6.03 CHS 6.03-pre1 ... > > Failed to load ldlinux.c32 > Boot failed: please change disks and press a key to continue. > First, let me clarify that all the scripts and procedures in the Clonezilla site are not related to this official Syslinux mailing list or to The Syslinux Project. They are done by the Clonezilla team. Now that I know you are working

Hi, I am currently trying to replace our companies elilo UEFI PXE boot with syslinux. I compiled all the needed files and the DHCP distributes them fine to the requesting client. However when I try to boot our companies miniroot the DHCP serves the file, but it seems like it never finishes. The image is generated with the following command: find . | grep -v 'name'.bz2 | cpio -o -H newc

On Mon, Oct 26, 2015 at 9:47 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Oct 26, 2015 at 2:09 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: >> I'm still trying fruitlessly to get some sort of local disk boot from >> syslinux EFI to work... using the 6.03 modules. Tried various >> combinations of configurations on Gene's test

> > > Ady, before responding to you further, I'll ask you now to take onje > more (fresh) look at this thread that I started over in the GParted > forums: > > http://gparted-forum.surf4.info/viewtopic.php?pid=31834 > > Please note that I have now followed-up on myself and that I have added > quite a lot of new & additional information. > > It now

Hi! I am having same issue but I am running Ubuntu v16.04. It does not mount during boot, but works if I mount it manually. I am running the Gluster-server on the same machines (3 machines) Here is the /tc/fstab file /dev/sdb1 /data/gluster ext4 defaults 0 0 web1.dasilva.network:/www /mnt/glusterfs/www glusterfs defaults,_netdev,log-level=debug,log-file=/var/log/gluster.log 0 0

Michael, If you actually get virtualbox PXE booting via UEFI, please let us know how. I spent about two weeks trying to get this to work. This virtualbox PXE booting via UEFI appears so new, it was poorly documented. As of two months ago, when I was doing all this testing. Allegedly, it has experimental support for UEFI PXE boot, if you have Intel NICs. (It uses the UEFI boot code from the

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit

On Mon, Aug 21, 2017 at 2:49 AM, Cesar da Silva <thunderlight1 at gmail.com> wrote: > Hi! > I am having same issue but I am running Ubuntu v16.04. > It does not mount during boot, but works if I mount it manually. I am > running the Gluster-server on the same machines (3 machines) > Here is the /tc/fstab file > > /dev/sdb1 /data/gluster ext4 defaults 0 0 > >

Hello, I am using lpxelinux.0 (latest stable version 6.03, using the official binaries from kernel.org) to kickstart servers as http transfers really helps over links with poor latencies... These servers are being booted in legacy mode, not in UEFI. This has worked very well until recently. Starting with RHEL 7.5, on some servers, we would see the machine rebooting while pxelinux is in the

Hi there, I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the

It looks like it is more like the issue in bug #26. In the tcpdump I can see the client attempt to RRQ the kernel but the client itself reports "No file found." I am having similiar issues as reported in both bug reports with getting Syslinux 6.02 to work as in syslinux64.efi gets pulled but then the client gets stuck on ldlinux.e64. Can I use http/nfs instead after syslinux64.efi gets

Hi! Please see bellow. Note that web1.dasilva.network is the address of the local machine where one of the bricks is installed and that ties to mount. [2017-08-20 20:30:40.359236] I [MSGID: 100030] [glusterfsd.c:2476:main] 0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.11.2 (args: /usr/sbin/glusterd -p /var/run/glusterd.pid) [2017-08-20 20:30:40.973249] I [MSGID: 106478]

> > Sounds like you may want to contact Cisco... > > And tell them what? There's a bug in their PXE/BIOS stack somewhere? Just some random and humble thoughts... Perhaps it would be worth some additional tests? Maybe a test with pxelinux.0 version 4.07? And using "LINUX", not "KERNEL": ### DEFAULT biginitrd PROMPT 0 LABEL biginitrd LINUX mykernel INITRD

Hello, On Wed, Jun 19, 2019 at 11:15:36PM +0000, Ady Ady via Syslinux wrote: > Just some random and humble thoughts... > > Perhaps it would be worth some additional tests? > > Maybe a test with pxelinux.0 version 4.07? And using "LINUX", not > "KERNEL": > > ### > DEFAULT biginitrd > PROMPT 0 > LABEL biginitrd > LINUX mykernel > INITRD