Jump to content











Photo
- - - - -

same config for uefi and legacy


  • Please log in to reply
6 replies to this topic

#1 bluedark

bluedark
  • Members
  • 6 posts
  •  
    France

Posted 3 weeks ago

Hello everyone.
I have my ipxe server that works great.
I just have a problem when I want to start my client computers on a winpe image in tftp.
I have to have 2 configurations for legacy positions and for uefi posts. For uefi, I put "kernel wimboot" then "initrd BCD"... For legacy, I have to put "kernel wimboot wimboot" then "initrd BCD BCD" ...
Is it possible to have the same config for all positions in legacy or uefi? Thank you in advance



#2 bluedark

bluedark
  • Members
  • 6 posts
  •  
    France

Posted 3 weeks ago

Config for Legacy :

kernel wimboot
initrd /tftpboot/bcd BCD
initrd /tftpboot/boot.sdi boot.sdi
initrd /tftpboot/boot.wim boot.wim
boot

For uefi:

kernel wimboot
initrd /tftpboot/BCD
initrd /tftpboot/boot.sdi
initrd /tftpboot/boot.wim
boot

 

Thanks in advance



#3 erwan.l

erwan.l

    Platinum Member

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

Posted 3 weeks ago

See a possibly related discussion here (read it all).

 

 

What error are you getting when you go for one unique config?

 

 

Overall you could go one config but use a logic in your ipxe script with iseq ${platform} pcbios vs iseq ${platform} efi.

Example here.



#4 bluedark

bluedark
  • Members
  • 6 posts
  •  
    France

Posted 2 weeks ago

it loads the 4 files well and here is the error after: "bad cpio magic. Fatal: could not extract initrd files".



#5 erwan.l

erwan.l

    Platinum Member

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

Posted 2 weeks ago

that vaguely rings a bell : wimboot cannot extract files from wimboot.

i remember something about wimboot version.

try latest one and then try them down going one major release down each time (2.6.x; 2.5.x, 2.4.x, etc).

 

your script is probably fine.

your issues lays with wimboot (releases here).

or else your bcd may be wrong as well in which case you could try this one from ipxe dev team.



#6 bluedark

bluedark
  • Members
  • 6 posts
  •  
    France

Posted A week ago

Finally I completely redo my ipxe server and it works with the same script ...

Here it is:

 

kernel wimboot

initrd BCD BCD

initrd boot.sdi boot.sdi

intird BOOT.WIM BOOT.WIM

The only difference is the boot.wim file which is in uppercase. It is true that the one that is contained in the iso of my winpe is written in uppercase.

I guess the problem came from there ...



#7 erwan.l

erwan.l

    Platinum Member

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

Posted A week ago

yes i am pretty sure wimboot is case sensitive although i see conflicting feedback here and there.

to be safe, dont test your luck and dont ignore the case :)

 

furthermore, the wim name must match the one in your bcd.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users