Confusing output of nv_update_engine if /etc/nv_boot_control.conf is missing


Just a clarification about error from my previous post from BUP update (Specifying the size rootfs of a partition (-S) breaks DT upgrade - #12 by mr.ivanov).

During run nv_update_engine via strace I found out that problem is not related to the rootfs location. It’s just missing /etc/nv_boot_control.conf file:

openat(AT_FDCWD, "/etc/nv_boot_control.conf", O_RDONLY) = -1 ENOENT (No such file or directory)

However I still want to share this info for another board users or engineers, because origin nv_update_engine error is bit confusing and looks like this:

nv_update_engine -i
$ nv_update_engine -i
Nvidia A/B-Redundancy Update tool Version 2.0
null input file!
Init SMD partition failed!
null input file!
Init SMD partition failed!
null input file!
A/B has been disabled. Need to enable A/B.
Error: installing bootloader updates failed: -22

I think it would be nice to have a more clear output from nv_update_engine, like Configuration file /etc/nv_boot_contol.conf not found instead of unobvious null input file!.

However, problem is resolved and I can confirm that BUP update from SATA pass correctly

1 Like

hello mr.ivanov,

we cannot reproduce this locally, this should be platform specific issue.