Ubuntu Core runs on, and can be built for, a diverse and constantly evolving set of platforms and devices.

The majority of our users and developers experience very few issues, but any technology this complex and diverse will likely encounter some issues and incompatibilities.

This page attempts to guide users to either an appropriate solution to their issues, or the correct forum/thread where they can get help.


Ubuntu Core 20 install error: TPM is in DA Lockout Mode

Installing Ubuntu Core 20 on a device with a hardware TPM (such as an Intel NUC) can sometimes result in a stalled installation and a TPM is in DA Lockout Mode error, as shown in the following example install log:

ubuntu snapd[15531]: handlers install.go:254:
   make system runnable
ubuntu snapd[115531]: secboot_tpm.go:483: 
   TPM provisioning error: the TPM is in DA lockout mode
ubuntu snapd[115531]: taskrunner.go:271:
   [change 2 "Setup system for run mode" task] failed: 
   cannot make system runnable: cannot seal the encryption keys:
   cannot provision TPM: the TPM is in DA lockout mode
ubuntu snapd[15531]: secboot_tpm.go:483: TPM provisioning error:
   the TPM is in DA lockout mode
ubuntu snapd[15531]: taskrunner.go:271:
   [change 2 "Setup system for run mode" task] failed:
   cannot make system runnable:
   cannot seal the encryption keys:
   cannot provision TPM:
   the TPM is in DA lockout mode 

This error typically means the TPM has been locked to protect the system against potential dictionary attacks (DA) and the TPM needs to be cleared before the Ubuntu Core installation will proceed.

To clear the TPM, boot a classic Ubuntu system (such as a live version of Ubuntu 20.04 LTS from USB storage) and run the following command from a terminal:

$ echo 5 | sudo tee /sys/class/tpm/tpm0/ppi/request

Now reboot the system and re-attempt the Ubuntu Core installation, which should continue without error.

Console-conf shows no-ip

During a snap refresh, console-conf may display an no-ip message.

Despite the no-ip message, you should still be able to connect to the device using SSH if you actually know the IP.

The snap changes command will show that one or more snaps are being updated and the device may need to reboot.

The solution to the no-ip error is to simply wait for any updates to complete.

Last updated a month ago. Help improve this document in the forum.