[Bug 2085541] Re: [SRU] [nano] [agx] [nx] No video output after suspend

[Loïc Minier]

Currently waiting for the 1019 kernels to be promoted to -updates as to
limit the number of test scenarios we have to cover for the SRU. The
1019 kernels contain a modprobe.d conf file to provide the right
arguments to the kernel driver, while the debdiff provided here ensures
that the module actually gets loaded on boot.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2085541

Title:
  [SRU] [nano] [agx] [nx] No video output after suspend

Status in nvidia-tegra-defaults package in Ubuntu:
  Fix Released
Status in nvidia-tegra-defaults source package in Jammy:
  In Progress
Status in nvidia-tegra-defaults source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * On nvidia Jetson Orin platforms installed with Ubuntu for Jetson
  classic server image, a connected monitor will not light up again
  after a suspend-resume cycle

   * On these platforms, a monitor will not display any output if it is
  connected after the system boots or when being disconnected and
  reconnected while the system is running

   * This will be fixed by adding the file /etc/modules-load.d/nvidia-
  drm.conf that force-loads the nvidia-drm module.

   *The module will also need to be loaded with the appropriate
  parameters modeset=1 and fbdev=1 which will be the default starting
  with the tegra-igx kernel 1019

  [ Test Plan ]
   * Install an Ubuntu for Jetson image on a Tegra platform and make sure to install a kernel version >= 1019 from jammy-proposed if it's not already the case. Connect a monitor to the Displayport and boot up the system. Then disconnect and reconnect the monitor to observe that the terminal is showing up on the monitor again.

   * With the monitor connected, run the following command and observe
  the terminal showing up on the monitor again after a suspend-resume
  cycle:

     $ sudo rtcwake -m no -s 30 && sudo systemctl suspend

  [ Where problems could occur ]

   * No additional problems should happen as the nvidia-drm kernel
  module is usually automatically loaded with these parameters when it
  is pulled in by an X11 dependency. Nvidia releases 2 desktop images
  using that mechanism (Jetpack and BaseOS). This intends to fix the
  behavior on a Ubuntu server image.

   * If a user installs this package on a different platform, running a
  different kernel, the nvidia-drm kernel module will not be present and
  subsequently not loaded and therefore does not impact such systems.

  [ Other Info ]

   * This is related to two internal bugs being discussed between
  Canonical and Nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-tegra-defaults 1.3~22.04.2
  ProcVersionSignature: User Name 5.15.0-1019.19-nvidia-tegra-igx 5.15.163
  Uname: Linux 5.15.0-1019-nvidia-tegra-igx aarch64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Thu Oct 24 13:14:55 2024
  Dependencies:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-tegra-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2085541/+subscriptions