Comment 29 for bug 1789650

That was weird. After the previous attempt, the system looked OK when it was fully deployed -- BootOrder was set correctly. I therefore tried replicating the login while deploying, and this time the /sys/class/firmware directory looked more normal, but both it and efibootmgr (once installed) showed no BootCurrent variable:

$ sudo efibootmgr -v
BootOrder: 0000,0002,0001,0003,0004,0005,0006,0007,0008
Boot0000* ubuntu HD(1,GPT,3867d6c3-0241-43b0-a31e-a519c8271305,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Hard Disk 0 FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(1d76b9fa-87f2-4ecf-ab6a-985c4a958d6a)IbmS.....
Boot0002* PXE Network FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(1d76b9fa-87f2-4ecf-ab6a-985c4a958d6a)IbmS.....
Boot0003 Enter Setup FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3cc3fdbd-9658-47c1-b672-6263c1c7e403)
Boot0004 Boot Devices FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3cc3fdbd-9658-47c1-b672-6263c1c7e403)IbmS....h
Boot0005 Boot Manager FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3cc3fdbd-9658-47c1-b672-6263c1c7e403)IbmS.....
Boot0006 Setup FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3cc3fdbd-9658-47c1-b672-6263c1c7e403)IbmS.....
Boot0007 Diagnostics FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(1d76b9fa-87f2-4ecf-ab6a-985c4a958d6a)IbmS.....
Boot0008 Firmware Log FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(3cc3fdbd-9658-47c1-b672-6263c1c7e403)IbmS.....
ubuntu@oil-jolteon:~$ ls /sys/firmware/efi/efivars/BootC*
ls: cannot access '/sys/firmware/efi/efivars/BootC*': Invalid argument

So there's some inconsistency. Maybe one in X boots works OK...?