It is just “sdkmanager” itself could run on ubuntu24.04. This tool has lots of functions more than just installing Jetson. For example, installing other platforms (e.g. DRIVE platform).
Originally Jetsons had only command line flash. This is useful for many host Linux distributions and releases, and is still possible. Later on, JetPack was introduced as a GUI front end to the flash software (the actual flash software is appropriately named the “driver package” because a Jetson in recovery mode is a custom USB device understood only by the custom driver). Yet later, a “smart network layer” was added to aid with some downloading and choices, which is what the SDK Manager (SDKM) is.
JetPack/SDKM works with many NVIDIA embedded devices, and not just Jetsons. It also works with some of the less known “Drive” products for self-driving cars, and perhaps with other less known devices.
At its heart the install of software to a Jetson via flash requires building parts of that software on the host PC. If you were to just use the driver package on command line, then there isn’t really any checking on whether the host PC has everything needed to do the job right. For example, if software is compiled, you might need not only the compiler, but in some circumstances you would need a specific release or range of releases of that compiler. This is via tools native to the host PC, and it is the limitation of what your destination flash target is, and not about the fact that your host PC is Ubuntu 20.04 or 22.04 or 24.04. The reason JetPack/SDKM can run on more platforms than it can flash to for a Jetson is because some of those other products outside the Jetson line do use a newer host PC, which is often not clear to end users.
I tend to refer people to this to find out what is compatible (the L4T release is just what you call Ubuntu after adding NVIDIA drivers, and this is what actually gets flashed by JetPack/SDKM through the driver package): https://developer.nvidia.com/linux-tegra
The SDK actually works with 24.04 for flashing as well (in my experience) - just need to replace /etc/lsb-release and /etc/os-release to fool the SDK into thinking it’s actually on ubuntu 22.02.
i.e., for `/etc/os-release, backup you original file and replace it with something like this:
Yes, some people have done this and it has been reported to work in many cases. Sometimes there are other issues, but mostly that would work. Just don’t forget to save the original files for restore.