UEFI PBA differs from documented testing behaviour about sedutil HOT 5 CLOSED

@phizev
Currently trying to setup my laptop whit sedutil and UEFI PBA.
Testing the PBA before sending it to my OPAL drive, behaviour is as you noticed different. What should I expect?
Currently after entering a empty/dummy password, the wholesystem just reboot...

from sedutil.

Hi,
The whole linux based PBA system needs to be better documented.
I would suggest testing with the Debug image of the PBA transferred to USB stick.
What to expect depends on how you have your system configured. If the drive in not setup (initialsetup) you can expect a NOT_AUTHORIZED error. If the drive is setup and you enter the correct password you should be told the drive was unlocked.
The Debug image will exit to the command prompt allowing you to see the output from the unlock attempt and the Release image will reboot the machine.

from sedutil.

@r0m30 Thanks for your advice.

I tried the debug UEFI PBA to see. My drive is not set up yet. I took a picture of my screen for you to see if this is normal behavior and not specific to my laptop: Picture

from sedutil.

If your drive is not set up that looks like it should work. I'm a little concerned about the INVALID_PARAMETER but I think that's because the Locking SP is not active.

Have you tried running a scan from the rescue image?

from sedutil.

a scan from the rescue image gives (wrote only usefull info) :

/dev/sda/ Opal device 
/dev/sdb/ Non-Opal HDD
ERR : Identity failed Invalid argument
/dev/sdc No
No more discs

Will try to setup the locking range after a backup today, will let you know.

EDIT: It is working as intended ! Had a surprise though because the keymap set for the PBAImage does not fit with my fr-latin9. Is is possible to change by editing some files in PBA?

from sedutil.