Search the Community

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.

Hello everyone! I'm trying to install nvidia graphic card driver to the Jetson Nano after I successfully started bookwork on it. I have nouveau running and I don't understand how/if it is possible to switch to nvidia one. Can you guys please help me to understand whether it is possible at all? Am I missing something? Probably was Googling wrong keywords. For now I understand that Nvidia SDK supported by nvidia requires too old version of their ubuntu-based l4t linux which I don't like at all.. Thanks in advance!

Hello, for the past few days I've been trying to install k3s on a Jetson Nano machine with the legacy Kernel 4.9, which I managed to recompile with EBPF support, but it seems there are some Kernel EBPF errors. So, I tried to install Armbian, which also doesn't have EBPF support compiled into the Kernel. I've tried to boot from many images from the Jetson Nano archive on the Armbian site, but none of them work. Is there any documentation on how I could compile the kernel on Armbian - Jetson Nano machine? Why can't I boot from any of the Armbian - Jetson Nano images from the archives? I have updated the legacy OS from Nvidia with the latest drivers boot loaders etc ... I also build https://github.com/marketplace/actions/rebuild-armbian a custom Armbian Image that not booting

Hi There, I would like to run Linux5 or Linux6 on Jetson nano, display using HDMI-DVI adapter. It worked fine with Jetpack4 (=Linux4). When I boot with armbian/Linux5.10, which is linux-image-current-jetson-nano, the display tells me it is out of sync then I would force the display as 1280x1024@60Hz, since it looks like Linux fb or X11 are trying to use 1280x1024@75Hz, so that I need edid/1280x1024.bin (maybe with video=1280x1024@60) using {linux-source}/tools/edid to maintain the resolution and sync. I tried both of gcc-10 and gcc-9 to build it, but failed with below error: edid.S: Assembler messages: edid.S:274: Error: cannot represent BFD_RELOC_8 relocation in this object file format Any workaround? or is this plan never work? Thank you.

Hi Friends Recently I have been trying Armbian 23.5 as alternative for NVIDIA official images. Tried both Ubuntu Gnome desktop and Debian Cinnamon desktop builds but somehow non of them discovers HDMI output. When Jetsno Nano is booting up I can see official "NVIDIA" screen for a while and then information about missing input (from TV on a TV). The hardware itself works OK - when I change SD card to one with an official image or another one with Debian 11 official - it works just fine. It's seems like a problem with Armbian build itself. Any advice is much appreciated. Kuba Logs: https://paste.armbian.com/omiheramof In addition to tle logs - please see X -configure output.

Greetings - I took the contents of the Armbian_23.8.1_Jetson-nano_bookworm_current_6.1.50 image and put it on my NFS server in an attempt to network boot my Jetson Nano device. After making some adjustments to the pxelinux.cfg so that it points to the correct files on my tftp server, the device fails to boot with the following u-boot output: Tegra210 (P3450-0000) # pxe boot 1: Armbian Retrieving file: /boot/jetson-nano-1/uInitrd Using eth_rtl8169 device TFTP from server 192.168.123.4; our IP address is 192.168.123.38 Filename '/boot/jetson-nano-1/uInitrd'. Load address: 0x83200000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######################### 840.8 KiB/s done Bytes transferred = 32807968 (1f49c20 hex) Retrieving file: /boot/jetson-nano-1/Image Using eth_rtl8169 device TFTP from server 192.168.123.4; our IP address is 192.168.123.38 Filename '/boot/jetson-nano-1/Image'. Load address: 0x84000000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################## 847.7 KiB/s done Bytes transferred = 27390464 (1a1f200 hex) append: root=/dev/nfs nfsroot=192.168.123.4:/rz2pool0/jetson-nano-nfs-1,vers=4.1,proto=tcp ip=dhcp console=ttyS0,115200n8 console=tty0 rw rootwait no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Retrieving file: /boot/jetson-nano-1/dtb/nvidia/tegra210-p3450-0000.dtb Using eth_rtl8169 device TFTP from server 192.168.123.4; our IP address is 192.168.123.38 Filename '/boot/jetson-nano-1/dtb/nvidia/tegra210-p3450-0000.dtb'. Load address: 0x83000000 Loading: ###### 847.7 KiB/s done Bytes transferred = 84279 (14937 hex) ## Loading init Ramdisk from Legacy Image at 83200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 32807904 Bytes = 31.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid I have verified that the uInitrd file and the vmlinuz files sha256 checksums match the ones from the Armbian image: 62ce5b826c319c4032e1bd973ba3675580990f228c7589be7e0991edc2079cab Image 1d8923fdaff529c62d6794b186b4b92d66ca6f2cacf8d0616da975e0d432ac68 initrd.img-6.1.50-current-media bdf62ae60589860cff80fc95b46998ad79d207649b92617c2b211d7f5793d585 System.map-6.1.50-current-media f22abfce4344c22bdb59087e8fa778c668c06839d010665933cd5499aa2ed104 uInitrd f22abfce4344c22bdb59087e8fa778c668c06839d010665933cd5499aa2ed104 uInitrd-6.1.50-current-media 62ce5b826c319c4032e1bd973ba3675580990f228c7589be7e0991edc2079cab vmlinuz-6.1.50-current-media It does take quite a bit of time for the Bad Data CRC error to appear, and the Data Size does not match the Bytes transferred listed earlier in the messages but that looks like it may be normal from my investigation thus far. I also noted that when trying to boot via SD card the GRUB2 bootloader is used and not the pxelinux loader, but I am unsure how to make an EFI bootloader work over the network. I also tried booting off a USB device, which works but a USB reset issue and/or switch from usb-storage to uas causes the system to become unusable because the boot device moves when systemd is not expecting it. I do have a good quality barrel jack 12V 4A power supply connected and no other devices in my network boot environment (when testing with the USB booting, there was only a USB SATA adapter attached). If anyone has any ideas, I would love to hear them.

I've tried two releases of Armbian for the Jetson Nano and was struggling to get SPI enabled on the Jetson. To check if SPI is enabled, I've been reading its status is through: cat /proc/device-tree/spi@7000d400/status which just returns disabled Here's what I tried: - enabling spi-spidev through armbian-config, but this option doesn't exist in armbian-config as it does for other releases for devices - making a custom device tree dts file and pointing extlinux.conf to it (below is the relevant snippet): spi@7000d400 { compatible = "nvidia,tegra210-spi\0nvidia,tegra114-spi"; reg = <0x00 0x7000d400 0x00 0x200>; interrupts = <0x00 0x3b 0x04>; #address-cells = <0x01>; #size-cells = <0x00>; clocks = <0x03 0x29>; clock-names = "spi"; resets = <0x03 0x29>; reset-names = "spi"; dmas = <0x24 0x0f 0x24 0x0f>; dma-names = "rx\0tx"; status = "okay"; num-chipselects = <5>; cs-gpios = <0x22 0x13 0>, <0x22 0x14 0>, <0x22 0x95 0>, <0x22 0xc8 0>, <0x22 0x26 0>; spidev@0 { compatible = "spidev"; reg = <0>; spi-max-frequency = <0x1f78a40>; status = "okay"; }; spidev@1 { compatible = "spidev"; reg = <1>; spi-max-frequency = <0x1f78a40>; status = "okay"; }; spidev@2 { compatible = "spidev"; reg = <2>; spi-max-frequency = <0x1f78a40>; status = "okay"; }; spidev@3 { compatible = "spidev"; reg = <3>; spi-max-frequency = <0x1f78a40>; status = "okay"; }; spidev@4 { compatible = "spidev"; reg = <4>; spi-max-frequency = <0x1f78a40>; status = "okay"; }; }; - looking at device tree overlays as explained here (https://docs.armbian.com/User-Guide_Allwinner_overlays/#using-custom-overlays) but armbian-add-overlay doesn't exist and there is no /boot/dtb/nvidia/overlay/ folder

When I take an image with the camera ( Camera V2 raspberry) with the pygame or cv2 module, I get a green screen. I looked for several documentations to solve this problem but never anything very specific. Do you have any idea?

I'm currently working on getting a custom kernel (5.4 kernel which was modified for a specific need regarding containers) running on a Jetson Nano. I've tried running the kernel image on NVIDIA's Jetpack but that didn't work. I've tried building the image directly on the Nano running Armbian and it hasn't really worked so far. It seems to either brick the Nano or not update the kernel version after an install (depending on if I replace /boot/Image). Would you all have any suggestions of what I can try or if it’s even possible? Thanks in advance!