Lenovo Yoga 11e

[Dave-Misco]

This morning i tried to capture a Lenovo Yoga e11 (consumer notebook)
When it boots to ipxe i get an errormessage:

bzImage… ok
Could not select: Exec format error (http://ipxe.org/2e008081)
Could not boot: Exec format error (http://ipxe.org/2e008081)
Could not boot: Exec format error (http://ipxe.org/2e008081)

iPXE>_

What does it mean and how to fix ?

[george1421]

We need some basic information here.

1. What version of FOG are you using?
2. What version of the FOS Engine kernel are you using?
3. Is the Yoga in uefi or bios (legacy) mode?
4. What specifically are you sending for dhcp option 67 {boot-file}?
5. Are you using dnsPROXY (dnsmasq) or dhcp to set dhcp options 66 {next-server} and dhcp option 67?

[Dave-Misco]

1. Running Version: 1.3.0-RC-15

2. bzImage Version: 4.8.1
   bzImage32 Version: 4.8.1

3. UEFI (No legacy available)

4. DHCP Config:

option space PXE;
option PXE.mtftp-ip    code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578

authoritative;
allow unknown-clients;
option ntp-servers ntp.webhostingbay.nl;
option time-servers ntp.webhostingbay.nl;
option broadcast-address 192.168.71.255;
option subnet-mask 255.255.252.0;
option routers 192.168.68.1;
ddns-update-style none;
option domain-name "assembly.local";
option domain-name-servers 192.168.68.11, 8.8.8.8;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;

# Assembly LAN
subnet 192.168.68.0 netmask 255.255.252.0 {
	max-lease-time 14400;
	default-lease-time 14400;
	allow unknown-clients;
	next-server 192.168.68.13;
	range 192.168.68.30 192.168.71.200;
	}

class "pxeclient" {
    match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";

    if substring (option vendor-class-identifier, 15, 5) = "00000" {
        # BIOS client 
        filename "undionly.kpxe";
    }
    elsif substring (option vendor-class-identifier, 15, 5) = "00006" {
        # EFI client 32 bit
        filename   "ipxe32.efi";
    }
    else {
        # default to EFI 64 bit
        filename   "ipxe.efi";
    }
   }

5. No.

p.s. We use FOG ‘vanilla’, e.g. boot.php gets send to the device

[Tom Elliott]

As it’s getting the bzImage loaded, but then failing:

According to the link, the file loading is corrupt or not loading as expected.

Can you provide a picture of the boot process from power off until the error occurs?

[abos_systemax]

@Tom-Elliott as Requested

[Tom Elliott]

From what I see in the picture, you’re booting using UEFI. (As indicated by “Succeeded to download NBP file.”

Can you get output of:

http://192.168.68.13/fog/service/ipxe/boot.php?mac=macofhosttryingtoboot

(Please replace macofhosttryingtoboot with the mac address of the host that’s trying to boot.

[abos_systemax]

@Tom-Elliott

http://192.168.68.13/fog/service/ipxe/boot.php?mac=543a:eb:15:37

#!ipxe
set fog-ip 192.168.68.13
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.68.13/fog/ consoleblank=0 rootfstype=ext4 mac=54:ab:3a:eb:15:37 ftp=192.168.68.13 storage=192.168.68.13://images/dev/ storageip=192.168.68.13 osid=9 irqpoll hostname=54ab3aeb1537 chkdsk=0 img=KansKleur_PaschalisSchool imgType=mps imgPartitionType=all imgid=18 imgFormat= PIGZ_COMP=-6 shutdown=1 hostearly=1 pct=5 ignorepg=1 type=up
imgfetch init_32.xz
boot

And with &arch=x86_x64
http://192.168.68.13/fog/service/ipxe/boot.php?mac=543a:eb:15:37&arch=x86_64

#!ipxe
set fog-ip 192.168.68.13
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.68.13/fog/ consoleblank=0 rootfstype=ext4 mac=54:ab:3a:eb:15:37 ftp=192.168.68.13 storage=192.168.68.13://images/dev/ storageip=192.168.68.13 osid=9 irqpoll hostname=54ab3aeb1537 chkdsk=0 img=KansKleur_PaschalisSchool imgType=mps imgPartitionType=all imgid=18 imgFormat= PIGZ_COMP=-6 shutdown=1 hostearly=1 pct=5 ignorepg=1 type=up
imgfetch init.xz
boot

[Tom Elliott]

@abos_systemax said in Lenovo Yoga 11e:

/

Under Storage Management -> All Storage Nodes, can you edit the Image and FTP Path’s so they read only: ‘/images’ instead of ‘//images’

[abos_systemax]

@Tom-Elliott

If I remove the preceding slash before Image Path, the //Images gets changed to /Images; however: It would seem that the WebRoom, FTP Path, SnapinPath and SSL Path are all wrong as well?

[george1421]

two things here, I’m not seeing the inits (virtual hard drive). I don’t pay attention to the pxe booting process anymore so that download may be hidden now.

second, we have seen some pretty flaky uefi firmware on the yogas. Please make sure you have the latest firmware for that device.

From the error message the process is never leaving the iPXE kernel so the FOS Engine isn’t to the point to start just yet.

[abos_systemax]

@george1421
I cannot remember seeing anything different than now; you are right that it doesn’t get to FOS; if I load the bzImage by hand, it’ll crash with the same error. This means that it doesn’t even reach the imgfetch init.xz at all

[Wayne Workman]

I found threads in the forums from about a year ago concerning the same device:
https://forums.fogproject.org/topic/7045/fog-menu-don-t-boot-windows-chainloading-failed
https://forums.fogproject.org/topic/5402/lenovo-11e-doesn-t-pass-menu-screen-on-ipxe
https://forums.fogproject.org/topic/4994/windows-8-1-uefi-gpt-questions

I found that in the first link, a community member posted the below which is quite interesting.

@thomasdec said in FOG menu don't boot Windows - Chainloading failed:

I found why the .efi file doesn’t work !
The problem come from an boot option.
I disable Security Chip in Security tab in Lenovo BIOS and now it’s work.
I can access FOG menu and image my computer.
Sorry for not finding it sooner !

@Sebastian-Roth @george1421 thanks again so much for your help !

[Dave-Misco]

@Wayne-Workman

Thanx for pointing this out !!!
The same occurs here, when i disable the security-chip fog boots normaly.

[Wayne Workman]

@Dave-Misco So your issue is resolved?