nvpower and nvpmodel startup fixes #1294
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The service unit file was not setting RemainAfterExit, leading to multiple executions of the setup script during boot, with subsequent executions generating errors. Signed-off-by: Matt Madison <matt@madison.systems>
* Fix the service type to be oneshot, with RemainAfterExit set to true. Trying to execute nvpmodel multiple times leads to spurious failures. * Add a dependency on nvpower.service, following how Jetson Linux does. Evidently the nvpower script now performs some setup the nvpmodel needs, which wasn't true in older L4T versions. Signed-off-by: Matt Madison <matt@madison.systems>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes for the
nvpowerandnvpmodelsystemd service units so they execute only once and in the correct sequence at boot time. Particularly on Orin Nano and NX modules, the GPU driver is very sensitive to when the power settings need to be applied via sysfs. Errors occur if the settings are applied too early, or if nvpower hasn't performed some of the scheduling-related setup that has to be in place, or if settings are applied multiple times.