Enable nv-oem-config on custom bootstrapped os

We are attempting to follow the directions in the developer guide to enable nv-oem-config on a custom Ubuntu 18.04.5 rootfs which was created via debootstrap. All dependencies are installed and we have followed the developer guide directions to enable the service on the image. This image does not contain any GUI, so we are running config on ttyTCU0.

The configuration starts on the terminal but immediately jumps from the “license” to “Lang” to “Timzone” and continues to do this on a loop. Any ideas would be appreciated.

  • using JP 4.4.1 L4T r32.4.4
  • ubiquity version 18.04.14.14
  • no /var/log/installer/debug file is created
  • /var/log/oem-config-log contains “OSError”:
    Ubiquity 18.04.14.14 (oem-config)
    debconf_ui selected; starting debconf frontend
    Ubiquity 18.04.14.14 (oem-config)
    Ubiquity 18.04.14.14 (oem-config)
    Traceback (most recent call last):
    File “/usr/sbin/oem-config”, line 655, in
    main(oem_config)
    File “/usr/sbin/oem-config”, line 639, in main
    install(args[0], query=options.query)
    File “/usr/sbin/oem-config”, line 272, in install
    open_terminal()
    File “/usr/sbin/oem-config”, line 107, in open_terminal
    ttyn = os.ttyname(0)
    OSError: [Errno 5] Input/output error
    Ubiquity 18.04.14.14 (oem-config)
    Traceback (most recent call last):
    File “/usr/sbin/oem-config”, line 655, in
    main(oem_config)
    File “/usr/sbin/oem-config”, line 639, in main
    install(args[0], query=options.query)
    File “/usr/sbin/oem-config”, line 272, in install
    open_terminal()
    File “/usr/sbin/oem-config”, line 107, in open_terminal
    ttyn = os.ttyname(0)
    OSError: [Errno 5] Input/output error
    Ubiquity 18.04.14.14 (oem-config)
    Traceback (most recent call last):
    File “/usr/sbin/oem-config”, line 655, in
    main(oem_config)
    File “/usr/sbin/oem-config”, line 639, in main
    install(args[0], query=options.query)
    File “/usr/sbin/oem-config”, line 272, in install
    open_terminal()
    File “/usr/sbin/oem-config”, line 107, in open_terminal
    ttyn = os.ttyname(0)
    OSError: [Errno 5] Input/output error
    Ubiquity 18.04.14.14 (oem-config)
    Traceback (most recent call last):
    File “/usr/sbin/oem-config”, line 655, in
    main(oem_config)
    File “/usr/sbin/oem-config”, line 639, in main
    install(args[0], query=options.query)
    File “/usr/sbin/oem-config”, line 272, in install
    open_terminal()
    File “/usr/sbin/oem-config”, line 107, in open_terminal
    ttyn = os.ttyname(0)
    OSError: [Errno 5] Input/output erro-

Change the value of this property from ttyGS0 to ttyTHS0 in below config file to try.

etc/nv-oem-config.conf.t194

Thank you for your reply
We are using a custom carrier which uses ttyTCU0 in place of ttyGS0. Changing the etc/nv-oem-config.conf.t194 to ttyTHS0 results in oem-config never showing.

When we follow the exact same procedure using ttyTCU0 (also using the custom BSP), but use the default sample roots, we do not see these behaviours.

We are able to complete the setup If we reconfigure Debconf to run the readline frontend in place of dialog.

Output from systemctl status nv-oem-config-debconf@ttyTCU0
It looks like Ubiquity is starting multiple times

nv-oem-config-debconf@ttyTCU0.service - End-user configuration afte
r initial OEM installation (Debconf UI)
Loaded: loaded (/lib/systemd/system/nv-oem-config-debconf@.service; disabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-12-15 16:26:06 U
TC; 5min ago
Process: 6714 ExecStopPost=/bin/sh -ec echo “ubiquity debian-installer/framebu
ffer boolean true” | debconf-set-selections (code=exited, status=0/SUCCESS)
Process: 4220 ExecStart=/bin/sh -ec for x in $(cat /proc/cmdline); do
case x in debug-oem-config) debug=--debug ;; ubiquity/frontend=*) export frontend="{x#*=}" ;; automatic-o
em-config) automatic=–automatic ;; esac;
done;
/usr/lib/nvidia/license/nvlicense-templates.sh; deb
conf-loadtemplate nvlicense /usr/lib/nvidia/license/nvlicense.templates;
exec env FRONTEND=“debconf_ui” nv-oem-config-firstboot $debug $automatic
(code=exited, status=1/FAILURE)
Process: 4203 ExecStartPre=/bin/sh -ec echo “ubiquity debian-installer/framebu
ffer boolean false” | debconf-set-selections (code=exited, status=0/SUCCESS)
Main PID: 4220 (code=exited, status=1/FAILURE)

Dec 15 16:25:47 test systemd[1]: Starting End-user configuration after initial O
EM installation (Debconf UI)…
Dec 15 16:25:52 test ubiquity[4259]: Ubiquity 18.04.14.14 (oem-config)
Dec 15 16:25:55 test ubiquity[4285]: Ubiquity 18.04.14.14 (oem-config)
Dec 15 16:25:59 test ubiquity[6691]: Ubiquity 18.04.14.14 (oem-config)
Dec 15 16:26:01 test ubiquity[6697]: Ubiquity 18.04.14.14 (oem-config)
Dec 15 16:26:03 test ubiquity[6703]: Ubiquity 18.04.14.14 (oem-config)
Dec 15 16:26:04 test ubiquity[6709]: Ubiquity 18.04.14.14 (oem-config)

Hi sysopinit,

Due to issue happened at your custom carrier board, please compare the differences between your system and our dev-kit, narrowing it down to some specific causes then maybe you can have clue on why this is happening.