Avoiding Ubuntu user creation after new rootfs install

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
1

Is there a way to add some files to the rootfs to avoid the kernel stopping after a new rootfs install and going through all the prompts at the graphic login console?

Can a file/files be put onto the file system to avoid this, or can I redirect it to a uart console?

On the OEM device, I don’t have the HDMI output to do this.

Thanks
Larry

3

Serial console should work for this. If not, then reboot once and try again with serial console. If that fails, then you’ve found a bug.

Any change you make to the host side “Linux_for_Tegra/rootfs/” will mostly be preserved upon flash. A few files in “Linux_for_Tegra/rootfs/boot” will change depending on flash arguments, but the rest (including login information) will be preserved upon flash.

One script which pretends it is running on a Jetson, and completes that first boot setup by modifying “Linux_for_Tegra/rootfs/”, is perhaps of interest for you. See:
https://forums.developer.nvidia.com/t/jetson-nano-all-usb-ports-suddenly-stopped-working/75784/37

4

Thanks. I’ll try these suggestions. One issue on our target board is that only uart1 is wired up to a header. Will the config prompts be only started on the usb boot console?
Larry

5

Config is either from the GUI with a monitor, or from serial console. I think regular text console won’t show this, but it might…I have never actually tried.

6

I put on a new kernel, dtbs, and rootfs for a new camera. After the first boot and subsequent boot, the console stops as shown below and I get the config screen on the HDMI. This is off the debug usb console.
Thanks
lc
[ 7.449644] using random host ethernet address
[ 7.472439] ov5693 2-0036: FLIR probing v4l2 sensor.
[ 7.472608] ov5693 2-0036: FLIR found DT match
[ 7.472698] ov5693 2-0036: FLIR alloc ok
[ 7.472774] ov5693 2-0036: FLIR Failed to find clocks
[ 7.472866] ov5693 2-0036: unable to get platform data
[ 7.473002] ov5693 2-0036: FLIR tegra camera driver registration failed
[ 7.473156] ov5693: probe of 2-0036 failed with error -14
[ 7.731916] random: crng init done
[ 7.732022] random: 7 urandom warning(s) missed due to ratelimiting
[ 7.884645] using random self ethernet address
[ 7.884778] using random host ethernet address
[ 9.073260] Please complete system configuration setup on desktop to proceed…

7

Is the above from serial console or the GUI? Does the above stop and not actually allow you to configure? If the above occurs with a regular console, then this may be normal. If this happens on serial console and GUI, then I think this is a bug.

If this is a bug, and reboot does not make final setup via serial console or GUI possible, then I do not know of any way to trigger the setup. It might be at this point you need to flash again, and make sure serial console and/or GUI is connected during flash.

8

That is from the serial console - the regular bootup serial console that is on the microUSB to the left of the RasPi connector.

Someone else answered a similar question suggesting the rootfs be pre-populated on the host machine with the needed files. Maybe that’s a work around?

Thanks
Larry @FLIR

9

Yes, preconfiguring the image on the host PC prior to flash will work around this. Check out the script located here:
https://forums.developer.nvidia.com/t/jetson-nano-all-usb-ports-suddenly-stopped-working/75784/37

10

from Host PC connected via usb cable to recovery port of AGX device it is possible to connect to OEM configuration setup, unless there is amonitor connected to AGX with

sudo picocom -b 115200 /dev/ttyACM0

if it doesn’t connect it might be required to reboot AGX & try again
https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fflashing.html%23wwpID0E0WB0HA

11

Thanks. So the key is disconnecting the HDMI?
Larry

12

hdmi connection triggers off the OEM configuration prompt
Exactly!
However the OEM configuration will need still the USB connection & execution of the command above manually from the Host PC

13

On our OEM device, we not only left off the forced recovery pin but also the USBC recovery USB. All I have is UART 1 working, but in my office with the devkit this will save me some work clicking on those setup screens.

Thanks
lc