I just upgraded SDKManager to 2.1.0.11682. Previously worked fine for flashing my Jetson Orin Nano Devkit. Now it runs almost all the way through, but at the end fails pointing out that Https://dl.bintray.com/etcher/debian gets a 404, then “The repository https://deb.etcher.io stable release does not have a release file.” Then “Installation failed: Depends on failed component”. Those repositories don’t exist, so this will always fail. I’m surprised everyone is not having this problem. How can I get past this, since I need to use SDKManager to flash Jetpack 6.0 rev 2 and Deepstream. Thanks
Hello,
Your topic will be best served in the Jetson category.
I will move this post over for visibility.
Cheers,
Tom
I could be wrong, but I wasn’t aware that Etcher is used in Linux. Can you say more about your host PC, e.g., is it a VM running in Windows?
The SDKManager program is on a Ubuntu 22.04 laptop connected by a USB cable to the Jetson Orin Nano Devkit. I believe Etcher runs on all OSs, but in any case SDKManager is trying to load those packages but they aren’t there now. I presume it would use them to flash the Jetson sd card across the cable. As I said, the program worked perfectly up to now, so maybe the new version of SDKManager is different, or etcher deleted those packages recently. All advice is welcome!
An additional clue:
https://deb.etcher.io in a browser gets translated automatically to Https://dl.bintray.com/etcher/debian, which is the other url in the error log. Bintray is a download center for repositories. So it appears that SDKManager is counting on that package to be there, but it’s not.
Further clue: When I set the SDKManager to only download the image but not install it, it works perfectly. So apparently it only wants to download the etcher package when it is set up to install the Jetpack on the Jetson Orin Nano. That tends to support the idea that it would use etcher to do the flashing. But why is it programmed to use a package that no longer exists in the download center Bintray?
Why are you getting this repo on your host PC?
Shouldn’t you just delete it if it’s no longer available?
I don’t think it’s related to Jetson/SDKM.
Thanks for your response, but I don’t quite understand it. It’s SDKManager that is trying to download this package, not any update I’m asking for. The SDKManager has a programmed list of packages to be able to flash Jetpack 6.0 on the Jetson, and after loading a ton of them it tries to get etcher (but only when it’s in Install mode, not Download only mode). I don’t understand where it is being instructed to get that package, but it’s fatal when it fails, which of course it always will. Am I missing something? Thanks for your patience.
Would be better if you put the complete log here so we know what exactly SDKM does.
Actually, your response got me curious, so I did a deep search in my host system. I found exactly that package listed in the /etc/apt/sources.list.d, which makes me think that’s responsible, though I don’t know why SDKM would be using that to flash the Jetson. As was recommended, I used the Software & Updates UI to remove that entry. I’ll retry running SDKM, and of course post the result. Thanks again.
Sure.
As I don’t see the log so I cannot judge, but the most basic thing is that whenever sudo apt update is performed, APT searches for all the repoes in /etc/apt/sources.list.d, and tries to download up-to-date packages lists from these repoes, so if these repoes are either dead or giving no reponse, then failure is expected.
I feel like it’s not that SDKM relies on this Etcher repo to download anything, but it just treats any APT failure as error and stops proceeding.
SDKM will try to run an update, but it uses the repos in your PC’s repository list. It isn’t that the Jetson wants a package, it is just consulting the repos in your PC’s list. If you do not use the Jetson, and you reboot and simply run these commands, do they work?
sudo apt update
sudo apt-get upgrade
1 Like
Yes, they both work, and no suspicious contents. I’m hopeful that with the etcher reference deleted, this will work.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.