Search the Community

Hi there, yesterday I tried to use nand install skript tool to move the content from my sd card on odroid n2 to emmc card for booting and using emmc card only. The process itself worked and the content of the sd cards was moved, but after unplugging sd card and plugging emmc card the boot process is not starting and nothing is shown on the hdmi monitor. I compared the /boot filesystems and both are identically. I checked the "armbianEnv.txt" file and it is ok for the new uuid of the emmc card. Everything seems to be identically but why is it not booting. Does someone have a hint what to check additionally what is maybe missing at beginning of the boot process. The LED is not blinking on boot process so something in the first steps of booting and loading does not work. Thank you in advance

Hi, has anyone got the Odroid VU7-C display to work on a Odroid N2+ running headless Armbian Jammy? Running the hardkernel stock 22.04, which is still on linux kernel 4.9, it works fine. I've already tried to change a few boot params in /boot/boot.cmd, inspired by https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-n2 like setenv display_autodetect "true" or setenv disable_vu7 "false" setenv hdmimode “800x480p60hz” setenv voutmode "dvi" Am I correct to run mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr as root after each change in boot.cmd? I noticed in the hardkernel image that there are a few binary .dtbo files in , notably 'display_vu7c.dtbo' in /boot/amlogic/overlays/odroidn2 - could I copy this file over to the armbian system in some way? Any advice gratefully received, also if anyone got another 7inch touchscreen working on the N2+ Armbian Jammy!

Hi All, On an Odroid N2+ board, I have tried to install ZFS following different suggestions I found on the web. None of them worked so far. I tried: https://forum.armbian.com/topic/19952-cant-install-kernel-headers-via-armbian-config/ https://forum.armbian.com/topic/18790-odroidhc4-with-5139-meson64-missing-zfs-modules/ https://forum.armbian.com/topic/17337-zfs-just-works-now-on-armbian-2-step-instructions-if-you-are-thick-like-me/ I installed both Armbian 22.05 Bullseye 5.10.110-meson64 first, and then Jammy 5.17. Could someone please help me? Thanks 🙂

Hello, I'm pretty new to Armbian and also to Odroid devices. I'm trying to use Armbian as main operating system (instead of official Ubuntu image). If I burn SD with official Ubuntu image, it work well, if I try to burn almost any of Armbian images for Odroid N2/N2+, I can't get them to work. I've tried theese images: Armbian 22.08.1 Bullseye Armbian 22.05.4 Bullseye Armbian 21.08.1 Bullseye Armbian 22.05.4 Jammy Armbian 22.05.4 Jammy Armbian 21.05.2 Hirsute Edge As per Ubuntu, I've downloaded them, burnt with BalenaEtcher on SD, put the SD in switched-off odroid, attach hdmi, lan, keyboard and power (at the end). I can see petitboot start but, when it try to boot from the SD, the hdmi lost signal and I can't find Odroid in my network. I've waited for 20 minutes before start asking. I wrote in github and they suggest me to try changing the dip switch but I don't know exactly what is it; maybe the SPI Boot Select Switch? In this case, I'm pretty sure it point the SD slot because petiteboot show me device which I can boot and if I try with Ubuntu SD, it works. Anyone could help me with Armbian versione (Bullese, Jammy and so on) and with my boot problem? Thank you in advance Stefano

Hello, While for Odroid-N2 ubuntu standard image wakeonlan worked I miss for armbian 20.08.22 Focal simple advice for bootenv or kernel parameters to enable it e.g. enabled_wol as with ubuntu standard image for N2. ethtool eth0 tells just it is disabled (d) and network settings doesnot work either. regards, Dieter

I have an Odroid-N2+ and I would like very much to Armbian on it. However, when I run lspcu I see that mitigations for hardware side channel attacks are missing: $ lscpu Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 6 On-line CPU(s) list: 0-5 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping: r0p4 CPU max MHz: 2016.0000 CPU min MHz: 1000.0000 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid Model name: Cortex-A73 Model: 2 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 Stepping: r0p2 CPU max MHz: 2400.0000 CPU min MHz: 1000.0000 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-5 Vulnerabilities: Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Spec store bypass: Vulnerable Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Vulnerable Srbds: Not affected Tsx async abort: Not affected How can they be enabled?

Armbian_22.05.4_Odroidn2_jammy_current_5.10.123_xfce_desktop.img ... comes up with the Armbian logo and circling dots... But the dots go on for an hour and a half. Here's what /var/log/bootstrap.log looks like.

Hi, Odroid N2+ Armbian 22.05 Jammy Kernel 5.10.y, Size: 360Mb, Updated: Jul 1, 2022 + XFCE installed by means of armbian-config htop shows Systemd: degraded (1/372 failed) root@n2p-dev:~# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● fwupd-refresh.service loaded failed failed Refresh fwupd metadata and update motd LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. root@n2p-dev:~# systemctl status fwupd-refresh × fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static) Active: failed (Result: exit-code) since Thu 2022-08-04 14:14:15 +05; 7h ago TriggeredBy: ● fwupd-refresh.timer Docs: man:fwupdmgr(1) Process: 10953 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE) Main PID: 10953 (code=exited, status=1/FAILURE) CPU: 79ms Aug 04 14:14:14 n2p-dev systemd[1]: Starting Refresh fwupd metadata and update motd... Aug 04 14:14:15 n2p-dev systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Aug 04 14:14:15 n2p-dev systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Aug 04 14:14:15 n2p-dev systemd[1]: Failed to start Refresh fwupd metadata and update motd. How do I can repair this? Where to look for? Thanx UPD: root@n2p-dev:~# /usr/bin/fwupdmgr refresh WARNING: UEFI capsule updates not available or enabled in firmware setup See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information. Updating lvfs Downloading… [***************************************] Downloading… [***************************************] Downloading… [***************************************] Successfully downloaded new metadata: 1 local device supported

Using a Realtek 8821CU Bluetooth + Wifi USB adapter. Working fine on stable build jammy with kernel 5.10.123. (current) Using the Armbian->Config->System->Other and selecting the latest 5.15 kernel. System reboots and confirm kernel has been updated and chosen. Wifi hotspots are all seen but fails to connect and repeatedly asks for password. Security is WAP2 personal. Setting the kernel back to 5.10.current reverts to Wifi working as expected. I will try the 5.17 kernel and report back. I have seen this before on other Deb distros. From memory this is caused by a missing/outdated kernel encryption module or wpa_supplicant. However don't quote me. It was quite some time ago.

I get a pink tinted screen, on the N2+. Tried different DMs (Gnome, XFCE, KDE), and a second N2+ I have. Changing my monitor's icc profile to a generic sRGB in GNOME and KDE does nothing. Using the same monitor and cable on my regular desktop I not have this problem.

I just (several days ago) installed Armbian 22.05 OdroidN2 Jammy XFCE. It uses kernel 5.10. Then I noticed there is an alternative version 22.05 jammy XFCE with kernel 5.17. Is it possible to update to the later kernel from the image I used without re-imaging and starting from scratch? I have already installed and setup a lot of other applications and data. I can see i have packages linux-image-current-meson64/jammy (linux-dtb... & linux-headers...) installed. On apt.armbian.com I found: (https://stpete-mirror.armbian.com/apt/pool/main/l/linux-5.17.5-meson64/) in the linux-5.17.5-meson64 Name Last modified Parent Directory linux-5.17.5-meson64 linux-dtb-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58 linux-headers-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58 linux-image-edge-meson64_22.05.1_arm64.deb2022-05-29 06:58 Can I apt install these and expect the upgrade to correctly happen?

Hi I had to upgrade my Odroid N2 from Armbian Buster to Armbian Bullseye to run newer versions of Nextcloudpi (24.x). So I did the upgrade by writing the Armbian 22.05 version to the eMMC and started Armbian. Works fine. Then I installed a fresh nextcloudpi (23.0.2) which is the same version I used on Armbian Buster. Works fine. I added the external disks (ncdata und ncbackup). After a restore of my nextcloudpi backup everything was well. But the next reboot did nothing, i.e. no output on the HDMI Interface, nothing. So, I did a power-off and looked at the eMMC via a Micro-SD adapter I have. Of course, no logs, nothing. Of course, there are no logs in /var/log because of the /dev/zram1 mounted at /var/log. Mounting /dev/zram1 on /var/log might be good if everything works, but if a reboot fails, you are host. I found a work-around: disable apache2 startup by editing the systemd unit file - I couldn't use systemctl because the system did not boot. After plugging in the external disks (nc-automount was enabled) and correcting the unit file, I could start apache2 and nextcloudpi is running well - until the next reboot. So, how do I disable the mount of /dev/zram1 to /var/log to find the real culprit ? Is it sufficient to delay the start of apache2 by adding ExecStartPre=/bin/sleep 30 ? Thanks for your advice. Kind regards Norbert

Odroid N2. Armbian Ubuntu 22.04 kernel 5.10.123. xfce. Bluman 2.2.4 Adapter is Realtek rtl8821CU Wifi/Bluetooth. Drivers were present. Device Sony SRS-X2. The device is seen when searching but fails to pair. The only message is "bluetooth pairing failed." and "br-connection-already-connected" I'm note sure by what already connected means. It definitely is not connected.

Hi! You can find the armbianmonitor output attached to this thread. The issue is: when I use HDMI audio output with wine applications the entire system freezes very soon, usually after some seconds from the launch of the application. Some fraction of the latest played sound keeps looping very fast and both mouse and keyboard are unresponsive. All I can do is to unplug the power. This happens both on Odroid N2 and Odroid N2+. Everything works fine if I use some bluetooth headphones. And everything works fine if I use HDMI audio output with linux native applications. The problem is in the combination of Wine applications and HDMI audio output. Armbian Monitor Output.txt

The image listed here with xfce is broken: https://www.armbian.com/odroid-n2/ Example download link to broken image: https://mirrors.dotsrc.org/armbian-dl/odroidn2/archive/Armbian_22.05.1_Odroidn2_focal_current_5.10.110_xfce_desktop.img.xz

Good day. I have a board ODROID N2 +, 2x TBS5520se. OS: Linux odroidn2 5.10.111-meson64 #trunk SMP PREEMPT Wed Apr 20 07:09:24 UTC 2022 aarch64 GNU / Linux After I managed to install the TBS drivers, I found that something was wrong. After running the kodi, the UHD channels hardly work at all. Does anyone have experience in solving this problem?

I am just looking for a working image that would have the 8821CU working. I've been able to make it work on Ordoid HC-4, but on N2+, it didn't work. Also, my N2 setup on armbian had some problem. I launched sudo armbian-config, tried to install headers and firmware, but I couldn't. It didn't provide any error message, it just showed the loading bar and quitted quickly (as if it completed). Then I tried Nigthly and I was able to download headers and firmware, but still wasn't able to get 8821CU working (now thinking about it, I don't recall checking out if it was detected from lsusb... I'm not entirely sure). Then I went back to stable and now I'm no longer able to boot. Should I fresh install focal again or try another image? DId I miss something during installation to get 8821CU working? Thank you.

Hi all. I've recently received the Odroid N2+. Since nobody else started a topic about it, I'll be the one. All works fine with Armbian since not much hardware changes have been made vs the N2. Except for the CPU frequency. With the Odroid Ubuntu you can set it to 2.4Ghz for the big cores A73 as overclock (2208 stock)., and 2016Mhz for the A53 cores (1908 stock). With Armbian the max clocks are 2Ghz for all cores. Using Armbian Focal 4.9 legacy. I tried setting the higher values in config.ini. Also tried with the "meson64_odroidn2_plus.dtb" file from the Odroid Ubuntu. Doesn't boot with that. (What do I know ) Other changes are the RTC battery that's now on the board. The heatsink has changed a little. But it's still more than sufficient to keep it cool even when overclocked. USB3 still rather s*cks on it. Slow and a lot of issues with 2.4Ghz dongles(wifi/keyboard...). Too bad they didn't do anything about that. But that probably could have complicated compatibility with N2 images. Also feels a bit more sluggish than RK3399 on NVMe vs 128GB eMMC on the N2+. That's what fast I/O does. I'll try on USB3-NVMe later. Here some pictures. 1st pic the N2+ with its case open. 2nd picture the N2 left and the N2+ on the right. Cheers all.

Hi, please ignore my username, it's quite old. System is an odroid n2+. After updating the system (apt dist-upgrade) and updating linux-image-current-meson64:arm64 21.08.1 to 21.08.6, my sd card could not be mount anymore. New firmware was: linux-image-current-meson64=21.08.6 / 5.10.81-meson64 System runs from emmc. The 256gb sd card is used for more internal storage. Kernel message: mmc0: error -84 whilst initialising SD card - repeated every few seconds. Downgrade back to linux-image-current-meson64=21.08.01 / 5.10.??-meson64 (did not remember minor version while changing kernel in armbian-config): works again as expected! After some digging and comments about sd card size, voltage, ..., i also found this: https://github.com/armbian/build/pull/3154 and the comment there: "remove the UHS-enabling patch, to avoid 1.8v vs 3.3v mess. Make sure to use only A1-rated SD cards as recommended." SD card is this one, labeled as A1: https://www.amazon.de/gp/product/B07H9FVB6M Works gread and flawless with previous kernel since some months. As I don't see this as a feature, is it a bug? If reported, any chance for a fix in a next firmware/kernel,.? Thanks Alex

Sometimes when reboot device goes to emergency mode and you can not connect to it remotelly. I read on internet, may be here, that make this [Firmware Bug]. I downgrade Kernel to "Igor" recommended 5.7.15 and there the [Firmware Bug] missing. I tested new and newest Kernel via armbian-config but the [Firmware Bug] is present everywhere. Kernel 5.7.15 seems good without this bug but i have no sounds on Audio out or via HDMI. --- journalctl -xb [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!

Hello, I want to have the GPU mali integration so I choose Armbian kernel 5.4 But there is no sound l. The command aplay -l not list any hardware. And no sound on HDMI An idea ? If I must choose another image can you tell me the good image ? And can I will keep the bifrost wayland integration ? Thanks a lot.

Hello, Ihave an Odroid N2 that run with armbian. 1) I can't upgrade armbian-zsh_21.08.6_all.deb The output of apt upgrade is : (Lecture de la base de données... 133099 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../armbian-zsh_21.08.6_all.deb ... Dépaquetage de armbian-zsh (21.08.6) sur (21.08.5) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/armbian-zsh_21.08.6_all.deb (--unpack) : impossible d'ouvrir « /etc/oh-my-zsh/plugins/osx/README.md.dpkg-new »: Aucun fichier ou dossier de ce type Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/armbian-zsh_21.08.6_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 2) Output of armbianmonitor -u : http://ix.io/3G3N Any tips or things to do. Thanks by advance

Hello at the moment I am struggling to flash a stable desktop environment on my N2, I tried followin images on emmc card without success : Armbian_21.08.1_Odroidn2_hirsute_edge_5.13.12_xfce_desktop : unstable I know, but did not even go through the booting process (stuck at some point in uboot) Armbian_21.05.4_Odroidn2_focal_current_5.10.43_xfce_desktop : found in the archive, it did boot but then froze while in desktop environment. I would have the following need : - use of a logitech mouse (wireless) - use of a bluetooth dongle - use of wacom tablet (I was able sometime ago with some image but cant rell which one no longer) Kind Regards

Hi all, Im having issues at booting on my board. Supported Buster version with kernel 5.10.y on Odroid N2(not plus), downloaded from https://www.armbian.com/odroid-n2/#kernels-archive-all From the UART connection I get the following logs that show kernel panics. odroidlogs2.txt odroidlogs1.txt

X windows system on term 7. turns black and then the Monitor goes in Power Saving modus. But the others terms still work ( not 100 percent sure ). Strangely enough that this happens only shortly after switching on. But if I cut the Power or reboot then it will run 24 hours or longer. Haven't tested more than 24 h. I recognize that late that I could switch to other terms i.e. term 1. At first I thought that the N2+ was under powered and tried another PSU but later I saw that only X window system on term 7 has crashed. Music per bluetooth continued playing. What I did was making updates before it happening.