similar to: Can't get initrdfile= or initrd+= to work

Hi folks My ultimate goal is to be able to add an initramfs to the end my syslinux.cfg resulting in an additional initramfs being loaded when the system boots. So I need to work out how to get initrd+= to work. I?ve been trying for days now everything I possibly can to get initrd+= to work but nothing I do works. I've also been trying to get initrdfile= to work but no success with that

Attached are 4 patches against Syslinux 4.06 providing two new options for the linux.c32 ComBoot32 module. If we are shifting gears towards 4.10 or 5 any time soon, feel free to let me know and I'll attempt to apply the patches to those and to deal with any conflicts. You can merge these commits onto your 4.06 from my 'multi_initrd' branch at:

On 10/11/14 14:36, Bernd Eggenm?ller wrote: > is there a way to boot a Windows PE image over PXE in UEFI mode. > If there is one, how do I write the entry in the syslinux.cfg file? I don't know the syslinux answer to this, but you can definitely do it via iPXE and wimboot: see http://ipxe.org/wimboot for instructions. Michael

Hi, is there a way to boot a Windows PE image over PXE in UEFI mode. If there is one, how do I write the entry in the syslinux.cfg file? Best regards, Bernd Mit freundlichen Gr??en Bernd Eggenm?ller Entwicklung baramundi software AG Beim Glaspalast 1 86153 Augsburg bernd.eggenmueller at baramundi.de www.baramundi.de Fon: +49 (821) 5 67 08 - 579 Fax: +49 (821) 5 67 08 - 19 Vorstand:

I know everyone is itching to test out another prerelease, and there's been quite a lot of activity since the last one. The shortlog is appended below. The feedback from testing the previous prereleases has been really constructive, so thanks to everyone for that. That feedback has been addressed in some of the commits listed below, but it's not all bug fixes, we've also got some new

On 25/11/14 02:01, Ady wrote: > --- a/src/cmdline.c Fri Nov 07 02:27:56 2014 > +++ b/src/cmdline.c Mon Nov 24 15:18:15 2014 > @@ -104,6 +104,8 @@ > /* Ignore unknown initial arguments, which may > * be the program name. > */ > + } else if ( strcmp( key, "initrdfile") == 0 ) { > + /* Ignore this keyword so to make this kernel work with sylinux

Hi folks, There are enough changes on the 'firmware' branch to warrant another prerelease. Things that jump out are the changes to update the current working directory when executing syslinux.efi (previously .c32 failed to load if installed to a non-standard directory such as /boot/syslinux, because the current working directory wasn't correct), the realloc() fix from Shao and a new

To start, I know I need to upgrade SYSLINUX, but since we are using the CMenu's it's not that easy of an upgrade. I have been (slowly) working on a new iPXE/pxelinux 4.04 install that I am migrating to. However, I have an interesting problem. Using any of the examples I have seen, I can not make pxechain.com work. "pxechain.com ::/path/pxelinux.0" "pxechain.com

I am trying to load a WinPE boot image using wimboot, and failing. The 3 files appear to load successfully (the output "Encapsulating ... <filename>" is displayed for each file, taking a few minutes on the .wim file as expected based on the size), but then the workstation just reboots, and I don't see output after that. Has anyone successfully loaded WinPE using wimboot with

Adding an option for initrdfile= boot argument to be ignored by wimboot worked just fine. They can add this patch, which is probably most sane, or syslinux could add the INITRDFILE configuration option instead of having to append the option for linux.c32 wimboot-2.4.0/src/cmdline.c @ Line ~107 } else if ( key == cmdline ) { /* Ignore unknown initial

> -----Original Message----- > From: Luke Ledgerd > Sent: Monday, November 24, 2014 1:10 PM > To: 'syslinux at zytor.com' > Subject: Windows PE booting without chainloading ipxe > > I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. > http://ipxe.org/wimboot > > MENU LABEL Windows 8.1

Hi, Hopefully you someone can tell me what I'm doing wrong. First, the code. I placed this at the bottom of the main loop in com32/modules/disk.c as a simple test of writing to the disk: printf(" Host bus: %s, Interface type: %s\n\n", d->edd_params.host_bus_type, d->edd_params.interface_type); zero_buf = calloc(1, d->edd_params.bytes_per_sector); for(int

I have an interest in booting Windows PE from PXELinux, and it seems that wimboot from ipxe project is the solution. http://ipxe.org/wimboot MENU LABEL Windows 8.1 Enterprise PE Rescue (wimboot) com32 linux.c32 /wimboot APPEND initrdfile=/windows/win81/bootmgr,/windows/win81/boot/bcd,/windows/win81/boot/boot.sdi,/windows/win81/sources/boot.wim The initrdfile= is supported in Syslinux from

Hey guys, I can't seem to figure out how to debug a COM32 app with GDB under qemu. I start "qemu -s" and then "gdb hello.elf ; target remote:1234" but can't set any breakpoints that work. I"m using syslinux4 (pathbased from the repo). Can anyone verify that they can use qemu+com32+gdb with something as simple as com32/samples/hello.c32 ? Also, is it

Hello, I'm trying to use a current Syslinux setup, that is working well for service linux based distros, to serve up recent Windows server installs. As I'm new here I'm reluctant to make any changes to the environment unless I've exhausted the current options. We are running Syslinux 3.71 on a Gentoo server and all the DHCP and tftpd are "working as they should". What

has anyone got memdisk to work directly? i mean such as: add_item("W98 Boot","Windows 98 Boot",OPT_RUN, "memdisk initrd=98se.ima",0); I have tried various methods, and I get the same results: Loading memdisk....Ready. MEMDISK 3.11 2005-09-02 Copyright 2001-2005 H. Peter Anvin MEMDISK: No ramdisk image specified! I know I can setup (in my case)

> Hi, > > I am trying to get a UEFI bootable USB. And I am unable to make it > working. I have two x86_64 systems and both of them 'hangs' when I > choose to boot UEFI from USB. > > I've created fat32 formated partition with ef00 type. I placed EFI/BOOT > there with content of efi64/ distribution, I've created syslinux.cfg and > renamed syslinux.efi

Hi, On 2018-08-03 00:09, Ady Ady via Syslinux wrote: > I guess you are in Gentoo. > > Even if you are not using Debian, you could: > > 1_ Download the syslinux-related binary packages from the Debian > "experimental" (_not_ to be confused with "unstable") repository > (currently, "6.04~git20171011.af7e95c3+dfsg1-3") and take: > > * from

On 2018-08-02 18:25, KARBOWSKI Piotr wrote: > Hi, > > I am trying to get a UEFI bootable USB. And I am unable to make it > working. I have two x86_64 systems and both of them 'hangs' when I > choose to boot UEFI from USB. > > I've created fat32 formated partition with ef00 type. I placed EFI/BOOT > there with content of efi64/ distribution, I've created

On Tue, Jun 14, 2016 at 4:44 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. >> >> >> There's a lot of variation. Do you have a shell option >> in your boot selections? > > > None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 >