ipmiutil reset appears to be coded to treat the -e (EFI) command line option as a target on par with PXE (-p) and Hard Disk (-h). This prevents construction of a request to EFI-boot to hard disk with -e -h, because the code as written treats -h and -e with equal weight, such the last one on the command line "wins".
Table 28-14 of the Intelligent Platform Management Interface Specification Second Generation (April 21, 2015 E7 Markup) positions the BIOS boot type (EFI-vs-legacy) flag in the data 1 byte of parameter 5. The boot device selector is a 4-bit field in the data 2 byte of that command. The intent seems to have been for boot type to act as an adjective or modifier which places the boot device selector in a larger context. The two fields were meant to be interpreted together, not in a mutually exclusive manner.
In order to execute an EFI hard disk boot on a server whose BIOS supports both EFI and legacy (CSM) boot, the ASUS ASMB9-iKVM requires a Set System Boot Options command that has both BIOS boot type = 1 (EFI) and boot device selector = 0010b.
This was discovered in 3.0.8 but affects all of the active branches.
Thank you for the detailed information, and for the patch. I see why this change is needed.
Fixed in ipmiutil-3.2.2