Hello,
i m trying to implement object -detection on Jetson Xavier-NX and using the jetpack version of 5.1.2. i have installed many packages which would be required to execute deepstream-sdk and after making all the required set-up when i tried to power on the board on next day, i m keep getting the boot error saying
Starting Update UTMP about system Runlevel Changes
Finished Update UTMP about system Runlevel Changes
What is the reason behind this and also How this can be dealt ?
Hi,
Do the system hang?
Could reboot the device make you access the system?
Thanks
I can access the system by taking SSH. Even if i reboot it multiple times also, it is not booting up successfully.
System doesn’t hang. Also i have cleared the cache and there is sufficient memory available
Hi,
Seems like it might be a similar issue discussed in this topic.
What packages you install?
To install the deepstream and related pacakge.
You could execute below commands. -referred link
sudo apt update
sudo apt install nvidia-jetpack
Thanks
I have reflashed the board and started making setup from the beginning.Here is what i did,
sudo apt update
sudo apt upgrade
trying to boot from SSD drive in order to have sufficient memory for which i m using 128GB SSD drive
a.lsblk
b. sudo mkfs.ext4 /dev/nvme0n1
c. sudo vi /boot/extlinux/extlinux.conf
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
FDT /boot/dtb/kernel_tegra194-p3668-0001-p3509-0000.dtb
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/nvme0n1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 video=efifb:off nospectre_bhb
d. sudo mount /dev/nvme0n1 /mnt
e. sudo cp -ax / /mnt
f. sudo umount /mnt
g. sudo reboot
i used df -h command to verify and it has booted from SSD drive only
then i proceeded to install further things like jetson-stats and nvidia-jetpack
a. sudo apt install python3-pip
b. sudo -H pip3 install --upgrade pip
c.sudo -H pip3 install -U jetson-stats
d. sudo apt install nvidia-jetpack
Finally, when i m rebooting then i m getting the above error
“Finished Update UTMP about System Runlevel Changes”
use ssh to share the dmesg to us.
Here is the dmesg file provided below
dmesg.txt (63.3 KB)
Hi,
There is no obvious error from the dmesg. Please help check
ps aux |grpe gdm3
share out /var/log/Xorg.0.log
What is the exact thing on your monitor now? Some logs and not GUI?
ps aux | grep gdm3
root 987 0.1 0.1 240032 7764 ? Ssl 17:07 0:00 /usr/sbin/gdm3
nx 2165 0.0 0.0 8572 648 pts/0 S+ 17:08 0:00 grep --color=auto gdm3
nx@jetson:~$ cat /var/log/Xorg.0.log
[ 16.696] (–) Log file renamed from “/var/log/Xorg.pid-1135.log” to “/var/log/Xorg.0.log”
[ 16.698]
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
[ 16.699] Build Operating System: linux Ubuntu
[ 16.702] Current Operating System: Linux jetson 5.10.120-tegra #1 SMP PREEMPT Thu Feb 6 12:39:11 IST 2025 aarch64
[ 16.702] Kernel command line: root=/dev/nvme0n1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 video=efifb:off nospectre_bhb
[ 16.703] Build Date: 11 October 2024 02:23:55PM
[ 16.703] xorg-server 2:1.20.13-1ubuntu1~20.04.18 (For technical support please see Enterprise open source support | Ubuntu)
[ 16.703] Current version of pixman: 0.38.4
[ 16.703] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 16.703] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 16.704] (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Feb 14 17:03:18 2025
[ 16.706] (==) Using config file: “/etc/X11/xorg.conf”
[ 16.707] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 16.707] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 16.709] (==) No Layout section. Using the first Screen section.
[ 16.709] (==) No screen section available. Using defaults.
[ 16.709] () |–>Screen “Default Screen Section” (0)
[ 16.709] () | |–>Monitor “”
[ 16.711] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
[ 16.711] () | |–>Device “Tegra0”
[ 16.711] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 16.711] () Option “AutoAddGPU” “false”
[ 16.711] (==) Automatically adding devices
[ 16.711] (==) Automatically enabling devices
[ 16.711] () Not automatically adding GPU devices
[ 16.711] (==) Automatically binding GPU devices
[ 16.711] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 16.714] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 16.714] Entry deleted from font path.
[ 16.714] (WW) The directory “/usr/share/fonts/X11/100dpi/” does not exist.
[ 16.714] Entry deleted from font path.
[ 16.714] (WW) The directory “/usr/share/fonts/X11/75dpi/” does not exist.
[ 16.715] Entry deleted from font path.
[ 16.716] (WW) The directory “/usr/share/fonts/X11/100dpi” does not exist.
[ 16.716] Entry deleted from font path.
[ 16.716] (WW) The directory “/usr/share/fonts/X11/75dpi” does not exist.
[ 16.716] Entry deleted from font path.
[ 16.716] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 16.716] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 16.716] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 16.716] (II) Loader magic: 0xaaaadbfeb010
[ 16.716] (II) Module ABI versions:
[ 16.716] X.Org ANSI C Emulation: 0.4
[ 16.716] X.Org Video Driver: 24.1
[ 16.717] X.Org XInput driver : 24.1
[ 16.717] X.Org Server Extension : 10.0
[ 16.720] (++) using VT number 1
[ 16.730] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 16.732] (II) no primary bus or device found
[ 16.732] (WW) “dri” will not be loaded unless you’ve specified it to be loaded elsewhere.
[ 16.732] (II) “glx” will be loaded by default.
[ 16.732] (II) LoadModule: “extmod”
[ 16.733] (II) Module “extmod” already built-in
[ 16.733] (II) LoadModule: “glx”
[ 16.735] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 16.743] (II) Module glx: vendor=“X.Org Foundation”
[ 16.744] compiled for 1.20.13, module version = 1.0.0
[ 16.744] ABI class: X.Org Server Extension, version 10.0
[ 16.744] (II) LoadModule: “nvidia”
[ 16.747] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 16.767] (II) Module nvidia: vendor=“NVIDIA Corporation”
[ 16.767] compiled for 1.6.99.901, module version = 1.0.0
[ 16.767] Module class: X.Org Video Driver
[ 16.768] (II) NVIDIA dlloader X Driver 35.4.1 Release Build (bugfix_main) (buildbrain@mobile-u64-6422-d7000) Tue Aug 1 12:40:10 PDT 2023
[ 16.769] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 16.769] (WW) Falling back to old probe method for NVIDIA
[ 16.770] (II) Loading sub module “fb”
[ 16.770] (II) LoadModule: “fb”
[ 16.771] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 16.772] (II) Module fb: vendor=“X.Org Foundation”
[ 16.772] compiled for 1.20.13, module version = 1.0.0
[ 16.772] ABI class: X.Org ANSI C Emulation, version 0.4
[ 16.772] (II) Loading sub module “wfb”
[ 16.772] (II) LoadModule: “wfb”
[ 16.773] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 16.774] (II) Module wfb: vendor=“X.Org Foundation”
[ 16.774] compiled for 1.20.13, module version = 1.0.0
[ 16.774] ABI class: X.Org ANSI C Emulation, version 0.4
[ 16.774] (II) Loading sub module “ramdac”
[ 16.775] (II) LoadModule: “ramdac”
[ 16.775] (II) Module “ramdac” already built-in
[ 16.780] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 16.780] (II) NVIDIA(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 16.780] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 16.780] (==) NVIDIA(0): RGB weight 888
[ 16.780] (==) NVIDIA(0): Default visual is TrueColor
[ 16.781] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 16.781] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 16.781] () NVIDIA(0): Option “AllowEmptyInitialConfiguration” “true”
[ 16.781] () NVIDIA(0): Enabling 2D acceleration
[ 16.781] (II) Loading sub module “glxserver_nvidia”
[ 16.781] (II) LoadModule: “glxserver_nvidia”
[ 16.782] (II) Loading /usr/lib/xorg/modules/extensions/libglxserver_nvidia.so
[ 16.834] (II) Module glxserver_nvidia: vendor=“NVIDIA Corporation”
[ 16.834] compiled for 1.6.99.901, module version = 1.0.0
[ 16.834] Module class: X.Org Server Extension
[ 16.834] (II) NVIDIA GLX Module 35.4.1 Release Build (bugfix_main) (buildbrain@mobile-u64-6422-d7000) Tue Aug 1 12:38:45 PDT 2023
[ 16.835] (II) NVIDIA: The X server supports PRIME Render Offload.
[ 16.836] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device!
[ 16.836] (EE) NVIDIA(0): Failing initialization of X screen
[ 16.837] (II) UnloadModule: “nvidia”
[ 16.837] (II) UnloadSubModule: “glxserver_nvidia”
[ 16.837] (II) Unloading glxserver_nvidia
[ 16.837] (II) UnloadSubModule: “wfb”
[ 16.837] (II) UnloadSubModule: “fb”
[ 16.837] (EE) Screen(s) found, but none have a usable configuration.
[ 16.837] (EE)
Fatal server error:
[ 16.837] (EE) no screens found(EE)
[ 16.839] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 16.839] (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
[ 16.839] (EE)
[ 16.998] (EE) Server terminated with error (1). Closing log file.
On the screen, it is not giving any error/log
I think this is wrong:
I suppose it is possible for that to work, but the first partition would be “nvme0n1p1”. Did you partition this before formatting it? It is probably possible to boot by formatting the rest of the disk (excluding metadata at the start), but I don’t know of anyone who does this for a rootfs. The only time I’ve seen this is for a non-operating system data device which does not use a filesystem. Something quite possible is that you’ve used nvme0n1, and some other software somewhere else assumes nvme0n1p1.
Assuming you have serial console or ssh, once it gets where it is in that dmesg, what is the Xorg log content? You can find the file name (there are times when the number increments) with:
ls -ltr /var/log/Xorg.*.log | tail -n 1
(I include this because when a server dies and respawns sometimes the old context gets incremented; it might also be important to know if this was for example Xorg.1.log and not Xorg.0.log because this is a clue)
I see Xorg did query EDID, which means that in theory the log would see the monitor specs, but the dmesg does not necessarily include information at the same detail level as the Xorg log.
What I saw here is the xorg log mentioned failing to find NV graphics device.
what should i do for not finding NV Graphics card? Any suggestions please
Is your method here really reproducible every time? For example, if you flash the board with fresh image and then do the installation
a. sudo apt install python3-pip
b. sudo -H pip3 install --upgrade pip
c.sudo -H pip3 install -U jetson-stats
d. sudo apt install nvidia-jetpack
Then you will always get crashed GUI?
yes
And in order to expand memory, i have configured it to boot from SSD drive
DTB Build time: Feb 7 2025 11:12:27
With your dmesg log provided, do you use a custom carrier board not a dev kit?
If you’re using a custom carrier board, please do below steps to avoid install nvidia dev kit stuff when execute sudo apt upgrade
sudo apt update
sudo apt install nvidia-jetpack
/etc/apt/sources.list.d/nvidia-l4t-apt-source.list sudo apt upgradeThanks
yes, I do use custom carrier board.
i will be following you instructions
Thank you
The above solution did not help me as the issue still persist
Hi,
Thank you for your replay
Let us confirm the situation:
Before you do the above step (update, upgrade, install packages…,), do you not get the error Finished Update UTMP about System Runlevel Changes and the monitor work normally?
Thanks