Fan runs on full on startup

The above is why the fan runs as it does. Mine is set like this:
FAN Dynamic Speed control=active hwmon2_pwm=64

I think 255 is likely “always on”. What do you see from:
grep 'FAN_SPEED_OVERRIDE' /usr/bin/jetson_clocks

What do you see from:
systemctl status nvfancontrol.service

Also, what do you see from:
cat /sys/devices/platform/pwm-fan/hwmon/hwmon2/pwm1

1 Like
$ grep -n 'FAN_SPEED_OVERRIDE' /usr/bin/jetson_clocks
29:FAN_SPEED_OVERRIDE=0
198:			if [ "${FAN_SPEED_OVERRIDE}" -eq "1" ]; then
602:				FAN_SPEED_OVERRIDE=1
$ systemctl status nvfancontrol.service
● nvfancontrol.service - nvfancontrol service
     Loaded: loaded (/etc/systemd/system/nvfancontrol.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-01-09 17:51:00 CET; 14h ago
   Main PID: 528 (nvfancontrol)
      Tasks: 1 (limit: 36321)
     Memory: 468.0K
     CGroup: /system.slice/nvfancontrol.service
             └─528 /usr/sbin/nvfancontrol &

jan 09 17:51:00 hugo systemd[1]: Started nvfancontrol service.
$ cat /sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1
255

NB: You asked for hwmon2 which does not exist on my unit, so I gave you hwmon1 instead.

Oh! Found the file you asked for. In the root home folder (/root).

$ sudo cat /root/.jetsonclocks_fan.txt
active

Ok, so that is progress. Try removing “/root/.jetsonclocks_fan.txt”, and reboot. If it reappears see what it says. From what I can see in the scripts you quoted hwmon1 (mine is hwmon2, which is why I used that, but since you have hwmon1, then this is what applies) should not be 255, but should instead be something else, e.g., 64.

After you remove that file, and before you reboot, does anything happen with fan speed when you do this?
sudo echo 64 > /sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1

Fan went quiet. Then, after rebooting, the .jetsonclocks_fan.txt file returned but now in user home folder.

$ cat ~/.jetsonclocks_fan.txt
active
$ cat /sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1
255

So that narrows it down a lot. I’m guessing it shouldn’t be quite like that. Run this command again:
sudo echo 64 > /sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1

Remove the “.jetsonclocks_fan.txt” again. Then run command “jetson_clocks --store”. Reboot, and see if the fan is now working as expected.

Did as you suggested. After reboot, I the fan is back on 255.

$ sudo cat /root/.jetsonclocks_fan.txt
active
$ cat ~/.jetsonclocks_fan.txt
cat: ~/.jetsonclocks_fan.txt: No such file or directory
$ cat /sys/devices/platform/pwm-fan/hwmon/hwmon1/pwm1
255

It sounds like the service “nvfancontrol.service” is overwriting the manual settings. Would someone from NVIDIA be able to comment on:

  • Should nvfancontrol.service be disabled?
  • If not, is nvfancontrol.service causing max fan speed at all times?
  • How to set fans to automatic instead of maximum at all times?

Note that nvfancontrol.service is new to the R34.x+ (which is what Orin uses), but did not exist in previous releases (so I don’t know the correct way to configure this; echo of a value to the correct “/sys” file is how control is performed, but I don’t know what software is changing it).

Bump. Any NVIDIA people around?

I’ve seen the same with previous DP version of JP5:

Also do you have file /etc/nvfancontrol.conf ? If yes, check that it has FAN_DEFAULT_PROFILE quiet

I have that file, and it had FAN_DEFAULT_PROFILE cool. I changed it and restarted, but the issue remains. I also tried restarting the service, which did not work either.

hello per.edwardsson,

we don’t see issues on latest Jetpack release.
there’s dynamic fan speed control, we don’t see fan stays-on flat out after system boot-up.

please moving to the latest JetPack release version for confirmation,
thanks

Did sudo apt dist-upgrade, upgraded a few packages, then rebooted. Still fans are on at boot. I believe I have the latest JetPack

$ apt list  | grep jetpack

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libnvidia-container0/bionic,stable,now 0.11.0+jetpack arm64 [installed]
nvidia-jetpack-dev/stable 5.0.2-b231 arm64
nvidia-jetpack-runtime/stable 5.0.2-b231 arm64
nvidia-jetpack/stable 5.0.2-b231 arm64

Note that jetpack packages are not installed. You may try installing these.

Do you see any service having failed to start ?

sudo systemctl --failed

You may also try to reinstall bootloader with:

sudo dpkg-reconfigure nvidia-l4t-bootloader

If not enough, you may post the output of:

cat /etc/nv_boot_control.conf

That does sound like a problem.

$ sudo apt update && sudo apt install nvidia-jetpack
Hit:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
Get:2 https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/arm64  InRelease [1 484 B]
Hit:3 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease
Hit:6 https://download.docker.com/linux/ubuntu focal InRelease
Hit:7 https://repo.download.nvidia.com/jetson/common r35.1 InRelease
Hit:8 https://repo.download.nvidia.com/jetson/t234 r35.1 InRelease
Hit:9 https://install.husarnet.com/deb all InRelease
Fetched 1 484 B in 11s (140 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
9 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-jetpack : Depends: nvidia-jetpack-runtime (= 5.0.2-b231) but it is not going to be installed
                  Depends: nvidia-jetpack-dev (= 5.0.2-b231) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Upgrading the 9 packages does not solve anything, nor does running sudo apt install --fix-broken, or disc-upgrade, or any other command found in How to Install JetPack :: NVIDIA JetPack Documentation. Perhaps this is interesting:

$ grep -nwr "nvidia" /etc/apt/sources.list.d/
/etc/apt/sources.list.d/nvidia-container-toolkit.list:1:deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://nvidia.github.io/libnvidia-container/stable/ubuntu18.04/$(ARCH) /
/etc/apt/sources.list.d/nvidia-container-toolkit.list:2:#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://nvidia.github.io/libnvidia-container/experimental/ubuntu18.04/$(ARCH) /
/etc/apt/sources.list.d/nvidia-l4t-apt-source.list:11:deb https://repo.download.nvidia.com/jetson/common r35.1 main
/etc/apt/sources.list.d/nvidia-l4t-apt-source.list:12:deb https://repo.download.nvidia.com/jetson/t234 r35.1 main

I notice that the two final entries look like they should (“r35.1” rather than “35.1”), but what about the first two?

Edit: Haha, forgot to reply to everything except your first line. Here are the outputs.

$ sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
$ sudo dpkg-reconfigure nvidia-l4t-bootloader
Restore link: APP to /dev/nvme0n1p1
Restore link: recovery to /dev/nvme0n1p6
Restore link: recovery-dtb to /dev/nvme0n1p7
Restore link: esp to /dev/nvme0n1p9
3701--0000--1--jetson-agx-orin-devkit-
Starting bootloader post-install procedure.
ERROR. Procedure for bl_only_payload update FAILED.
Cannot install package. Exiting...

Yikes.

$ cat /etc/nv_boot_control.conf
TNSPEC 3701-500-0000-J.0-1-1-jetson-agx-orin-devkit-
COMPATIBLE_SPEC 3701--0000--1--jetson-agx-orin-devkit-
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

Apparently installing Nvidia-container before installing jetpack makes jetpack weird. I fixed it, so now

 apt list  | grep jetpack

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libnvidia-container0/stable,now 0.11.0+jetpack arm64 [installed]
nvidia-jetpack-dev/stable,now 5.0.2-b231 arm64 [installed,automatic]
nvidia-jetpack-runtime/stable,now 5.0.2-b231 arm64 [installed,automatic]
nvidia-jetpack/stable,now 5.0.2-b231 arm64 [installed]

Issue, however, remains, and above post is still correct (ie unable to reconfigure boot loader, no failed services, nv_boot_control.conf unchanged)

hello per.edwardsson,

Jetpack components should be included. could you please also share your full steps to flash AGX Orin. for example, we’re using SDK Manager for setting up development environment and flashing JetPack release image to the target.

Download the files secureboot_R35.1.0_aarch64.tbz2, Jetson_Linux_R35.1.0_aarch64.tbz2, Tegra_Linux_Sample-Root-Filesystem_R351.0_aarch64.tbz2. Untar them in the same folder, in my case ~/nvidia_flash. Since I have an SSD connected on the M2 connector, I would like to utilise that space. I am not sure I have done this step correctly, so feel free to feedback. I find the size of my M2 disk and enter that into the file ./tools/kernel_flash/flash_lft_nvme.xml, in row 2, setting sector_size and num_sectors to match my disk. I then do sudo ./apply_binaries.sh. I also did sudo ./tools/l4t_create_default_user.sh to create a user. I then perform the flashing in two steps. First, I run sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash -c tools/kernel_flash/flash_l4t_nvme.xml --external_device nvme0n1p1 --showlogs -S 450GiB jetson-agx-orin-devkit nvme0n1p1. After that completes, I replace --no-flash with --flash-only. Sometimes I have to retry once or twice before succeeding, which is why I split it up.

From now, fan is on. Any advice?

hello per.edwardsson,

could you please also confirm by using SDK Manager for setting up development environment and flashing JetPack release image to the target.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.