DRIVE OS Version: 6.0.4.0 -1
Issue Description: Received a new Drive AGX Orin Developer Kit with Drive OS already installed. Able to connect to debug port, accept EULA and create username/password. Used the DP-DP cable to connect to the display monitor. Didn’t flash anything on the board after receiving. Tried couple of reboots but still the display is not working. Attached the serial port logs.
NvShell Initialization Start-COM4.txt (12.1 KB)
DriveAGX-COM6.txt (148.2 KB)
Dear @venkatalavanya.byreddy ,
The last DRIVE OS release is 6.0.10. Is there any reason to use DOS 6.0.4? If not, please upgrade to last release
Our dev kit originally came with Drive OS 6.0.4, but we don’t have any specific reason to remain on that version. We’ll go ahead and update to Drive OS 6.0.10 as recommended.
We attempted to update to Drive OS 6.0.10 using Ubuntu 20.04, but the process failed with the error shown below. Could you please advise us on the next steps to resolve this issue
2026-02-06 16:26:27 INFO : b’NV_WORKSPACE:'b’NV_TARGETUSER:'b’NV_TARGETPWD:'b’NV_EULA_ACCEPTED:'b’mount: /drive//drive-linux/filesystem/targetfs: failed to setup loop device for /drive/drive-linux/filesystem/targetfs-images/driveos-oobe-desktop-ubuntu-20.04-rfs.img.\r\n’b’umount: /drive//drive-linux/filesystem/targetfs.img: not mounted.\r\n’b’Script scripts/linux_pre_flash.sh fails.\r\nDRIVEOS filesystem Username/Password setup has not been completed.\r\n’b’umount: /drive//drive-linux/filesystem/targetfs.img: not mounted.\r\n’Extracting the PDK failed!
2026-02-06 16:26:27 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2026-02-06 16:26:27 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_ytw148pm7jscxvigbhklodu90n3q6a5f.txt and /drive/driveinstaller/driveinstaller.log.
