First setup failed

Hi,

I followed the official tutorial (https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-2gb-devkit#setup). The first boot fails before the “nvicia initial setup” process (i.e. before the “Review and accept NVIDIA Jetson software EULA”, “Select system language, keyboard layout, and time zone”, …)

I got this screen

then I have a login screen.

As it crashed before I had the opportunity to define a login/password, I can’t login.
I tried with Display Attached and in Headless Mode ; it fails in both cases.

Here the message in headless mode:

debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
System configuration setup wasn't completed. Please reboot device and try again

I tried with 2 different SD cards (see below), same issue.

Looking at /var/log/syslog (on another PC), I found this:

...
May  7 10:29:20 localhost systemd[1]: Started NVIDIA Late Init Script.
May  7 10:29:20 localhost NetworkManager[4117]: <info>  [1651919360.3636] devices added (path: /sys/devices/virtual/net/l4tbr0, iface: l4tbr0)
May  7 10:29:20 localhost NetworkManager[4117]: <info>  [1651919360.3637] device added (path: /sys/devices/virtual/net/l4tbr0, iface: l4tbr0): no ifupdown configuration found.
May  7 10:29:20 localhost systemd[1]: Started Serial Getty on ttyGS0.
May  7 10:29:20 localhost systemd[1]: Started Update UTMP about System Runlevel Changes.
May  7 10:29:20 localhost systemd[1]: nv-oem-config.service: Failed with result 'signal'.
May  7 10:29:20 localhost systemd[1]: Stopped End-user configuration after initial OEM installation.
May  7 10:29:20 localhost systemd[1]: Startup finished in 1.850s (kernel) + 1min 2.747s (userspace) = 1min 4.598s.
...

Notice the May 7 10:29:20 localhost systemd[1]: nv-oem-config.service: Failed with result 'signal'.

In “/var/log/oem-config.log” I have this:

Ubiquity 18.04.14.17 (oem-config)
Ubiquity 18.04.14.17 (oem-config)
/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py:54: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib, Atk, Gio
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:5: PyGIWarning: NM was imported without specifying a version first. Use gi.require_version('NM', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NM, NMA
/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:5: PyGIWarning: NMA was imported without specifying a version first. Use gi.require_version('NMA', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import NM, NMA
/usr/lib/ubiquity/plugins/ubi-timezone.py:195: PyGIWarning: TimezoneMap was imported without specifying a version first. Use gi.require_version('TimezoneMap', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import TimezoneMap
Traceback (most recent call last):
  File "/usr/sbin/l4t_payload_updater_t210", line 1366, in <module>
    main(param)
  File "/usr/sbin/l4t_payload_updater_t210", line 1351, in main
    print_VER(arg)
  File "/usr/sbin/l4t_payload_updater_t210", line 57, in print_VER
    system_info_obj.print_current_ver()
  File "/usr/sbin/l4t_payload_updater_t210", line 527, in print_current_ver
    if ver[0] == 'NV1' or 'NV' not in ver[0]:
IndexError: list index out of range
Exception in GTK frontend (invoking crash handler):
Traceback (most recent call last):
  File "/usr/sbin/oem-config", line 655, in <module>
    main(oem_config)
  File "/usr/sbin/oem-config", line 641, in main
    install(query=options.query)
  File "/usr/sbin/oem-config", line 270, in install
    wizard = ui.Wizard(distro)
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 321, in __init__
    mod.ui = mod.ui_class(mod.controller)
  File "/usr/lib/ubiquity/plugins/nvqspi-update.py", line 39, in __init__
    if not self.check_pre_req():
  File "/usr/lib/ubiquity/plugins/nvqspi-update.py", line 72, in check_pre_req
    [self.script, '-c'], universal_newlines=True).strip()
  File "/usr/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/lib/nvidia/qspi-update/nvqspi-update.sh', '-c']' returned non-zero exit status 1.

Traceback (most recent call last):
  File "/usr/sbin/oem-config", line 655, in <module>
    main(oem_config)
  File "/usr/sbin/oem-config", line 641, in main
    install(query=options.query)
  File "/usr/sbin/oem-config", line 270, in install
    wizard = ui.Wizard(distro)
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 321, in __init__
    mod.ui = mod.ui_class(mod.controller)
  File "/usr/lib/ubiquity/plugins/nvqspi-update.py", line 39, in __init__
    if not self.check_pre_req():
  File "/usr/lib/ubiquity/plugins/nvqspi-update.py", line 72, in check_pre_req
    [self.script, '-c'], universal_newlines=True).strip()
  File "/usr/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/usr/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/lib/nvidia/qspi-update/nvqspi-update.sh', '-c']' returned non-zero exit status 1.

A bit frustrating… It fails before any setup, in a very early stage (i.e. the issue is not caused by users).

Any idea on what happen (and how to fix / bypass it) ?

Thanks

Additional information:

  • md5sum “jetson-nano-2gb-jp461-sd-card-image.zip”: f862a729f0bd9d4a3be52c32a3bc9f2a
  • md5sum “sd-blob.img” : f1198c9276622b679ab5281bcaf52291
  • Jetson board: Jetson Nano 2Gb Developer Kit
  • Model: P3541
  • SD Card (first attempt): Kingston Canvas Select Plus 32Gb
  • SD Card (second attempt): PNY Elite 32Gb
  • USB-C Power Supply: RaspberryPi official 3A Power Supply

Hi,

It’s a long shot, but maybe it will help you:

I also experienced an issue with the setup (it crushed on start), due to “not safe” removal of the SD card after flashing it with JetPack.

I flashed the SD card with Linux + Etcher, after the Etcher finished the Linux OS couldn’t eject the SD card and gave me weird error, something about old driver, so I just “violently” removed it and this is probably why it did not work.

I flashed the SD card again with the JetPack image, tried to eject it and get the same error from OS, so in order to remove the SD “non violently” I turned off the computer and this time the setup worked well and did not crush.

Do you eject\safely remove your SD after the flash? if not, try it, it may cause this issue.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.