JetPack 6.0 not recognized by Jetson AGX Orin (suspect of problem with graphics server)

[filipe.cechim]

Problem description

After a recent firmware update, our Jetson AGX Orin started showing unusual behavior towards the graphic system.
Currently, Jetson is using JetPack 6.0 (36.4.4), but it had not been a problem until now. Firefox is not working and the general behavior of the device is unusual.
According to GPTs which I used to solve the problem, the system started using Wayland with Weston as default graphic server, breaking the compatibility with tools based in X11 or tools that use GPU acceleration.

Environment

Device: Jetson AGX Orin 64GB

JetPack: 6.0 (R36.4.4)

Kernel: 5.15.148-tegra

CUDA: 12.6 (nvcc OK)

Driver NVIDIA: 540.4.0 (modinfo nvidia)

Display manager: Weston (Wayland) active by default configuration

nvidia-smi: all GPU fields are followed by N/A

Observed problems:

glxinfo | grep "OpenGL renderer" returns:

Error: unable to open display

nvidia-smi returns:

GPU 0: Orin (nvgpu) — N/A marked for every aspect
No running processes found

Browsers won't open

Graphic acceleration seems inactive

$DISPLAY empty

No application recognizes OpenGL or GPU use;

What was already tested

lsmod | grep nvgpu: driver correctly loaded

dpkg -l | grep nvidia: all NVIDIA packages appearing correctly (e.g.: nvidia-l4t-x11, nvidia-l4t-weston, nvidia-l4t-cuda, etc.)

Reinstalling graphics packages, such as mesa-utils, libgl1-mesa-glx, libglx-mesa0

nvcc --version shows CUDA 12.6

Weston is active through weston.service

Main doubts

Could the firmware update have reactivated Wayland/Weston and misconfigured the graphic stack?

Is it safe to deactivate weston.service and force X11 utilisation?

Does JetPack 6.0 have Wayland/Weston with CUDA + OpenGL acceleration complete support?

What would be the safest way to restore the environment to a functional one without reinstalling the entire system?

What we need to avoid

We cannot format or reinstall the system because of the fundamental work that would be lost.
We need a safe way to get a working environment that functions with GPU + graphics acceleration.

I appreciate any help!
I may send more logs or use specific commands, if necessary.

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

I understand your concern about the unusual behavior of your Jetson AGX Orin’s graphic system after a recent firmware update. The issue seems to be related to the switch from X11 to Wayland with Weston as the default graphic server, which is causing compatibility problems with tools that rely on X11 or GPU acceleration.

Firstly, it’s essential to note that JetPack 6.0 (36.4.4) is a relatively new version, and it’s possible that some configurations or settings might have changed, leading to the issues you’re experiencing.

To address your problem, I’ll provide a step-by-step approach to help you recover a working environment with GPU acceleration.

Step 1: Verify the graphics driver

Check the graphics driver version using the nvidia-smi command. You’ve already provided the output, but I’ll summarize the key points:

• The driver version is not explicitly mentioned, but it’s likely that the issue is related to the driver or its configuration.
• The output indicates that the system is using the amdgpu driver, which is not compatible with NVIDIA GPUs. This might be a misconfiguration or a bug.

Step 2: Check the X11 configuration

Since you mentioned that Firefox is not working, and the system is using Wayland with Weston, it’s possible that the X11 configuration is not set up correctly. You can try to switch back to X11 by editing the /etc/X11/default-display-manager file and setting it to lightdm or gdm3 (depending on your preferred display manager).

Step 3: Configure the graphics driver

To configure the graphics driver, you can try the following:

• Install the nvidia-driver package (if not already installed) using the apt package manager.
• Run the nvidia-xconfig command to generate a new X11 configuration file.
• Restart the X11 server or reboot the system to apply the changes.

Step 4: Verify GPU acceleration

To verify that GPU acceleration is working, you can use the glxinfo command. If GPU acceleration is enabled, you should see a list of OpenGL extensions and the GPU model.

Comparison with other NVIDIA GPUs

It’s worth noting that the amdgpu driver is not compatible with NVIDIA GPUs. If you’re using an NVIDIA GPU, you should use the nvidia driver instead. You can compare the configuration and behavior of your Jetson AGX Orin with other NVIDIA GPUs, such as the Jetson TX2, to see if there are any differences in the graphics driver or configuration.

Additional troubleshooting steps

If the above steps don’t resolve the issue, you can try:

• Checking the system logs for any error messages related to the graphics driver or X11.
• Running the nvidia-bug-report.sh script to generate a detailed report of the graphics driver and system configuration.
• Searching for similar issues on the NVIDIA forums or other online resources.

Conclusion

In summary, the issue seems to be related to the switch from X11 to Wayland with Weston, which is causing compatibility problems with tools that rely on X11 or GPU acceleration. By verifying the graphics driver, checking the X11 configuration, configuring the graphics driver, and verifying GPU acceleration, you should be able to recover a working environment with GPU acceleration. If the issue persists, you can try additional troubleshooting steps or seek further assistance from NVIDIA support or online forums.

[DavidDDD]

Hi,

Please refer to below topics to check whether fix the issue

Why Chromium Suddenly Broke on Jetson Orin (and How to Bring It Back) -...

Thanks

[filipe.cechim]

Thank you! It worked for Firefox as the browser returned to normal conditions after I followed the instructions provided in this link.

But the AGX Orin JetPack still seems to be missing or unrecognized when I execute jtop as you may see below:

[whitesscott]

Here’s how to fix jtop