Jump to content











Photo
- - - - -

[Solved] wimboot from pxelinux default menu?


  • Please log in to reply
4 replies to this topic

#1 sebus

sebus

    Frequent Member

  • Advanced user
  • 355 posts

Posted 30 August 2013 - 10:26 AM

I see that it is possible to do from syslinux menu

ie here or here

 

but how to do it  from pxelinux default menu

 

This http://reboot.pro/to...oting-winpe-40/ shows that it is possible, but could not get it to work

 

I use pxelinux menu from ipxe 1.0.0+ boot, with latest 1.0.3 wimboot

 

Which files from latest 6.0.1 syslinux do I need (and where in tftpboot folder structure?)

LABEL wimbootpe
     menu label Wimboot PE
     com32 linux.c32
     append wimboot initrdfile=bootmgr.exe,boot/BCD,boot/boot.sdi,boot/winpe.wim

WinPE 3.0 (Win7 x86) files (they boot fine via TFTP)

 

Thanks

 

sebus



#2 sebus

sebus

    Frequent Member

  • Advanced user
  • 355 posts

Posted 31 August 2013 - 06:41 PM

So without new syslinux (> then 4.7 with patches, did the patches make to 5 or only above?)

 

I have it going with pxelinux default menu item (from syslinux 4.06) - just 2 files needed: pxelinux.0 and vesamenu.c32

   LABEL IPXE.KRN
       MENU label iPXE kernel
       KERNEL ipxe.lkrn
       initrd wim-boot.ipxe

where wimboot.ipxe is:

#!ipxe
dhcp net0 && echo IP address: ${net0/ip} ; echo Subnet mask: ${net0/netmask}
    kernel http://192.168.50.50:8080/tftpboot/wimboot
    initrd http://192.168.50.50:8080/tftpboot/BOOTMGR          BOOTMGR
    initrd http://192.168.50.50:8080/tftpboot/BOOT/BCD         BCD
    initrd http://192.168.50.50:8080/tftpboot/BOOT/BOOT.SDI    BOOT.SDI
    initrd http://192.168.50.50:8080/tftpboot/wims/BOOT.WIM BOOT.WIM
    boot

sebus



#3 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2447 posts
  • Location:Nantes - France
  •  
    France

Posted 31 August 2013 - 06:56 PM

interesting quote from the first article you mention in your first post which explained several issues between ipxe and pxelinux lately :

 

 the Syslinux team decided to shake things up with the V5 branch and have changed the way their COM32 modules work (now based on ELF) and changed the “core” to require a library (ldlinux.c32) for anything beyond ”pure boot”. This makes it very possible to encounter breakage, for anyone who’s used to the “old way”. 



#4 sebus

sebus

    Frequent Member

  • Advanced user
  • 355 posts

Posted 31 August 2013 - 07:16 PM

Fair enough to them, would be nice to have these changes easy to find...

 

Anyway, used Syslinux 5.01 with these files:

 

\tftpboot\ldlinux.c32
\tftpboot\libcom32.c32
\tftpboot\libutil.c32
\tftpboot\linux.c32
\tftpboot\pxelinux.0
\tftpboot\vesamenu.c32
 

My old menus work fine as well as what I needed

LABEL wimbootpe
     menu label Wimboot PE
     com32 linux.c32
     append wimboot initrdfile=bootmgr,boot/BCD,boot/boot.sdi,wims/boot.wim

So issue solved

 

sebus



#5 sebus

sebus

    Frequent Member

  • Advanced user
  • 355 posts

Posted 31 August 2013 - 08:10 PM

So I can either:

- use syslinux 4.06 files and

KERNEL ipxe.lkrn
  initrd wim-boot.ipxe

or

- use syslinux 5.01 files and

LABEL wimbootpe
menu label Wimboot PE
com32 linux.c32
append wimboot initrdfile=bootmgr,boot/BCD,boot/boot.sdi,wims/boot.wim

Using Syslinux 5.01 I can NOT boot ipxe.lkrn (working that way in 4.06)

or even using:

KERNEL ipxe.lkrn
APPEND dhcp && chain http://webserver/wim-boot.ipxe

nor this one:

KERNEL ipxe.lkrn
append initrd=http://webserver/wim-boot.ipxe


It just stays on black screen (no error, no nothing). I made pause as first line of the script, never gets there, which mean ipxe.lkrn does not load (will try to test with Syslinux 6.01 when I have time)

sebus

EDIT

6.01, 6.02 did not work, apparently 6.03-pre seems to work
 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users