Jump to content

Search the Community

Showing results for tags 'odroidn2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
    • Orange Pi 5
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. I have recently managed to get SPI boot to USB SSD working on my Odroid N2+. However, to get there, I had to manually set setenv rootdev "/dev/sda1" in my /boot/boot.cmd With that set, SPI boot works. However, obviously I should not set it manually there, and the setting gets overwritten by armbian-config. My understanding is, that I should let boot.cmd unchanged (rootdev "/dev/mmcblk0p1") and armbianEnv.txt should do its magic, but the rootdev setting in armbianEnv.txt is simply ignored upon SPI boot and it fails to boot, as it tries to load the root fs from SD card... Any pointers, what might go wrong here or how to persist the boot.cmd change?
  2. I'm testing the Armbian image for Odroid N2+ ( Armbian_22.08.7_Odroidn2_jammy_current_5.19.17_xfce_desktop) to see if it's a good migration path from the HardKernel base image. Unfortunately I need to get both i2c bus running on the GPIO and so far only the first bus seems to work (i2c-0). Looking into /sys/bus/i2c/devices , it looks like i2c-1 is tied to the hdmi port instead of the 2nd i2c bus on the GPIO : lrwxrwxrwx 1 root root 0 Dec 31 1969 0-0051 -> ../../../devices/platform/soc/ffd00000.bus/ffd1c000.i2c/i2c-0/0-0051 lrwxrwxrwx 1 root root 0 Dec 31 1969 i2c-0 -> ../../../devices/platform/soc/ffd00000.bus/ffd1c000.i2c/i2c-0 lrwxrwxrwx 1 root root 0 Dec 31 1969 i2c-1 -> ../../../devices/platform/soc/ff600000.bus/ff600000.hdmi-tx/i2c-1 I also tried to load the uart dtbo using armbian-config, but they do not show up in /dev after a reboot. so it looks like none of the overlay are actually loading. Here is the content of my armbianEnv.txt : verbosity=1 console=both overlay_prefix=meson bootlogo=true rootdev=UUID=9355737e-ddfc-4d22-a953-b2bb4bf41a56 rootfstype=ext4 overlays=g12-gxl-cma-pool-896MB i2cA i2cB uartA uartC usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u so.. how do I enable the i2c port properly, as well as the uarts ... and I will need to also enable pwm on pin 12 and 33 (pwm_ef pwm_cd overlay on Hardkenel images). These is my current overlay line on Hardkernel images : overlays="i2c0 i2c1 uart0 uart1 pwm_ef pwm_cd" Thanks.
  3. Hello I use the odroidn2 build, (slightly patched with dts add patch) for my Dreambox one/two (s922X). My Broadcom Wlan chip BRCM4356A2 is not supported in either etch or current. This patches: https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-mmc-1-arm64-amlogic-mmc-meson-gx-Add-core-tx-rx-eMMC-SD-SD.patch https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-mmc-2-arm64-amlogic-dts-meson-update-meson-axg-device-tree.patch prevent that. https://pastebin.com/Cbvd82R8 If I go back to the previous patch: https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-gx-mmc-set-core-clock-phase-to-270-degres.patch.disable Wifi is ok. Do I have to change something on my dts: https://pastebin.com/PCa4jTgj to be able to use the standard patches? Many thanks for the answer. PS: For running audio I also had to add an asound.state and an axg-sound-card.conf. Thank's Emanuel
  4. Is there a way to enable the audio jack? Only the HDMI audio is working.
  5. - To my surprice I was able to upgrade odroid-n2+ to kernel 6.0.10 on a debian bookworm install. Had previously tried to compile kernel 6.0.9 and 6.0.10 from kernel.org and also through the armbian build with no success. The 6.0.9 and 6.0.10 from kernel.org did work but did both lack wifi connections - did try many dongle without success. This deb package from imola.armbian.com do work like a charm on debian bookworm. ------------------------------------- Did download https://imola.armbian.com/beta/pool/main/l/ linux-dtb-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-headers-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-image-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-source-edge-meson64_22.11.0-trunk.0138_all.deb and did dpkg -i linux............deb -------------------------------------- ls /boot armbianEnv.txt Image armbianEnv.txt.out initrd.img-6.0.10-meson64 armbian_first_run.txt.template System.map-6.0.10-meson64 boot.bmp uImage boot.cmd uInitrd boot.scr uInitrd-6.0.10-meson64 config-6.0.10-meson64 vmlinuz-6.0.10 dtb vmlinuz-6.0.10-meson64 dtb-6.0.10-meson64 -------------------------- ➜ src cat /etc/os-release PRETTY_NAME="Debian GNU/Linux bookworm/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=bookworm ID=debian -------------------------- OS: Armbian (22.08.8) aarch64 Host: Hardkernel ODROID-N2Plu Kernel: 6.0.10-meson64 -------------------------
  6. Installing Bullseye from download list works fine, but after `apt update / apt upgrade` or a firmware update through armbian-config, boot process gets stuck with Uboot logo in the corner and won't proceed any further. Any ideas? Using a EMMC card and BalenaEtcher to burn.
  7. The /sbin/armbian-install script that ships in Armbian_22.08.7_Odroidn2_bullseye_current_5.19.17_minimal.img.xz has a couple of faulty lsblk arguments that cause it to exit instead of allowing the user to select the installation target partition. The script works properly after both instances of the string MOUNTPOINTS are changed to MOUNTPOINT which is easily done with sed -ie s/MOUNTPOINTS/MOUNTPOINT/ /sbin/armbian-install
  8. Hi, in addition to this topic I would like to mention that the current Odroid N2 Firmware (Armbian 22.05.0-trunk.0004 Jammy with Linux 5.10.103-meson64 / U-Boot 2022.01-armbian (Mar 03 2022 - 19:25:51 +0000) odroid-n2/n2-plus) as well has difficulties with both the orange and the red coloured eMMC modules at this time. The orange coloured eMMC module is recognised but couldn't be activated ("unable to select a mode : -5"): The red coloured eMMC module cannot be used due to a partition type mismatch (ext4 vs. dos): I don't know if there is already a corresponding Jira issue and/or development activities going on. Cheers Uli PS: odroidn2:~:% sudo armbianmonitor -u System diagnosis information will now be uploaded to curl: (52) Empty reply from server Please post the URL in the forum where you've been asked for.
  9. Hello Armbian community, I recently purchased a Odroid N2+ board and am trying different OS. I flashed Armbian_22.08.1_Odroidn2_jammy_current_5.10.139.img.xz on eMMC card. The first boot up works fine. I was prompted to set root password, new user credential and locals without any issue. I then used 'armbian-config' to navigate the different settings. In the system security menu, I applied the firmware update (that's what the menu called), I assume it runs apt update && apt upgrade. After completion, it prompts me to reboot. So I did. Then the Armbian cannot boot up anymore. I am using Odroid N2+ headless, so I can only see the board blue led not flashing with only red led on and NIC is on. I can ping the IP address, but nothing else. I tried to reflash the image again. The first boot up works fine. This time I tried to freeze the kernel. Then firmware update (apt upgrade). Reboot, dead again. I tried to reflash the image third time. The first boot up works fine. in 'armbian-config', I also tried update boot, not freeze kernel, firmware update. Reboot, dead again. I have to give up. I flashed another debian image on it. It runs fine. I haven't tried any other Armbian images. I don't want to waste Armbian developer's time looking into my issue. Just want to share my experiences here in case other users have the similar issue. Or maybe this image does have some issue. Thanks.
  10. Hello everyone, Upgrading from distro isn't supported officially but I tried it anyways and thought I should share my findings. In short, it worked for me. Others have reported issues so maybe we can figure out what causes these issues. My N2+ is fairly vanilla, so I didn't heavily modify it. Running 5.10.x kernel since that is recommended for de N2+ Step 1. Fully upgrade your system on Focal sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade Step 2. Shutdown you N2+ and make an image backup of your emmc using dd or Win32DiskImager in case something goes wrong Step 3. Boot up your N2+ again, disable all 3rd-party applications and PPA and change the release your sources list. sudo sed -i s/deb/#deb/ /etc/apt/sources.list.d/*.list sudo sed -i s/focal/jammy/ /etc/apt/sources.list Step 4. Update sources sudo apt-get update Step 5. This is were the tricky part starts, upgrading packages. Apt will ask to automatically restart services, allow this. Apt will also ask to replace configuration files, personally I kept all my configurations after manually checking them. sudo apt-get upgrade sudo apt-get dist-upgrade Step 6. Reboot the device And if everything works fine Step 7. Re-enable 3rd party applications and PPA and change the release sudo sed -i s/#deb/deb/ /etc/apt/sources.list.d/*.list sudo sed -i s/focal/jammy/ /etc/apt/sources.list.d/*.list sudo apt-get update sudo apt-get dist-upgrade Step 8. Do a last reboot and done, you should be on Jammy. Remember manually upgrading like this is not officially supported by armbian!
  11. I tried 3 las disk images in SD card, update and OMV is not available fo install. In all tutorials show that OMV is available there. But when on my N2, it's not available.
  12. 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
  13. 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!
  14. 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 🙂
  15. 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
  16. Hi everyone! Been using Armbian for a few days and loving it!! Banging job! I'd like to ask though, is there a way to change the threshold for when the fan kicks in on the N2+? As it's hardcoded to 65C correct? Thanks!
  17. 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
  18. 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?
  19. 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.
  20. 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
  21. 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.
  22. 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.
  23. 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?
  24. 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
  25. 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.
  • Create New...