I am a Nano developer and my laptop bit the dust. I bought a new ThinkPad X1 top of the line laptop. It will not run Ubuntu 18.04. I have spent an entire week trying to get it to work without avail. Control-C will not work, the system just hangs and has severe performance issues. I can’t get to the point where I can install sdkmanager. Several of the system processes hang after a few minutes.
I used the same install partitioning scheme that works on Ubuntu 20.04 and 22.02 without having any issues with the Ubuntu OS. My concern is that most folks buying new laptops may not be able to program with Jetson Nano.
My laptop takes Ubuntu 20.04 and 22.02 and runs them just fine and was able to take and download the images for Jetson Xavier just fine.
I think it is very irresponsible to ask a customer run an unsupported operating system 18.04 of Ubuntu to use a Jetson Nano.
Would you please re-consider adding Jetson Nano to the 5.x release so that we can run on a supported operating system ( one with patches etc.) like Ubuntu 20.04 or Ubuntu 22.04?
At least could you tell me how I can use Ubuntu 20.04.6 to work with the Jetson Nano modules P3450 board? i.e. The 3449-0000 carrier board and 3448-0000 Module? Would you provide me a trade in for an Orion so that I can get on with doing things amazing instead of just trying forever to do them?
Other developer Operating systems would be considered at this point as well, but the website is misleading to say the least when it says that sdkmanager can support a certain version of Linux like 22.04 but the 5.X sdk has no os images it can send to the Jetson and says "No available releases to host OS: Ubuntu 22.04/20.04. This means that the sdkmananger 5.x module itself has no images that can be generated on that SDK and developer OS system ( i.e. on 20.04 or 22.04) for a Jetson Nano.
Yea, just love the jetson Nano and hate to see it die since it is affordable to use and learn /develop on. I think the marketplace can be won in the $125-$250 range.
I have spent way too much this past 4 years alone trying to keep up. Supporting this will make a lot of developers glad, especially the ones in school or the ones that don’t get $300K /year today.
We could use a way forward as I suggested maybe a trade in if it will cost too much to put the support into 5.x. $499 is above my price range at my current salary.
I’m a bit confused why you are hung up on SDK Manager. The easiest way to install software to your Jetson Nano devkit is 1) flash the microSD card (from any computer/OS); 2) power on the devkit with that card inserted.
Note: As of now, the latest card image we released is for JetPack 4.6.1 / Jetson Linux 32.7.1. There have been a couple point releases since then for security updates. (The releases are all visible here). After booting your devkit with the JP 4.6.1 card, you can use apt or your favorite Debian package manager to update to latest point release. Instructions here.
Hey, why do you still sell Jetson Nano? Jetson Nano’s software is out of date. Please tell your customers that Ubuntu 18 and CUDA 10 are a pain to use. There is no option to upgrade, which makes this promising device a paperweight.
I think it is very irresponsible to ask a customer run an unsupported operating system 18.04 of Ubuntu to use a Jetson Nano.
Very true
I’m a bit confused why you are hung up on SDK Manager. The easiest way to install software to your Jetson Nano devkit is 1) flash the microSD card (from any computer/OS); 2) power on the devkit with that card inserted.
No offense, but I feel that your answer only tries to solve a symptom but not the cause of the problem. The main question was: Would you please re-consider adding Jetson Nano to the 5.x release so that we can run on a supported operating system ( one with patches etc.) like Ubuntu 20.04 or Ubuntu 22.04?
You may apply to the EDU discount …
Please don’t force people to buy new hardware just because Nvidia is withholding software updates to maximize profits.
I will bring this message to internal team again even that decision/plan has been made quite a long time ago.
Please let someone on that team work on it for a short time and give Jetson Nano a newer OS and a driver for CUDA 11.
With some tweaks Ubuntu 20.04/22.04 it’s working under jetson nano
But it would be interesting to reconsider :
Vulkan 1.3 support Why? DXVK 2.0 needed Vulkan 1.3 for emulation Directx wrapper layer and needed good compatibility with Directx11.x/12 emulation
Fix support for Xorg 1.21 it’s installed by default in repos in ubuntu 22.04 or latest debian the workarround for now it’s apt hold keep to 1.20 and never update if not fixed see why randr variable are changed broken l4t driver. Fix randr variable naming (!468) · Merge requests · xorg / xserver · GitLab
CUDA 11/12 Although I don’t use CUDA, there are people who use CUDA
As for Vulkan, there are already things that run at Mesa3D NVK that the L4T driver does not do so is a shame that Jetson Nano’s support stuck here with 1.2.131 with no new extensions ~3 years old .
With some tweaks Ubuntu 20.04/22.04 it’s working under jetson nano
No, the important things don’t work, and please don’t make people waste their time. It’s more important to let nvidia know that there are many Jetson Nanos out there that need an update ASAP.
The only thing Iill would need is to fix the points mentioned above CUDA11/12 , Vulkan 1.3 , better wayland support , and update oficial rootfs base then I agree with you because there is not implemented
But that I have been with ubuntu 22.04 for more than a year without breaking if you keep what needs to be kept.
As long as they put up with what I have mentioned, I would be satisfied, at least on my part.
I agree with klip’s complaints about the Nano. I would also like to share my concerns regarding my recent purchase of the Nano. Specifically, the description on NVIDIA’s Jetson Nano Developer Kit webpage states: “and begin using the same NVIDIA JetPack SDK used across the entire NVIDIA Jetson™ family of products.” Linking this statement to the 5.1.2 version of JetPack feels misleading since the Jetson Nano Developer Kit does not support version 5.1.2.
Kay did ask, and I’m the “internal team” guy who answered above.
I’m glad you replied; I see now that I answered the laptop/SDKM bit, but missed John’s 2nd question:
Would you please re-consider adding Jetson Nano to [JetPack] 5.x
We’re not going to reconsider. Here are two answers in an attempt to give some background:
First answer:
It was easy to decide that we should not support Jetson Nano with JetPack 5. Doing so would have required tradeoffs we just could not make. Instead, we’ve been able to launch 7 different Orin modules, upstream Jetson support to the Linux Kernel (preparing for JP6), enable CUDA upgrades without requiring a BSP upgrade, and much more. The big picture is that NVIDIA is pioneering AI and accelerated computing, and this progress with Jetson is an important part.
Second answer:
It was a brutally hard decision to not support Jetson Nano with JetPack 5. Nano put us on the map with so many developers. We poured our hearts into launching that devkit and up-leveling our developer collateral. To this day we still have a weekly meeting to review the latest Jetson community projects, still springing from the ground we prepared with Jetson Nano.
One of the great things about being on the Jetson team is our ability to bring all the huge work NVIDIA does into a tiny little package – launching Nano in 2019 really epitomized this. The engineering cost was high to repackage the Tegra X1 SoC (already 4 years old) as Jetson Nano and support it with the brand new codeline we had been preparing for AGX Xavier, but what a great decision. But almost 4 years later, we’ve got a new generation of awesomeness to stuff into a tiny box, and that box is Orin.
Moving on to Geoffry’s concern:
Aargh, you are completely correct. That was an awesome summary… until JetPack 5. I’ve passed this along to the marketing team and asked them check Nano (and TX2) pages for such wording and update.
It was easy to decide that we should not support Jetson Nano with JetPack 5. Doing so would have required tradeoffs we just could not make.
I wish you could provide more details. Intuitively I’d think it’s not that much work since you have all source code available.
Your explanation reads like an advertisement for the great things the Jetson team has achieved, ignoring the fact that the same team dropped Jetson Nano software support after a few years.
I’ll have to sell my collection of Jetson Nanos and I hope nvidia will stop advertising devices that are EOL
@prlawrence
there is a point that i think your product team is missing. The new orin nano is not a direct replacement for the original nano which we are requesting an extended software support. There are 3 reasons for this:
Hardware codec encoder is not available in orin nano. This makes the new one much worse than the older one when streaming from a camera.
carrier board is not available in the orin series.
price tag is way more than the original $100.
All of the above makes the orin nano a new product line that is not targeting the tinkering market. It is a product designed specifically for the entry AI segment.
I think you are missing the point. Not everyone here is asking for jetpack 5 support.
Some of the users here (myself included) simply want the userspace updates that are independent of your kernel, bootloader, and firmware changes. We already know that you have functional fully conformant Vulkan 1.3 on TX1 as over 1 year ago Conformant Products - The Khronos Group Inc . So bring these changes to Jetpack 4.X line.
Why Jetpack 4.X isn’t refreshed onto Focal or Jammy officially I do not know. The Vulkan/EGL/GLES/OpenGL userspace components are already fully compatible with these newer distros. CUDA 10.2 compiler support requires older than available GCC for Jammy but you could fix that internally. CUDA runtime itself works fine.
I have to reiterate what @theofficialgman says. Even if it’s not JetPack 5, what seem like a few relatively minor driver updates would make a world of difference.