Shutdown computer with Syslinux – poweroff.c32 & acpioff.c32

biospxe-bootsyslinux

Does anyone know how i could shutdown ACPI Bios computer (without APM) using Syslinux ?

This is the configuration I am using :

 LABEL Shutdown
    MENU LABEL ^Shutdown computer
    KERNEL /tools/poweroff.c32
    TEXT HELP
        Shutdown the computer
    ENDTEXT

On a non-APM Bios computer I got the error:

 APM not present

I heard that new Bios use most of the time ACPI instead of APM.
So i tried acpioff.c32 from https://launchpadlibrarian.net/187530745/acpioff.c32

and replaced poweroff.c32 with it

 mv acpioff.c32 poweroff.c32

But i got the error :

 Failed to load com32 poweroff.c32

Maybe it require some dependencies? but I didn't found them…

I tested it from CDRom, USB Key and LPXE with the same result

Does anyone know how I could have shutdown works on ACPI using Syslinux ?

Thanks

PS

I already tried COM32 instead of KERNEL, but it is the same as said in :
http://www.syslinux.org/wiki/index.php?title=SYSLINUX#KERNEL_file

KERNEL recognized extension (case sensitive)

.0 PXE bootstrap program (NBP) [PXELINUX only] .bin "CD boot sector"
[ISOLINUX only]

.bs Boot sector [SYSLINUX only]

.bss Boot sector, DOS superblock will be patched in [SYSLINUX only]

.c32 COM32 image (32-bit COMBOOT)

.cbt COMBOOT image (not runnable from DOS)

.com COMBOOT image (runnable from DOS)

.img Disk image [ISOLINUX only]

I tried with Syslinux libraries from BIOS folder and EFI64 with the same result

This is the list of file I included :

Best Answer

You can't mix com32 modules from one version of syslinux/pxelinux with another version of syslinux/pxelinux.

If you want to build a working pxelinux and acpioff.c32, build the code from the tip of this branch: https://github.com/awalls-cx18/syslinux/tree/acpi_off?files=1

Related Solutions

Centos – PXE Boot FreeBSD ISO from a Linux PXE server

So, /tftpboot/images/freebsd_isos/FreeBSD-9.0-RELEASE-amd64-bootonly.iso exists correct?

LABEL FreeBSD 9.0 NO KS eth0
        MENU LABEL FreeBSD9.0 AMD64
        LINUX /memdisk
        APPEND iso
        INITRD /tftpboot/images/freebsd_isos/FreeBSD-9.0-RELEASE-amd64-bootonly.iso

This should work. It's of the format of what I have used.

SLES 11 SP3 with Bootable Driver Kit – unable to fetch image error

Sorry for the late response, this is how I got it to work.

1 - Mount SLES 11 SP3 to /sles11sp3

2 - Mount the bootable driverkit to /bdk

3 - Copy the grub.efi file into /var/lib/tftpboot/ directory.

# cp /bdk/EFI/BOOT/grub.efi /var/lib/tftpboot/

4 - Copy the bootx64.efi, kernel and initrd, and grub.cfg into /var/lib/tftpboot/uefisp3/ directory.

# cp /bdk/EFI/BOOT/bootx6.efi /var/lib/tftpboot/uefisp3/
# cp /bdk/boot/x86_64/loader/linux /var/lib/tftpboot/uefisp3/
# cp /bdk/boot/x86_64/loader/initrd /var/lib/tftpboot/uefisp3/
# cp /sles11sp3/EFI/BOOT/grub.cfg /var/lib/tftpboot/uefisp3/

All of the files can be copied from either SLES DVD or Driver Kit, except for the initrd file. The initrd file must be copied from the driver kit.

5 - Modify grub.cfg file. The only important menu entry for me is the installation, so I removed the rest of the menu entries.

menuentry 'Auto Installation' {
  set gfxpayload=keep
  echo 'Loading kernel ...'
  linuxefi /images/sles11sp3/linux splash=silent textmode=1 showopts install=http://192.168.0.10/sles/sles11sp3 autoyast=http://192.168.0.10/sles/autoyast/sles11sp3towerbdk.ks
  echo 'Loading initial ramdisk ...'
  initrdefi /images/sles11sp3/initrd
}

6 - Add the following inside autoyast file:

  <add-on>
    <add_on_products config:type="list">
      <listentry>
        <media_url><![CDATA[http://192.168.0.10:80/sles/bdk]]></media_url>
        <product>driver-kit</product>
        <product_dir>/</product_dir>
      </listentry>
    </add_on_products>
  </add-on>

7 - Add the uefisp3 group in the dhcpd.conf file.

group {
        filename "uefisp3/bootx64.efi";
        next-server 192.168.0.10;
    host test { hardware ethernet 40:F2:H9:A6:49:C7; fixed-address 192.168.0.50; option host-name test; }
}

8 - Restart dhcp and tftp services.

@Pat Thanks for the tcpdump idea that led to some of the findings.

Related Topic