search for: initrdfil

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 ==...

...iour. This option can be specified more than once, and can take a comma-separated list of files. Please note: This option uses the plus-sign symbol, so _please_ bring forward any conflicts with existing processing of the kernel command-line or of Syslinux config-files which may result. The "initrdfile=" option allows you to load a file and encapsulate it as though you had used 'cpio -o -H newc', and pass the resulting blob alongside the other items that might have been specified with "initrd=" or "initrd+=". This is useful for taking a raw file from the Syslinu...

...E 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 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 patches to5.03 onwards on the mailing list but it seems wimboot has moved on from last year so the documentation on various blogs say...

...nitramfs 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 either. Now totally out of ideas I?d like to ask if anyone can suggest what I might be doing wrong. I?m using syslinux 6 I believe. Here is an example of one of the many many syslinux.cfg variations I have tried. SERIAL 0 TIMEOUT 1 PROMPT 1 DEFAULT tinycore LA...

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:

[This email is either empty or too large to be displayed at this time]

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 patches to5.03 onwards on the mailing list but it seems wimboot has moved on from last year so the documentation on various blogs saying this c...

...2008 R2* * kernel win2008R2/memdisk* * append iso bigraw initrd=win2008R2/W2k8R2PXE.img* Second idea is to use WinPE and then create a boot script to get the real media but so far I can't get the WinPE to load. *label WinPE* * com32 linux.c32 winpe/wimboot* * append wimboot* * initrdfile=winpe/bootmgr,winpe/bcd,winpe/boot.sdi,winpe/winpe.wim* This does nothing, it's probably to be expected as I'm trying to sidestep the fact that I'm supposed to updgrade to 5.01 acc. to this guide <http://www.howtogeek.com/162070/it-geek-how-to-network-boot-pxe-the-winpe-recovery-d...

...but it got to "Encapsulating winpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. Here is relative portion of pxelinux: LABEL SCCM OSD Boot MENU LABEL ^2. SCCM OSD Boot com32 linux.c32 append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim TEXT HELP Deployment of Operating System via SCCM. Jason Jones Sr. Associate, Network Services | End User Computing 3947 N Oak St Ext | Valdosta, GA 31605 O +15137844955 E jason.s.jones at convergys.com -----Original Message----- From: Michae...

...right place to ask this question. I was trying to compile and build kernel 3.2.0, by following <Linux Administration - A Beginner's Guide> written by Wale Soyinka. Error occurs after running the following command: # new-kernel-pkg -v --mkinitrd --depmod --install 3.2.0-custom initrdfile is /boot/initrd-3.2.0-custom.img running depmod for 3.2.0-custom creating initrd: /sbin/mkinitrd --allow-missing -f /boot/initrd-3.2.0-custom.img 3.2.0-custom found /boot/initrd-3.2.0-custom.img and using it with grubby adding 3.2.0-custom to /boot/grub/grub.conf /etc/lilo....

...e output after that. Has anyone successfully loaded WinPE using wimboot with syslinux.efi? Ideas on why it's not working for me? - boot loader is /syslinux-6.03/efi64/efi/syslinux.efi - wimboot version 2.6.0 - menu entry: LABEL WinPE MENU LABEL + Windows PE KERNEL linux.c32 APPEND wimboot gui initrdfile=bcd,boot.sdi,boot.wim Kyle

...k 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 features and modules, such as Shao's new hexdump.c32 module and initrdfile= support for the linux.c32 module, as well as strerror cleanups from Gene (we've now got a *decent* strerror() implementation). This won't be the last 5.00 prerelease as we're aware of a resource leak bug and there's a couple of items on my TODO list that I wanted to implement bef...

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 */ > } else { > die ( "Unrecognised argument \"%s%s%s\"\n", key, > ( value ? "=" : "" ), ( value ? value : "" ) ); Thanks; applie...

On 28/08/14 19:38, Jason Jones wrote: > Anyone have luck with pxechn32 and bootmgfw.efi? > > I'm getting the "Unable to retrieve first package" issue as reported by others. > > Really, any advice for UEFI booting into a winpe environment off of pxelinux 6.03 would be beneficial. As it happens, I released a new version of wimboot with support for UEFI yesterday. The

What about using linux.c32?? It has some special initrd features, which someone has very kindly documented: ? http://www.syslinux.org/wiki/index.php?title=Linux.c32 Shao Miller Synthetel Corporation W: https://www.synthetel.com

I looked into Linux.c32 and added that to my setup.menu file. LABEL Install Windows MENU LABEL ^Install Windows COM32 linux.c32 APPEND wimboot initrdfile=Windows7SP2/bootmgr,Windows7SP2/boot/bcd, Windows7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim Now it boots so I have the installation startup page, but when I start the installation I get where I should "select the driver to be installed". It seems it can't find my C: drive. I h...

...inpe.wim..." and never went through the rest of the way. Ultimately PXELINUX apparently timed out and the machine rebooted. > > Here is relative portion of pxelinux: > > LABEL SCCM OSD Boot > MENU LABEL ^2. SCCM OSD Boot > com32 linux.c32 > append wimboot initrdfile=bootmgr.exe,BCD,boot.sdi,winpe.wim The UEFI version of wimboot does not expect to find its files wrapped up into an initrd; it uses the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL to retrieve them from the underlying media. It would be fairly simple to extend the UEFI version of wimboot to handle an init...

...ple script to find gnu-efi files efi: Add /usr/lib32 to the list of possible gnu-efi paths efi: Add -mno-red-zone to CFLAGS Shao Miller (6): linux.c32: Move some initrd=x,y,z code out of main linux.c32: Add new initrd+= option for multiple initrds linux.c32: Introduce initrdfile= option initramfs chain handling: Accounting fixes for padding, etc. hexdump.c32: Simple file hex-dumper core: Fix realloc() code transcription error -- Matt Fleming, Intel Open Source Technology Center

Anyone have luck with pxechn32 and bootmgfw.efi? I'm getting the "Unable to retrieve first package" issue as reported by others. Really, any advice for UEFI booting into a winpe environment off of pxelinux 6.03 would be beneficial. Jason Jones Sr. Associate, Network Services | End User Computing 3947 N Oak St Ext | Valdosta, GA 31605 O +15137844955 E jason.s.jones at