Attempting to build the newest L4T release (32.3.1) from source and flash to a TX2 on a development kit carrier. I can build flash successfully, but the Ubiquity Installer (version 18.04.14.12) hangs after completing the wizard. Curious to see if any has had similar problems.
I’m building the kernel within a Docker container based off Ubuntu 18.04 with all of the build requirements installed. I’m able to flash directly from within the container by mounting /dev inside the container and running in privileged mode.
Steps to Reproduce:
I followed the instructions to build and flash the kernel from https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3231/index.html. I tried to keep everything as vanilla as possible to get a minimum working example before modifying the kernel:
- Installed cross-compile toolchain to `/opt/gcc-linaro-7.3.1-2018.05-x86_64_aarch64-linux-gnu`.
- Used the SDK Manager (v22.214.171.12417) to download and install the JetPack 4.3 SDK to `/usr/src/jetpack/l4t` on my host (all following paths are relative to this SDK path).
- Executed `source_sync.sh` to download the sources and checkout tag `tegra-l4t-r32.3.1` for all repositories.
- `make O=/usr/src/jetpack/l4t/build/kernel-4.9 -j4 | tee kernel-build.log`
- `make O=/usr/src/jetpack/l4t/build/kernel-4.9 INSTALL_MOD_STRIP=1 modules_install INSTALL_MOD_PATH=/usr/src/jetpack/l4t/build/kernel-4.9/modules | tee modules-install.log`
- `cp -rf build/kernel-4.9/arch/arm64/boot/Image kernel/Image`
- `cp -rf build/kernel-4.9/arch/arm64/boot/dts/* kernel/dtb/`
- `sudo cp -rf build/kernel-4.9/modules/lib/modules/* rootfs/lib/modules/`
- Put DevKit into recovery mode.[./]
- `sudo ./flash.sh -K kernel/Image jetson-tx2 mmcblk0p1 | tee flash.log`
After flashing, the TX2 boots up (I have an HDMI output hooked up to the dev kit), and I can see the dmesg scroll. The Ubiquity Installer starts and I can enter the account info, but it hangs after completing the wizard. I know from a previous setup that the module is supposed to automatically restart, but I have to manually restart the board after it hangs. After restart the user I created has no root privileges, and I have no way to modify the system.
From what I can see, it looks like the problem occurs after “Configuring Hardware…”
Any hints as to where to look for problems?
screenshots.zip (12.5 MB)