Hello, recently we found that after a reboot, the system automatically upgrades from R36.4.3 to R36.4.3. This causes some of our custom carrier board drivers to fail. Deleting the file /etc/apt/sources.list.d/nvidia-l4t-apt-source.list does not prevent this behavior.
In previous R35.x versions, removing /etc/apt/sources.list.d/nvidia-l4t-apt-source.list successfully prevented any upgrades, even after running apt upgrade.
Is there any way to completely prevent L4T version upgrades, including both automatic and passive updates?
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that the Jetson Orin NX is automatically upgrading from R35.43 to R35.43 after a reboot, which is causing issues with custom carrier board drivers. The user wants to know if there is a way to completely prevent L4T version upgrades, including both automatic and passive updates.
After reviewing the provided context, I found that there is no explicit mention of a method to completely prevent L4T version upgrades. However, I can provide some insights and possible solutions based on the available information.
Disable automatic updates: The context mentions that the do-release-upgrade command is disabled because Jetson Linux does not officially support Ubuntu release 22.04 at this time. This suggests that automatic updates might be disabled by default. However, it is unclear if this applies to all types of updates or just specific ones.
Remove update packages: Deleting the update packages might not be sufficient to prevent upgrades, as the system seems to be automatically downloading and installing updates. However, it is worth trying to remove the update packages and see if it prevents the upgrade.
Use apt-mark: The apt-mark command can be used to hold packages at a specific version, preventing them from being updated. However, this method might not be effective in preventing L4T version upgrades, as it is unclear if the upgrade process uses the apt package manager.
Modify the OTA update behavior: The context mentions that the OTA update tools have broken support for AGX Xavier 64Gb. This suggests that the OTA update behavior might be configurable. However, it is unclear if modifying the OTA update behavior would prevent L4T version upgrades.
Use a custom bootloader: The context mentions that the bootloader can be modified to prevent OTA updates. However, this approach requires significant technical expertise and might not be feasible for all users.
In summary, while there is no explicit method mentioned in the context to completely prevent L4T version upgrades, users can try disabling automatic updates, removing update packages, using apt-mark, modifying the OTA update behavior, or using a custom bootloader. However, the effectiveness of these methods is unclear, and users should exercise caution when attempting to prevent upgrades.
Comparison with other Jetson devices:
The context mentions that the Jetson AGX Xavier has broken support for OTA updates. This suggests that the upgrade behavior might be different between Jetson devices.
The Jetson Orin Nano has a similar issue with OTA updates causing an unbootable state. This suggests that the upgrade behavior might be similar between Jetson Orin devices.
In conclusion, while there is no straightforward method to completely prevent L4T version upgrades, users can try various approaches to mitigate the issue. However, the effectiveness of these methods is unclear, and users should exercise caution when attempting to prevent upgrades.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***