Flashing instructions remove necessary dpkg directory

Software
1

When I try to install software I get thousands of errors like:

dpkg: warning: files list file for package 'emacsen-common' missing; assuming package has no files currently installed

I’ve figured out that this is because of a line in the flashing instructions:

sudo mv /var/lib/dpkg/info/ /var/lib/dpkg/backup/

I tried to fix them with sudo apt-get install --reinstall (as suggested in Install ZED Link Drivers after reflash leads to dpkg warnings - #2 by Maria_Elizabeth ), but it only seemed to cause more warnings than I was getting before.

Gemini is suggesting to me that that the real issue with processing the kernel packages might be the contents of /etc/nv_boot_control.conf, and that I appear to have a generic version of that file rather than a Zed-specific version of that file. Is there a Zed-specific version that can be shared? (I have a Zed Box Orin 16GB). If so, the flashing script might need to be updated to install that file so that users don’t have to wipe the /var/lib/dpkg/info directory

2

Hi @benmccann
Your problem is not clear.

Do you have the full error log? It might contain important information that can help us understand the cause of the issue.

3

There’s really nothing else in the error logs. Just thousands of lines complaining about the files list is missing from /var/lib/dpkg/info/ having been removed. I think I solved that issue, but I can’t get the camera to work anymore and I’m wondering if reinstalling all the packages messed something up and I need to reflash again.

The big question I still have is whether there’s anything Zed-specific that’s supposed to live in /etc/nv_boot_control.conf ?

4

Normally, if this is required and you reinstall the ZED X Driver, it will restore it.

5

I wonder if the directions on Flash your ZED Box Orin - Stereolabs are potentially out of order and if perhaps Update the System (Step 5) should come after Install ZED Link Drivers (Step 9). Because I think that updating the system might require /etc/nv_boot_control.conf to be correctly populated to identify the carrier board. I think the reason the /var/lib/dpkg/info/ directory needs to be blown away in the instructions might be as a workaround for that file not having been updated yet.

6

Thank you @benmccann
We will check this internally and eventually fix the guide with your suggestions.