we have arch linux securely booted. why? well... that's a whole nuther subject.
1st issue was how to install the hash from the boot usb stick. 2nd ignore the efivars output... i would have really suffered have i not used arch for some time now.
installing the hash, In the HashTool main menu, select Enroll Hash, choose \loader.efi and confirm with Yes. Again, select Enroll Hash and then (../) to enter the archiso directory, then select vmlinuz-efi and confirm with Yes. Then choose Exit to return to the boot device selection menu. i messed this up due to some wording issues, but the ../ up directory entry was the thing to do. luckily if you york this it will return you to it after a couple of failures. this did lead to some confusion with the efivars command... keep reading.
the thing in the wiki that was not good was that "> efivars -l" said i was not in a secured boot or something to that effect after installing the hash file, but the uefi was set to secure boot and the menu showed me the correct boot options, so onward my good fellow. not sure what that was about...
i was able to make the efi partition correctly in fdisk not parted as the wiki showed, but i made mine 512MB instead of 100MB as per the wiki. i'm sure parted works. the imprtant thing is make sure to mount the /boot directory in that efi partition formatted as fat32 or something very smiliar to this, mind you this is just a reference.
mkfs.vfat -F32 /dev/sdxZ
mkdir -p /mnt/boot
mount /dev/sdxZ /mnt/boot, where sdxZ is the efi system mine was sda2.
...also the 'BIOS boot' partition of 1M that wendell made in his nuc video was made with ext4 on my system even after assigning it the correct hex code in fdisk. i say that because '> lsblk -f' says it was ext4. i've never made a partition of that type so i am ignorant to it's function. googling didn't help much. maybe it needs to be ext4, but i what i gathered it was supposed to be an unformatted partition.
anyway, if you found yourself here trying to boot arch in a secure boot environ, then you're not crazy, it's convoluted. your milage may vary.
i made 4 partions with a GPT table.
1 bios boot
2 efi system
3 / (ext4 20GB of a 128GB ssd)
4 swap (i only have 4GB of ram on the test rig, so i made this 4GB as well)
but the thing about gpt and i guess i could do this with mbr, is supposedly i can now have 124 more partitions to put test installs on and gummi or efi is supposed to detect the install and place it into the efi boot menu. i am not holding my breath on that one. anyway, probably no one will look at this and correct my mistakes... so good luck!
cheers.
ps: it takes longer to boot (from 4 seconds to 8) and now i cannot clone the disk. i'm not sure if i care for efi at all.