Igor

Study this: https://github.com/armbian/os/wiki

If you have downloaded "Debian" from Orangepi site, you are already using Armbian. Only some slightly changed old version and without Armbian & community support. To try Armbian, you burn SD card and boot from it. No need to install it anywhere yet. To install it, just run armbian-install and select correct (root) partition. Since this is Linux and your are using 3rd party OS (and bootloader), backup of /storage is recommended before proceeding. Just to be on a safe side.

This forum is also bug tracker. Otherwise it eventually reflects here https://www.armbian.com/participate/ and / or here: https://github.com/armbian/build Helping on the project is the only way. Telling us what to do is pointless. We are aware of many problems, just capacity to keep things maintained is limited. There are thousands of problems in the code made & maintained by thousands of people. We also make daily repository - beta.armbian.com , which is still tested better then rolling Linux levels. Its usually good, but sometimes things breaks. Repository management is done by those scripts: https://github.com/armbian/os/blob/main/.github/workflows/repository-update.yml https://github.com/armbian/build/tree/main/tools/repository Edit: Stable repo index is updated only manually: https://github.com/armbian/os/actions/runs/9760276553/workflow#L342-L345 Here some better mechanism has to be implemented.

You always proceed with Armbian install instructions. If there are some special hacks, they are described at download pages https://www.armbian.com/odroid-n2/ the rest is generic https://docs.armbian.com/User-Guide_Getting-Started/ All our images works without Hardkernel proprietary SPI boot loader, so choose eMMC. In case you have troubles with HA image, try some other (1st minimal was tested manually) from download page to make sure. Getting IP takes some time, but more then few minutes (big slow SD card).

Nobody knows what you are doing. Which device?

We have some repo troubles lately. Will be fixed soon.

Yes, that is expected. Remove it and it should boot from nvme.

This is common. Sometimes other (similar or identical) board's DT is used and we always bundle more DTs in the package.

Proposed solution: https://github.com/armbian/build/pull/6828

First thing in the morning, I tried to do a clean install to Odroid M1. It didn't go without problems, but I have at least identify some troubles. If you start with a new blank nvme, one partition formatted as ext4, it works without any intervention: https://paste.armbian.com/ovusomagef ___ _ _ _ __ __ _ / _ \ __| |_ __ ___ (_) __| | | \/ / | | | | |/ _` | '__/ _ \| |/ _` | | |\/| | | | |_| | (_| | | | (_) | | (_| | | | | | | \___/ \__,_|_| \___/|_|\__,_| |_| |_|_| Welcome to Armbian-unofficial 24.8.0-trunk Bookworm with Linux 6.6.36-current-rockchip64 No end-user support: built from trunk System load: 15% Up time: 0 min Memory usage: 2% of 7.51G IP: CPU temp: 42°C Usage of /: 1% of 1.8T Last login: Sat Jun 29 08:20:35 2024 from 10.0.10.242 Bug is in the partition prepare. I used some nvme where there were some MSDOS and ZFS partitions previously on SSD. Partition maker prompted out "are you sure to delete those or smth". This is the problem ... but after that, everything goes smooth: df Dat. sist. 1K-blokov Upor. Na voljo Upo% Priklop na udev 3859648 0 3859648 0% /dev tmpfs 787644 9308 778336 2% /run /dev/nvme0n1p1 1921724608 2074264 1821958288 1% / tmpfs 3938204 0 3938204 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 3938204 0 3938204 0% /tmp /dev/zram1 47960 332 44044 1% /var/log tmpfs 787640 0 787640 0% /run/user/0 tmpfs 787640 0 787640 0% /run/user/1000

For Odroid M1 we also changed booting process - it is possible to boot Armbian on NVME directly from SPI. Flashing SPI bootloader is probably 1st step. Then having one partition is second one if it won't boot from second. My 2c tips from the head (which is not in perfect operating state. It was a long week) Serial console logs would help to see where is the problem.

yes

We are aware of that and we are working on a new armbian-config, but we are low on human capacity and it goes painfully slow. https://github.com/armbian/configng The only change is here, apt -> beta, beta -> apt: cat /etc/apt/sources.list.d/armbian.list deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com jammy main jammy-utils jammy-desktop But you need to reinstall related armbian packages. Armbian-config does that for you ...

Try this: delete partition on NVBME and leave the installer to make it for you.

There are updated images v24.5.2, which should work OOB.

I have moved status to "Community maintained" as there is nothing we can do at short time. There is always a solution for end users: "Current images doesn't work? Use old images from archive and report to forums ..." You did and lets hope someone will look into. If nobody picks up, there is little we can do. Yearly budget is less then zero. There is a build system https://github.com/armbian/build that we take care of with care and you can build image on your own. You can choose different kernels, debug, etc., perhaps you can find out what is wrong, perhaps someone else will. This hardware suppose to be for advanced users who knows how to fix it. And we provide help with community, build framework, tips. We can't debug all hardware instead of you. Its impossible. I mean, we will fix this eventually, but certainly not anytime soon. We only have testers, but coordinating that is already at extreme end. So much time is lost for that and broken images often slips trough, some versions of devices needs extra touch ... We can't afford to have a dedicated developer for Pinebooks and dev team is overloaded with many other problems. New custom hardware keeps coming in. More new toys you buy, less you support us, quicker your hardware will become obsolete as it needs constant maintenance. Support resources, ours and general community, are small and expensive and our interaction exists mainly when you are unhappy. And people only make donations when they are happy ... your happiness costs us a lot. I am afraid you don't. Core of frustration is almost complete absence of your help. When you are asking us to invest a week of work to fix your software on your computer, check here: https://www.armbian.com/participate/ and match hours of work on what you are asking for. Help us one week, 24/7, help us all the time, ... This is ofc just a suggestion, a tip how you can fight fixing your problems on your computer.

6.1.y works?

Orangepi OS (Arch) is custom / re-branded Manjaro and Manjaro is not doing much else then shipping (selling) their Arch derived OS while taking our and community work on kernel maintainace. This is the story how Orangepi "supports" open source - by primarily supporting code dealers that already mainly have negative contribution to open source development. But who cares other then small group of people called "developers"? In general, HW vendors have interest to block or at least control other OS providers and it is possible they purposefully compiled SPI boot-loader to not load anything else then their OS. This would explain why you can't load our OS. Manjaro already provided (or tried to) this "solution" to Pine64, so average users would have troubles changing OS. Details: https://blog.brixit.nl/why-i-left-pine64/ For us, this is easy to work-around, but bulk of people might still need to stick to their official promo/spy/pirate-ware. Solution? Debian based OS: sudo apt update sudo apt install mtd-utils sudo flash_eraseall /dev/mtd0 Arch based OS: sudo pacman -Syy sudo pacman -S mtd-utils sudo flash_erase /dev/mtd0 Then boot armbian from SD card and run: sudo armbian-install And choose "update MTD boot-loader" or "Install it to NVME", which will also update boot-loader and transfer image to SSD. Tested right now with Opi5 lying on my desk.

Updated images for Khadas Edge2 https://www.armbian.com/khadas-edge-2/ 6.1.y for multimedia 6.10 for experimenting

Hmm, can you give us a bit more information on how to reproduce this? If I start with a clean image, which you have used? Bullseye is not well maintained by upstream, so we don't provide images anymore. Its suggested to use Bookworm from some time. Edit: https://github.com/armbian/build/blob/main/lib/functions/compilation/packages/armbian-zsh-deb.sh#L40-L54 Looks like this doesn't work well in your case. Needs some adjustments, ideas are welcome.

Yes, it is possible. We have to look into this.

It is possible we break it unintentionally while fixing something else. @Alessandro Lannocca Would lately applied changes affect this? It seems its bookworm related.

This part https://github.com/armbian/os/blob/main/userpatches/extensions/ha.sh#L110-L111 is critical. BTW. This hardware will now be officially supported https://www.armbian.com/inovato-quadra/ and there will be dedicated HA image too. Ofc if image is used on some other hardware there is no warranty that things will work.