You might also consider adding this to the end of “/etc/rc.local” (assumes “~ubuntu/jetson_clocks.sh”, but in later releases it might be “/usr/bin/jetson_clocks”):
sleep 60
# For releases prior to R32.x:
~ubuntu/jetson_clocks.sh
# For releases of R32.x+:
/usr/bin/jetson_clocks
It’s easy to test or remove if it doesn’t help. The reason I suggest this instead of the profile is that profile might require a login. The profile login method would actually be a better choice in cases where you know someone is logging in (there is no need for a timer and no waste of heat/power until it is needed).
You could also consider nvpmodel setup this way, or simply setting that model as default.
The sleep 60 is because until the kernel reaches a stage where “/sys” files can accept input the command will fail. I’m blindly assuming that 60 seconds after rc.local is reached login and jetson_clocks will be available.