Failing to apt-get update after installing Jetpack 3.1?

Hi all,

I seem to be running into an issue, which appears to be quite common.
That is, after installing Jetpack, for both the TX2 and on the host machine, the host machine enters an unusable state, where it thinks it’s architecture is arm64, rather than amd64 (in my case).

Currently I have ended up at this particular solution.

Which seems to band-aid the problem.
Note: I still get a warning about Invalid ‘Date’ entry.

I was wondering if there was an appropriate/permanent solution to this problem?

Cheers.

Does your host work in console mode, but not GUI (e.g., CTRL-ALT-F2)? Does it have an NVIDIA video card?

Note that you can always remove the foreign architecture, fix the issues, and then install the foreign architecture again.

Does your host work in console mode, but not GUI?

The host works in gui mode.

Does it have an NVIDIA video card?

No.

Note that you can always remove the foreign architecture, fix the issues, and then install the foreign architecture again.

The problem seems to stem from the foreign architecture, but I am hesitant to remove it, since it was introduced by the Jetpack installer. I decided to explicitly tell the source to search for amd64 packages, rather than the new default of arm64.

By doing so, the system seems to behave normally again, but I’m assuming that theres an underlying issue, as it seems like the default architecture is still arm64.

What you are describing is having the system think arm64 is native, but x86_64 is foreign. What it needs is to know x86_64 is native, and arm64 is foreign. Is the only arm64 addition through JetPack? Have any arm64 additions or configurations been achieved via something like "dpkg --add-architecture "? What do you see from “sudo dpkg-architecture --list”?

Note: After each architecture addition or removal it may be necessary to purge any cache and then do another “apt update” to see the correct listings for given architectures.