ArmOnJetson

I understand that, it's just that the release from 3 weeks ago: 24.11.0-trunk.351 was working fine on the jetson nano. I just deleted the image and upgraded to 25.02 by accident. So I was wondering, if someone still had an image saved somewhere.

It was the only image I could get working. The 25.02 doesn't boot, the older versions from the archive 23.8.1 don't work either for some reason. Unfortunately I deleted the image and the rolling release moved on to 25.02.

Is Armbian finally broken on the Jetson Nano? Upgraded my install to the Linux v6.6 25.02 version and it does not complete a boot anymore. Neither on my upgraded Armbian, nor on a fresh install. The bootlog doesn't even tell anything interesting. Edit: Does anyone have a link to an Armbian 24.11 image, that I can install instead of the current 25.02 one? Below the bootlog, where it gets stuck with the 25.02 image. [ 1.583513] ledtrig-cpu: registered to indicate activity on CPUs [ 1.593473] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 1.603948] drop_monitor: Initializing network drop monitor service [ 1.611220] NET: Registered PF_INET6 protocol family [ 2.296894] Freeing initrd memory: 53328K [ 2.353291] Segment Routing with IPv6 [ 2.357098] In-situ OAM (IOAM) with IPv6 [ 2.361194] NET: Registered PF_PACKET protocol family [ 2.366721] Key type dns_resolver registered [ 2.377905] registered taskstats version 1 [ 2.382740] Loading compiled-in X.509 certificates [ 2.395868] Key type .fscrypt registered [ 2.399939] Key type fscrypt-provisioning registered [ 2.431191] Key type encrypted registered [ 2.435273] AppArmor: AppArmor sha1 policy hashing enabled [ 2.440839] ima: No TPM chip found, activating TPM-bypass! [ 2.446387] Loading compiled-in module X.509 certificates [ 2.451850] ima: Allocated hash algorithm: sha1 [ 2.456434] ima: No architecture policies found [ 2.461021] evm: Initialising EVM extended attributes: [ 2.466157] evm: security.selinux [ 2.469468] evm: security.SMACK64 [ 2.472778] evm: security.SMACK64EXEC [ 2.476435] evm: security.SMACK64TRANSMUTE [ 2.480522] evm: security.SMACK64MMAP [ 2.484177] evm: security.apparmor [ 2.487574] evm: security.ima [ 2.490532] evm: security.capability [ 2.494101] evm: HMAC attrs: 0x1 [ 2.512924] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.525700] clk: Disabling unused clocks [ 2.542482] Freeing unused kernel memory: 9664K [ 2.566901] Checked W+X mappings: passed, no W+X pages found [ 2.572745] Run /init as init process

Hello joseph2025, The HDMI and Displayport output DO NOT WORK. There's no way around that. If you want to use Armbian on the Jetson Nano, you will have to use it headless and remote connect to it via SSH, the USB, or serial connection. Everything else, beside the display output, does work.

Since this is an old thread and I spent way too much time trying to get an OS working on the Jetson Nano, here's a bit of info on what worked and didn't work. For brevity, I'll just list the things I struggled with. I'm currently running the v24.11 rolling Armbian Linux 6.6.51-current-arm64 version on the Jetson Nano which is booting from an SSD. HDMI & Displayport output do not work. Keep this in mind, I used a serial connection with a TTL to USB adapter to setup the Jetson Nano. To get WiFi working: (I tried network manager, wpa_supplicant, etc, none of it worked) sudo nmcli device wifi connect “mySSID” password “myPassword” To boot from a USB device, flash the image with BalenaEtcher, etc and then edit the following file: /boot/armbianEnv.txt Add the following and change the PARTUUID to the one from your storage device. (Run sudo blkid to get the PARTUUID) rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u rootdev=PARTUUID=73b59773-eeca-2144-9da5-aea82ed1899b So it's still possible to run the current OS on the jetson, as long as no graphical output is needed.